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
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
Am 10.10.2013 10:30, schrieb Adam Carter:
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
server:
# ip route s
default via 10.96.25.129 dev br0
10.96.25.128/25 dev br0 proto kernel scope link src 10.96.25.131
192.168.1.0/24 dev eno2 proto kernel scope link src 192.168.1.201
# !tra
traceroute 172.32.99.12
traceroute to 172.32.99.12 (172.32.99.12), 30 hops max, 60 byte packets
On 10/09/2013 06:50 AM, Stefan G. Weichinger wrote:
Any hints on this?
I need a vacation, btw ;-)
What's on 10.96.25.2?
Am 09.10.2013 14:42, schrieb Michael Orlitzky:
On 10/09/2013 06:50 AM, Stefan G. Weichinger wrote:
Any hints on this?
I need a vacation, btw ;-)
What's on 10.96.25.2?
I don't have any idea ... this out of my scope ... some upstream machine
maintained by someone else.
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
7 matches
Mail list logo
