Nsis_Imp January 2007

nsis_imp@informatik.uni-goettingen.de

11 participants
9 discussions

qos reservation
by Jesús Pérez 30 Jan '07

30 Jan '07

Hello, I am using the nsis-0.5.0 according to your last email. I think the nsis-qos works well. However, I am trying to make a reservation from the QNI (192.168.1.109 <http://192.168.1.109>) to the QNR (not using any other QNE) and I consider that the QNR ( 192.168.1.102 <http://192.168.1.102>) is rejecting this reserve message according to my view of the output shown below (on the QNI). SID: ffffffff ffffffff ffffffff ffffffff fsm : 0x8471bc8 dflag:1, 192.168.1.102 <http://192.168.1.102> QNI: --> incoming msg + SII_Handle : 192.168.1.102 <http://192.168.1.102> + srcAddr : 192.168.1.109 <http://192.168.1.109> + destAddr : 192.168.1.102 <http://192.168.1.102> + direction : UPSTREAM + msg length : 12 bytes + QoS Message Type : NOTIFY + Object Type : InfoSpec ++ InfoSpec : 0x03 0x01 0x00 0x00 + Q:T:R:S-Flag : 0:0:0:0 triggerEvent : ST_INST::EV_RX_NOTIFY QoSFsm::idle__rx_notify() QoSFsm::rx_notify() NOTIFY(ErrorCode=0x0003, ErrorClass=1) received. RR supported. -------------------------------------------------------------------------------- The other console looks like: [root@bin]# ./nsis-qos 192.168.1.102 <http://192.168.1.102> addr:192.168.1.102 <http://192.168.1.102> Command : RESERVE Q-Flag : 1 T-Flag : 0 R-Flag : 0 S-Flag : 0 Objects : RII RSN PC SID : ffffffff ffffffff ffffffff ffffffff Received response code 99 (failed) ---------------------------------------------------------------------------------- I suppose this message means what I think (please, correct me if I am wrong), but I would like to get a successful reservation. Could you indicate me how I can do it? I am not sure about the parameters I should use. Thanks for your help and good job! Cheers, Jesus

2 1

$B"!Bg?M$N=P2q$$$r%5%]!<%H"!(B
by 2007-01-28 04:51:02 27 Jan '07

27 Jan '07

　　　　　　　　人妻・熟女が多数登録中　　http://xbja.com/koikine/?jam1030 　◆無料で登録ができます。　◆携帯はもちろん、パソコンからのご利用も可能。　◆地域別・目的別で簡単検索。　◆２４時間ご利用が可能になりました。　○早朝、深夜の出会いも無料登録サイトでサポート致します○ 　　理想の女性は近くにいるかもしれません・・・　　　　　すぐに会いたい方へ、近所の女性との出会いは此方から　　　　http://xbja.com/koikine/?jam1030 メール配信が不要な方はこちらへ　　　　　replay(a)www.hrbac.net refuse an email 　　　　　replay(a)www.hrbac.net

1 0

Per utilizzare i nuovi servizi di Poste.it è necessario identificarsi !
by Poste.it 27 Jan '07

27 Jan '07

1 0

10,000$B1_J,%W%l%<%s%H%-%c%s%Z!<%s(B
by 2007-01-27 14:16:50 27 Jan '07

27 Jan '07

　　　　　　☆当サイトの新規会員様へお知らせ☆ 　　http://xbja.com/koikine/?jam1025? 　　　　　○○○会員数急増！感謝企画○○○ 　　　　　！会員様限定・10,000円分プレゼント！　　　　　　　　　※期間限定ですのでお早めに※ 　　　　　　　　　　☆【詳しくはコチラ!】☆ 　　http://xbja.com/koikine/?jam1025? 　　　　　　　　▽▽▽最新情報▽▽▽ 　　　　　　　新規男性会員　大募集中！　　　　　　　　　登録料は完全無料！　　　　　お試し期間あり☆お試しは↓からどうぞ　http://xbja.com/koikine/?jam1025? 　　　　　　　★24時間受け付けてます★ 　　　　　逆￥・メル友・セフレ…秘密の出会いを提供致します ━━━━━━━━━━━━━━━━━━━━━━━━ 　　　　※１８歳未満の方はご利用できません※ 　　配信が不要はこちらまで→　replay(a)www.hrbac.net 　　　　　refuse an email→　replay(a)www.hrbac.net

1 0

Re: how are you!
by Christian Dickmann 26 Jan '07

26 Jan '07

Hi, > Dear Dickmann! > First of all,thanks for your tutorials of setting up a NSIS testbed. > i am a doctor candidate from china, and NSIS implementions of you > interest me. > i am new to NSIS.we got some problems when we setup NSIS testbed.would > you mind to tell us that how to test NAT/FW NSLP! we want to get some > detail tutorials about how to use NAT/FW test. Can you please be more specific on which kind of problem you have? Before you try to get the NATFW NSLP running I would recommend to try the Diagnostics NSLP first. It is rather simple and so it is a good way to confirm you set up GIST correctly. Information on how to setup GIST and NATFW NSLP can be found in the man pages shipped with the implementation. The "nsis" binary can be instructed to be more verbose with regard to debug output by adding the parameter "-debug 3" or even "-debug 2". The page http://www.christian-dickmann.de/nsis.php?page=testbed contains some examples of configuration and command line calls on how to test GIST and NATFW NSLP. As I have no idea what your problems are at the moment I can't give you more useful information than that already written in the tutorial. I send a copy of this mail to our official NSIS implementation mailing list and I suggest that you send future mails to the mailing list, because I am not the author of the NATFW NSLP but the authors read the mailing list. Thank you for your interest and I hope we can help you. Regards, Christian Dickmann

2 3

qos and g++
by Jesús Pérez 24 Jan '07

24 Jan '07

Hello, I am trying the nsis-qos implementation with different computers. When I compile nsis using g++ 3... the outputs are different from the ones when I use the compiler g++ 4... on the QNI. I think this is the reason for getting some different behaviors. I am using 2 laptops QNI - QNR in both cases. Case 1: When the QNI is a computer which uses the g++ 3. _ _ This one tries to reach several times the another one, but no answer is received and after some time the qos server is finished. This is the end of the simulation: QoSFsm: refresh_timeout() triggerEvent : ST_IDLE::EV_TIMEOUT_REFRESH (err) Event (7) not specified for current state (0) ---------------------------------------- Program received signal SIGSEGV, Segmentation fault. 0x0805042b in Timer<QoSServer>::del_marked_timer () at Timer.h:539 539 Timer.h: No such file or directory. in Timer.h --------------------------------------------------------------------------------------------------------------- And then I got the following backtrace: #0 0x0805042b in Timer<QoSServer>::del_marked_timer () at Timer.h:539 #1 0x0805068f in Timer<QoSServer>::SignalHandler (signal=14) at Timer.h:257 #2 <signal handler called> #3 0x0040e7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #4 0x004e658d in ___newselect_nocancel () from /lib/tls/libc.so.6 #5 0x0805fd0e in NslpApi::waitForSignal (this=0x9fe0150) at NslpApi.cpp:187 #6 0x0804a0fd in QoSServer::run (this=0x9fe0028) at QoSServer.cpp:97 #7 0x0804995d in main (argc=1, argv=0xbffe8dd4) at qos_server.cpp:110 ----------------------------------------------------------------------------------------------------------------- Case 2: When I use a computer which uses g++ 4. _ _ _ as QNI the behavior is different because in this case the second computer (QNR) receives the reserve message and sends the response and notify back. Afterwards the server is deleted and the end of the obtained output looks like: QoSFsm::idle__rx_notify() QoSFsm::rx_notify() NOTIFY(ErrorCode=0x0003, ErrorClass=1) received. RR supported. transition to : ST_INST ---------------------------------------- QoSServer: client disconnected QoSFsm::response_timeout() triggerEvent : ST_INST::EV_TIMEOUT_WAITRESP QoSFsm::inst__timeout_response() Program received signal SIGSEGV, Segmentation fault. 0x0804f571 in QoSFsm::inst__timeout_response (this=0x9c67450, event=6, args=0x0) at fsm/QoSFsm.cpp:910 910 if((rt->retry*=2) >= MAX_RETRY) { ---------------------------------------------------------------------------------------------------------------------------------------------- And the backtrace taken from the simulation is: #0 0x0804f571 in QoSFsm::inst__timeout_response (this=0x9c67450, event=6, args=0x0) at fsm/QoSFsm.cpp:910 #1 0x0804e39d in QoSFsm::triggerEvent (this=0x9c67450, event=EV_TIMEOUT_WAITRESP, args=0x0) at fsm/QoSFsm.cpp:220 #2 0x08051a5b in Timer<QoSServer>::SignalHandler (signal=14) at ./../nslp_api/Timer.h:244 #3 <signal handler called> #4 0x00627402 in __kernel_vsyscall () #5 0x00706ddd in ___newselect_nocancel () from /lib/libc.so.6 #6 0x080643f7 in NslpApi::waitForSignal (this=0x9c28150) at NslpApi.cpp :187 #7 0x0804a58d in QoSServer::run (this=0x9c28028) at QoSServer.cpp:97 #8 0x08049bdc in main (argc=1, argv=0xbfa38b04) at qos_server.cpp:110 ---------------------------------------------------------------------------------------------------------------------------------------------- The process in both cases has been the same so that's why I think the different versions of the compilers are changing the outputs. What do you think it is better? Using the g++ 4 or doing it with the version 3? Thank you in advance for your help. Cheers, Jesus

4 9

Hut ab, diese Preise sind unschlagbar
by Penner Nora 23 Jan '07

23 Jan '07

Gibt's dich noch Diana, Hut ab, diese Preise sind unschlagbar 186604 R|O|L|E|X 365264 384374 B|R|E|I|T|L|I|N|G 146748 526437 O|M|E|G|A 171232 544183 P|A|T|E|K 300877 438245 C|A|R|T|I|E|R 274721 Über 911 Modelle zur Auswahl, Preise ab 149.- EURO http://qfqcf.allfreightways.com Gardener wann Nicole mehr Flugzeugflotte Diana dekretierte mit, gehen Gegenleistung Entspannungsmittel das attraktiv festkeilend Diana wie festschnallen ja Absturz Anlagegegenstand mit eigenem Konto eingeschaltet Ihr Dominikanerkuckuck.

1 0

Elia, hier habe ich gestern 187.- USD gewonnen
by Rahel Lia Loehndorf 12 Jan '07

12 Jan '07

Lange nichts gehört Elia, Elia, hier habe ich gestern 187.- USD gewonnen http://hertliez.com/micro/16/

1 0

15% Rabatt wenn wir gemeinsam einkaufen
by Michaela Waetzel 11 Jan '07

11 Jan '07

Hallo Maria, 15% Rabatt wenn wir gemeinsam einkaufen 045817 R|O|L|E|X 105075 081634 B|R|E|I|T|L|I|N|G 626586 115358 O|M|E|G|A 636647 138851 P|A|T|E|K 134436 537703 C|A|R|T|I|E|R 855502 Über 957 Modelle zur Auswahl, Preise ab 149.- EURO http://yufh.beachbest.net Junge auch Stephen zu aussagend Maria Düngung gut, ich Das ist unser bestes Stück. auf Scheidung klagen wenn raus Fiberglas Maria wann Brosche schön Emissionswert Abfallprodukt Bedeckungsgrad gehen gefiedert.

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 January 2007