On 02/03/15 17:56, Jarmo Hurri wrote:
Ed Greshko <ed.greshko(a)greshko.com> writes:
> echo 0 > /proc/sys/net/ipv4/conf/all/accept_redirects
>
> and make sure you get
>
> cat /proc/sys/net/ipv4/conf/all/accept_source_route
> 0
That didn't help, because for some (weird?) reason after setting
accept_redirects=0 for all, my system still had accept_redirects=1 for
em1. However, setting accept_redirects=0 for em1 seems to have helped,
at least in a short test. So thanks a bunch!
An IP redirect is sent by a (typically) router when it determines that a packet it has
received would be better routed by an alternate path and it informs the source by sending
it an ICMP redirect. In this case, it would seem your system received a redirect telling
your system that 91.198.174.192 is directly connected to em1.
I would use wireshark to try and trap ICMP messages looking for the source of the
redirects.
Can you explain what is happening here? I am assuming that Windows
has
this configured suitably in the first place, and that is why I am seeing
the issue in Linux only.
I don't know anything about Windows and what they do. Sorry.
--
If you can't laugh at yourself, others will gladly oblige.