This is probably the well-known problem that occurs with dynamic IP address assignment.
The TCP connection that is set up initially uses the IP address that diald knows about.
When the real link is established to your isp, you get allocated a different IP
address,
so the replies to your initial packets, which are sent to your original IP address,
are not recognised as being part of your datastream.
When you retry after the link is up, you are using the new address, and it all works.
Solutions are:
(Best) Get a static IP address, if your ISP will give you one.
(If you can't do that) Try to ensure that the link is brought up by something other
than a
TCP connection. A nameserver lookup will do, so don't run your own nameserver, and
make sure that you are not storing any known addresses.
(What I do) Live with it.
--brian
On Friday, April 30, 1999 4:25 AM, Sanjiv Bawa [SMTP:[EMAIL PROTECTED]] wrote:
> I have diald working. The problem is that when it first dials out in
> response to incoming packets (which are masqueraded) it seems to drop the
> first few packets.
>
> So, if a WinNT machine on the lan sends out a request for a particular web
> page, diald dials fine but the browser will wait for ever or report an
> error
>
> If I hit stop and then retry it when I know the connection is up, it will
> work fine.
>
> How do I fix this ?
>
> Thanks to everyone.
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
