From: Aaron Wood <woody77@gmail.com>
To: David Reed <dpreed@reed.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Recording RF management info _and_ associated traffic?
Date: Sun, 25 Jan 2015 15:21:47 -0800 [thread overview]
Message-ID: <CALQXh-OE61XKcz9_OqW7ZTi=3rzpD3DDZ-oyutG7QDEHFi8SLg@mail.gmail.com> (raw)
In-Reply-To: <1422217048.025611275@apps.rackspace.com>
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
On Sun, Jan 25, 2015 at 12:17 PM, <dpreed@reed.com> wrote:
> There is no reason why one cannot set up an enterprise network to support
> roaming, yet maintaining the property that IP addresses don't change while
> roaming from AP to AP. Here's a simple concept, that amounts to moving
> what would be in the Ethernet bridging tables up to the IP layer.
>
>
>
> All addresses in the enterprise are assigned from a common prefix (XXX/16
> in IPv4, perhaps). Routing in each access point is used to decide whether
> to send the packet on its LAN, or to reflect it to another LAN. A node's
> preferred location would be updated by the endpoint itself, sending its
> current location to its current access point (via ARP or some other
> protocol). The access point that hears of a new node that it can reach
> tells all the other access points that the node is attached to it.
> Delivery of a packet to a node is done by the access point that receives
> the packet by looking up the destination IP address in its local table, and
> sending it to the access point that currently has the destination IP
> address.
>
I'm not familiar with routing protocols. Do any of the current ones do
this, or is this an idea for a new protocol?
-Aaron
[-- Attachment #2: Type: text/html, Size: 1910 bytes --]
next prev parent reply other threads:[~2015-01-25 23:21 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 2:20 Richard Smith
2015-01-20 16:59 ` Rich Brown
2015-01-21 23:40 ` Richard Smith
2015-01-21 23:58 ` David Lang
2015-01-22 9:04 ` Richard Smith
2015-01-22 9:18 ` David Lang
2015-01-22 18:19 ` Richard Smith
2015-01-22 22:09 ` David Lang
2015-01-22 22:55 ` Roman Toledo Casabona
2015-01-24 14:59 ` dpreed
2015-01-24 15:30 ` Kelvin Edmison
2015-01-25 4:35 ` David Lang
2015-01-25 5:02 ` Dave Taht
2015-01-25 5:04 ` Dave Taht
2015-01-25 6:44 ` David Lang
2015-01-25 7:06 ` David Lang
[not found] ` <CAA93jw64KjW-JjLxB3i_ZK348NCyJYSQACFO34MaUsBBWyZ+pA@mail.gmail.com>
2015-01-25 7:59 ` Dave Taht
2015-01-25 9:39 ` David Lang
2015-01-25 15:03 ` Chuck Anderson
2015-01-25 20:17 ` dpreed
2015-01-25 23:21 ` Aaron Wood [this message]
2015-01-25 23:57 ` David Lang
2015-01-26 1:51 ` dpreed
2015-01-26 2:09 ` David Lang
2015-01-26 4:33 ` Valdis.Kletnieks
2015-01-26 4:44 ` David Lang
2015-01-27 0:14 ` dpreed
2015-01-27 0:23 ` David Lang
2015-01-26 2:19 ` Dave Taht
2015-01-26 2:43 ` David Lang
2015-01-26 2:58 ` Dave Taht
2015-01-26 3:17 ` dpreed
2015-01-26 3:32 ` David Lang
2015-01-26 3:45 ` Dave Taht
2015-01-27 0:12 ` dpreed
2015-01-27 0:31 ` David Lang
2015-01-27 0:36 ` Dave Taht
2015-01-26 3:19 ` David Lang
2015-01-26 4:25 ` Valdis.Kletnieks
2015-01-26 4:39 ` David Lang
2015-01-26 16:42 ` Valdis.Kletnieks
2015-01-25 8:07 ` Outback Dingo
2015-01-30 16:14 ` Richard Smith
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='CALQXh-OE61XKcz9_OqW7ZTi=3rzpD3DDZ-oyutG7QDEHFi8SLg@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@reed.com \
/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