I'm using DSL and a local DNS server, and my initial packets don't seem
to be disappearing. My configuration files were posted recently.
Possibly the difference is, I can get my interface up in a second or two,
whereas PPP may need over 30 seconds. If the app. that initiates the
connection has a 30 second timeout for opening the connection, conceivably
it could give up in disgust. Or, the local DNS will certainly time out in
30 secs or less, and may be returning "nonexistent domain" or, more likely,
"server failed", when asked to resolve an outside name.
There may (or may not) be a configuration parameter in DNS that can be
tweaked to lengthen the timeout.
James F. Carter Voice 310 825 2897 FAX 310 206 6673
UCLA-Mathnet; 6115 MSA; 405 Hilgard Ave.; Los Angeles, CA, USA 90095-1555
Internet: [EMAIL PROTECTED] (finger for PGP key)
UUCP:...!{ucsd,ames,ncar,gatech,purdue,rutgers,decvax,uunet}!math.ucla.edu!jimc
On Tue, 6 Jun 2000, Jeff Bamford wrote:
> [This is a repost, the first one had the subject mangled]
>
> I've been trying to get diald to work over a couple of weekends.
> I am able to start a PPP connection manually via "ifup ppp0" and I can get
> diald to start a connection on its own. Where is breaks down is that the
> first packet (i.e. the one that brought up the interface) seems to die.
> This appears in the FAQ as section 6.11 (v1.14 28 January '97), explaining
> that it appears to be related to running local DNS and having a dynamic
> address.
>
> Given that the local DNS is required (ISP has multiple nameservers
> and I need DNS here) and that the dynamic IP is unlikely to change has
> anyone got this combination to work. I can post configuration files if
> required.
>
>
> Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
