Re: connection refused - routing problem?

[Steve Whitehouse <steve@gw.chygwyn.com>]

Hi,

> 
> Since sending this email I have upgraded tcpdump from 3.3 to 3.4 and now the
> tcpdump shows the correct area:
> 
> 15:42:39.746813 endnode-hello endnode vers 2 eco 0 ueco 0 src 1.104 blksize
> 1498 rtr 0.0 hello 0 data 0
> 15:42:53.672175 endnode-hello endnode vers 2 eco 0 ueco 0 src 1.106 blksize
> 1498 rtr 0.0 hello 0 data 0
> 
Ok. This is still not right though.. hello should have some non-zero value
if it was reading the whole message.

> I have added some other hosts to my decnet.conf file:
> 
> node            1.104           name            frey
> node            1.106           name            fulla
> 
> but all hosts still just return socket: connection refused
> 
> Martin
> 
I presume that it takes some time for the message to appear, probably
a few seconds ? If it does that would certainly indicate a routing
problem (I've just taken a look at the code). If it returns straight
away, then its probably not that, but it may still be related to having
more than one ethernet card,

Steve.
-----------------------------------------------------------------------------
To unsubscribe from this list, send a mail to majordomo@dreamtime.org
containing the line "unsubscribe linux-decnet"
-----------------------------------------------------------------------------