Nsis_Imp

nsis_imp@informatik.uni-goettingen.de

264 discussions

RE: [Nsis_imp] Testing openNSIS in Netkit
by Christian Dickmann 28 Apr '08

28 Apr '08

Sounds like a bug in our routing table reading code then. We set the wrong 5 bits. Now the interesting question is: What happens if you set readRoutingTable = no in the nsis.conf of the router? Does it still output 255.255.255.31 on startup? If so, I will check how to fix this ASAP. We always use /8 /16 or /24 as netmasks, so this never came up ... Christian > -----Original Message----- > From: Julien Lange [mailto:jlange@info.fundp.ac.be] > Sent: Sunday, April 27, 2008 5:38 PM > To: Christian Dickmann > Cc: nsis_imp(a)informatik.uni-goettingen.de > Subject: Re: [Nsis_imp] Testing openNSIS in Netkit > > Here is the output: > ---------------------- > router1:~# route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 192.168.0.8 0.0.0.0 255.255.255.248 U 0 0 0 > eth1 > 192.168.0.0 0.0.0.0 255.255.255.248 U 0 0 0 > eth0 > ---------------------- > > > Actually, I don't understand where this "31" is coming from... I set up > the interfaces using: > ---------------------- > ifconfig eth0 192.168.0.2 netmask 255.255.255.248 broadcast > 192.168.0.7 up > ifconfig eth1 192.168.0.10 netmask 255.255.255.248 broadcast > 192.168.0.15 up > ---------------------- > > > Christian Dickmann wrote: > >>From the router: > > (err) Read Route from IP Routing Table: To:192.168.0.0/255.255.255.31 > > with local IP: 192.168.0.2 > > > > 255.255.255.31 doesn't sound like a valid netmask. > > Shouldn't /29 translate to 255.255.255.248? > > (2^7 + 2^6 + 2^5 + 2^4 + 2^3 = 128 + 64 + 32 + 16 + 8 = 248) > > > > What does "route -n" show on that box? > > > > Christian > > > >> -----Original Message----- > >> From: Julien Lange [mailto:jlange@info.fundp.ac.be] > >> Sent: Sunday, April 27, 2008 5:00 PM > >> To: Christian Dickmann > >> Cc: nsis_imp(a)informatik.uni-goettingen.de > >> Subject: Re: [Nsis_imp] Testing openNSIS in Netkit > >> > >> Thank you very much for the quick answer, > >> > >> I've attached the files... the *.txt files are the output of the > > nodes. > >> > >> Best regards, > >> > >> > >> Julien. > >> > >> Christian Dickmann wrote: > >>> Hi, > >>> > >>> as the error message indicates, most likely your configuration > (e.g. > >>> nsis.conf) is wrong. Can you please send me the output when > starting > >>> all the 3 nsis instances when adding --debug 2? > >>> Also, please send me all 3 nsis.conf files. > >>> > >>> Thanks, > >>> Christian > >>> > >>>> -----Original Message----- > >>>> From: nsis_imp-bounces(a)informatik.uni-goettingen.de > >> [mailto:nsis_imp- > >>>> bounces(a)informatik.uni-goettingen.de] On Behalf Of Julien Lange > >>>> Sent: Sunday, April 27, 2008 3:20 PM > >>>> To: nsis_imp(a)informatik.uni-goettingen.de > >>>> Subject: [Nsis_imp] Testing openNSIS in Netkit > >>>> > >>>> Hello, > >>>> > >>>> I've been triyng to test openNSIS using Netkit > >>> (http://www.netkit.org/) > >>>> for some days without success. > >>>> > >>>> I use opennsis v0.5.0. My first test implies two hosts and one > >>>> router (see description below). > >>>> > >>>> When I run nsis daemon on the two hosts but not on the router, > >>>> everything works fine (ie I can "nsis-ping" them in both > > direction). > >>>> But as soon as I run nsis daemon also on the router, the hosts > > can't > >>>> communicate with each other, neiter with the router. > >>>> > >>>> I got this error from the router's stdout (trying to ping H1 from > >> H2): > >>>> --------------------------- > >>>> *** GistException: findOutgoingLocalAddress failed: No local > > address > >>>> was found for this destination address (192.168.0.1). Please check > >>>> your configuration *** > >>>> --------------------------- > >>>> > >>>> I tried to specify the ip addresses manually in nsis.conf, with > the > >>>> same results. > >>>> > >>>> Do you have some advice to help to solve this? > >>>> > >>>> Thank you very much in advance, > >>>> > >>>> > >>>> > >>>> Julien. > >>>> > >>>> ------------------------------------------------------ > >>>> Here is the description of the test network: > >>>> > >>>> ------ > >>>> - H1 - eth0:192.168.0.1 > >>>> ------ > >>>> . > >>>> . (net = 192.168.0.0/29) > >>>> . > >>>> ------ eth0:192.168.0.2 > >>>> - R - > >>>> ------ eth1:192.168.0.10 > >>>> . > >>>> . (net = 192.168.0.8/29) > >>>> . > >>>> ------ eth0:192.168.0.9 > >>>> - H2 - > >>>> ------ > >>>> > >>>> _______________________________________________ > >>>> Nsis_Imp mailing list > >>>> Nsis_Imp(a)informatik.uni-goettingen.de > >>>> https://user.informatik.uni- > goettingen.de/mailman/listinfo/nsis_imp > >>> > >>> > >>> > > > > > > > >

1 0

RE: [Nsis_imp] Testing openNSIS in Netkit
by Christian Dickmann 28 Apr '08

28 Apr '08

Seems like you did not modify your nsis.conf. The output still shows the old IP addresses. > -----Original Message----- > From: Julien Lange [mailto:jlange@info.fundp.ac.be] > Sent: Sunday, April 27, 2008 6:18 PM > To: Christian Dickmann > Cc: nsis_imp(a)informatik.uni-goettingen.de > Subject: Re: [Nsis_imp] Testing openNSIS in Netkit > > I just tested with a /24 network, but I got the same result :(... I > send you the output from the router (with debug enabled, sorry I guess > I forgot last time). > > J. > > Christian Dickmann wrote: > > Seems like we do not have a debug output, but looks like the bug is > > also in this code path. > > Lets me take a look. > > While I am doing this, is it an option for you to just a /24 network? > > > > Christian > > > >> -----Original Message----- > >> From: Julien Lange [mailto:jlange@info.fundp.ac.be] > >> Sent: Sunday, April 27, 2008 5:59 PM > >> To: Christian Dickmann > >> Subject: Re: [Nsis_imp] Testing openNSIS in Netkit > >> > >> I've attached the ouput of the router with "readRoutingTable = > no"... > > I > >> don't see the "31" anymore, but the problem is still there. > >> I tried to nsis-ping during the capture, from host1 to host2... And > I > >> still get the error. > >> > >> > >> > >> Christian Dickmann wrote: > >>> Sounds like a bug in our routing table reading code then. We set > the > >>> wrong 5 bits. > >>> Now the interesting question is: What happens if you set > >>> readRoutingTable = no in the nsis.conf of the router? > >>> > >>> Does it still output 255.255.255.31 on startup? > >>> > >>> If so, I will check how to fix this ASAP. > >>> > >>> We always use /8 /16 or /24 as netmasks, so this never came up ... > >>> > >>> Christian > >>> > >>>> -----Original Message----- > >>>> From: Julien Lange [mailto:jlange@info.fundp.ac.be] > >>>> Sent: Sunday, April 27, 2008 5:38 PM > >>>> To: Christian Dickmann > >>>> Cc: nsis_imp(a)informatik.uni-goettingen.de > >>>> Subject: Re: [Nsis_imp] Testing openNSIS in Netkit > >>>> > >>>> Here is the output: > >>>> ---------------------- > >>>> router1:~# route -n > >>>> Kernel IP routing table > >>>> Destination Gateway Genmask Flags Metric Ref > >>> Use > >>>> Iface > >>>> 192.168.0.8 0.0.0.0 255.255.255.248 U 0 0 > >>> 0 > >>>> eth1 > >>>> 192.168.0.0 0.0.0.0 255.255.255.248 U 0 0 > >>> 0 > >>>> eth0 > >>>> ---------------------- > >>>> > >>>> > >>>> Actually, I don't understand where this "31" is coming from... I > > set > >>> up > >>>> the interfaces using: > >>>> ---------------------- > >>>> ifconfig eth0 192.168.0.2 netmask 255.255.255.248 broadcast > >>>> 192.168.0.7 up > >>>> ifconfig eth1 192.168.0.10 netmask 255.255.255.248 broadcast > >>>> 192.168.0.15 up > >>>> ---------------------- > >>>> > >>>> > >>>> Christian Dickmann wrote: > >>>>> >From the router: > >>>>> (err) Read Route from IP Routing Table: > >>> To:192.168.0.0/255.255.255.31 > >>>>> with local IP: 192.168.0.2 > >>>>> > >>>>> 255.255.255.31 doesn't sound like a valid netmask. > >>>>> Shouldn't /29 translate to 255.255.255.248? > >>>>> (2^7 + 2^6 + 2^5 + 2^4 + 2^3 = 128 + 64 + 32 + 16 + 8 = 248) > >>>>> > >>>>> What does "route -n" show on that box? > >>>>> > >>>>> Christian > >>>>> > >>>>>> -----Original Message----- > >>>>>> From: Julien Lange [mailto:jlange@info.fundp.ac.be] > >>>>>> Sent: Sunday, April 27, 2008 5:00 PM > >>>>>> To: Christian Dickmann > >>>>>> Cc: nsis_imp(a)informatik.uni-goettingen.de > >>>>>> Subject: Re: [Nsis_imp] Testing openNSIS in Netkit > >>>>>> > >>>>>> Thank you very much for the quick answer, > >>>>>> > >>>>>> I've attached the files... the *.txt files are the output of the > >>>>> nodes. > >>>>>> Best regards, > >>>>>> > >>>>>> > >>>>>> Julien. > >>>>>> > >>>>>> Christian Dickmann wrote: > >>>>>>> Hi, > >>>>>>> > >>>>>>> as the error message indicates, most likely your configuration > >>>> (e.g. > >>>>>>> nsis.conf) is wrong. Can you please send me the output when > >>>> starting > >>>>>>> all the 3 nsis instances when adding --debug 2? > >>>>>>> Also, please send me all 3 nsis.conf files. > >>>>>>> > >>>>>>> Thanks, > >>>>>>> Christian > >>>>>>> > >>>>>>>> -----Original Message----- > >>>>>>>> From: nsis_imp-bounces(a)informatik.uni-goettingen.de > >>>>>> [mailto:nsis_imp- > >>>>>>>> bounces(a)informatik.uni-goettingen.de] On Behalf Of Julien > Lange > >>>>>>>> Sent: Sunday, April 27, 2008 3:20 PM > >>>>>>>> To: nsis_imp(a)informatik.uni-goettingen.de > >>>>>>>> Subject: [Nsis_imp] Testing openNSIS in Netkit > >>>>>>>> > >>>>>>>> Hello, > >>>>>>>> > >>>>>>>> I've been triyng to test openNSIS using Netkit > >>>>>>> (http://www.netkit.org/) > >>>>>>>> for some days without success. > >>>>>>>> > >>>>>>>> I use opennsis v0.5.0. My first test implies two hosts and > one > >>>>>>>> router (see description below). > >>>>>>>> > >>>>>>>> When I run nsis daemon on the two hosts but not on the router, > >>>>>>>> everything works fine (ie I can "nsis-ping" them in both > >>>>> direction). > >>>>>>>> But as soon as I run nsis daemon also on the router, the hosts > >>>>> can't > >>>>>>>> communicate with each other, neiter with the router. > >>>>>>>> > >>>>>>>> I got this error from the router's stdout (trying to ping H1 > >> from > >>>>>> H2): > >>>>>>>> --------------------------- > >>>>>>>> *** GistException: findOutgoingLocalAddress failed: No local > >>>>> address > >>>>>>>> was found for this destination address (192.168.0.1). Please > >>> check > >>>>>>>> your configuration *** > >>>>>>>> --------------------------- > >>>>>>>> > >>>>>>>> I tried to specify the ip addresses manually in nsis.conf, > with > >>>> the > >>>>>>>> same results. > >>>>>>>> > >>>>>>>> Do you have some advice to help to solve this? > >>>>>>>> > >>>>>>>> Thank you very much in advance, > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> Julien. > >>>>>>>> > >>>>>>>> ------------------------------------------------------ > >>>>>>>> Here is the description of the test network: > >>>>>>>> > >>>>>>>> ------ > >>>>>>>> - H1 - eth0:192.168.0.1 > >>>>>>>> ------ > >>>>>>>> . > >>>>>>>> . (net = 192.168.0.0/29) > >>>>>>>> . > >>>>>>>> ------ eth0:192.168.0.2 > >>>>>>>> - R - > >>>>>>>> ------ eth1:192.168.0.10 > >>>>>>>> . > >>>>>>>> . (net = 192.168.0.8/29) > >>>>>>>> . > >>>>>>>> ------ eth0:192.168.0.9 > >>>>>>>> - H2 - > >>>>>>>> ------ > >>>>>>>> > >>>>>>>> _______________________________________________ > >>>>>>>> Nsis_Imp mailing list > >>>>>>>> Nsis_Imp(a)informatik.uni-goettingen.de > >>>>>>>> https://user.informatik.uni- > >>>> goettingen.de/mailman/listinfo/nsis_imp > >>>>>>> > >>>>> > >>>>> > >>> > >>> > >>> > > > > > > > >

2 1

Re: [Nsis_imp] Testing openNSIS in Netkit
by Julien Lange 28 Apr '08

28 Apr '08

I just tested with a /24 network, but I got the same result :(... I send you the output from the router (with debug enabled, sorry I guess I forgot last time). J. Christian Dickmann wrote: > Seems like we do not have a debug output, but looks like the bug is also > in this code path. > Lets me take a look. > While I am doing this, is it an option for you to just a /24 network? > > Christian > >> -----Original Message----- >> From: Julien Lange [mailto:jlange@info.fundp.ac.be] >> Sent: Sunday, April 27, 2008 5:59 PM >> To: Christian Dickmann >> Subject: Re: [Nsis_imp] Testing openNSIS in Netkit >> >> I've attached the ouput of the router with "readRoutingTable = no"... > I >> don't see the "31" anymore, but the problem is still there. >> I tried to nsis-ping during the capture, from host1 to host2... And I >> still get the error. >> >> >> >> Christian Dickmann wrote: >>> Sounds like a bug in our routing table reading code then. We set the >>> wrong 5 bits. >>> Now the interesting question is: What happens if you set >>> readRoutingTable = no in the nsis.conf of the router? >>> >>> Does it still output 255.255.255.31 on startup? >>> >>> If so, I will check how to fix this ASAP. >>> >>> We always use /8 /16 or /24 as netmasks, so this never came up ... >>> >>> Christian >>> >>>> -----Original Message----- >>>> From: Julien Lange [mailto:jlange@info.fundp.ac.be] >>>> Sent: Sunday, April 27, 2008 5:38 PM >>>> To: Christian Dickmann >>>> Cc: nsis_imp(a)informatik.uni-goettingen.de >>>> Subject: Re: [Nsis_imp] Testing openNSIS in Netkit >>>> >>>> Here is the output: >>>> ---------------------- >>>> router1:~# route -n >>>> Kernel IP routing table >>>> Destination Gateway Genmask Flags Metric Ref >>> Use >>>> Iface >>>> 192.168.0.8 0.0.0.0 255.255.255.248 U 0 0 >>> 0 >>>> eth1 >>>> 192.168.0.0 0.0.0.0 255.255.255.248 U 0 0 >>> 0 >>>> eth0 >>>> ---------------------- >>>> >>>> >>>> Actually, I don't understand where this "31" is coming from... I > set >>> up >>>> the interfaces using: >>>> ---------------------- >>>> ifconfig eth0 192.168.0.2 netmask 255.255.255.248 broadcast >>>> 192.168.0.7 up >>>> ifconfig eth1 192.168.0.10 netmask 255.255.255.248 broadcast >>>> 192.168.0.15 up >>>> ---------------------- >>>> >>>> >>>> Christian Dickmann wrote: >>>>> >From the router: >>>>> (err) Read Route from IP Routing Table: >>> To:192.168.0.0/255.255.255.31 >>>>> with local IP: 192.168.0.2 >>>>> >>>>> 255.255.255.31 doesn't sound like a valid netmask. >>>>> Shouldn't /29 translate to 255.255.255.248? >>>>> (2^7 + 2^6 + 2^5 + 2^4 + 2^3 = 128 + 64 + 32 + 16 + 8 = 248) >>>>> >>>>> What does "route -n" show on that box? >>>>> >>>>> Christian >>>>> >>>>>> -----Original Message----- >>>>>> From: Julien Lange [mailto:jlange@info.fundp.ac.be] >>>>>> Sent: Sunday, April 27, 2008 5:00 PM >>>>>> To: Christian Dickmann >>>>>> Cc: nsis_imp(a)informatik.uni-goettingen.de >>>>>> Subject: Re: [Nsis_imp] Testing openNSIS in Netkit >>>>>> >>>>>> Thank you very much for the quick answer, >>>>>> >>>>>> I've attached the files... the *.txt files are the output of the >>>>> nodes. >>>>>> Best regards, >>>>>> >>>>>> >>>>>> Julien. >>>>>> >>>>>> Christian Dickmann wrote: >>>>>>> Hi, >>>>>>> >>>>>>> as the error message indicates, most likely your configuration >>>> (e.g. >>>>>>> nsis.conf) is wrong. Can you please send me the output when >>>> starting >>>>>>> all the 3 nsis instances when adding --debug 2? >>>>>>> Also, please send me all 3 nsis.conf files. >>>>>>> >>>>>>> Thanks, >>>>>>> Christian >>>>>>> >>>>>>>> -----Original Message----- >>>>>>>> From: nsis_imp-bounces(a)informatik.uni-goettingen.de >>>>>> [mailto:nsis_imp- >>>>>>>> bounces(a)informatik.uni-goettingen.de] On Behalf Of Julien Lange >>>>>>>> Sent: Sunday, April 27, 2008 3:20 PM >>>>>>>> To: nsis_imp(a)informatik.uni-goettingen.de >>>>>>>> Subject: [Nsis_imp] Testing openNSIS in Netkit >>>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> I've been triyng to test openNSIS using Netkit >>>>>>> (http://www.netkit.org/) >>>>>>>> for some days without success. >>>>>>>> >>>>>>>> I use opennsis v0.5.0. My first test implies two hosts and one >>>>>>>> router (see description below). >>>>>>>> >>>>>>>> When I run nsis daemon on the two hosts but not on the router, >>>>>>>> everything works fine (ie I can "nsis-ping" them in both >>>>> direction). >>>>>>>> But as soon as I run nsis daemon also on the router, the hosts >>>>> can't >>>>>>>> communicate with each other, neiter with the router. >>>>>>>> >>>>>>>> I got this error from the router's stdout (trying to ping H1 >> from >>>>>> H2): >>>>>>>> --------------------------- >>>>>>>> *** GistException: findOutgoingLocalAddress failed: No local >>>>> address >>>>>>>> was found for this destination address (192.168.0.1). Please >>> check >>>>>>>> your configuration *** >>>>>>>> --------------------------- >>>>>>>> >>>>>>>> I tried to specify the ip addresses manually in nsis.conf, with >>>> the >>>>>>>> same results. >>>>>>>> >>>>>>>> Do you have some advice to help to solve this? >>>>>>>> >>>>>>>> Thank you very much in advance, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Julien. >>>>>>>> >>>>>>>> ------------------------------------------------------ >>>>>>>> Here is the description of the test network: >>>>>>>> >>>>>>>> ------ >>>>>>>> - H1 - eth0:192.168.0.1 >>>>>>>> ------ >>>>>>>> . >>>>>>>> . (net = 192.168.0.0/29) >>>>>>>> . >>>>>>>> ------ eth0:192.168.0.2 >>>>>>>> - R - >>>>>>>> ------ eth1:192.168.0.10 >>>>>>>> . >>>>>>>> . (net = 192.168.0.8/29) >>>>>>>> . >>>>>>>> ------ eth0:192.168.0.9 >>>>>>>> - H2 - >>>>>>>> ------ >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Nsis_Imp mailing list >>>>>>>> Nsis_Imp(a)informatik.uni-goettingen.de >>>>>>>> https://user.informatik.uni- >>>> goettingen.de/mailman/listinfo/nsis_imp >>>>>>> >>>>> >>>>> >>> >>> >>> > > > > (err) Configuration: Using 192.168.0.1 as local IPv4 address (err) Configuration: Using 192.168.0.9 as local IPv4 address (err) Setting Debug Level to 2 NSIS daemon v0.5.0 starting ... My PID id = 454 FD is -1 TEST: no (warn) *** Connection over Unix Socket *** (warn) register_unix_sd : new connection sd[8] added to Event Loop. (warn) *** Received API Call *** (err) Registered NSLP with NSLPID 3 (warn) Debug client connected (warn) Debug Client send 3 (warn) *** Connection over Unix Socket *** (warn) register_unix_sd : new connection sd[10] added to Event Loop. (warn) *** Received API Call *** (err) Registered NSLP with NSLPID 5 (warn) *** Connection over Unix Socket *** (warn) register_unix_sd : new connection sd[11] added to Event Loop. (warn) *** Received API Call *** (err) Registered NSLP with NSLPID 1 (warn) *** Received RAO packet (value = 00 00) *** (warn) *** Dmode message from : 192.168.0.1:4> *** (info) GIST message: Version = 1 Hop Count = 49 NSLP ID = 3 Message length = 112 (info) Type = QUERY (info) S flag = 1 (info) R flag = 1 (info) E flag = 0 (info) GistMriPathCoupled: length = 56 (info) Direction = Downstream (info) Source IP = 192.168.0.1 (info) Dest IP = 192.168.1.9 (info) GistSessionId: length = 20 (info) 01000000 01000000 01000000 01000000 (info) GistNetworkLayerInfo: length = 28 (info) IntAddr = 192.168.0.1 (info) RouteStateValidityTime = 100000 (info) GistQueryCookie: length = 36 (warn) *** This is a UNknown flow *** (info) FSM: Change state to 0 (info) FSM: Event 5 while state is 0 (crit) *** GistException: findOutgoingLocalAddress failed: No local address was found for this destination address (192.168.0.1). Please check your configuration *** (warn) *** Received RAO packet (value = 00 00) *** (warn) *** Dmode message from : 192.168.0.1:4> *** (info) GIST message: Version = 1 Hop Count = 4 NSLP ID = 3 Message length = 112 (info) Type = QUERY (info) S flag = 1 (info) R flag = 1 (info) E flag = 0 (info) GistMriPathCoupled: length = 56 (info) Direction = Downstream (info) Source IP = 192.168.0.1 (info) Dest IP = 192.168.1.9 (info) GistSessionId: length = 20 (info) 01000000 01000000 01000000 01000000 (info) GistNetworkLayerInfo: length = 28 (info) IntAddr = 192.168.0.1 (info) RouteStateValidityTime = 100000 (info) GistQueryCookie: length = 36 (warn) *** This is a known flow *** (info) FSM: Event 5 while state is 0 (crit) *** GistException: findOutgoingLocalAddress failed: No local address was found for this destination address (192.168.0.1). Please check your configuration *** (warn) *** Received RAO packet (value = 00 00) *** (warn) *** Dmode message from : 192.168.0.1:4> *** (info) GIST message: Version = 1 Hop Count = 4 NSLP ID = 3 Message length = 112 (info) Type = QUERY (info) S flag = 1 (info) R flag = 1 (info) E flag = 0 (info) GistMriPathCoupled: length = 56 (info) Direction = Downstream (info) Source IP = 192.168.0.1 (info) Dest IP = 192.168.1.9 (info) GistSessionId: length = 20 (info) 01000000 01000000 01000000 01000000 (info) GistNetworkLayerInfo: length = 28 (info) IntAddr = 192.168.0.1 (info) RouteStateValidityTime = 100000 (info) GistQueryCookie: length = 36 (warn) *** This is a known flow *** (info) FSM: Event 5 while state is 0 (crit) *** GistException: findOutgoingLocalAddress failed: No local address was found for this destination address (192.168.0.1). Please check your configuration *** (warn) *** Received RAO packet (value = 00 00) *** (warn) *** Dmode message from : 192.168.0.1:4> *** (info) GIST message: Version = 1 Hop Count = 4 NSLP ID = 3 Message length = 112 (info) Type = QUERY (info) S flag = 1 (info) R flag = 1 (info) E flag = 0 (info) GistMriPathCoupled: length = 56 (info) Direction = Downstream (info) Source IP = 192.168.0.1 (info) Dest IP = 192.168.1.9 (info) GistSessionId: length = 20 (info) 01000000 01000000 01000000 01000000 (info) GistNetworkLayerInfo: length = 28 (info) IntAddr = 192.168.0.1 (info) RouteStateValidityTime = 100000 (info) GistQueryCookie: length = 36 (warn) *** This is a known f(err) Configuration: Using 192.168.0.1 as local IPv4 address (err) Configuration: Using 192.168.0.9 as local IPv4 address (err) Setting Debug Level to 2 NSIS daemon v0.5.0 starting ... My PID id = 454 Starting pingServer (pid: 455) ... [49;39m** Process 455 got signal 15: SIGTERM low *** (info) FSM: Event 5 while state is 0 (crit) *** GistException: findOutgoingLocalAddress failed: No local address was found for this destination address (192.168.0.1). Please check your configuration *** [49;39m** Process 454 got signal 2: SIGINT (err) Configuration: Using 192.168.0.1 as local IPv4 address (err) Configuration: Using 192.168.0.9 as local IPv4 address (err) Setting Debug Level to 2 NSIS daemon v0.5.0 starting ... My PID id = 454 Starting diagServer (pid: 457) ... (err) Diag: connected to GIST server [49;39m** Process 457 got signal 2: SIGINT [49;39m** Process 457 got signal 15: SIGTERM (err) Configuration: Using 192.168.0.1 as local IPv4 address (err) Configuration: Using 192.168.0.9 as local IPv4 address (err) Setting Debug Level to 2 NSIS daemon v0.5.0 starting ... My PID id = 454 Starting qosServer (pid: 456) ... overall_rate 100mbit, default_rate 100kbit, default_max_rate 100mbit, float max_bw 0.000000 (TC) Running "tc qdisc delete dev eth0 root handle 1:" (IpTables) Running "iptables -t mangle -F PREROUTING" (TC) Running "tc qdisc add dev eth0 root handle 1: htb default 2" (TC) Running "tc class add dev eth0 parent 1: classid 1:1 htb rate 100mbit burst 15k" (TC) Running "tc class add dev eth0 parent 1:1 classid 1:2 htb rate 100kbit ceil 100mbit" (TC) Running "tc qdisc add dev eth0 parent 1:2 handle 2: sfq perturb 10" QoSServer: connected to GIST server [49;39m** Process 456 got signal [49;39m** Process 456 got signal 15: SIGTERM

1 0

RE: [Nsis_imp] Testing openNSIS in Netkit
by Christian Dickmann 28 Apr '08

28 Apr '08

>From the router: (err) Read Route from IP Routing Table: To:192.168.0.0/255.255.255.31 with local IP: 192.168.0.2 255.255.255.31 doesn't sound like a valid netmask. Shouldn't /29 translate to 255.255.255.248? (2^7 + 2^6 + 2^5 + 2^4 + 2^3 = 128 + 64 + 32 + 16 + 8 = 248) What does "route -n" show on that box? Christian > -----Original Message----- > From: Julien Lange [mailto:jlange@info.fundp.ac.be] > Sent: Sunday, April 27, 2008 5:00 PM > To: Christian Dickmann > Cc: nsis_imp(a)informatik.uni-goettingen.de > Subject: Re: [Nsis_imp] Testing openNSIS in Netkit > > Thank you very much for the quick answer, > > I've attached the files... the *.txt files are the output of the nodes. > > > Best regards, > > > Julien. > > Christian Dickmann wrote: > > Hi, > > > > as the error message indicates, most likely your configuration (e.g. > > nsis.conf) is wrong. Can you please send me the output when starting > > all the 3 nsis instances when adding --debug 2? > > Also, please send me all 3 nsis.conf files. > > > > Thanks, > > Christian > > > >> -----Original Message----- > >> From: nsis_imp-bounces(a)informatik.uni-goettingen.de > [mailto:nsis_imp- > >> bounces(a)informatik.uni-goettingen.de] On Behalf Of Julien Lange > >> Sent: Sunday, April 27, 2008 3:20 PM > >> To: nsis_imp(a)informatik.uni-goettingen.de > >> Subject: [Nsis_imp] Testing openNSIS in Netkit > >> > >> Hello, > >> > >> I've been triyng to test openNSIS using Netkit > > (http://www.netkit.org/) > >> for some days without success. > >> > >> I use opennsis v0.5.0. My first test implies two hosts and one > >> router (see description below). > >> > >> When I run nsis daemon on the two hosts but not on the router, > >> everything works fine (ie I can "nsis-ping" them in both direction). > >> > >> But as soon as I run nsis daemon also on the router, the hosts can't > >> communicate with each other, neiter with the router. > >> > >> I got this error from the router's stdout (trying to ping H1 from > H2): > >> --------------------------- > >> *** GistException: findOutgoingLocalAddress failed: No local address > >> was found for this destination address (192.168.0.1). Please check > >> your configuration *** > >> --------------------------- > >> > >> I tried to specify the ip addresses manually in nsis.conf, with the > >> same results. > >> > >> Do you have some advice to help to solve this? > >> > >> Thank you very much in advance, > >> > >> > >> > >> Julien. > >> > >> ------------------------------------------------------ > >> Here is the description of the test network: > >> > >> ------ > >> - H1 - eth0:192.168.0.1 > >> ------ > >> . > >> . (net = 192.168.0.0/29) > >> . > >> ------ eth0:192.168.0.2 > >> - R - > >> ------ eth1:192.168.0.10 > >> . > >> . (net = 192.168.0.8/29) > >> . > >> ------ eth0:192.168.0.9 > >> - H2 - > >> ------ > >> > >> _______________________________________________ > >> Nsis_Imp mailing list > >> Nsis_Imp(a)informatik.uni-goettingen.de > >> https://user.informatik.uni-goettingen.de/mailman/listinfo/nsis_imp > > > > > > > >

2 1

RE: [Nsis_imp] Testing openNSIS in Netkit
by Christian Dickmann 28 Apr '08

28 Apr '08

Hi, as the error message indicates, most likely your configuration (e.g. nsis.conf) is wrong. Can you please send me the output when starting all the 3 nsis instances when adding --debug 2? Also, please send me all 3 nsis.conf files. Thanks, Christian > -----Original Message----- > From: nsis_imp-bounces(a)informatik.uni-goettingen.de [mailto:nsis_imp- > bounces(a)informatik.uni-goettingen.de] On Behalf Of Julien Lange > Sent: Sunday, April 27, 2008 3:20 PM > To: nsis_imp(a)informatik.uni-goettingen.de > Subject: [Nsis_imp] Testing openNSIS in Netkit > > Hello, > > I've been triyng to test openNSIS using Netkit (http://www.netkit.org/) > for some days without success. > > I use opennsis v0.5.0. My first test implies two hosts and one router > (see description below). > > When I run nsis daemon on the two hosts but not on the router, > everything works fine (ie I can "nsis-ping" them in both direction). > > But as soon as I run nsis daemon also on the router, the hosts can't > communicate with each other, neiter with the router. > > I got this error from the router's stdout (trying to ping H1 from H2): > --------------------------- > *** GistException: findOutgoingLocalAddress failed: No local address > was > found for this destination address (192.168.0.1). Please check your > configuration *** > --------------------------- > > I tried to specify the ip addresses manually in nsis.conf, with the > same > results. > > Do you have some advice to help to solve this? > > Thank you very much in advance, > > > > Julien. > > ------------------------------------------------------ > Here is the description of the test network: > > ------ > - H1 - eth0:192.168.0.1 > ------ > . > . (net = 192.168.0.0/29) > . > ------ eth0:192.168.0.2 > - R - > ------ eth1:192.168.0.10 > . > . (net = 192.168.0.8/29) > . > ------ eth0:192.168.0.9 > - H2 - > ------ > > _______________________________________________ > Nsis_Imp mailing list > Nsis_Imp(a)informatik.uni-goettingen.de > https://user.informatik.uni-goettingen.de/mailman/listinfo/nsis_imp

2 1

Testing openNSIS in Netkit
by Julien Lange 28 Apr '08

28 Apr '08

Hello, I've been triyng to test openNSIS using Netkit (http://www.netkit.org/) for some days without success. I use opennsis v0.5.0. My first test implies two hosts and one router (see description below). When I run nsis daemon on the two hosts but not on the router, everything works fine (ie I can "nsis-ping" them in both direction). But as soon as I run nsis daemon also on the router, the hosts can't communicate with each other, neiter with the router. I got this error from the router's stdout (trying to ping H1 from H2): --------------------------- *** GistException: findOutgoingLocalAddress failed: No local address was found for this destination address (192.168.0.1). Please check your configuration *** --------------------------- I tried to specify the ip addresses manually in nsis.conf, with the same results. Do you have some advice to help to solve this? Thank you very much in advance, Julien. ------------------------------------------------------ Here is the description of the test network: ------ - H1 - eth0:192.168.0.1 ------ . . (net = 192.168.0.0/29) . ------ eth0:192.168.0.2 - R - ------ eth1:192.168.0.10 . . (net = 192.168.0.8/29) . ------ eth0:192.168.0.9 - H2 - ------

1 0

opennsis compilation on amd64
by Julien Lange 25 Apr '08

25 Apr '08

Hello, I'm trying to compile openNSIS 0.5.0 on my 64bits linux, without any success. I get this error: Can someone help to fix this? --------------------- fsm/GistFsmReceiver.cpp: In member function ‘void GistFsmReceiver::Set_State_Lifetime(int, void*)’: fsm/GistFsmReceiver.cpp:251: error: cast from ‘void*’ to ‘int’ loses precision make[2]: *** [GistFsmReceiver.o] Error 1 make[2]: Leaving directory `/home/ilove/software/opennsis/nsis-0.5.0/gist' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/ilove/software/opennsis/nsis-0.5.0' make: *** [all] Error 2 --------------------- In order to ease my tests, in would have been great to be able to use this machine (I got opennsis to work on a 32bits platform easily). Thank you in advance for your help! Best regards, Julien.

2 1

Available NSIS Implementations as of Jan 2008
by Martin Stiemerling 08 Jan '08

08 Jan '08

[This mail has been sent to the NSIS list, nsis-imp@ietf, and nsis- imp@goettingen. Sorry for any duplicates you may receive] Dear all, I'm preparing a web page with a list of all available NSIS GIST, QoS NSLP, and NATFW NSLP implementations. Please send the following information to nsis-chairs(a)tools.ietf.org if you have a implementation or multiple implementations of GIST, QoS or NATFW NSLP, or any other NSIS component: - Name of release - What (GIST, QoS NSLP, NATFW NSLP) - based on which draft version - (if possible) feature set (e.g. full QoS NSLP implementation, GIST but only D-MODE, etc) - available for which operating system (e.g., Linux, FreeBSD, Windows, OpenWRT, etc) - License (e.g. closed source, GPL, etc) - Link to software or web page - Implementation tested at interop? - Contact e-mail address Thanks in advance Martin stiemerling(a)netlab.nec.de NEC Laboratories Europe - Network Research Division NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England 2832014

1 0

QoS reservations
by Bertrand Goareguer 21 Dec '07

21 Dec '07

Hello, When reserving some resources, the resources are reserved on all the interfaces of the node. I guess the resources should instead be reserved only on the outgoing interface for this flow. Function NsisConfiguration::findOutgoingLocalAddress() can be used to retrieve the outgoing IP address. From there, a match can probably easily be found with the local interface that is configured with this IP address. Am I right, or the reservation on all the interfaces of the node was made on purpose ? Regards, Bertrand

2 1

GIST routing state teardown
by Bertrand Goareguer 07 Dec '07

07 Dec '07

Hi, I realized that after tearing a session down in the QoS-NSLP, this session was effectively torn down in the QoS-NSLP but the routing state for the session was not deleted at the GIST layer. Therefore, I could see some refreshing QUERY/RESPONSE messages every 50 seconds. Looking at the NSIS NTLP draft, I understood there were two ways for the routing state to be deleted : - either when there is no activity for this session (in this case a timer has to be reset each time some data corresponding to this session is either sent or received) -or when the signaling application calls the SetStateLifetime() function of the API with 0 as the state lifetime. It seems that the first solution is not implemented in the 0.5.1-dev version of the NSIS stack (I couldn't see any timer being reset in the GistFsmSender::Rx_Data_Msg() and GistFsmSender::Establ_Api_SendMsg() functions). Then I tried to use the second solution : calling the SetStateLifetime() function of the API when releasing the reservations for a flow in the QoS-NSLP. But at the GIST layer the SetStateLifetime() function (in ./nsis-0.5.1-dev/gist/nslp_api/nslp_api.cpp) only displays the MRI. I wanted to add a condition so that if the state_lifetime parameter was equal to 0, the fsm corresponding to the session should be deleted. The problem was that I couldn't identify the fsm because the SID is not part of the parameters of the SetStateLifetime() function (although Appendix B.5 of the NSIS NTLP drafts say the SID should be one of the parameters). Can anyone confirm this before I start looking at how to add the SID to the parameters ? Regards, Bertrand

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nsis_Imp