Re: [Linux-decnet-user] DECnet routing

[Steven W. <st...@ch...>]

Hi,

On Fri, Oct 06, 2006 at 01:26:04PM -0400, Alan Kemmerer wrote:
> Hi,
> 	My last message was premature. The problem is not the packet size.
> It is in the routing code. 
> I need to get the routing code working correctly for our network. 
> Since it is segmented by L1 routes 
> What I need to do is have the endnode populate its neighbors from the hello
> messages.
> If the destination is not on the local segment, send the packet to the L1
> Router
> Or if the packets source is the L1 Router send the reply to the L1 router
> and not the destination.
> 
> Below is the tcpdump of a ping from 1.43(VMS) to 1.99(linux)
> from linux.
> 
> 1.99 is on a segment by itself with the router 1.405
> 
> 1.43 is on a different segment with router 1.405
>
Would it be possible for you to do the tcpdump again, but with the -e
flag so that we get the link layer headers too? Also if you could send
the content of /proc/net/decnet_neigh it would be very helpful. If the
router doesn't appear there, then that would explain the problem.

Since the endnode hello you included doesn't include the router it
would appear that this is the reason for the routing problem.

Since the router hello is multicasted, the things to check are
that Linux is listening on the correct address and that your network
card is set up to receive multicast. The command 

/sbin/ip link ls

will tell you that and

/sbin/ip maddr ls

well tell you if its listening to the correct multicast address. You
could also try /sbin/ip link set eth0 promisc on    just to see if it
makes any difference. It will take a few seconds for Linux to pick
up the router in any case,

Steve.