Hi Allan, 
Thanks for the reply,
I have got the name table entry when this issue was seen. here it is 
root> tipc-config -nt |grep 1.1.5
553707482  10240            10240           <1.1.5:2228833412>         
2228833413
                                                          <1.1.5:520270085>     
     520270086
                  655370          655370         <1.1.5:2219147253>         
2219147254
                                                          <1.1.5:520257525>     
     520257526
                  2181056512    2181056512  <1.1.9:2560015065>         
2560015067
                  10240            10240           <1.1.5:2227425003>         
2227425004
                                                          <1.1.5:520257378>     
     520257379
                  10240            10240           <1.1.5:2227424980>         
2227424981
                                                           <1.1.5:520257358>    
      520257359
It seems that both ports :  1f02 7ff5 -------------- 520257525
                                       8445 7ff5  ------------ 2219147253
are availabe in the name table, what I understand (please correct me if I am 
wrong) is these are not multicast messages.
It seems that some times previous port values are retained even after 
re-starting tipc application.
I am not sure if this could happen.
Thanks
Jitendra

----- Original Message ----
From: "Stephens, Allan" <[EMAIL PROTECTED]>
To: jitendra kolhe <[EMAIL PROTECTED]>; tipc-discussion@lists.sourceforge.net
Sent: Monday, September 17, 2007 9:50:05 AM
Subject: RE: [tipc-discussion] TIPC Messages are Sometimes beingmis-directed to 
the wrong TIPC destport


Hi there:

On initial inspection, I can't see a clear indication of a problem.  The
two messages you dumped both appear to be valid connectionless messages
that are being sent to TIPC port name {285213679, 655370}; the first
message has been mapped to port ID <1.1.5:520257525>, while the second
was mapped to <1.1.5:221914753>.

This sort of multiple mapping will happen in TIPC if you have bound the
same TIPC name to two or more sockets; TIPC will distribute the traffic
between the destination ports on a round-robin basis.  However, the fact
that the two destination port reference values are identical in their
lower 16 bits (i.e. xxxx7ff5) makes me suspect that the upper 16 bits of
the destination port field of the message header have become corrupted
somehow.

So my advice to you is: a) print out TIPC's name table to ensure that
you don't have multiple instances of the TIPC port name you're trying to
send to, then b) upgrade your setup to use TIPC 1.5.12 to see if that
makes any difference.  (The TIPC change history doesn't indicate that
any fixes were made that would address your problem, but it's normally a
good idea to run the latest version of TIPC just to be safe.)

Regards,
Al 

> -----Original Message-----
> From: jitendra kolhe [mailto:[EMAIL PROTECTED] 
> Sent: Friday, September 14, 2007 5:49 PM
> To: Stephens, Allan; tipc-discussion@lists.sourceforge.net
> Subject: Re: [tipc-discussion] TIPC Messages are Sometimes 
> beingmis-directed to the wrong TIPC destport
> 
> Hi thanks, for the reply.
> Here are the details..
> 
>     * your version of TIPC : tipc-1.5.10
>     * your hardware platform: PPC Architecture
>     * your operating system: Kernel - 2.6.10
> 
> Thanks,
> Jitendra
> 
> ----- Original Message ----
> From: "Stephens, Allan" <[EMAIL PROTECTED]>
> To: jitendra kolhe <[EMAIL PROTECTED]>; 
> tipc-discussion@lists.sourceforge.net
> Sent: Friday, September 14, 2007 5:35:30 PM
> Subject: RE: [tipc-discussion] TIPC Messages are Sometimes 
> beingmis-directed to the wrong TIPC destport
> 
> 
> Hi there:
> 
> Can you please provide a bit more information about your setup,
> specifically:
> 
>     * your version of TIPC (eg. TIPC 1.5.9)
>     * your hardware platform (eg. Pentium 3)
>     * your operating system (eg. Linux running Fedora Core 3 
> with kernel version 2.6.11)
> 
> This info will make it easier to identify the cause of your problem.
> 
> Regards,
> Al 
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of 
> > jitendra kolhe
> > Sent: Friday, September 14, 2007 4:00 PM
> > To: tipc-discussion@lists.sourceforge.net
> > Subject: Re: [tipc-discussion] TIPC Messages are Sometimes 
> > beingmis-directed to the wrong TIPC destport
> > 
> > Hi all,
> > 
> > I am verynew to TIPC, I had been thru user-guide but I am 
> not sure if 
> > this is a TIPC KLM, issue or some user application that 
> uses TIPC. We 
> > sometimes see TIPC packets are being mis-directed to wrong 
> dest port.
> > Can anyone help us to Identify the issue out here.
> > 
> > Here is a hex dump of TIPC messages.
> > Correct Message,
> >         0x0000:  4148 0316 4008 0000 10f1 110a 0100 1001 
> > [EMAIL PROTECTED]
> >         0x0010:  e4d3 ab8c 1f02 7ff5 0100 1001 0100 1005 
> > ................
> >         0x0020:  1100 03ef 000a 000a 0100 1001 e4d3 ab27 
> > ...............'
> >         0x0030:  ffff ffff ffff ffff 0000 0000 0000 1acf 
> > ................
> >         0x0040:  ffff ffff ffff ffff ffff ffff ffff ffff 
> > ................
> >         0x0050:  ffff    
> > The destport here is HEX 1f02 7ff5 which translates to TIPC 
> > destport=520257525.
> > Incorrect Message
> >         0x0000:  4148 0316 4008 0000 10f7 1111 0100 1001 
> > [EMAIL PROTECTED]
> >         0x0010:  e4d3 ab8c 8445 7ff5 0100 1001 0100 1005 
> > .....E..........
> >         0x0020:  1100 03ef 000a 000a 0100 1001 e4d3 ab27 
> > ...............'
> >         0x0030:  ffff ffff ffff ffff 0000 0000 0000 1ad6 
> > ................
> >         0x0040:  ffff ffff ffff ffff ffff ffff ffff ffff 
> > ................
> >         0x0050:  ffff     
> > which has a destport of HEX 8445 7ff5, which translates to TIPC 
> > destport=2219147253.
> > Thanks
> > 
> > 
> >        
> > ______________________________________________________________
> > ______________________
> > Got a little couch potato? 
> > Check out fun summer activities for kids.
> > http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activit
> > ies+for+kids&cs=bz
> > 
> > --------------------------------------------------------------
> > -----------
> > This SF.net email is sponsored by: Microsoft Defy all challenges. 
> > Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > tipc-discussion mailing list
> > tipc-discussion@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/tipc-discussion
> >
> 
> 
>        
> ______________________________________________________________
> ______________________
> Building a website is a piece of cake. Yahoo! Small Business 
> gives you all the tools to get online.
> http://smallbusiness.yahoo.com/webhosting 
>


       
____________________________________________________________________________________
Yahoo! oneSearch: Finally, mobile search 
that gives answers, not web links. 
http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tipc-discussion

Reply via email to