On the ipfire router. A quick google turns up commands like: ip route get <IP> and ip route list cache match <IP> and if a redirected route exists, it is labelled that way in the output of such commands.
If this is happening, it will be triggered by any traffic is forwarded to 10.96.25.1. Also, it shouldnt cause any problems. Other than a traceroute output not quite being what you expect, is there any problem? If everything's good dont worry about it (unless your curiosity is piqued). On Thu, Oct 10, 2013 at 5:26 PM, Stefan G. Weichinger <li...@xunil.at>wrote: > Am 10.10.2013 06:45, schrieb Adam Carter: > > There might have been a icmp redirect from 10.96.25.1 telling ipfire that > > there's a better way to get to that network, and its via 10.96.25.2. > > > > On my system it seems to be off by default (I havent set it in > > /etc/sysctl.conf) which makes sense as redirects can be used for MITM > > attacks. > > $ cat /proc/sys/net/ipv4/conf/all/accept_redirects > > 0 > > So I would have to check that on the router? Or both? Just will check > both, sure ... > > Could this lead to mislead keepalive packets from libvirtd? > Maybe I should ask their network-admins for more details ... huge > company, unknown structures ;-) > > Thanks, Stefan > > >
