Re: [tipc-discussion] TIPC 2.0.0 packets not being transmitted

[Matthew C. <lin...@gm...>]

Hi All,

Did my info reveal anything?  I'm trying to get some middleware built on
these zynq boards and TIPC is a dependency, so I really need it working.
Thanks.

Matt


On Fri, Oct 17, 2014 at 12:54 PM, Matthew Clark <lin...@gm...>
wrote:

> Hi, Jon,
>
> Here's how I configured the zc706's.  And how I'm checking what's going on
>
> # ifconfig eth0 192.168.100.193
> # modprobe tipc
> # tipc-config -netid=1227 -addr=1.1.3 -be=eth:eth0/1.1.0
>
> ---
>
> # ifconfig eth0 192.168.100.194
> # modprobe tipc
> # tipc-config -netid=1227 -addr=1.1.4 -be=eth:eth0/1.1.0
>
> # tipc-config -n
> Neighbors:
> <1.1.3>: down
>
> # tcpdump not port 22
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
> 16:52:45.644933 TIPC v2.0 1.1.4 > 1.1.3, headerlength 40 bytes,
> MessageSize 56 bytes, Link State Protocol internal,
> messageType MCAST_MSG (0x20000000)
> 16:52:45.734227 TIPC v2.0 1.1.3 > 1.1.0, headerlength 40 bytes,
> MessageSize 40 bytes, Neighbor Detection Protocol internal,
> messageType Link request
> 16:52:45.734286 TIPC v2.0 1.1.4 > 1.1.3, headerlength 40 bytes,
> MessageSize 40 bytes, Neighbor Detection Protocol internal,
> messageType Link response
> 16:52:45.864952 TIPC v2.0 1.1.4 > 1.1.0, headerlength 40 bytes,
> MessageSize 40 bytes, Neighbor Detection Protocol internal,
> messageType Link request
>
> # tipc-config -ls
> Link statistics:
> Link <broadcast-link>
>   Window:20 packets
>   RX packets:0 fragments:0/0 bundles:0/0
>   TX packets:0 fragments:0/0 bundles:0/0
>   RX naks:0 defs:0 dups:0
>   TX naks:0 acks:0 dups:0
>   Congestion link:0  Send queue max:0 avg:0
>
> Link <1.1.4:eth0-1.1.3:unknown>
>   DEFUNCT  MTU:1500  Priority:10  Tolerance:1500 ms  Window:50 packets
>   RX packets:0 fragments:0/0 bundles:0/0
>   TX packets:0 fragments:0/0 bundles:0/0
>   TX profile sample:0 packets  average:0 octets
>   0-64:0% -256:0% -1024:0% -4096:0% -16384:0% -32768:0% -66000:0%
>   RX states:0 probes:0 naks:0 defs:0 dups:0
>   TX states:0 probes:0 naks:0 acks:0 dups:0
>   Congestion link:0  Send queue max:0 avg:0
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Fri, Oct 17, 2014 at 11:16 AM, Jon Maloy <jon...@er...>
> wrote:
>
>>
>>
>> > -----Original Message-----
>> > From: Matthew Clark [mailto:lin...@gm...]
>> > Sent: October-17-14 10:31 AM
>> > To: Ying Xue
>> > Cc: tip...@li...
>> > Subject: Re: [tipc-discussion] TIPC 2.0.0 packets not being transmitted
>> >
>> > >
>> > >
>> > > On Thu, Oct 16, 2014 at 9:41 PM, Ying Xue <yin...@wi...>
>> > wrote:
>> > > > I'm trying to get a TIPC cluster using a variety of ARM based
>> > > > processors, but I'm having issues with some zc706 Zynq boards
>> > > > running a Yocto-built kernel 3.14.2. Some see its neighbors perfect
>> > > > well, but the zc706 boards can't be seen by anyone and think
>> > > > everyone else is down. I ran wireshark and from what I can tell, the
>> > > > ZC706 boards simply aren't broadcasting any packets. I see TIPC
>> > > > packets flying around from the overos and zedboard,
>> > > but
>> > > > nothing from the zynqs.
>> > > >
>> > > > Can anyone help me debug this? I'm at a bit of a loss to explain the
>> > > > behavior. Thanks!
>> > > >
>> > > It sounds like a new bug.
>> > > I saw the two important changes were recently made on tipc neighbour
>> > > discovery protocol:
>> > > c82910e2a8d6fc9dd321a1f30dd4e89fb779cfe1 (tipc: clean up neigbor
>> > > discovery message reception)
>> > > 38504c28a201a80d12a6a0f821fecb331cb1f223 (tipc: improve and extend
>> > > media address conversion functions) Can you please confirm whether
>> > > above two patches are merged into 3.14.2 tree?
>> > > If yes, please try to revert them and verify again.
>> > > Regards,
>> > > Ying
>> > >
>> >
>> > Hi, Ying,
>> >
>> > I'm building from the latest meta-xilinx layer for Yocto, which calls
>> in commit
>> >
>> > https://github.com/Xilinx/linux-
>> > xlnx/commit/2b48a8aeea7367359f9eebe55c4a09a05227f32b
>> >
>> > This was committed back in April 25, where the commits you reference
>> > above are dated mid-May.  I checked my discover.c and the changes the
>> > commits above reference are not included.  Should I try them?
>>
>> Those commits were not intended to fix any problems; just to make
>> the code and algorithm  more comprehensible. I doubt it will make any
>> difference.
>>
>> When you have configured the zc706, can you confirm that it actually
>> has the correct address, and that the correct interface(s) is enabled?
>> If so, and everything is correct, you may have to instrument the code
>> and look at what is happening in the discovery logics (discover.c)
>> We can help you out with the latter, if you are positive that the
>> configuraton
>> is ok, and the discovery broadcast actually don't go to the wrong
>> interface.
>>
>> Regards
>> ///jon
>>
>> >
>> > Matt
>> >
>> ------------------------------------------------------------------------------
>> > Comprehensive Server Monitoring with Site24x7.
>> > Monitor 10 servers for $9/Month.
>> > Get alerted through email, SMS, voice calls or mobile push
>> notifications.
>> > Take corrective actions from your mobile device.
>> > http://p.sf.net/sfu/Zoho
>> > _______________________________________________
>> > tipc-discussion mailing list
>> > tip...@li...
>> > https://lists.sourceforge.net/lists/listinfo/tipc-discussion
>>
>
>