I have installed diald and ip masquerading successfully on
my linux box at home. I also have a Win95 box at home -- both
machines are on a 10bt hub.
The setup works fine (as far as I've tested it so far), but I have
noticed a problem. When I connect to my ISP, I'm given a dynamic IP
address, which in and of itself isn't causing any problems. However,
on the Win95 box (for example), if I enter http://152.2.254.81 in
Netscape, I never get the page to show up.
I believe this is due to the fact that the original TCP request brings
up the link, but is given the _default_ IP address as specified in
the diald.conf. When the link is actually established, I'm given the
_actual_ IP address by my ISP, which the HTTP request can't "switch to".
So, the request inside Netscape times out.
I've noticed, though, that setting up DNS on the Win95 box to my ISP's
nameserver, and then entering the name (and not the IP address) in
Netscape, works ok. This makes sense to me, since the hostname lookup
will establish the link correctly, can recover (being UDP), then the
HTTP request succeeds.
So my question is, is there a way around this problem? Is this just
one of the drawbacks of having a dynamic IP address? Are my first
TCP requests always doomed to fail because of this problem?
Thanks for any help or information.
--kip
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
