From: Jonathan Thibault <jonathan@navigue.com>
To: bridge@lists.osdl.org
Subject: Re: [Bridge] bridge, vlan and *no* stp/bpdu
Date: Tue, 11 Mar 2008 11:44:19 -0400 [thread overview]
Message-ID: <47D6A8D3.1030201@navigue.com> (raw)
In-Reply-To: <96CF49BD8B56384395D698BA99007FA32FA169@exchange.pacwire.local>
Hello Leigh,
This was one of the first things I looked at when I noticed that it
didn't reach the client. As far as I can tell, no, the mac isn't on the
wrong port. Come to think of it, I think the problem might have to do
with the bridge not learning the affected machine's MAC at all until I
removed in.3 from the bridge completely. I'll do further tests and
confirm this shortly, especially if you think there is something to it.
Also of note, since I monitor the trunk itself (and I only filter by mac
when I do), I would have seen the reply if it went to the wrong vlan
anyway, or is that logic wrong?
Anyway, if the problem is that the bridge stops learning a specific
machine's MAC, is there a way for me to manually add the MAC to the
bridge table and see if it solves the problem? If such is the case,
it's not really a solution, but it would certainly narrow down the scope
of the problem.
Jonathan
Leigh Sharpe wrote:
> Can you do a brctl showmacs br0, and see if the machines which are not
> receiving an ARP response are being seen by the bridge as being on the
> wrong VLAN?
>
>
> Ie, I'm wondering if the bridge sees their MAC address on an interface
> other than the one they are really connected to. If that's the case, the
> bridge would send their response out of the wrong interface, which may
> result in the symptoms you are describing. I think there may be some
> ebtables rules which could help here, but my memory fails me at this
> point.
>
> Regards,
> Leigh
>
> Leigh Sharpe
> Network Systems Engineer
> Pacific Wireless
> Ph +61 3 9584 8966
> Mob 0408 009 502
> Helpdesk 1300 300 616
> email lsharpe@pacificwireless.com.au
> web www.pacificwireless.com.au
>
>
next prev parent reply other threads:[~2008-03-11 15:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 0:43 [Bridge] bridge, vlan and *no* stp/bpdu Leigh Sharpe
2008-03-11 15:44 ` Jonathan Thibault [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-18 2:38 Leigh Sharpe
2008-03-18 4:38 ` Malcolm Scott
2008-03-19 14:58 ` Jonathan Thibault
2008-04-11 18:04 ` Jonathan Thibault
2008-04-13 10:59 ` Malcolm Scott
2008-03-11 22:07 Leigh Sharpe
2008-03-12 17:43 ` Jonathan Thibault
2008-03-11 0:43 Leigh Sharpe
2008-03-07 19:47 Jonathan Thibault
2008-03-07 20:08 ` Andy Gospodarek
[not found] ` <47D1B45F.7020409@navigue.com>
[not found] ` <bdfc5d6e0803071423ia2c794fn662a6e875ffafe09@mail.gmail.com>
2008-03-08 16:26 ` Jonathan Thibault
2008-03-09 7:36 ` richardvoigt
2008-03-09 15:53 ` Jonathan Thibault
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=47D6A8D3.1030201@navigue.com \
--to=jonathan@navigue.com \
--cc=bridge@lists.osdl.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