Nsis_Imp June 2006

nsis_imp@informatik.uni-goettingen.de

6 participants
10 discussions

RE: [Nsis_imp] help adjusting nsis.conf
by Christian Dickmann 19 Jun '06

19 Jun '06

Hi, > I'm trying to test the nsis implementation but I have some difficults to > adjust the configuration file (nsis.conf). I will try to help. I know, that the configuration is a little bit confusing at the beginning. BTW: Any suggestions how to improve the configuration to make it more intuitive are welcome. > I have a laptop with one > wireless interface (192.168.1.101) that access to wired network through an > access point (192.168.1.1). The wired network is 193.144.186.0 with defaul > gateway 193.144.186.1. The route command in the laptop show the following > info: So your local addresses are only 192.168.1.101, as 192.168.1.1 and 193.144.186.1 are addresses of routers, right? > Then, I had adjusted the nsis.conf as is showed below but I got the > following error messages when I ran "nsis -i" command: > > (err) Using 192.168.1.1 as local IPv4 address > (err) Using 193.144.186.1 as local IPv4 address > > Someone know what my mistake is? That is somehow misleading. "(err)" only refers to the "debug level" of the message printed, not to an actual error. We will improve this in a future version to make it more intuitive. But as I understand you, you configured the wrong addresses. As explained above, if I understand you right, you have only one local address and thus the following configuration should be sufficient: IPv4.entries = 1 IPv4[0].addr = 192.168.1.101 IPv4[0].net = 0.0.0.0 IPv4[0].mask = 0 IPv4[0].natfw.useAsExternalAddress = yes Only for routers or end-hosts with multiple addresses, the configuration has to list more than one entry. I hope that helps, otherwise feel free to contact us again. Thank you for your interest. Christian Dickmann

1 0

help adjusting nsis.conf
by Choque Ollachica, Johnny 19 Jun '06

19 Jun '06

Hi all, I'm trying to test the nsis implementation but I have some difficults to adjust the configuration file (nsis.conf). I have a laptop with one wireless interface (192.168.1.101) that access to wired network through an access point (192.168.1.1). The wired network is 193.144.186.0 with defaul gateway 193.144.186.1. The route command in the laptop show the following info: # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1 Then, I had adjusted the nsis.conf as is showed below but I got the following error messages when I ran "nsis -i" command: (err) Using 192.168.1.1 as local IPv4 address (err) Using 193.144.186.1 as local IPv4 address Someone know what my mistake is? Cheers, Johnny nsis.conf --------- IPv4.entries = 2 # The first entry is meant as a default route. It is used when # no subsequent entry matches. IPv4[0].addr = 192.168.1.1 IPv4[0].net = 0.0.0.0 IPv4[0].mask = 0 # Use this address as the external address for NatFW NSLP IPv4[0].natfw.useAsExternalAddress = yes # Default network is public (i.e. the global internet) IPv4[0].natfw.isPrivateNet = no # This entry defines the outgoing local interface card IPv4[1].addr = 193.144.186.1 # These entries define the network segment you want to reach # with the previously defined outgoing interface card IPv4[1].net = 193.144.186.0 IPv4[1].mask = 24 # The network 192.168.0.0/24 is private IPv4[1].natfw.isPrivateNet = yes

1 0

RE: [Nsis_imp] Compiling NSIS 4.0 at FreeBSD 6.0
by Christian Dickmann 19 Jun '06

19 Jun '06

Hi, this seems to be a last minute bug. We removed the code requiring the include to support FreeBSD again, but obviously missed the include itself. Sorry for the inconvenience. Christian Dickmann > -----Original Message----- > From: nsis_imp-bounces(a)informatik.uni-goettingen.de [mailto:nsis_imp- > bounces(a)informatik.uni-goettingen.de] On Behalf Of Gotthard, Petr > Sent: Monday, June 19, 2006 5:52 PM > To: nsis_imp(a)informatik.uni-goettingen.de > Subject: [Nsis_imp] Compiling NSIS 4.0 at FreeBSD 6.0 > > Hello, > I've tried to compile NSIS 4.0 at FreeBSD 6.0, but got the following > error > In file included from ./QoSServer.h:42, > from fsm/QosFsmQne.cpp:29: > ./QoSClient.h:30:18: argz.h: No such file or directory > > Curiously, no <argz.h> is needed, since after removing this include (see > the following patch) everything was compiled. > > diff -Nru nsis-0.4.1-dev/nslp/qos/QoSClient.h > nsis-0.4.1-new/nslp/qos/QoSClient.h > --- nsis-0.4.1-dev/nslp/qos/QoSClient.h Sun May 21 03:11:03 2006 > +++ nsis-0.4.1-new/nslp/qos/QoSClient.h Mon Jun 19 16:56:46 2006 > @@ -27,7 +27,6 @@ > #define _QOS_CLIENT_H_ > > #include <string.h> > -#include <argz.h> > #include "../nslp_api/NslpApi.h" > #include "../nslp_api/NslpApiCallback.h" > #include "clientapi/QoSCommunicator.h" > > > regards > Petr > _______________________________________________ > Nsis_Imp mailing list > Nsis_Imp(a)informatik.uni-goettingen.de > https://user.informatik.uni-goettingen.de/mailman/listinfo/nsis_imp

1 0

Compiling NSIS 4.0 at FreeBSD 6.0
by Gotthard, Petr 19 Jun '06

19 Jun '06

Hello, I've tried to compile NSIS 4.0 at FreeBSD 6.0, but got the following error In file included from ./QoSServer.h:42, from fsm/QosFsmQne.cpp:29: ./QoSClient.h:30:18: argz.h: No such file or directory Curiously, no <argz.h> is needed, since after removing this include (see the following patch) everything was compiled. diff -Nru nsis-0.4.1-dev/nslp/qos/QoSClient.h nsis-0.4.1-new/nslp/qos/QoSClient.h --- nsis-0.4.1-dev/nslp/qos/QoSClient.h Sun May 21 03:11:03 2006 +++ nsis-0.4.1-new/nslp/qos/QoSClient.h Mon Jun 19 16:56:46 2006 @@ -27,7 +27,6 @@ #define _QOS_CLIENT_H_ #include <string.h> -#include <argz.h> #include "../nslp_api/NslpApi.h" #include "../nslp_api/NslpApiCallback.h" #include "clientapi/QoSCommunicator.h" regards Petr

1 0

RE: [Nsis_imp] NSIS 4.0 compiling error
by Choque Ollachica, Johnny 19 Jun '06

19 Jun '06

Hi Christian, I have just tested the nsis-0.4.1-dev.tar.gz in Fedora Core 5 (gcc 4.1.1). The compilation process was successful. Sorry for my late answer. I haven't had enough time yet to test it running in several hosts. Cheers, Johnny > -----Mensaje original----- > De: Christian Dickmann [mailto:mail@christian-dickmann.de] > Enviado el: miércoles, 14 de junio de 2006 10:56 > Para: Stephane Ouellette > CC: nsis_imp(a)informatik.uni-goettingen.de; johnny.choque(a)unican.es > Asunto: Re: [Nsis_imp] NSIS 4.0 compiling error > > Hi all, > > based on the patch provided by Stephane, I created an updated release. > It can be found at > http://user.informatik.uni-goettingen.de/~cdickman/nsis-0.4.1- > dev.tar.gz > > @Johnny: Does this version work for you? > @Stephane: Thank you very much. > > If this version works for Johnny, 0.4.1 will be officially > released as a bugfix release. > > Christian Dickmann > > On Tue, 13 Jun 2006 22:24:42 -0400, Stephane Ouellette > <stephane.ouellette(a)polymtl.ca> wrote: > > Christian Dickmann wrote: > >> > >>> Christian, > >>> > >>> this is caused by g++ v4.0 and up. I was preparing a patch just > >> before > >>> version 0.4.0 was released but it's not done yet. Version 4.0+ of > >>> g++ > >> just > >>> follow the C++ standard... > >>> > >>> The fix is simple. The class qualifications must be removed. > >> > >> Hi, > >> > >> thank you for this information. However, I know of two > machines with > >> g++ 4.x where compiling works fine. One of them is a Mac OS X box. > >> Today, I downloaded Knoppix 5.0 to try g++ 4.x by my own. > >> "g++ -v" prints > >> "gcc version 4.0.4 20060507 (prerelease) (Debian 4.0.3-3)". > >> The compile process worked as expected, no error. > >> > >> So maybe your gcc version has some bug? Which exact > version do you run? > >> Can you provide the required patch, because without the chance to > >> reproduce, I am not exactly sure, what needs to be done. > >> > >> Thanks for your help. > >> > >> Christian Dickmann > >> > > > > Christian, > > > > I use g++ 4.1.0 from Fedora 5. The attached patch must > be applied. > > > > Regards, > > > > Stephane Ouellette. > > > > >

1 0

Patch: Splitting waitForSignal() in NSLP API
by Gotthard, Petr 18 Jun '06

18 Jun '06

Hello, I made a small patch for the nsis-0.4.1-dev: The current NSLP API waitForSignal() is blocked until a signal comes from GIST. This doesn't allow applications to use a custom select() function, i.e. to wait for custom sockets/timeouts within the same thread. I would propose to split the functionality of waitForSignal() into two new functions: getSockets() and processSockets(). The waitForSignal() should call these new functions and an own select(), so the original functionality is preserved. If you agree to my changes, could you please "adopt" these changes into the official nsis implementation? thanx and regards Petr Gotthard

2 1

RE: [Nsis_imp] NSIS 4.0 compiling error
by Christian Dickmann 14 Jun '06

14 Jun '06

> Christian, > > this is caused by g++ v4.0 and up. I was preparing a patch just before > version 0.4.0 was released but it's not done yet. Version 4.0+ of g++ just > follow the C++ standard... > > The fix is simple. The class qualifications must be removed. Hi, thank you for this information. However, I know of two machines with g++ 4.x where compiling works fine. One of them is a Mac OS X box. Today, I downloaded Knoppix 5.0 to try g++ 4.x by my own. "g++ -v" prints "gcc version 4.0.4 20060507 (prerelease) (Debian 4.0.3-3)". The compile process worked as expected, no error. So maybe your gcc version has some bug? Which exact version do you run? Can you provide the required patch, because without the chance to reproduce, I am not exactly sure, what needs to be done. Thanks for your help. Christian Dickmann

2 2

RE: [Nsis_imp] NSIS 4.0 compiling error
by Christian Dickmann 13 Jun '06

13 Jun '06

Hello, > When I have tried to compile NSIS 4.0 in Fedora Core 5 I have got the > following error messages: I have never seen this error message before, nor do I have a clue, what this error messages means. Did you try to compile any of our releases before 0.4.0? Is there anything special to your system? 64-bit? Non x86-CPU? Which version of g++ do you run? (i.e. What is the output of "g++ -v"?) > libxorp/eventloop.hh:229: error: extra qualification 'EventLoop::' on > member 'add_selector' > > Below I attach a complete listing of the messages showed during of the > configure and compilation process. > > Someone have any ideas how to find a solution for that error? No real solution yet, but hopefully we can find something special to your system which might help to address this problem. Thanks for your interest, Christian Dickmann

3 2

NSIS 4.0 compiling error
by Choque Ollachica, Johnny 12 Jun '06

12 Jun '06

Hello, When I have tried to compile NSIS 4.0 in Fedora Core 5 I have got the following error messages: libxorp/eventloop.hh:229: error: extra qualification EventLoop:: on member add_selector Below I attach a complete listing of the messages showed during of the configure and compilation process. Someone have any ideas how to find a solution for that error? Thanks in advance, Johnny # ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for ranlib... ranlib checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking openssl/ssl.h usability... yes checking openssl/ssl.h presence... yes checking for openssl/ssl.h... yes checking for OpenSSL ... yes checking net/bpf.h usability... no checking net/bpf.h presence... no checking for net/bpf.h... no checking netinet/sctp.h usability... no checking netinet/sctp.h presence... no checking for netinet/sctp.h... no checking for basic SCTP support... yes checking for proper IPv6 support... yes configure: creating ./config.status config.status: creating Makefile config.status: creating gist/Makefile config.status: creating library/Makefile config.status: creating nsis/Makefile config.status: creating nslp/Makefile config.status: creating nslp/nslp_api/Makefile config.status: creating nslp/qos/Makefile config.status: creating nslp/natfw/Makefile config.status: creating nslp/diag/Makefile config.status: creating nslp/ping/Makefile config.status: creating applications/Makefile config.status: creating applications/ping/Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands # make make all-recursive make[1]: Entering directory `/home/jchoque/nsis-0.4.0' Making all in library make[2]: Entering directory `/home/jchoque/nsis-0.4.0/library' if g++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -MT Socket.o -MD -MP -MF ".deps/Socket.Tpo" \ -c -o Socket.o `test -f 'socket/Socket.cpp' || echo './'`socket/Socket.cpp; \ then mv -f ".deps/Socket.Tpo" ".deps/Socket.Po"; \ else rm -f ".deps/Socket.Tpo"; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -MT SCTPSocket.o -MD -MP -MF ".deps/SCTPSocket.Tpo" \ -c -o SCTPSocket.o `test -f 'socket/SCTPSocket.cpp' || echo './'`socket/SCTPSocket.cpp; \ then mv -f ".deps/SCTPSocket.Tpo" ".deps/SCTPSocket.Po"; \ else rm -f ".deps/SCTPSocket.Tpo"; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -MT TCPSocket.o -MD -MP -MF ".deps/TCPSocket.Tpo" \ -c -o TCPSocket.o `test -f 'socket/TCPSocket.cpp' || echo './'`socket/TCPSocket.cpp; \ then mv -f ".deps/TCPSocket.Tpo" ".deps/TCPSocket.Po"; \ else rm -f ".deps/TCPSocket.Tpo"; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -MT TCPTLSSocket.o -MD -MP -MF ".deps/TCPTLSSocket.Tpo" \ -c -o TCPTLSSocket.o `test -f 'socket/TCPTLSSocket.cpp' || echo './'`socket/TCPTLSSocket.cpp; \ then mv -f ".deps/TCPTLSSocket.Tpo" ".deps/TCPTLSSocket.Po"; \ else rm -f ".deps/TCPTLSSocket.Tpo"; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -MT UDPSocket.o -MD -MP -MF ".deps/UDPSocket.Tpo" \ -c -o UDPSocket.o `test -f 'socket/UDPSocket.cpp' || echo './'`socket/UDPSocket.cpp; \ then mv -f ".deps/UDPSocket.Tpo" ".deps/UDPSocket.Po"; \ else rm -f ".deps/UDPSocket.Tpo"; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -MT GistTimer.o -MD -MP -MF ".deps/GistTimer.Tpo" \ -c -o GistTimer.o `test -f 'timer/GistTimer.cpp' || echo './'`timer/GistTimer.cpp; \ then mv -f ".deps/GistTimer.Tpo" ".deps/GistTimer.Po"; \ else rm -f ".deps/GistTimer.Tpo"; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -MT GistTimerWheel.o -MD -MP -MF ".deps/GistTimerWheel.Tpo" \ -c -o GistTimerWheel.o `test -f 'timer/GistTimerWheel.cpp' || echo './'`timer/GistTimerWheel.cpp; \ then mv -f ".deps/GistTimerWheel.Tpo" ".deps/GistTimerWheel.Po"; \ else rm -f ".deps/GistTimerWheel.Tpo"; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -MT GistException.o -MD -MP -MF ".deps/GistException.Tpo" \ -c -o GistException.o `test -f 'GistException.cpp' || echo './'`GistException.cpp; \ then mv -f ".deps/GistException.Tpo" ".deps/GistException.Po"; \ else rm -f ".deps/GistException.Tpo"; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -MT DebugLogger.o -MD -MP -MF ".deps/DebugLogger.Tpo" \ -c -o DebugLogger.o `test -f 'DebugLogger.cpp' || echo './'`DebugLogger.cpp; \ then mv -f ".deps/DebugLogger.Tpo" ".deps/DebugLogger.Po"; \ else rm -f ".deps/DebugLogger.Tpo"; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -MT IPaddr.o -MD -MP -MF ".deps/IPaddr.Tpo" \ -c -o IPaddr.o `test -f 'IPaddr.cpp' || echo './'`IPaddr.cpp; \ then mv -f ".deps/IPaddr.Tpo" ".deps/IPaddr.Po"; \ else rm -f ".deps/IPaddr.Tpo"; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -MT ConfigFileReader.o -MD -MP -MF ".deps/ConfigFileReader.Tpo " \ -c -o ConfigFileReader.o `test -f 'ConfigFileReader.cpp' || echo './'`ConfigFileReader.cpp; \ then mv -f ".deps/ConfigFileReader.Tpo" ".deps/ConfigFileReader.Po"; \ else rm -f ".deps/ConfigFileReader.Tpo"; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -MT NsisConfiguration.o -MD -MP -MF ".deps/NsisConfiguration.T po" \ -c -o NsisConfiguration.o `test -f 'NsisConfiguration.cpp' || echo './'`NsisConfiguration.cpp; \ then mv -f ".deps/NsisConfiguration.Tpo" ".deps/NsisConfiguration.Po"; \ else rm -f ".deps/NsisConfiguration.Tpo"; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -MT GistTLSException.o -MD -MP -MF ".deps/GistTLSException.Tpo " \ -c -o GistTLSException.o `test -f 'GistTLSException.cpp' || echo './'`GistTLSException.cpp; \ then mv -f ".deps/GistTLSException.Tpo" ".deps/GistTLSException.Po"; \ else rm -f ".deps/GistTLSException.Tpo"; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -MT BPFSocket.o -MD -MP -MF ".deps/BPFSocket.Tpo" \ -c -o BPFSocket.o `test -f 'socket/BPFSocket.cpp' || echo './'`socket/BPFSocket.cpp; \ then mv -f ".deps/BPFSocket.Tpo" ".deps/BPFSocket.Po"; \ else rm -f ".deps/BPFSocket.Tpo"; exit 1; \ fi rm -f libnsis.a ar cru libnsis.a Socket.o SCTPSocket.o TCPSocket.o TCPTLSSocket.o UDPSocket.o GistTimer.o GistTimerWheel.o GistException.o DebugLogger.o IPaddr.o ConfigFileReader.o NsisConfiguration.o GistTLSException.o BPFSocket. o ranlib libnsis.a if gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -MT xlog.o -MD -MP -MF ".deps/xlog.Tpo" \ -c -o xlog.o `test -f 'libxorp/xlog.c' || echo './'`libxorp/xlog.c; \ then mv -f ".deps/xlog.Tpo" ".deps/xlog.Po"; \ else rm -f ".deps/xlog.Tpo"; exit 1; \ fi if g++ -DHAVE_CONFIG_H -I. -I. -I.. -O2 -MT asyncio.o -MD -MP -MF ".deps/asyncio.Tpo" \ -c -o asyncio.o `test -f 'libxorp/asyncio.cc' || echo './'`libxorp/asyncio.cc; \ then mv -f ".deps/asyncio.Tpo" ".deps/asyncio.Po"; \ else rm -f ".deps/asyncio.Tpo"; exit 1; \ fi libxorp/eventloop.hh:229: error: extra qualification EventLoop:: on member add_selector make[2]: *** [asyncio.o] Error 1 make[2]: Leaving directory `/home/jchoque/nsis-0.4.0/library' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/jchoque/nsis-0.4.0' make: *** [all] Error 2

1 0

Release of NSIS implementation (0.4.0)
by Bernd Schloer 04 Jun '06

04 Jun '06

Hi, we would like to release a new version of the NSIS implementation (0.4.0) available at http://user.informatik.uni-goettingen.de/~nsis In order to permit linking the NSLP-API into non-free NSLPs the licenses of the corresponding files were changed into the Lesser GPL (LGPL). This release also contains a skeleton NSLP which can be used as a template to develop further NSLPs. These files are released under the 3-clause BSD-License. The rest of the project is still licensed under the GPL. Further changes are: * Changed buildsystem to automake and autoconf o Added support for FreeBSD, MacOSX o (As end-hosts, routers sniff but do not intercept RAO messages) o Added support for big-endian o IPv6 and SCTP are no longer required to build the package * Changed license o NSLP-API is now LGPL to allow usage in closed source NSLPs o New "skeleton NSLP" is BSD to allow building closed source NSLPs o The remaining code remains to be licensed under the GPL * Add richer support for SCTP * All modules now use a common configuration file * Improved documentation (introduced man pages) * Diagnostics NSLP added * Alignment to byte format of GIST-09 * Added "skeleton NSLP" for others to start creating own NSLPs. * QoS NSLP changes o IPv6 support added o QSPEC object support added o message processing refined o timer handling refined o QoSLogger support, improved debug levels o new structure of FSM-Code o man pages for nsis-qosd(8) and nsis-qos(1) added * Nat/Firewall NSLP changes o new Nat/Firewall NSLP client API o built-in GIST-independent protocol emulation o DebugLogger support, improved debug levels o rewritten Nat/Firewall NSLP client o more fine-grained command-line options o man pages for nsis-natfwd(8) and nsis-natfw(1) added o message parsing updated to draft-ietf-nsis-nslp-natfw-11 o replaced IP address/port placeholders o lots of minor protocol behavior improvements Xiaoming Fu Bernd Schloer Christian Dickmann Henning Peters University of Goettingen For further information =============================================================== Questions, inquiries, comments, please kindly report to the following mailing list: nsis_imp(a)cs.uni-goettingen.de To subscribe: send an email to nsis_imp-request(a)cs.uni-goettingen.de with the text subscribe YOUR-EMAIL-ADDRESS in the message body.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nsis_Imp June 2006