[lkml]   [1999]   [Oct]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRE: IP Masq weirdness
Why does it have to be outside of the ip_masq code?  From what i'm seeing it
seems to be in the masq code itself. That's the only way i would be able to
telnet and use lynx from the linux machine with the proper ip, and yet any
masq'd machines use the wrong ip. Or am i wrong? It seems like the routing
code and such would have to be correct, but that masq is choosing the wrong
external ip, or overriding what the routing code is saying, setting the
masq'd ip to the device ip instead of what the route table says, or i don't

Joseph Gooch

> -----Original Message-----
> From: []
> Sent: Sunday, October 17, 1999 2:43 PM
> To: Juanjo Ciarlante
> Cc:;
> Subject: Re: IP Masq weirdness
> Hello!
> > 2.2.11 adds a sysctl for route cache flushing: [Alexey?]
> No, it was always present, so that it will not help.
> Actually, the only change outside of ip_masq made in 2.2.11 was
> made in ipv4/devinet.c. Try to backout this change and look what
> will occur. If it will help, then it is big puzzle. In this case
> you have to describe your configuration in more details.
> Alexey

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:54    [W:0.049 / U:1.624 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site