On Thu, 11 Mar 1999, Derek Scherger wrote:
> The first is around item 6.11 in diald-faq.txt which reads "I'm using
> dynamic addresses, and the first TCP session over a line always
> freezes." The "solution" described there seems somewhat incomplete. It
> sounds to me like the "real" solution to this problem is the kernel's
> ip_dynaddr stuff. See ip_dynaddr.txt in linux/Documentation/networking.
> Shouldn't echo 1 > /proc/sys/net/ipv4/ip_dynaddr fix this problem?
> Unfortunately I have not been able to get it to work. If telnet traffic
> brings the line up the first few packets have 0.0.0.0 as the address,
> once the dynamic address has been established, future packets do seem to
> have the right address in them, but telnet is still not able to connect.
> What's up doc?
I've seen something similar on ippp connections. Do you have
"ip" installed (from ftp.inr.ac.ru:/ip-routing/). Diald will
use it if it can and using it can force the source address
to be used on a route which appears to work around the problem.
> My second problem is related to routing and the use of ethertap
> interfaces with diald. Once I have my diald's up and running on tap0,
> tap1 and tap2 I set up the appropriate routes to each interface and all
> is great.
Are you doing that *outside* diald?
> Traffic is routed to the proper interface, diald brings up the
> link, the interface changes to ppp0, yahoo! The problem comes in after
> the link is shut down. The ppp0 interface is removed and the specific
> routes for that ISP go with it (i.e. they disappear). Should this
> happen? One fix I guess is to re-add the routes in my ip-down.diald
> script but I'm not sure this should be required.
If you add routes outside diald bad things happen. When the ppp
interface goes down there is no target interface for the routes
so they disappear as well (it doesn't happen when the interface
comes up because the ppp interface is set up *before* diald pulls
the addresses from the proxy so there is still somewhere for the
routes to point. We don't leave the proxy live anymore because,
apparently, changing the addresses is Right(tm) and changing
routes is Wrong(tm) - especially if there is a routing daemon
around).
Anyway, if you want to have specific routes through a diald
managed interface you should use the addroute and delroute script
options. Diald will call them at the appropriate times, telling
them the current interface and IP addresses to use.
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]
