On Sun, Jun 06, 1999 at 12:56:07PM -0700, Benjamin Diedrich wrote:
>
> I use ip masquerading with a win 95 machine. Sometimes, when using pppd
> by itself, I get the following message, but never with diald:
>
> Jun 6 09:10:19 debian kernel: IP_MASQ:ip_fw_masquerade(): change
> masq.addr from 199.2.132.98 to 199.2.132.135
>
> This suggests to me that the local IP address is updated for pppd alone
> and not diald.
???
Does it work for local clients. Say you do a
telnet 17.254.0.91 80
while the link is down, do you get through to the remote
host (Apple's web server in this case - double Enter will
get you out again)?
It might just be Netscape on Windows not trying for long
enough, and timing out. Diald might be slowing down the
connect a little when compared with pppd (are you using
dial on demand with pppd, or what?).
I wonder how your routing is set up when the link is up.
The interface which the _kernel_ is routing the packets
to should have the new source IP address. If diald is
taking the packets from one interface with a wrong source
address and forwarding them through user space to another
interface, then the kernel will never notice it needs
to renumber. On the other hand in this case I can't see
how it would work at all.
It might help to send the output of
cat /proc/version
ifconfig -a
route -n
when diald has started the interface so I can see what is
happening.
--
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]
