Nsis_Imp November 2006

nsis_imp@informatik.uni-goettingen.de

18 participants
21 discussions

Automake file
by sergiole＠tml.hut.fi 04 Dec '06

04 Dec '06

Hi, I would like to ask you the following. I created 2 new files with the authentication-object and I am going to integrate these to NATFW NSLP. The problem is that I can not re-create the file Makefile.in because the file configure.ac is missing. I updated Makefile.am with my files and when I run automake I got root@workstation5:~/nsis0.5.0-dev/nslp/natfw# automake automake: `configure.ac' or `configure.in' is required Are you using some script to create Makefile.in? Regards, Sergio Lembo

2 4

$B$O$8$a$^$7$F!#H~5*$G$9(B(*^_^*)
by 石橋　美紀 30 Nov '06

30 Nov '06

1 0

bug NatFwDataTerminalInfoObject
by sergiole＠tml.hut.fi 28 Nov '06

28 Nov '06

Hi, I think that I found a bug in the file nsis-0.5.0-dev\nslp\natfw\objects\NatFwDataTerminalInfoObject.cpp observe the following method void NatFwDataTerminalInfoObject::analyze(unsigned char * buffer, unsigned int length) { tail = buffer; iPtr = tail; pPtr = tail; sPtr = tail; tail += 2; dsprefixPtr = tail; tail += 3; dsprotocolPtr = tail; tail += 4; destportPtr = tail; tail += 6; srcportPtr = tail; tail += 8; addrPtr = tail; tail = buffer + length; } In my opinion you should change the following lines tail += 2; tail += 3; tail += 4; tail += 6; tail += 8; by tail += 2; tail += 1; tail += 1; tail += 2; tail += 2; or alternatively by tail = buffer + 2; tail = buffer + 3; tail = buffer + 4; tail = buffer + 6; tail = buffer + 8; Regards, Sergio Lembo

1 0

$B"#"#"#:FAw%a!<%k!#;j5^3NG'$7$F$/$@$5$$"#"#"#(B
by サポートセンター 26 Nov '06

26 Nov '06

1 0

Parameters in NSLP NATFW 0.4.0
by Sergio Lembo 21 Nov '06

21 Nov '06

Hello, We are testing the NATFW NSLP and have some questions about the parameters used in nsis-natfw 0.4.0 (release nsis-0.4.0.tar.gz) <1> We would like to know how to use the parameters in nsis-natfw 0.4.0. (The examples and tutorials are for version 0.3.0). Although we made some advances debugging the code, we have some problems. Our scenario is the following node A (initiator) 10.1.1.5/24 ------> node B (FW) 10.1.1.7/24 and 10.1.2.7/24 ------> node C 10.1.2.11/24 For example, we execute the following in node A (initiator): ./nsis-natfw --create -s 10.1.1.5 -d 10.1.2.11 --sport 5004 --dport 5009 Then in node B (FW), we observe a system call to iptables like the following iptables -A natfwforward -p tcp -s 10.1.1.5/32 -d 10.1.2.11/32 -j ACCEPT When actually we want to have a call like the following iptables -A natfwforward -p tcp -s 10.1.1.5/24 sport 5004 -d 10.1.2.11/24 d --dport 5009 -j ACCEPT We debugged the code and could not find these port numbers at the FW side (node B) Since the ports are not received, the condition "if (srcPort && destPort)" in FwApi.cpp is false and iptables is executed without the ports. In case that you have some draft with examples about how to use nsis-natfw 0.4.0. we would like to learn how to use the parameters. Also, we do not understand how to specify a range of ports, for example source ports from 1024 to 65535 is specified like "--sport 1024:65535" in iptables, but nsis-natfw does not recognize this syntax. Furthermore we tried to use parameter --deny, but we got always an ACCEPT target in iptables. <2> Some processes are terminated unexpectedly, ** Process 16577 got signal 11: SIGSEGV *** Unix Socket: Connection reset by peer *** ** Process 16576 got signal 15: SIGTERM *** Unix Socket: Connection reset by peer *** Below there is a link to a file with a log of the outputs in the 3 nodes, in case you want to know more details. http://users.tkk.fi/~sergiole/061106natfw_debug.txt Regards Sergio ----------------------- Sergio Lembo sergio.lembo(at)hut.fi -----------------------

5 12

Re: [Nsis_imp] using ping
by Jesús Pérez 21 Nov '06

21 Nov '06

Hello, I have already downloaded and tried the new nsis version and the ping works perfectly. I don't know which problem I had with the previous one. The frames were duplicated because I was capturing in promiscuous mode in the wireless network and that's why we saw the ones from the laptop which sends the ping and the ones from the access point to the second laptop. Also the different addresses were of the laptops and ap. There is something a bit strange on the ethereal captures only when I use a hub, it is the Checksum of UDP. Some of the frames have the correct checksum for one computer and incorrect for the another one and vice versa. It doesn't look important, because the system works properly. Thank you for your help Cheers Jesús Christian Dickmann wrote: > Hi, > > >> >> Here are the files taken from both machines. I will have a look at >> this tool also, > > > This capture is really strange. > 1. The initial GIST Query is duplicated > 2. Two GIST Responses are sent but to different MAC addresses > 3. To that Response no GIST Confirm is sent > > Are you able to provide an additional capture when nsis-ping is > started on the other node? > Can you please test the latest nsis-0.5.0-dev version? > http://user.informatik.uni-goettingen.de/~nsis/beta.html > > I think your network setup is really messed up in some way. It would > be interesting to see if a direct hub connection with the wireless > turned off changes the behavior. > > Christian Dickmann >

1 0

using ping
by Jesús Pérez 17 Nov '06

17 Nov '06

Hello, I sent you an email a week ago explaining that I could not run the nsis-ping on two laptops with wireless interfaces (laptop A: 128.0.0.102 and B: 128.0.0.114). I have already tried a "normal" ping between both laptops and it works. However, the nsis-ping doesn't work despite changing slightly the configuration files as follows: -A nsis.conf: IPv4.entries = 1 IPv4[0].addr = 128.0.0.102 IPv4[0].net = 128.0.0.0 IPv4[0].mask = 24 # 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 ------------------------------------------------------------------------------------ -B nsis.conf: IPv4.entries = 1 IPv4[0].addr = 128.0.0.114 IPv4[0].net = 128.0.0.0 IPv4[0].mask = 24 # 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 ----------------------------------------------------------------------------------------- I have check some variables in the code and I saw that in PingClient.cpp -> readAnswer res = 0 after calling poll, instead of 1 as when laptop sends a ping to itself. I changed the debug level to 2 as you recommended me, but is quite difficult to see what could be wrong for me because the laptop B doesn't receive any messages: The output for laptop A (sender) is: (err) Using 128.0.0.102 <http://128.0.0.102> as local IPv4 address (err) Setting Debug Level to 2 NSIS daemon v0.5.0-dev starting ... My PID id = 5768 FD is -1 TEST: no Starting pingServer (pid: 5769) ... Starting qosServer (pid: 5770)... (warn) *** Connection over Unix Socket *** (warn) register_unix_sd : new connection sd[6] added to Event Loop. (warn) *** Received API Call *** (warn) *** Connection over Unix Socket *** (warn) register_unix_sd : new connection sd[7] added to Event Loop. (warn) *** Received API Call *** QoSServer: connected to GIST server Ping client connected (warn) *** Received API Call *** (info) *** API-Call SendMessage() *** (info) nslp_data : (info) nd_size : 28 (info) nslp_id : 0x0001 (info) sid : (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) (info) mri->msgRoutingMethod : 0x0000 (info) mri->s : 0 (info) mri->f : 0 (info) mri->t : 0 (info) mri->p : 0 (info) mri->ipVersion : 0x04 (info) mri->reserved : 0x00 (info) mri->d : 0 (info) mri->b : 0 (info) mri->a : 0 (info) mri->srcAddr : 128.0.0.102 <http://128.0.0.102> (info) mri->destAddr : 128.0.0.114 <http://128.0.0.114> (info) mri->srcPrefix : 0x20 (info) mri->destPrefix : 0x20 (info) mri->protocol : 0x00 (info) mri->diffserv_field : 0x00 (info) reliab. : 0 (info) security : 0 (info) local : 0 (info) installRoutingState : 1 (info) timeout : 2000 (info) ip_ttl : 10 (warn) *** Starting new Downstream FSM *** (info) FSM: Change state to 0 (info) FSM: Event 0 while state is 0 (info) *** Dmode message > query (with rao) *** (info) FSM: Change state to 3 (warn) *** Received API Call *** (info) *** API-Call SendMessage() *** (info) nslp_data : \uffff (info) nd_size : 28 (info) nslp_id : 0x0001 (info) sid : (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) 0x00 (info) (info) mri->msgRoutingMethod : 0x0000 (info) mri->s : 0 (info) mri->f : 0 (info) mri->t : 0 (info) mri->p : 0 (info) mri->ipVersion : 0x04 (info) mri->reserved : 0x00 (info) mri->d : 0 (info) mri->b : 0 (info) mri->a : 0 (info) mri->srcAddr : 128.0.0.102 <http://128.0.0.102> (info) mri->destAddr : 128.0.0.114 <http://128.0.0.114> (info) mri->srcPrefix : 0x20 (info) mri->destPrefix : 0x20 (info) mri->protocol : 0x00 (info) mri->diffserv_field : 0x00 (info) reliab. : 0 (info) security : 0 (info) local : 0 (info) installRoutingState : 1 (info) timeout : 2000 (info) ip_ttl : 10 (info) FSM: Event 0 while state is 3 (info) FSM: Event 4 while state is 3 (warn) *** Received API Call *** (info) *** API-Call SendMessage() *** ... ... ---------------------------------------------------------------------------------------------- The output for the laptop B (receiver) is: (err) Using 128.0.0.114 <http://128.0.0.114> as local IPv4 address (err) Setting Debug Level to 2 NSIS daemon v0.5.0-dev starting ... My PID id = 2659 FD is -1 TEST: no Starting pingServer (pid: 2660) ... Starting qosServer (pid: 2661)... QoSServer: connected to GIST server (warn) *** Connection over Unix Socket *** (warn) register_unix_sd : new connection sd[6] added to Event Loop. (warn) *** Connection over Unix Socket *** (warn) register_unix_sd : new connection sd[7] added to Event Loop. (warn) *** Received API Call *** (warn) *** Received API Call *** ---------------------------------------------------------------------------------------------- If you know why it happens, I would appreciate your help. Thanks, Cheers, Jesus

2 2

$B:#F|$8$c$J$$$H4V$K9g$$$^$;$s(B
by 楠木　明海 13 Nov '06

13 Nov '06

━【 ▼注目▼ 】━━━━━━━━━━━━━━━━━━━━━━━━━━ ■ 先日はご応募ありがとうございました。 ■■ 当グループにて厳選なる審査の結果 ■■■ nsis_imp様にお会いしたいという ■■■■ 女性会員様がいらっしゃいます。 http://www.camellia.cx/g/ ■■■■■ 本日、採用報告連絡を差し上げておりますが ■■■■■■ お相手の女性会員様からのお言葉で ■■■■■■■ 『都合を合わせてすぐにでもお会いしたい』というお言葉を ■■■■■■■■　頂いておりますので大至急ご連絡をしてください。 ━【 http://www.camellia.cx/g/ 】 ━━━━━━━━━━━━━━━━━ ■□ご連絡方法□■□■□■□■□■□■□■□■□■□■□■□■□■□ □ ■今回お会いしたいとおっしゃっていただいた □女性会員様との連絡方法は簡単です。 ■ http://www.camellia.cx/g/　よりアクセスしていただいて連絡フォームより □ご連絡してください。 ■ □■□■□■□■□■□■□■□■□■□■□■□■□■□■□■□■□■ □━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━□ ┏┌┌┌ 　上記でご説明いたしましたフォームに入力するだけの簡単操作ですが ┏┏┌┌　ご不明な点がございましたらサポートセンターまでお問い合わせください ┏┏┏┌　＜　http://www.camellia.cx/g/　＞にご連絡いただければすぐにでも ┏┏┏┏ 今回、nsis_imp様とお会いしたいと交際希望の女性会員様との ┏┏┏┏　【　連絡手段　】をご連絡いたしますのでそのままお待ちください。 □━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━□ □★ご利用について★□ ┠─────── 入会料　　０円 ┠─────── 紹介料　　０円 ┠─────── 退会料　　０円 ┃ ┗━ 男性に限り登録から退会まで無料でご利用できます。　　　　　　　　　　　　　　　http://www.camellia.cx/g/

1 0

Announcement: New NSIS development version available
by Christian Dickmann 11 Nov '06

11 Nov '06

Hi, we are proud to announce the release of a new development version (0.5.0-dev) of our NSIS implementation. The new version includes a lot of bugfixes and improvements over the last development release with regard to stability and specification compliance. Especially, several problems encountered during the NSIS interop meeting hosted by University of Coimbra in October are resolved in the new version. You can download the new version from our beta version page: http://user.informatik.uni-goettingen.de/~nsis/beta.html We encourage anyone to try this development version and appreciate feedback of any kind, such as installation/setup experience, bug reports, feature requests, etc. Please note, that a new version of our ethereal/wireshark NSIS dissector will be made available during this weekend. The new version will feature minor bugfixes, as well as updates to the latest protocol specification versions. Christian Dickmann and Bernd Schloer On behalf of University of Goettingen NSIS team

1 0

$B0l<!;n839g3J$N$*CN$i$;!#(B
by 採用担当 11 Nov '06

11 Nov '06

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 November 2006