Re: ebtables mac update

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

В Чтв, 01/07/2010 в 11:10 -0500, Grant Taylor пишет:
> On 07/01/10 04:08, ðÏËÏÔÉÌÅÎËÏ ëÏÓÔÉË wrote:
> > Yes, because I just switched ethernet cables.
> 
> Ok.
> 
> > 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).
> 
> Agreed.
> 
> > The fact that problem persisted tells me that the problem is in modems 
> > and not in linux bridge.
> 
> Agreed.
> 
> Will you try one more step after you re-run the test?  Namely, when the 
> boxen can't ping each other, try rebooting one or both of the modems and 
> see if the problem continues after doing so.

I've done this in production enviroment (with linux bridge involved) as
well as in test enviroment (just 2 modems and 2 computers).

Those SHDSL modems should have equal setup except that one should be a
Server and the other a Client.

In both those situations rebooting Client doesn't help, but rebooting
Server one solves the problem.

> I have a feeling you have just about all the evidence you need to go 
> back to your modem vendor's support and say "Listen up... what you told 
> me was wrong and here's my proof.".

The thing is that we have 2 pairs of modem, one VDSL and one SHDSL. They
both have this problem, and my initial post to support was about VDSL
modems were they told that problem is in something else. I can't prove
that because VDSL modems has broken and are now being repaired.

At another post about this problem regarding SHDSL modems they just
suggested unofficial firmware, which I'm afraid to update b/c if
something wrong I don't have any kind of backup there. Moreover I called
local service, they say any service will lead to transportation to
capital city and will take 1-3 months :/ This is what is being happened
with VDSL.

Thanks again.

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