On Mon, Jun 07, 1999 at 12:23:44AM +1200, Michael Doerner wrote:
> it was already described here under the subject 'connection failure' about a
> week ago and I really thought this will fix my problem .. but it doesn't!
You have a different problem.
> When I use nslookup on the Linux box, the name server on this box auto
> forwards the request to a 'real' name server at my ISP. This request
> triggers a dial out to the ISP. While the modems are negotiating, I can see
> the UDP package waiting when I monitor with 'diald-top'.
But you have dynamic IP address, so these packets have the wrong
IP address. There's no real point in diald buffering these packets,
it might as well drop them unless you have static IP.
> As soon as the modems have done their job and there is a proper connection,
> the UDP package (actually there are 2 in the meantime) are dropped and a
Probably they are sent, not dropped, but they have the wrong source
address so you don't get the answer. Still, they will start the remote
server looking for the IP number ahead of time, so it's not all bad.
> while later, the original 'nslookup' tells me it can't access the name
> server.
It's giving up too soon. Get it to keep
trying/retransmitting. One way is to put duplicate entries
in /etc/resolv.conf (or however it is you configure the
real name server for a forwarding name server).
Or you might be able to get your modem to connect quicker
with AT commands. This is a black art.
When it retries after the link is up it should use the
correct source address. You can check with tcpdump -n
that this is happening.
> The solution for this seems to be setting the variable
> /proc/sys/net/ipv4/ip_dynaddr with ie. 7. I did this 'echo 7 > /proc...' and
> I checked the contents with cat /proc ...
Try 5 and it won't fill up your logs.
> BUT: it does NOT work???
It's only for TCP, not UDP ie it is for the case where your
local name server gets a hit in its cache and doesn't have
to ask the real server.
> There is another diald option '-buffer-packets' which I tried for this but
> it also didn't help. Where is that option for? I don't understand this.
It's for people with static IP. It should probably be documented
that way.
--
Erik Corry [EMAIL PROTECTED] Ceterum censeo, Microsoftem esse delendam!
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
