beacon handle.

nice72
Posts: 10
Joined: Wed Nov 26, 2014 3:47 pm

beacon handle.

Postby nice72 » Thu Apr 23, 2015 7:25 pm

Dear Sir,

I am developing a mesh system using esp8266.

Although implementation of most of the functions, there are some limitations.

Due to the limitations of memory, our esp8266 system can support only six client.

We know, all systems that limit the number of supported client.

For the construction of a faster mesh system, I have one request.

I hope to handle 802.11's tx and rx beacon packet.

If esp8266 can add user defined tag information and interpret the packet,
I'll able to handle quickly and easily in the our mesh system.

Please, I hope that my request is allowed.

Thanks,
Peter

israellot
Posts: 14
Joined: Fri Mar 27, 2015 1:11 am

Re: beacon handle.

Postby israellot » Thu Apr 23, 2015 8:42 pm

Similar to what I requested on viewtopic.php?f=7&t=371
Please Espressif, allow us to mesh!

israellot
Posts: 14
Joined: Fri Mar 27, 2015 1:11 am

Re: beacon handle.

Postby israellot » Thu Apr 23, 2015 8:47 pm

By the way, what's your approach to mesh os esp8266 nice72?

nice72
Posts: 10
Joined: Wed Nov 26, 2014 3:47 pm

Re: beacon handle.

Postby nice72 » Fri Apr 24, 2015 7:39 am

Hi !!

As you know, mesh is required to support the multi to multi node.

However, a wireless LAN solutions of esp8266 can not fully support it.

Frenkly speaking, In order to support a single to multi node, I chose a multi tree node method.

Is this a question you want answered ?

Thanks
Peter

PS : The status of the child node that can be found on the console log of the top-level node.

11800> wsts

========WLAN COMMON===================
----wlan mode........3
1 : station mode
2 : softap mode
3 : station + softap mode
----channal..........1
----phy mode.........3
1 : 11b - softAP, station
2 : 11g - softAP, station
3 : 11n - station
----sta mac..........[18:fe:34:9d:b5:c4]
----ap mac..........[1a:fe:34:9d:b5:c4]
========STATION=======================
----status...........5
0 : idle
1 : connecting
2 : wrong password
3 : no ap found
4 : connect fail
5 : got ip
----ssid............[iot_hub]
----passwd..........[]
----auto connection..0
----dhcp client......1
---------ip..........172.017.123.046
nm..........255.255.254.000
gw..........172.017.123.254
========AP============================
----ssid............[dvmesh_1]
----password........[13579ertyta]
----channel..........1
----authmode.........0
0 - open
1 - wep
2 - wpa_psk
3 - wpa2_psk
4 - wpa_wpa2_psk
----hidden...........0
0 - announced
1 - hidden
----maxcon...........4
max : 4
----bintv............100ms
100~60000ms
----dhcp server......1
---------ip..........010.010.001.001
nm..........255.255.255.000
gw..........010.010.001.001
----wifi station
[00] 010.010.001.002 18:fe:34:9d:b5:bf
[01] 010.010.001.003 18:fe:34:9d:b5:c2
[02] 010.010.001.004 18:fe:34:9d:b5:c1
[03] 010.010.001.005 18:fe:34:9d:b5:bb
========MESH==========================
----state............[CON_MQTT__]
----hop..............1
----udp..............(tx:48)(txfree:48)(txerr:0)(tout:0)
----fifo.............(perr:0)
----up/down pkt......(up:0)(down:0)
----bad bssid
empty
----up dev...........06:08:52:1f:87:c0
----dev pool
no devid ip tout hop echo
000 18:fe:34:9d:b5:bf 010.010.001.002 00 01 12/12
001 18:fe:34:9d:b5:c2 010.010.001.003 00 01 12/12
002 18:fe:34:9d:b5:c1 010.010.001.004 00 01 12/12
003 18:fe:34:9d:b5:bc 010.010.001.003 00 02 12/12
004 18:fe:34:9d:b5:bb 010.010.001.005 00 01 12/12
005 18:fe:34:9d:b5:bd 010.010.001.005 00 02 12/12

11800>

israellot
Posts: 14
Joined: Fri Mar 27, 2015 1:11 am

Re: beacon handle.

Postby israellot » Fri Apr 24, 2015 8:14 pm

But what if we work with only probe requests and responses?
We would be still 802.11 compliant and could broadcast data multi-to-multi node. That's what I'm talking.
A protocol would need to be written on top of it but could work, no association required.

nice72
Posts: 10
Joined: Wed Nov 26, 2014 3:47 pm

Re: beacon handle.

Postby nice72 » Fri Apr 24, 2015 10:05 pm

Your opinion is correct.
I just would like to add that I want the data to the beacon packet.
Slave node can verify this with additional data. And, it is possible to perform more additional features.
And the confirmation of the received beacon packet is to use sniffer function.
So I need a ESP API function of adding tag information in the beacon packet.
It is possible?

israellot
Posts: 14
Joined: Fri Mar 27, 2015 1:11 am

Re: beacon handle.

Postby israellot » Sat Apr 25, 2015 12:39 am

I believe it is
I'm working on reverse engineer the ESP libraries to gain access to wifi functions not exposed in the SDK.
I will let you know if I get any result.

israellot
Posts: 14
Joined: Fri Mar 27, 2015 1:11 am

Re: beacon handle.

Postby israellot » Sat Apr 25, 2015 5:50 am

I managed to send probe requests with arbitrary data.

Anki
Posts: 25
Joined: Thu Apr 09, 2015 3:00 am

Re: beacon handle.

Postby Anki » Thu Apr 30, 2015 2:56 am

@israellot

Can you post any information about how you add data to the beacon? I am also interested in this feature.

eyal
Posts: 12
Joined: Thu Apr 09, 2015 8:52 pm

Re: beacon handle.

Postby eyal » Thu May 28, 2015 8:19 am

israellot wrote:I managed to send probe requests with arbitrary data.

This feature is of great value for ultra low power IoT as it can reduce the "on" time significantly thus reducing the power budget.
@israellot, can you post information of how this was achieved?

Who is online

Users browsing this forum: No registered users and 15 guests