Per Baekgaard wrote:
> I've now come a bit further with my problem in getting diald 0.99.4 to work
> on a RH 6.2 system (kernel 2.2.14) and pppd 2.3.11 (in part thanks to
> Mark Johson).
>
> The problem seems to be that when I start up diald with a defaultroute
> (which is what I need in order to get the autodial to my ISP to work),
> a line is added to the route table like this:
>
> 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 tap0
Try this:
0. undo your fix to sys-linux.c
1. use
remote 192.168.0.102
local 192.168.0.101
in diald.conf
2. /etc/rc.d/init.d/diald restart; route add default gw 192.168.0.102
BTW -- two more issues: I get a double line in my routing table; apparently
> both pppd and diald inserts a line for the ppp0 connection... and I keep
> getting errors about SIOCSIFMETRIC not supported on my tap0 and ppp0 sockets.
> Any hints to this also greatly appreciated.
>
> -- Per.
>
Assuming you've done as suggested above, look at flags via 'ifconfig tap0'; isn't
one entry for a host, another for a network, a third for the gateway? Although
(the network entry is) perhaps redundant, no harm done.
I believe I saw a response by Mike Jagdis in a list archive stating that support
for SIOCSIFMETRIC is in the 2.0 kernels, but not those y.x <> 2.0. I believe the
metric is used for usage accounting by packet.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
