On Tue, 16 Mar 1999, Lourdes Jones wrote:
> Did you change the logic for the call to ip in the latest version?
Only to look in /bin and /usr/bin as well as /sbin and /usr/sbin.
> The route command is formatted for ip but the string '/sbin/ip' or even 'ip'
> is never output to the routing command so it is in effect calling
> /sbin/route with the wrong set of arguments.
Which *should* only happen if you have PATH_IP defined as "" in
config.h or path-ip "" in the run time config. This is a bug
though - path_ip == "" should be treated the same as path_ip == NULL.
Setting path-ip "" should cause diald to ignore ip and use route.
Otherwise you have to actually delete ip.
> After the link goes up for the first time, local traffic still does not
> bring up the link. It looks like it may be because you are doing a
> '/sbin/ip route add ...' (which gives an error of 'RTNETLINK error: File
> exists') because tap0 already exists with routing rather than an '/sbin/ip
> route replace' which produces no error at all.
If the route exists it isn't a problem. The problem is that we
annoy the user by letting the error be reported :-).
> [The ifconfig error is 'SIOCSIFMETRIC: Operation not supported' which from
> earlier emails is reported to be harmless.
Harmless as long as you weren't relying on an interface metric
to determine preferred interfaces...
> tap0 is not in point to point mode though which may effect things.]
Not *these* things. But the interface broadcast and p-t-p flags
are no longer changable so any daemon (routed, timed, smbd, nmbd,
xdm etc.) which starts after diald has set up will merrily see
the interface as broadcastable and broadcast away on it unless
firewalled. Again I am told that this is Correct Behaviour
and no one should want different.
> Now there is a default route in place but traffic on the local net does not
> trigger a dialup.
>
> Resolution: manually setting up the same route commands with the replace
> parameter allows local traffic to trigger the link once again.
>
> The critical command is '/sbin/ip route replace 10.0.0.2 dev tap0 scope link
> src 10.0.0.1 metric 0 ' which seems to be retained there after so it diald
> continues to work even after the next dialing.
>
> Hope this make sense, (I've got to get some sleep)
Unfortunately not :-(. Replacing a route with an identical
route shouldn't change anything...
Mike
--
.----------------------------------------------------------------------.
| Mike Jagdis | Internet: [EMAIL PROTECTED] |
| 280, Silverdale Road, Earley, | Voice: +44 118 926 6996 |
| Reading RG6 7NU ENGLAND | Work: +44 118 989 0403 |
`----------------------------------------------------------------------'
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
