Les Mikesell wrote:
> Chan Chung Hang Christopher wrote:
>> Christopher Chan wrote:
>>> On Thursday, July 08, 2010 05:09 PM, Kahlil Hodgson wrote:
>>>> On 07/08/2010 05:08 PM, Christopher Chan wrote:
>>>>>> Hmmm ... which bond mode are you using?
>>>>> Why mode 4 of course.
>>>> Ouch. Never used that mode.
>>> Huh? Like why? It's the recommended mode unless the switch does not
>>> suppoprt it or the boards don't.
>>>
>> Oh sorry, got a bit grouchy there. I don't like overtime and was getting
>> tired too. Did not read your mail properly.
>>
>
> I think some bridge or vlan scenarios require promiscuous mode (and the
> corresponding disabling of hardware acceleration). Maybe the real issue is that
> something accidentally disabled it and you now only work when tcpdump
> re-enables it. I'm not sure how this is supposed to be managed atomically when
> multiple programs may manipulate it and it needs to be propagated across
> multiple bonded nics, but maybe something went wrong there. At least some
> things log the change so maybe you can get a hint about when it was turned on
> and off.
>

/me wonders if the loading of the bridge and another related module has
anything to do with this.

I'll prepare a list of targets for rmmod.
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

On Thursday, July 08, 2010 09:40 PM, JohnS wrote:
>
> On Thu, 2010-07-08 at 07:51 -0500, Les Mikesell wrote:
>> I think some bridge or vlan scenarios require promiscuous mode (and the
>> corresponding disabling of hardware acceleration). Maybe the real issue is that
>> something accidentally disabled it and you now only work when tcpdump
>> re-enables it. I'm not sure how this is supposed to be managed atomically when
>> multiple programs may manipulate it and it needs to be propagated across
>> multiple bonded nics, but maybe something went wrong there. At least some
>> things log the change so maybe you can get a hint about when it was turned on
>> and off.
> ---
>
> Check out /proc/net/bonding/bond/YOUR_BOND. Make sure your slave IDs
> are the same as in aggregator ID. If not it will cause the problem your
> having. Bad NIC hardware also it's failing over for a reason as the log
> showed.
>

They check out. What did help besides running tcpdump forever was to do
a 'service network restart'. That made the network behave. I wonder
what's going on...
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

At Fri, 09 Jul 2010 10:30:06 +0800 CentOS mailing list <centos@centos.org> wrote:

>
> On Thursday, July 08, 2010 09:40 PM, JohnS wrote:
> >
> > On Thu, 2010-07-08 at 07:51 -0500, Les Mikesell wrote:
> >> I think some bridge or vlan scenarios require promiscuous mode (and the
> >> corresponding disabling of hardware acceleration). Maybe the real issue is that
> >> something accidentally disabled it and you now only work when tcpdump
> >> re-enables it. I'm not sure how this is supposed to be managed atomically when
> >> multiple programs may manipulate it and it needs to be propagated across
> >> multiple bonded nics, but maybe something went wrong there. At least some
> >> things log the change so maybe you can get a hint about when it was turned on
> >> and off.
> > ---
> >
> > Check out /proc/net/bonding/bond/YOUR_BOND. Make sure your slave IDs
> > are the same as in aggregator ID. If not it will cause the problem your
> > having. Bad NIC hardware also it's failing over for a reason as the log
> > showed.
> >
>
> They check out. What did help besides running tcpdump forever was to do
> a 'service network restart'. That made the network behave. I wonder
> what's going on...

Are there 'services' that the network 'depends' on, but which are are
started *later* then network? Running 'service network restart' as a cure
suggests this. Do you have any special or custom init scripts relating
to your bonding (maybe something that loads special kernel modules or
something like that)?

> _______________________________________________
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
>

--
Robert Heller -- Get the Deepwoods Software FireFox Toolbar!
Deepwoods Software -- Linux Installation and Administration
http://www.deepsoft.com/ -- Web Hosting, with CGI and Database
heller@deepsoft.com -- Contract Programming: C/C++, Tcl/Tk


_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

> Are there 'services' that the network 'depends' on, but which are are
> started *later* then network? Running 'service network restart' as a cure
> suggests this. Do you have any special or custom init scripts relating
> to your bonding (maybe something that loads special kernel modules or
> something like that)?

Hmm, now that you mention it, I highly suspect the qemu/libvirt network
but I have already shot down these two services along with dnsmasq. What
else will setup the 192.168.122.0 space?
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos