Re: connection refused - routing problem?

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

Hi,

> 
> Hi,
> 
> Hoping someone can help with this problem.
> 
> martin ~-> sethost devaxp
> sethost V1.0.3
> Connecting to devaxp
> socket: Connection refused
> 
> Interstingly, when I can proc/net/decnet at the same time it goes from:
> 
> Remote  Source Remote Object Link    Data  Packets Link  Packets
> Node    Port   Port   Number State   Out     In    Out     In
> 
>    0.0  0000   0000          OPEN      1      0      1      0
>    0.0  0000   0000       29 OPEN      1      0      1      0
> 
> to:
> 
> Remote  Source Remote Object Link    Data  Packets Link  Packets
> Node    Port   Port   Number State   Out     In    Out     In
> 
>    0.0  0000   0000          OPEN      1      0      1      0
>    0.0  0000   0000       29 OPEN      1      0      1      0
>  1.187  200E   0000       42   CI      1      0      1      0
> 
Ok. Thats what you'd expect to see as the first step...

> I am running Linux 2.2.14 with dnk2214.tgz patch and dnprogs-2.05.tar.gz. The
> machine has two network cards:
> 
> eth0 a 3com Boomerang 3c905 which is assigned a tcpip address
> eth1 a DEC DC21142 (rev 48) based card (EtherExpress?)
> 
Unless its changed that patch series was only designed to run with
a single network card. Having two in the machine may work but I'm not
sure without digging that patch out.

> I have tried:
> 
> [1] putting eth1 in to promiscuous mode - no good.
> [2] running tcpdump -ieth0 decnet produces:
> 
> tcpdump: SIOCGIFADDR: eth1: Cannot assign requested address
> 
Thats rather odd. If you are having problems getting tcpdump to work
then its better to try Alexey Kuznetsov's version on ftp.inr.ac.ru
as its got a few enhancements over the version that most distributions
seem to ship. 

> [3] running tcpdump -ieth0 decnet does show messages such as:
> 
> 12:50:10.201726 endnode-hello endnode vers 2 eco 0 ueco 0 src 26.516 blksize
> 55813 rtr 0.0 hello 0 data 0
> 12:50:11.072250 endnode-hello endnode vers 2 eco 0 ueco 0 src 26.4 blksize
> 55813 rtr 0.0 hello 0 data 0
> 
That looks ok... I presume that your machines have decnet addresses of
26.516 and 26.4 respectively. The only thing to remember about this is
that tcpdump is broken for decnet (on every version I've ever seen) which
is why evey field after the src address is rubbish in this trace. Its best
to use the -x switch and look at the hex dump directly.

The one thing that I don't see is the "CI" packet though which the previous
/proc/net/decnet listing that you sent had indicated.

> Do I need iproute2?
> 
No. Not for this setup. The routing stuff which uses iproute2 is only
in the latest code in the 2.3.xx series kernels. Even then you won't
need it for your set up (so far as I can tell).

> If so, can anyone suggest what I do with iproute2 to get this working. I cannot
> easily use the eth0 network card.
> 
> Thanks
> 
> Martin

One idea is to try the latest 2.3.xx kernel. The code in these kernels
is much more uptodate than either Eduardo/Patrick's 2.2.xx patch (which
is what you appear to have) or my 2.2.xx patch.

If for some reason you don't want to use the latest version, I'll take
a look though the old code, but I'd suggest that its best to use the
newer code if at all possible,

Steve.

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