From: Robert A Jenkins (terhi.victor@logonet.com)
Date: Sat Mar 04 2000 - 14:37:33 EET
Hi,
Problem: I delete my default 44.0.0.0 route or change it to a different
gateway machine, and the machine can no longer connect to it's own services!
Details:-
My main Linux box 'router' (using RH5.2 + ax25-utils-2.1.42a) has been
running fine for ages. This machine also runs a convers server, which can be
connected to either by the conv command from the Node, or externally via
Netrom as 'nnconv'.
I have recently set up am internet gateway on another machine ('gate' with
RH6.0 using kernel ipip & tunl0). I have just got the full Gateways route
list added to this setup today, and everything works fine from this
machine...
To allow local users to access the new 44.xxxx routes, I need to change (on
'router') the default 44.0.0.0 route to use 'gate' as a gateway. That route
is currently set via a radio link to another system (which is off air at the
moment anyway).
As soon as I make any changes to the 44.0.0.0 net route, I get 'no route to
host' when trying to connect to the convers server! Nor can I ping 'router'
from it's own console.
The kernel IP address is 44.131.57.214, all radio ports are using
44.131.57.225 (There are three ethernet interfaces on 214, 215 & 216 with
'gate' [57.213] on 216).
There is no visible route to 44.131.57.225, but it can not be actually using
the existing net route via ax0 as there is no system on the other end of
that link!
If I add a route to 44.131.57.225 using 'lo' as the interface, I can then
ping it, but it still won't connect to the convers server - axconv gives a
'broken pipe' error.
Any ideas appreciated!
Regards,
Tony Jenkins, g8tbf.
mailto:pcgl@america-net.com.br
This archive was generated by hypermail 2b29 : Sat Mar 04 2000 - 14:38:05 EET