From: Benny Amorsen <benny+usenet@amorsen.dk>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] MAC learning and VLAN
Date: Wed, 19 Aug 2009 16:17:14 +0200 [thread overview]
Message-ID: <m3hbw3nb11.fsf@ursa.amorsen.dk> (raw)
In-Reply-To: <OF1FFD7F2D.3373FC10-ONC1257617.0048E18B-C1257617.004AB048@transmode.se> (Joakim Tjernlund's message of "Wed, 19 Aug 2009 15:35:47 +0200")
Joakim Tjernlund <joakim.tjernlund@transmode.se> writes:
> Yes, this appears how linux impl. VLANs but I wonder if this
> is how VLAN aware switch would impl. it? Looing into 802.1Q it
> sees this is referred to as SVL resp. IVL? I guess linux only
> supports IVL?
Generally a VLAN aware switch is unable to bridge between different
VLAN's. You would be unable to configure your example except on the
fanciest of switches.
>> Imagine replacing eth0.1 with eth1 and eth0.2 with eth2. If a certain
>> MAC address is learned on eth1, it would be wrong to send packets
>> destined for that MAC address through eth2. That's pretty much the point
>> of bridging.
>
> Yes it would be wrong, but eth0.1 and eth0.2 are on the same physical LAN
> and could share learned MAC addresses but as it is impl. in linux
> it does not seem possible.
What would be the point? What is it you're trying to accomplish? If the
machines can communicate on VLAN 1, why do you want them to send traffic
on VLAN 2 instead?
/Benny
next prev parent reply other threads:[~2009-08-19 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 10:06 [Bridge] MAC learning and VLAN Joakim Tjernlund
2009-08-19 12:42 ` Benny Amorsen
2009-08-19 13:35 ` Joakim Tjernlund
2009-08-19 14:17 ` Benny Amorsen [this message]
2009-08-19 14:32 ` Joakim Tjernlund
2009-08-19 16:40 ` Benny Amorsen
2009-08-19 17:07 ` Joakim Tjernlund
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=m3hbw3nb11.fsf@ursa.amorsen.dk \
--to=benny+usenet@amorsen.dk \
--cc=bridge@lists.linux-foundation.org \
--cc=joakim.tjernlund@transmode.se \
/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