Thank you I'll try testing it on FreeBSD / NetBSD / OpenBSD when I have
a moment.
The Dell - RHEL - Broadcom/Intel crew have something similar to bonding
called "NIC Team"; but I'm pretty sure its proprietary (not 802.3ad)
http://www.dell.com/content/topics/global.aspx/power/en/ps1q03_bhutani?c=u
I have submitted patch #1712645, which prints something more useful and prints
it only once.
Jan
On Fri, 2007-05-04 at 09:53 +0200, Jan Safranek wrote:
> [I am sorry for not sending cc: to the list]
>
> On Thu, 2007-05-03 at 10:44 -0400, Brian A. Seklecki wrote:
> > I've never used the bonding
[I am sorry for not sending cc: to the list]
On Thu, 2007-05-03 at 10:44 -0400, Brian A. Seklecki wrote:
> I've never used the bonding feature in RHEL described here; but I've
> used Cisco IOS EthernetChannel, FreeBSD Netgraph, OpenBSD trunk(4); --
> all 802.3ad + LACP compliant.
>
> They all use
got it. bug 1693039
thanks.
MV
Thomas Anders wrote:
> Mike Varley schrieb:
>
>> I just ran into a problem with this functionality: the ipAddressTable
>> (in the ip-mib code) leaked memory; this is because the table did not
>> allow duplicate IP addresses.
>>
>> I believe the ip-mib is using t
I will do a search and see if anything turns up. Before I began my
investigation, I did a search to see if any bugs like this had been
fixed; since we are using 5.3 and the current is 5.4!
Anyhow, no bugs turned up, then I looked at the 5.4 source and it seems
the errors are still present.
Tha
> Unfortunately it's quite common to have one IP shared among more
> interfaces - e.g. in PPTP server.
This is a proxy-arp config? Are we talking about an embedded platform
here?
> The same applies to situation, where
> there are more interfaces without IP address (e.g. when channel bonding
>
Mike Varley schrieb:
> I just ran into a problem with this functionality: the ipAddressTable
> (in the ip-mib code) leaked memory; this is because the table did not
> allow duplicate IP addresses.
>
> I believe the ip-mib is using the ip-addresses as indexes into the
> table, therefore it is a
Hi Jan,
I just ran into a problem with this functionality: the ipAddressTable
(in the ip-mib code) leaked memory; this is because the table did not
allow duplicate IP addresses.
I believe the ip-mib is using the ip-addresses as indexes into the
table, therefore it is a limitation of the MIB to
Greetings,
is it possible for SNMP to handle multiple interfaces with the same IPv4
address? Net-snmp (5.4) throws error messages to log:
$ ifconfig eth1 192.168.100.1 up
$ ifconfig eth2 192.168.100.1 up
$ /etc/init.d/snmpd start
$ tail /var/log/messages
error on subcontainer 'ia_addr' insert (-
