-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-mesh ip network example (IDFGH-6505) #8158
Conversation
… the netif callback
…with delayed task, added needed kconfig properties
|
Thanks for your contribution. |
I kept the |
Thanks for your contribution on ESP-MESH, we will check your code and give you feedback soon. |
@wizche Can you please rebase the PR and remove the |
Closing due to lack of reply. Feel free to submit a newer PR if you'd still prefer us to consider these changes. Thanks. |
This is an attempt to "fix" #7528
EDIT2 (17.01.2021): Well I was completely wrong so here my findings after investigating this more.
Adapting the
internal_communication
wont work because even if we dont start the DHCP server/client the request are not relayed to the root node and therefore we cannot use the root node as the only DHCP server. As @shenjun7 pointed out Root as the only dhcp server to allocate IP to non-mesh nodes requires a lot of changes, we will update in the future.Starting a DHCP server on every node is also not feasible since we will have duplicates IP across the (mesh) network.
So basically the only solution I could find is based on my initial idea of adapting
ip_internal_network
. The idea is to have the entrypoint node (the one where non-mesh device will connect to) to reconfigure its soft-ap part to expose a different SSID.Specifically I introduce the
ap
console command that will reconfigure the node in the following way:Even though this works, I experience major connectivity issues, not only from the non-mesh device but from the node themselves. I see packet drops, frame size error (when encapsulating into the mesh packet) and general instability.
You can check the README in
nonmesh_ip_internal_network
for additional details.