You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both the ESP32 and Pico-W network divers support dhcp name reservation for clients connected to the access point, but neither currently supports dns name resolution for hosts on the network. The IDE included libraries for both platforms support lightweight DNS name servers that should be started on the AP interface along with the DHCP servers that are currently supported in AtomVM. This will allow clients on the soft-AP to reach each other by hostname, so that the use of static IPs is not required for successful communication between hosts. AtomVM currently does not support requesting a static IP for devices in STA mode, thus making any communication on a device provided access point impossible, except between clients and the device providing the access point, since the IP of any other hosts cannot be known or discovered.
Perhaps a simpler alternative to low level device specific implementations would be to add dns server support as an Erlang module. This service should start automatically for the AP interface. It could also be useful to provide a dns server on any interface, allowing for isolation (and control) of dns records for a fleet of deployed AtomVM devices.
The text was updated successfully, but these errors were encountered:
Both the ESP32 and Pico-W network divers support dhcp name reservation for clients connected to the access point, but neither currently supports dns name resolution for hosts on the network. The IDE included libraries for both platforms support lightweight DNS name servers that should be started on the AP interface along with the DHCP servers that are currently supported in AtomVM. This will allow clients on the soft-AP to reach each other by hostname, so that the use of static IPs is not required for successful communication between hosts. AtomVM currently does not support requesting a static IP for devices in STA mode, thus making any communication on a device provided access point impossible, except between clients and the device providing the access point, since the IP of any other hosts cannot be known or discovered.
Perhaps a simpler alternative to low level device specific implementations would be to add dns server support as an Erlang module. This service should start automatically for the AP interface. It could also be useful to provide a dns server on any interface, allowing for isolation (and control) of dns records for a fleet of deployed AtomVM devices.
The text was updated successfully, but these errors were encountered: