From: Michael Richardson <mcr@sandelman.ca>
To: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= <toke@toke.dk>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] treating 2.4ghz as -legacy?
Date: Thu, 19 Dec 2013 09:32:01 -0500 [thread overview]
Message-ID: <3924.1387463521@sandelman.ca> (raw)
In-Reply-To: <87zjnxxk3u.fsf@toke.dk>
Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>> I believe that Linux allows having both tagged and untagged packets on
>> the samy physical interface, so the APs could communicate on a VLAN
>> and one could be the gateway to the rest of the network (similar type
>> of overhead in this case to GRE tunnels in that all traffic would get
>> routed through one system, but I think it would still be less)
> What happens to the VLAN tags if the traffic goes through a
> non-VLAN-aware switch?
A switch which is totally ignorant of VLAN will simply pass all traffic to
all ports (modulo mac learning). This is distinguished from a VLAN aware
switch that has it turned off (common for netgear equipment), which might
intolerant.
For many homes, the 3800 may be the only physical switch... a homenet router
discovery protocol would also notice if 3800s were directly attached...
The layer-2 VLAN idea fails if we have a routed homenet and there are a
variety of devices invoved. That's why, I think that GRE over IP would win
for most homes, and yet keep the wired multicast and wireless multicast
separate.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
next prev parent reply other threads:[~2013-12-19 14:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 19:46 Dave Taht
2013-12-16 20:19 ` Sebastian Moeller
2013-12-16 20:25 ` Toke Høiland-Jørgensen
2013-12-16 20:48 ` Kelvin Edmison
2013-12-16 21:28 ` David Lang
2013-12-16 22:06 ` Fred Stratton
2013-12-17 17:54 ` Michael Richardson
2013-12-17 18:51 ` Jim Gettys
2013-12-17 22:25 ` dpreed
2013-12-17 22:32 ` Jim Gettys
2013-12-17 23:43 ` Stephen Hemminger
2013-12-18 1:33 ` Theodore Ts'o
2013-12-18 3:04 ` David Lang
2013-12-18 5:05 ` Theodore Ts'o
2013-12-18 5:49 ` David Lang
2013-12-18 14:17 ` Chuck Anderson
2013-12-18 15:19 ` dpreed
2013-12-18 16:54 ` Michael Richardson
2013-12-18 18:18 ` Toke Høiland-Jørgensen
2013-12-18 19:24 ` David Lang
2013-12-18 20:07 ` Michael Richardson
2013-12-18 20:14 ` David Lang
2013-12-19 9:31 ` Toke Høiland-Jørgensen
2013-12-19 14:32 ` Michael Richardson [this message]
2013-12-19 20:05 ` David Lang
2013-12-19 21:01 ` Chuck Anderson
2013-12-20 0:50 ` Theodore Ts'o
2013-12-20 5:18 ` dpreed
2013-12-18 14:06 ` Michael Richardson
2013-12-27 23:56 ` Maciej Soltysiak
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3924.1387463521@sandelman.ca \
--to=mcr@sandelman.ca \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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