lkml.org 
[lkml]   [2000]   [Oct]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: PATCH: Linux 2.2.17 not RFC1812 compliant
On Fri, 6 Oct 2000, Mario Lorenz wrote:

> Hi folks,
>
> Linux 2.2.17 (only tested version, I assume all other 2.2 series suffer from
> the same problem and possibly 2.4 as well - but I havent even looked at that).
>
> Assuming a configuration with linuxbox1 eth0 has adresses 192.168.129.1 and
> 192.168.130.1, and IP forward being enabled, and another box on the same
> ethernet with IP 192.168.129.10 and a route to 192.168.130.1 via 192.168.129.1
> (eg that machine doesnt handle multiple logical nets on the same ether very
> well). Now this machine pings eg 192.168.130.10.
>
> The linux box will issue a redirect redirecting to 192.168.130.10, assuming
> that 192.168.129.10 can talk directly to 192.168.130.10. Under RFC 1812
> Rule 5.2.7.2 I think this is illegal (different IP networks...).
>
[SNIPPED...]

You don't have to modify the kernel. You just have to provide the correct
netmasks. The ICMP redirect is proof enough that your netmask on one
or both of the interfaces is incorrect.


Cheers,
Dick Johnson

Penguin : Linux version 2.2.17 on an i686 machine (801.18 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

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