We present same issue on Raspbian (openHABian) Jessie
Our devices are WiFi connected to LAN router with proper hostname and dinamic ip. We can hold them properly on eth0 ethernet interface, but soon or late this hostname or even the ip fails on LAN pong when we are on wlan0.
Currently we are making a new setup from Raspian Stretch. Just to repeat the process cleanly. Any advise on this issue will be appreciated. We'll be pleasesd to share any log.
So, we are clear that WiFi does not die, at least, not always. And also, hotplugging an ethernet wire and then disconnecting it: renews wlan presence on LAN.
Our power-management and Country code
are catched on wlan interface definition.
- We are using  fork to allow our users to get WiFi AP configuration over the RPi3 (that has been overlayed  to RS485 on /dev/AMA0
, just in case it could be relevant). As known, forked nodejs webapp  writes on /etc/network/interfaces
any input given from user: Essid and password.
So the app gets connected dinamically to any DHCP server
on LAN. We've added Static IP
feature and we are now changing to wpa-supplicant
on given fork. On this context we arrive to this forum thread issue.
- Currently, we are on avahi
with  a fork on Bonjour Browser
so we are able to jump another related issue specific to Android who is unable to resolve dns names
. So, in order to be able to allow our users to browse configured hostname on such Android devices
, we have forked a feature that identifies our hostname-ip avahi broadcasting notificacions. In that sense, we go together with Openhab-discovery  feature. So we can browse the workstation service for every RPi3 near Openhab services
.That allows a kind of usertaping on a ListView Item to launch a WebView with proper IP to our RPi3 default http. On that road, we have default Samba Openhabian setup
- As standard ISP routers (target of our project) are not very reliable on listing real-time their connected clients, we can't get conclusions on that testing.
Why LAN device recognition works fine on Ethernet and fails, irregularly, on WiFi?
This quote, at this very moment, is the most biggest simplification of the issue.
While doing the Strech thing, next, we are suposed to sniff some traffic on our test-setup
. Which now holds some devices RPi-3 linking a mqtt broker on a BaaS
. Just to ensure that we are not blowing up interface capacity. We've tested that our mqtt-clients keep connected to cloud broker although we can't ping hostname or IP from a desktop on LAN. So that, WiFi is not dead.
Thanks in advance!
 We are NOT experimenting this issue https://github.com/openhab/openhab-distro/issues/162
and /etc/avahi/avahi-daemon.conf can be set to either broadcast IP6 or IP4. We could search the issue this side by i.e. [ .a] or [ .b]
[ .a] https://raspberrypi.stackexchange.com/q ... er-a-while
[ .b] https://raspberrypi.stackexchange.com/q ... ame-in-lan