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@informatik.uni-goettingen.de [mailto:nsis_imp- bounces@informatik.uni-goettingen.de] On Behalf Of pfer Sent: Thursday, September 07, 2006 8:24 PM To: nsis_imp@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
nsis_imp@informatik.uni-goettingen.de