[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IP4 address conservation method
- Subject: IP4 address conservation method
- From: swmike at swm.pp.se (Mikael Abrahamsson)
- Date: Wed, 5 Jun 2013 18:57:51 +0200 (CEST)
- In-reply-to: <CAP-guGX=7n+=7kB5FeteTfkn5rVC3eCNPpsicCaWOuY_w-uGvA@mail.gmail.com>
- References: <[email protected]> <CAP-guGV_VihKzm1b6u29nkT0WL6=QE8=hLOKz4k1pg6UNbrK5g@mail.gmail.com> <[email protected]> <CAP-guGX=7n+=7kB5FeteTfkn5rVC3eCNPpsicCaWOuY_w-uGvA@mail.gmail.com>
On Wed, 5 Jun 2013, William Herrin wrote:
> Nothing. The problem is that the arp source IP doesn't fall within the
> interface netmask at the receiver. Some receivers ignore that... after
> all, why do they care what the source IP is? They only care about the
> source MAC. Other receivers see a spoofed packet and drop it.
Why wouldn't it be within the source IP mask? I would imagine
local-proxy-arp would work exactly the same way as if a directly connected
host with the IP the ARP request was for would have answered.
--
Mikael Abrahamsson email: swmike at swm.pp.se