Re: Diald problems ... continued ...
On Saturday 23 Nov 2002 1:47 pm, John Hasler wrote:
> Dave Selby writes:
> > Unfortunately pppds demand dialling doesnt work very well with dynamic IP
> > addresses alloctaion.
>
> It's working fine here.
>
> > It will dial up but then says it cand find the URL, you click OK,
> > re-request the URL while the link is up and it will work fine. This
> > happens every time it dials up.
>
> I think this is happening because the DNS lookup is timing out before the
> connection comes up. It has nothing to do with dynamic IP. I think that
> you will have the same problem with diald. If you don't, please let me
> know: I have the same problem.
Ive done some digging, and found out some info ....
DIALD does indeed have the same problem as discussed, but on the diald
website I found this in the FAQ section ....
******************************************************************
6.11 I'm using dynamic addresses, and the first TCP session over a line
always freezes.
If your IP address is assigned dynamically when the connection comes up, then
any TCP session that brings the link up will still be trying to use the IP
address assigned to your machine by diald before the connection came up. The
TCP protocol does not allow for active TCP sessions that move from one
address to another. This really requires support for some kind of mobile TCP
protocol. Both you and your provider would have to cooperate for this to
work. This problem is not likely to go away in the near future. It would be
much easier to get a static address. As a work around, you should avoid make
TCP connections directly to a known IP address. This means your /etc/hosts
file must not contain the IP addresses of any machines other than your local
machine(s), and you should not be running named in such a way that it can
pick up external addresses (which as near as I can tell means you must not
run named). Also, making a connection by giving a numeric address, e.g.
telnet 123.100.2.1
will fail. The point of this exercise is to bring the diald link up with a
nameserver query rather than a TCP session start. Once the link comes up the
nameserver query will be resolved, and the TCP session will be started with
the correct (dynamically assigned) address.
*************************************************************************
My experience of pppd having this problem was on an old red hat system, which
is why I was trying to get diald going on debian !!
I will now pay my attention to pppd dial on demand for debian !!! it seems
easier to configure, then follow the above ...
Its one BIG LEARNING CURVE !!!
dave
PS if you have any sucsess with the above, please let me know, I will do
likewise.
Reply to: