On 15-Mar-98 Guy Roelant wrote (concerning Re: ip over linux makes linux crash):
>> Hold on a second. on4ufa.ampr.org is 44.144.0.2 on Ethernet, right ?
> yes indirect.... by encap....
Oh, so you are routing from one netrom port to the next ? No network cable on your
computer ? Doesn't really matter, I am just wondering and trying to understand the
structure of all this. Oh, read that on4ufa is indeed on the Net (dah, that's where
I sent this mail too... Reading really helps...).
>> /sbin/arp -H netrom -s 44.144.90.5 ON4AAK -i nr0
>> This assigns 44.144.90.5 to the netrom port, meaning you are 44.144.0.2 on
>> Ethernet and 44.144.90.5 on Netrom.
> are you sure? the ip nr of the netrom port is 44.144.0.2
> /usr/sbin/nrattach -i 44.144.0.2 nr0
My fault. Didn't notice the different call, meaning hardware-address in this case.
I am too used to 12:34:45:78:90:12 Ethernet MACs...
>> /sbin/route add -host 44.144.90.5 dev nr0
> No,No, 90.5 is the gateway on the other end of the netrom part!
Ok, looks good. Sorry about the confusion. So netrom is point-to-point in this
case ? Man, maybe more complicated than I thought. Hope I don't confuse more then
I help...
>> /sbin/route add -net 44.144.9.0 netmask 255.255.255.0 gw 44.144.90.5
> there are more stations on the other end... an whole class c!!
Ah, so that net is 44.144.9.0 ? Netmask looks ok to me, I hope I remembered right...
Can you do a "arp -an" and mail the results ? Since the 44.144.9.13 can reach
44.144.0.2 but not 44.144.0.1 (right ?) can you also mail a "route -n" from
44.144.0.2 ? I still suspect a TCP packet pile up somewhere. Hm.
Jochen
---