> Anybody know why diald doesn't think that ppp0 has come up when it has?
Because you've started pppd from your connect script? (which is, as
regular readers know, incorrect)
> As best as I can tell, diald is waiting for some sort of indication
> that my PPP link is up.
No, it is waiting for your connect script to complete so that it
can start pppd.
> In fact, until diald kills pppd (reason given: connect
> script timed out), packets go out through the link fine.
Voila. Your config is bogus. Your connect script should establish a modem
connection *NOT* a network interface.
> [...] I have an
> ip-up script defined in diald.conf that never gets called.
It never gets called because diald is still waiting for your connect
script to finish playing with the modem. i.e. IP is not up.
> 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.
That' right. Er, where *did* you get this set up from?
> I've also tried having diald invoke the connect script both
> with and without the "&" following (background).
Never, *ever* background the connect script!
> PS: does anyone know if I need to keep the SLIP stuff in my
> kernel if diald
> is using ethertap instead of sl0?
Only if you run out of ethertap interfaces for some reason. (There is a
kernel limit of either 8 or 16 I think). If diald can't get an ethertap
interface it will fall back to SLIP.
Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
