Stop this from clogging DMESG

[Dan Nelson]

In the last episode (Apr 02), W. J. Williams said:
> --- Dan Nelson <dnelson at allantgroup.com> wrote:
> > In the last episode (Apr 02), W. J. Williams said:
> > > arp: 192.168.0.2 is on lo0 but got reply from 00:d0:b7:b7:66:eb on fxp1
> > > 
> > > Hi, how do I stop this line from appearing 50,000,000 times per day
> > > in my DMESG output.  I am sure it has something to do with the two
> > > nics I am running on this box.
> > > 
> > > fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> > >         inet 192.168.0.2 netmask 0xfffff800 broadcast 192.168.7.255
> > > fxp1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> > >         inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
> > 
> > You have overlapping networks, for one.  
> > 
> > fxp0's network range is 192.168.0.0 -> 192.168.7.255
> > fxp1's network range is 192.168.1.0 -> 192.168.1.255
> > 
> > The 192.168.1/24 subnet is accessible to both cards, so the fxp1
> > interface is redundant.  Try removing the card completely.
> 
> *********************************************
> 
> this box is in a lab-learning environment...how do I stop and keep both
> cards...should I make range for fxp1 192.168.8.x?

That's probably a good idea.  Also make sure the NICs are not plugged
into the same ethernet segment, since if they are they will see the
same broadcast packets and start complaining about other things.  Use
IP aliases on a single card if you only have one ethernet segment
available.

-- 
	Dan Nelson
	dnelson at allantgroup.com