Re: ebtables mac update

["Покотиленко Костик" <casper@meteor.dp.ua>]

В Срд, 30/06/2010 в 18:54 -0500, Grant Taylor пишет:
> Покотиленко Костик wrote:
> > Funny thing is that the problem persist. Tonight I've made some tests 
> > with 782M. I've connected two computers in my office (win7 and linux) 
> > through this pair directly. I seccessfully tested ping both 
> > directions, then switched them so that each crossed the bridge and 
> > was unable to ping.
> 
> When you switch then, do the Linux and Windows systems know that their 
> network cable has been unplugged?

Yes, because I just switched ethernet cables.

> If they do, they will very likely flush their caches.
> 
> If the problem persists after the Linux and Windows systems flush their 
> cache, I'm strongly thinking that the problem is with the DSL bridges.

In this case, from the Windows and Linux boxes point of view nothing
should change, either they still remembering other's MAC (this case it
will just send unicast direct packet) or not (broadcast ARP is send).

> > Regarding this I can surely tell (this is all about 782M pair) that 
> > after box crossing the bridge MAC-port table is not updating (how it 
> > should be if it were switch's logic). Packets with srcMAC of crossed 
> > box CAN cross the bridge, but with dstMAC of crossed box CANNOT cross 
> > the bridge.
> 
> That really sounds like the something is not forwarding traffic b/c it 
> still thinks that the destination MAC is on the local side.
> 
> Please clarify, when you ran your test, did you try trading sides of the 
> Linux bridge individually or the Linux bridge in combination with the 
> DSL bridge?
> 
> Can you try repeating your test on either side of the Linux bridge?

I repeat, that in this test case with 782M modems I brought them both to
office, connected with 2 meters phone cable, and connected Windows box
to one modem, Linux to other, then switched.

So the scheme was this:

Win --- 782M Server ----- 782M Client --- Linux

and after switch:

Linux --- 782M Server ----- 782M Client --- Win

The fact that problem persisted tells me that the problem is in modems
and not in linux bridge.

-- 
Покотиленко Костик <casper@meteor.dp.ua>