Re: How to ignore arp error message

2003-04-04 Thread Dancho Penev
On Fri, Apr 04, 2003 at 10:04:21AM +1000, Carl Morley wrote:
From: Carl Morley [EMAIL PROTECTED]
To: [EMAIL PROTECTED], 'Dancho Penev' [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: How to ignore arp error message
Date: Fri, 4 Apr 2003 10:04:21 +1000
Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Murphy
Sent: Friday, 4 April 2003 09:52
To: Dancho Penev
Cc: [EMAIL PROTECTED]
Subject: Re: How to ignore arp error message
Dancho Penev [EMAIL PROTECTED] wrote:

On Thu, Apr 03, 2003 at 07:14:24AM +1000, Carl Morley wrote:
From: Carl Morley [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Thu, 3 Apr 2003 07:14:24 +1000
Subject: How to ignore arp error message

arp: 10.1.21.80 moved from 00:03:47:f1:b8:3b to 00:03:47:f1:b8:3a on
fxp2
arp: 10.1.21.80 moved from 00:03:47:f1:b8:3a to 00:03:47:f1:b8:3b on
fxp2
is it possible to ignore these messages?
# sysctl net.link.ether.inet.log_arp_movements=0
Where ISP = blueyonder.co.uk that is a very useful sysctl.

Many Thanks.
John.
Yes I agree!  Thanks to Dancho.  But I am actually having problems
running it; 
sysctl: unknown oid 'net.link.ether.inet.log_arp_movements';

But I suspect that I am due to do a cvsup etc.  Will see what happens
after that!
Sorry I forgot to say that this sysctl variable is for 5.0, I don't know
is it exist in 4.x branch.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
--
Regards,
Dancho Penev
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: How to ignore arp error message

2003-04-03 Thread Dancho Penev
On Thu, Apr 03, 2003 at 07:14:24AM +1000, Carl Morley wrote:
From: Carl Morley [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Thu, 3 Apr 2003 07:14:24 +1000
Subject: How to ignore arp error message
Hi,
I have a server on a network which is inhabited by an Intel rack-mount
box running Win2k.  The Intel server has got two of it's NIC's 'teamed'
- the Intel redundant NIC method.  

Problem is that to the FreeBSD box, it looks like the MAC address of
that IP address keeps changing, so I get endless kernel messages like
the ones below.  You can see the swap from 3a to 3b, and can probably
guess the next in the sequence!  Yeah, back to 3a
arp: 10.1.21.80 moved from 00:03:47:f1:b8:3b to 00:03:47:f1:b8:3a on
fxp2
arp: 10.1.21.80 moved from 00:03:47:f1:b8:3a to 00:03:47:f1:b8:3b on
fxp2
1.  Does anyone know if my fellow admin (who looks after the Intel box)
has configured incorrectly?  Or is this a symptom of all 'teamed' NIC's?
2.  If nothing can be done on the Intel box, is it possible to ignore
these messages?
# sysctl net.link.ether.inet.log_arp_movements=0

Cheers,
Carl.
___

Webize Pty Ltd
ph: (03) 9561 3353
fx: (03) 9561 4583
[EMAIL PROTECTED]
___ 



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


Re: How to ignore arp error message

2003-04-03 Thread John Murphy
Dancho Penev [EMAIL PROTECTED] wrote:

On Thu, Apr 03, 2003 at 07:14:24AM +1000, Carl Morley wrote:
From: Carl Morley [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Thu, 3 Apr 2003 07:14:24 +1000
Subject: How to ignore arp error message

arp: 10.1.21.80 moved from 00:03:47:f1:b8:3b to 00:03:47:f1:b8:3a on fxp2
arp: 10.1.21.80 moved from 00:03:47:f1:b8:3a to 00:03:47:f1:b8:3b on fxp2

is it possible to ignore these messages?

# sysctl net.link.ether.inet.log_arp_movements=0

Where ISP = blueyonder.co.uk that is a very useful sysctl.

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


RE: How to ignore arp error message

2003-04-03 Thread Carl Morley
Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Murphy
Sent: Friday, 4 April 2003 09:52
To: Dancho Penev
Cc: [EMAIL PROTECTED]
Subject: Re: How to ignore arp error message

Dancho Penev [EMAIL PROTECTED] wrote:

On Thu, Apr 03, 2003 at 07:14:24AM +1000, Carl Morley wrote:
From: Carl Morley [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Thu, 3 Apr 2003 07:14:24 +1000
Subject: How to ignore arp error message

arp: 10.1.21.80 moved from 00:03:47:f1:b8:3b to 00:03:47:f1:b8:3a on
fxp2
arp: 10.1.21.80 moved from 00:03:47:f1:b8:3a to 00:03:47:f1:b8:3b on
fxp2

is it possible to ignore these messages?

# sysctl net.link.ether.inet.log_arp_movements=0

Where ISP = blueyonder.co.uk that is a very useful sysctl.

Many Thanks.
John.

Yes I agree!  Thanks to Dancho.  But I am actually having problems
running it; 
sysctl: unknown oid 'net.link.ether.inet.log_arp_movements';


But I suspect that I am due to do a cvsup etc.  Will see what happens
after that!
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]

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


How to ignore arp error message

2003-04-02 Thread Carl Morley
Hi,
I have a server on a network which is inhabited by an Intel rack-mount
box running Win2k.  The Intel server has got two of it's NIC's 'teamed'
- the Intel redundant NIC method.  

Problem is that to the FreeBSD box, it looks like the MAC address of
that IP address keeps changing, so I get endless kernel messages like
the ones below.  You can see the swap from 3a to 3b, and can probably
guess the next in the sequence!  Yeah, back to 3a

arp: 10.1.21.80 moved from 00:03:47:f1:b8:3b to 00:03:47:f1:b8:3a on
fxp2
arp: 10.1.21.80 moved from 00:03:47:f1:b8:3a to 00:03:47:f1:b8:3b on
fxp2

1.  Does anyone know if my fellow admin (who looks after the Intel box)
has configured incorrectly?  Or is this a symptom of all 'teamed' NIC's?
2.  If nothing can be done on the Intel box, is it possible to ignore
these messages?

Cheers,
Carl.

___

Webize Pty Ltd
ph: (03) 9561 3353
fx: (03) 9561 4583
[EMAIL PROTECTED]
___ 
 


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