ESP8266 Community Forum

- Thu Oct 08, 2015 10:15 am #30883 Thanks Martin and Kolban.
I get the impression that the ESP8266 does the hardest work and leave the simple.
Creates an AP and assigns IP's then keep separate stations not make much sense.
Can not be done by software?
So far I have only worked with AT commands but I'll start with the API.
I will be posting my "progress".
By the way, congratulations to Martin by the book, I'm thinking of donating ...

Bless you!

- Thu Oct 08, 2015 10:28 am #30885 (BTW, the congrats for the book should be given to Kolban, not to me)

Of course, there is a workaround that can be done in software, but it is a bit ugly :
S1 can send a command to AP that tell him "Hi AP, here is a command to be send to S2, could you forward it to him ?"

- Sun Oct 11, 2015 12:59 pm #31109 @martinayotte, it's slightly different. Wlan access points can choose to apply "client isolation" (or not). On many access points this is something you can configure. On the ESP8266 this is set fixed to "enabled". So any client can communicate to the access point, but the access point will not pass traffic between clients. That's by design.

It has nothing to do with routing, because this is layer 2 functionality, it the access point passes traffic between clients it's bridging, not routing.

If one is looking for a proper access point, one should buy a proper access point. The ESP8266 is NOT an access point. The basic AP mode is meant to have smartphones connected and enable them to access the ESP8266 itself. So it's perfecly understandable that it has client isolation enabled.

- Sun Oct 11, 2015 4:04 pm #31121 Hi Erik,

Understood, and that's why I've wrote :

which the current SDK and/or Espressif chip don't offer

The workaround I've suggested is, you're right some kind of bridging in software, but it is ugly, it's rely on custom protocol, etc.