From: "Покотиленко Костик" <casper@meteor.dp.ua>
To: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
Cc: netfilter@vger.kernel.org
Subject: Re: ebtables mac update
Date: Thu, 01 Jul 2010 13:11:49 +0300 [thread overview]
Message-ID: <1277979109.4200.20.camel@casper.meteor.dp.ua> (raw)
In-Reply-To: <4C2C66F1.1080602@plouf.fr.eu.org>
В Чтв, 01/07/2010 в 11:59 +0200, Pascal Hambourg пишет:
> Pokotilenko Kostik (approximate romanization) 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.
> >
> > tcpdump from linux showed:
> >
> > 1. while pinging from linux to win7:
> >
> > - Linux sends broadcast ARP-WHO-HAS win7-ip and no one replays
> > - I was able to see win7's ARP-WHO-HAS some-other-ip after that linux
> > probably learned it's MAC and started to send unicast ping requests,
> > still no replay
> > - I also saw some unicast packets from win7 crossed the bridge
> >
> > 2. while pinging from win7 to linux:
> >
> > - linux gets broadcast ARP-WHO-HAS linux-ip
> > - linux replays unicast ARP-IS-AT
> > - those two repeat, so win7 doesn't get replay
> >
> > 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.
>
> An explanation may be that the MAC table in each modem is updated only
> with the source address of packets received on the ethernet port and not
> those received through the VDSL link, based on the assumption that the
> other modem already takes care of them.
>
> Do the modems have a management interface that shows the contents of the
> MAC table ?
They do have management interface, but I was unable to find a way to see
MAC table. I'll discuss this with Zyxel support maybe they'll clear that
out. Main thing is that tonight I got chance to pull modems off
production and make those tests in simplified enviroment.
Thanks to all. Now it doesn't seem related to linux bridge, so if there
is new input I'll continue this thread.
--
Покотиленко Костик <casper@meteor.dp.ua>
next prev parent reply other threads:[~2010-07-01 10:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 10:43 ebtables mac update Покотиленко Костик
2010-06-29 12:36 ` Pascal Hambourg
2010-06-29 14:29 ` Покотиленко Костик
2010-06-29 14:57 ` Grant Taylor
2010-06-30 9:24 ` Покотиленко Костик
2010-06-30 15:39 ` Pascal Hambourg
2010-06-30 23:38 ` Покотиленко Костик
2010-06-30 23:54 ` Grant Taylor
2010-07-01 9:08 ` Покотиленко Костик
2010-07-01 16:10 ` Grant Taylor
2010-07-01 17:00 ` Покотиленко Костик
2010-07-01 17:13 ` Покотиленко Костик
2010-07-01 9:59 ` Pascal Hambourg
2010-07-01 10:11 ` Покотиленко Костик [this message]
2010-07-01 10:49 ` Pascal Hambourg
2010-07-01 11:05 ` Покотиленко Костик
2010-06-29 14:45 ` Grant Taylor
2010-06-29 17:03 ` Jan Engelhardt
2010-06-29 19:02 ` Grant Taylor
2010-06-30 9:09 ` Покотиленко Костик
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1277979109.4200.20.camel@casper.meteor.dp.ua \
--to=casper@meteor.dp.ua \
--cc=netfilter@vger.kernel.org \
--cc=pascal.mail@plouf.fr.eu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).