From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Routed LANs vs WOL & Windows troubles
Date: Sun, 12 Apr 2015 12:40:17 +0000 [thread overview]
Message-ID: <C7617157-725D-4C69-A4D8-2D6DB7D3A622@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <876191o8yp.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 1943 bytes --]
Yes please!
--
Cheers,
Kevin@Darbyshire-Bryant.me.uk
Sent from my phone, apologies for brevity, spelling & top posting
> On 12 Apr 2015, at 12:57, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> writes:
>
>> 4) (A bonus Monty Python question) I've a second wireless access point
>> at the other end of the garden, attached by a suitable length of Cat
>> 6. Devices at mid travel point ideally roam from House wifi to Shed
>> wifi...but now they change IP address as well. To be honest I'm not
>> sure how this actually works in a bridged environment either since the
>> MAC now migrates from local wireless bridge interface to local wired
>> interface and potentially back again as I wander around the
>> garden...how does it really know where to send frames to this
>> magically roaming device?
>
> Dunno about the rest of your list, but I have successfully set up
> multiple access points with roaming by using VLANs between them. Of
> course VLAN-aware switches help, but if you have the access points
> connected directly via a wire, you can use the VLAN support in openwrt,
> to basically bridge the wifi interfaces of the two access points. That
> way you avoid the problems with broadcasting across the LAN/WLAN border,
> but can still get roaming on the same IP subnet. You'll want to have one
> access point running DHCP, and the other just being passively serving as
> the access point.
>
> This can be setup via openwrt config files; can share my config if
> you're interested.
>
>> It appears a lot of 'it just works' functionality is designed for
>> bridged LAN/WLAN scenarios and hates routed but maybe I've got the
>> wrong end of a stick.
>
> For some things, having the reflector functionality of avahi-daemon
> turned on somewhere it can see both subnets helps on discovery and 'just
> works'-iness :)
>
> -Toke
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3089 bytes --]
next prev parent reply other threads:[~2015-04-12 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 17:01 Kevin Darbyshire-Bryant
2015-04-12 11:57 ` Toke Høiland-Jørgensen
2015-04-12 12:40 ` Kevin Darbyshire-Bryant [this message]
2015-04-12 14:29 ` Toke Høiland-Jørgensen
2015-04-12 18:18 ` Kevin Darbyshire-Bryant
2015-04-12 18:23 ` Toke Høiland-Jørgensen
2015-04-12 14:18 ` Alan Jenkins
2015-04-12 18:31 ` Kevin Darbyshire-Bryant
2015-04-12 21:57 ` Dave Taht
[not found] <552CDDB9.40909@darbyshire-bryant.me.uk>
2015-04-14 19:48 ` Kevin Darbyshire-Bryant
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=C7617157-725D-4C69-A4D8-2D6DB7D3A622@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--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