Re: Stop this from clogging DMESG

2003-04-04 Thread Luke Hollins
On Wed, 2 Apr 2003, W. J. Williams wrote:

 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.

there is a sysctl to stop it:
net.link.ether.inet.log_arp_wrong_iface: 1
if you set it to 0 it shouldn't print it anymore.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Stop this from clogging DMESG

2003-04-02 Thread W. J. Williams
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=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 192.168.0.2 netmask 0xf800 broadcast 192.168.7.255
inet6 fe80::2d0:b7ff:feb7:66eb%fxp0 prefixlen 64 scopeid 0x1
ether 00:d0:b7:b7:66:eb
media: Ethernet autoselect (100baseTX full-duplex)
status: active
fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255
inet6 fe80::202:b3ff:fe10:e413%fxp1 prefixlen 64 scopeid 0x2
ether 00:02:b3:10:e4:13
media: Ethernet autoselect (100baseTX full-duplex)
status: active
ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500
sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552
faith0: flags=8002BROADCAST,MULTICAST mtu 1500
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
inet 127.0.0.1 netmask 0xff00


=
Will Williams
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Stop this from clogging DMESG

2003-04-02 Thread W. J. Williams

--- Dan Nelson [EMAIL PROTECTED] 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=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
  inet 192.168.0.2 netmask 0xf800 broadcast 192.168.7.255
  fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
  inet 192.168.1.1 netmask 0xff00 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?

=
Will Williams
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Stop this from clogging DMESG

2003-04-02 Thread W. J. Williams

--- Dan Nelson [EMAIL PROTECTED] wrote:
 In the last episode (Apr 02), W. J. Williams said:
  --- Dan Nelson [EMAIL PROTECTED] 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=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 192.168.0.2 netmask 0xf800 broadcast
 192.168.7.255
fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 192.168.1.1 netmask 0xff00 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, thx...yes, I only have one ethernet switch, but i believe it is
capable of handling virtual LANs...should I build VLANS on the switch to
separate the ethernet segments?  I am running 8 pcs and simulating various
things (VPNS, firewalls, etc) .It is a 24-port 3com 3300 switch.  I just
got my gig-e nic running now as well, so will experiment with routing
traffic through it. thoughts?

=
Will Williams
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Stop this from clogging DMESG

2003-04-02 Thread Dan Nelson
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=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
 inet 192.168.0.2 netmask 0xf800 broadcast 192.168.7.255
 fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
 inet 192.168.1.1 netmask 0xff00 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.

-- 
Dan Nelson
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Stop this from clogging DMESG

2003-04-02 Thread Dan Nelson
In the last episode (Apr 02), W. J. Williams said:
 --- Dan Nelson [EMAIL PROTECTED] 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=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
   inet 192.168.0.2 netmask 0xf800 broadcast 192.168.7.255
   fxp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
   inet 192.168.1.1 netmask 0xff00 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
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]