[lkml]   [2001]   [Oct]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: how to see manually specified proxy arp entries using "ip neigh"

    > What do you think will happen when a broadcast ARP request for
    > arrives to both eth0 and eth2?

    Nothing. Linuxes attached to the segment even will not notice this.
    Just check and guess why. :-)

    Windows will dump a funny popup saying that someone uses
    their address, but however will continue to work. Probably
    with short periods of service deaths if the router is not a router
    really, but drops everything instead.

    > How can it be done better?

    I permanently remind that the situation when a part of protocol
    is firewalled, and part of it has _no_ firewall hooks does not smell well.
    Proxy arp rules are essentially some underdeveloped private ARP-only
    firewall rules.

    So, if you rely on core facilities, believe to them and do not break
    them with some additional filters.

    If you broke them f.e. announcing a pseudo-router with forwarding
    enabled but dropping everything with a firewall rule, ARP must not
    take care of this. That part of code which drops IP is responsible
    for ARPing being in sync to its rules.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:08    [W:0.021 / U:10.268 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site