So close yet so far...
Anybody know why diald doesn't think that ppp0 has come up when it has? As
best as I can tell, diald is waiting for some sort of indication that my PPP
link is up. Otherwise, everything seems OK. It dials when it should, and ppp
is working fine. In fact, until diald kills pppd (reason given: connect
script timed out), packets go out through the link fine.
Initially, I though this was some sort of diald config issue, and maybe it
is, but I'm starting to think that it's more. I think this because I have an
ip-up script defined in diald.conf that never gets called. The ip-up script
that ppp calls when it has come up is working fine. So I'm thinking that the
30 seconds where packets do make it out through ppp0 are actually getting
there without diald being involved at all.
I've tried all manner of config options in both ppp and diald. In ppp I've
had all of the following set or not set in many combinations: defaultroute,
noipdefault, noauth. In diald I've tried reroute and defaultroute in various
combinations. I've also tried having diald invoke the connect script both
with and without the "&" following (background).
PS: does anyone know if I need to keep the SLIP stuff in my kernel if diald
is using ethertap instead of sl0?
Thanks for any and all help,
Brian
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
