Nsis_Imp September 2006

nsis_imp@informatik.uni-goettingen.de

12 participants
9 discussions

NSIS for end users - It's reality
by Christian Dickmann 30 Sep '06

30 Sep '06

Hi, the NSIS team of the University of Goettingen is proud to announce the release of a new development version of our NSIS package, which offers a lot of new features. We now support Traffic Control (tc) on Linux to really reserve resources and allow the integration of NSIS/QoS into applications by offering a QoS NSLP API. This development version also comes with a lot of bugfixes and updates to new draft versions of GIST and QoS NSLP. However, the most exciting new feature is the support for Windows XP and OpenWRT[1]! The Windows XP version is a demonstration prototype, which is able to detect the UDP port used by Skype[2] and trigger the local QoS NSLP daemon to request resources for phone calls. In addition, we support OpenWRT, which is a Linux distribution for embedded devices, i.e. broadband Wireless LAN / DSL routers. On a lot of such routers, like the Linksys WRT54G (see the OpenWRT homepage[1] for a list of supported hardware), OpenWRT can be installed as an alternative firmware. All new features combined, NSIS usage in SOHO networks becomes reality! The Windows machine triggers the request and the DSL router reserves the resources by the use of the Traffic Control tool. You can find the development versions for all platforms of the NSIS package on our beta version page. The ChangeLog which lists all changes is also available on that page. Please see the individual README files on how to use the packages. 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. Christian Dickmann On behalf of University of Goettingen NSIS team [1] OpenWRT: http://www.openwrt.org [2] Skype: http://www.skype.com

4 3

Few issues in NATFW NSLP
by Dinesh Gurnani 28 Sep '06

28 Sep '06

Hi, I am using the current version 0.4.0 of NSIS for my undergraduate project. I am using the following network configuration. Host1 ----------------- Firewall ----------------------- Host2 IP Addresses: Host1 = 10.0.0.3 Firewall = 10.0.0.2 , 10.0.1.2 Host2 = 10.0.1.2 Following are few issues which I observed: 1. When I give the command "nsis-natfw --create -s 10.0.0.3 -d 10.0.1.3 --deny --debug=0" from the Host1, there is an error message on the firewall "iptables: No chain/target/match by that name". I observed that the function initNatFwChains() is not being called anywhere. At one place where it is called, the line is commented out. 2. When I uncommented this line and compiled the code again, the create command worked but whether I give "--allow" or "--deny", it always establishes and ACCEPT rule in the the iptables and no DROP rule as it should for "--deny" case. 3. This create session did not expire after default lifetime of 600 s. 4. I am not receiving any output in response to the above mentioned CREATE command. The command executes but no output is given. Are these bugs in the code or am I missing something ? Any help will be appreciated. Best Regards, Dinesh

2 1

NSIS integration with traffic generator
by Satheesh Babu 19 Sep '06

19 Sep '06

Hi, I am planning to integrate NSIS with a UDP/TCP traffice generator. The traffic generator basically has a sender and a receiver and generates traffic based on the user specification with various TCP/UDP options. I would now like to integrate this generator with NSIS, NSLP QoS. The idea is to reserve enough bandwidth in the routers for my traffic and generate the traffic. In order to do so, which NSLP QoS API should I use in my generator code? And is there any API documentation that details the methods that should be used? If this is not possible, is there any other way? Thank you, Sateesh

3 3

questions about routing in NTLP
by 斌斌王 18 Sep '06

18 Sep '06

Hi all ! I have some questions about routing in NTLP. As we know there are two major functions in NTLP: (1) Routing. (2) Transport. I have read the implementation code of nsis-0.4.0. And I know that the function of "Transport" is implementd by the GistMAEntry class, which uses the socket classes provided in ../library/socket. however, I have been very confused on the "Routing" function. I don't know how it is being realized. And I realized there are many library files in ..\library\libxorp. Further more, I don't understand this words " Incoming messages are fetched from the socket by callbacks called by XORP(socket_events.cpp) ". What is the role of XORP as it here? how does XORP and GIST work together? I am looking forward someone can reply to my questions. Thank u very much! Bestwishes! Sky Wang 2006-9-18 -- journey

2 1

[Fwd: Re: [Caspdev] Re: GIST and QoS NSLP code]
by Bernd Schloer 12 Sep '06

12 Sep '06

-------- Original Message -------- Subject: Re: [Caspdev] Re: GIST and QoS NSLP code Date: Tue, 12 Sep 2006 16:47:09 +0200 From: Bernd Schloer <bschloer(a)cs.uni-goettingen.de> To: Kappler, Cornelia <cornelia.kappler(a)siemens.com>, Norocel Munteanu <norocel.munteanu(a)encom-consult.com> CC: Xiaoming Fu <fu(a)cs.uni-goettingen.de> References: <DAA882AD01598448BB6FAB8C4D96F9DB027ABD52(a)blns00fa.ww002.siemens.net> <45067AFA.8020604(a)cs.uni-goettingen.de> Hello Cornelia and Norocel, questions are welcome, directly or over the mailing list. I'm very interested in the interoperability tests between the QoS NSLPs. Currently in our implementation QoS NSLP draft 11 and QSPEC object support of draft 11 are implemented. QSPEC processing is still limited. Basic resource reservation with TC is possible. Please find the latest development snapshot here: http://user.informatik.uni-goettingen.de/~bschloer/nsis-0.4.1-dev-2006-09-1… Bernd Xiaoming Fu wrote: > Hi Cornelia, > > Great you're developing NSIS programs too. I think the most efficient > way is to communicate through the mailing list: > http://user.informatik.uni-goettingen.de/~nsis/help.html > Our folks should be available to answer any type of our GIST/NSIS > implementation related questions. > > Best regards, > Xiaoming > > Kappler, Cornelia wrote: > >> Hi Xiaoming, >> >> as you know at Siemens we are also developing a QoS NSLP code, >> together with the company Encom Consult. Our code runs over your GIST >> (as well as over the Roke GIST), and they are testing interoperability >> with your QoS NSLP. In these tests a number of questions came up >> concerning details of the interfacing. Could Norocel and his group at >> Encom contact you directly? >> >> Cheers, Cornelia >> > _______________________________________________ > Caspdev mailing list > Caspdev(a)informatik.uni-goettingen.de > https://user.informatik.uni-goettingen.de/mailman/listinfo/caspdev

1 0

question about QSPEC
by Filippo Cacace 12 Sep '06

12 Sep '06

Hi, I am a researcher at the Universita' Campus Bio-Medico of Rome. We are developing a test-bed for QoS support on wireless access network. The basic idea is to have a mobility manager on mobile stations that sends QoS request to a control entity of the Wireless AN. The QoS information is used by the control entity to set 802.11e (802.11 + QoS support) parameters and decide to which sending queue each flow belongs. QoS NSLP is just the tool we needed to send QoS reservation on the Wireless AN, so we are very glad that an open source implementation already exists. However, the man page for nsis-qosd, in the section KNOWN BUGS, reports that the QSPEC support is still missing. I would like to ask whether you are planning to implement it soon, or otherwise if you have any hint/suggestion to implement it. Thank you in advance, Filippo Cacace

2 1

dual reception problem - solved
by pfer 08 Sep '06

08 Sep '06

Hello there! Thanks for the answers, it works now. It was a bit unclear to me that having 1 instance of GIST and 1 instance of my NSLP code needs 2 api-s for different nslp-ids, but only for reception. As I believe it now, you wrote GIST mainly with having 1 nslp-id per NSLP-application code in mind. What it needed was two separate api instances, with same callbacks registered, but different nslp-ids. Then I issue 2 api->waitforsignal calls (for both pointers), and receive messages correctly with both nslp-ids. However, I use only one api for the sendmessage call, I just alter the nslp-id of the message. This is not nice , but it just works. So finally, I believe this is the way. Thanks again, Ferenc __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

RE: [Nsis_imp] rmd dual reception
by Christian Dickmann 07 Sep '06

07 Sep '06

As I understand it, you try to use the SAME NslpApi object and regsiter it for two NSLP IDs. As I understand my code, you should get a GistException saying "This socket already registered for a diffrent NSLP ID". Don't you get this one? 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 pfer > Sent: Thursday, September 07, 2006 8:24 PM > To: nsis_imp(a)informatik.uni-goettingen.de > Subject: [Nsis_imp] rmd dual reception > > Hello all! > > I've got a little problem here, and I do not know the > reason. > > It's about message reception. > > My topology: > > A-B-C > > A is RMD-Ingress > B is RMD-Core > C is RMD-Egress > (modified QoS-NSLPs running everywhere above GIST) > > A does dual message sending: sends a reserve to C with > > C-mode on, and another reserve to C with D-mode on. > (using ip-of-A and ip-of-C in mri) > > B registers only for NSLP-ID 4 (intra-domain), while > C registers for both 4 and 6 ids, to get both > intra-domain A-B-C and A-C edge2edge only messages. > > Problem is, C only receives edge2edge message, but not > the intra-domain one. > This only occurs if C registers to GIST with both > NSLP-IDs. If I register only either 4 or 6, it gets > the appropriate edge2edge or intra-domain reserve > fine. > (but just one of course). > > GIST transmission is fine, I used debug mode on node > C, > which showed both API-Call Resvmsg-s, with the correct > NSLP-ids. > > I suspect the problem might be either with select() in > waitforsignal() (perhaps receiving messages with a too > short delay??) > or > the way I registered the two NSLP-ids. > > I did not alter much of NslpAPI.cpp, so my guess is > the latter. > > Please see the attached text file for a small code > snippit I use. > > Thanks for the help in advance, > > Ferenc Pintér > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com

1 0

rmd dual reception
by pfer 07 Sep '06

07 Sep '06

Hello all! I've got a little problem here, and I do not know the reason. It's about message reception. My topology: A-B-C A is RMD-Ingress B is RMD-Core C is RMD-Egress (modified QoS-NSLPs running everywhere above GIST) A does dual message sending: sends a reserve to C with C-mode on, and another reserve to C with D-mode on. (using ip-of-A and ip-of-C in mri) B registers only for NSLP-ID 4 (intra-domain), while C registers for both 4 and 6 ids, to get both intra-domain A-B-C and A-C edge2edge only messages. Problem is, C only receives edge2edge message, but not the intra-domain one. This only occurs if C registers to GIST with both NSLP-IDs. If I register only either 4 or 6, it gets the appropriate edge2edge or intra-domain reserve fine. (but just one of course). GIST transmission is fine, I used debug mode on node C, which showed both API-Call Resvmsg-s, with the correct NSLP-ids. I suspect the problem might be either with select() in waitforsignal() (perhaps receiving messages with a too short delay??) or the way I registered the two NSLP-ids. I did not alter much of NslpAPI.cpp, so my guess is the latter. Please see the attached text file for a small code snippit I use. Thanks for the help in advance, Ferenc Pintér __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com void API_Module::Run() { apiCallback = new NslpApiCallback<API_Module>(); apiCallback->SetCallback(this, &API_Module::RecvMessage, &API_Module::MessageStatus, &API_Module::NetworkNotification); api = new NslpApi(); api->register_nslpid(CORE_NSLP_ID); api->connectToGist(apiCallback); #if RMD if(TheParams.TheNodeType == BorderNode) { // api = new NslpApi(); api->register_nslpid(EDGE_NSLP_ID); api->connectToGist(apiCallback); } #endif while(true) { //here comes my main event-handling loop ... } ... }

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nsis_Imp September 2006