OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Dan Harnett (danhwzrd.com)
Date: Thu Feb 01 2001 - 18:44:22 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    On Thu, Feb 01, 2001 at 06:16:46PM -0600, Gunnar Wolf wrote:
    > > Anyone know the cause of the following messages in dmesg output ?
    > > arplookup: unable to enter address for w.x.y.z
    > > Box is x86, 2.8, running ipf and ipnat.
    >
    > I get very often similar messages with a setup such as two separate
    > subnetworks coexist on the same Ethernet segment; your machine is looking
    > at the packets that are for it, but cannot understand why an origin
    > address of w.x.y.z is in its wire, when there should only be w.x.v.z
    > there.

    If this is the case, adding a simple static route will avoid any
    further messages. You would also see lower latency times between
    traffic across the two (or more) subnets.

    i.e.

    Say you have a host with the IP address 192.168.1.2 which belongs to
    subnet 192.168.1.0/24. Subnet 192.168.5.0/24 is also on the same
    physical segment.

            route add -net 192.168.5.0 -interface 192.168.1.2

    See route(8) for more info.

    --
    Dan Harnett <danhwzrd.com>