> Hi all,
>
> We at on4ufa.ampr.org [44.144.0.2] have the following situation:
> We are using ip over netrom to route a part of belgian ampr.org ip
> We are using 2.0.33 + ax25-utils-2.1.42a + ax25-module14e +
> net-tools-1.32alpha
Hi Guy,
I can't help you all the way (I don't know anything about NETROM), but I'll
fire a few shots...
>
>
> following lines in rc.local:
> /sbin/arp -H netrom -s 44.144.90.5 ON4AAK -i nr0
Is this necessary? (I'm not using NETROM, so I can't tell).
> /sbin/route add -host 44.144.90.5 dev nr0
> /sbin/route add -net 44.144.9.0 netmask 255.255.255.0 gw 44.144.90.5
Ehh, wait... Your gateway is not part of the subnetwork? I've never tried
this... Isn't 255.255.0.0 an option as netmask? Or even 255.0.0.0? Then your
gateway is on the subnet as well....Perhaps a look at the routing table might
help here...
> 44.144.9.13 can ping, telnet,ftp,... to 44.144.0.2
Directly? Or is this going through the gateway 44.144.90.5?
>
> but as soons as 44.144.9.13 goes to for example 44.144.0.1 .... on4ufa
> crashes complete!!
> a ping to 44.144.0.1 works but as soons as there is a bit of data.... all
> locks up.
What kind of data? Ping sends data as well...
> The only thing you can do at that moment is switch off the computer...!!!
As I said, I'm not into NETROM, but why would the traffic from
44.144.0.1->44.144.9.13 have anything to do with on4ufa?? I can't think of any
special reason why this would even bother on4ufa. Have I missed something
here? What about their IP routing tables (the 0.1 and 9.13 nodes...)? Are they
using on4ufa as their gateway? Apart from this, on4ufa doesn't seem to have a
route to the 44.144.0.0 network, but that might have been created
automagically somewhere. Again, a look at IP routing tables would help here.
If there is no route to 44.144.0.0, then that certainly seems an error to me.
>
>
> So the crashes only occur when there is data comming in/out via netrom and
> going out via encap on the ethernet!!
>
> Has anyone seen something like this?
> Could the mss value play any part in this??
MaxSegmentSize only applies to TCP connections (telnet, ftp); ping uses ICMP.
The one thing that binds them is the MaxTransferUnit on the interface, since
that applies to all IP traffic.
You might need to tweak that one with ifconfig...
On the other hand, you said the problems started with transport of 'data'. If
you mean using telnet/ftp instead of ping, it could indeed indicate TCP
problems. What happens when you ping large frames between the machines (ping
-s 512 or something like that...)?
>
>
> btw. optimize as router is switched on in the kernel. and always defragment
> is switched on.
>
> I already tried 2.0.31/32 but they had the same problem...
(Sick) You might try 2.0.33...
>
>
> Any assistance would be much appreciated !!!!
>
> 73's the Guy (bfoye.natnivkiqy@mx.dy.fi)
Good luck (btw, great job on your site),
Jan, pa3gyf