[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] Connect two machines running LWIP applications via WLAN
From: |
Sylvain Rochet |
Subject: |
Re: [lwip-users] Connect two machines running LWIP applications via WLAN |
Date: |
Tue, 4 Apr 2017 15:38:09 +0200 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
Hi,
On Tue, Apr 04, 2017 at 03:30:46PM +0200, Sylvain Rochet wrote:
> Hi,
>
> On Tue, Apr 04, 2017 at 03:12:09PM +0200, Dirk Ziegelmeier wrote:
> > I sent this link because of the first answer:
> >
> >
> > It is not possible to bridge between wireless (client a.k.a. station mode)
> > and wired interfaces according to this thread on linux-ath5k-devel
> > <http://web.archive.org/web/20110925231256/http://kerneltrap.org/mailarchive/linux-ath5k-devel/2010/3/21/6871733>
> > .
> > One should set up NAT instead:
>
> The master (access-point) of a wireless network must be aware of all
> existing managed nodes, this is why you have to associate (and I hope
> authenticate as well :-) ) your client. What you want to achieve with a
> bridged wireless network is a wireless mesh network, which isn't
> supported with basic equipments, and which is achieved using proprietary
> protocols or with WDS for a very basic tree.
>
> Knowing that, it is obvious that it doesn't work. In other words, for
> general cases, layer 1 domain and layer 2 domain must be the same for
> wireless networks.
Erm, I have to add that master can be bridged to a wired network, since
it is the central point, and this is the only way (without mesh, WDS,
blabla.) to bridge a wireless network and therefore extend the layer 2
domain over the wireless layer 1 domain. The bridge limitation only
applies to managed nodes (client).
Sylvain
signature.asc
Description: Digital signature