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
I have 1 device which is an Ethernet device and in order to connect it to my network, I have a portable Zyxel Wifi client bridging Wifi to Ethernet for it.
This causes an interesting problem since it (the Zyxel Wifi client) is proxy arping for Ethernet-only device it is bridging for.
The result is that you see the Zyxel's MAC address regularly flip between its own IP address (used for web management) and that of the Ethernet-only device.
Not too sure how to solve this. Maybe a way to indicate that a particular MAC address belong to WiFi client proxy arping?
The text was updated successfully, but these errors were encountered:
interesting, I will study the way to differentiate two devices.
Do you have pi.hole installed?
Are the IP addresses of the Ethernet device and the Zyxel Wifi client within the same LAN as the raspberry?
Are using both the pi.hole DHCP server?
Pihole is installed but it is not offering DHCP addresses. This is because I also have a Firewalla Blue installed on my network in DHCP mode which means it must be the one offering up DHCP addresses.
The IP address of the Ethernet device (in this case it is a Juicebox EV charger) is different from the Zyxel Wifi client.
I think the Zyxel is just preventing ARP requests (not sure about what happens when the Juicebox broadcasts) from making it through.
I suspect, from Pi.Alert's perspective, there might not be much you can do about not being able to see MAC address of the devices behind another device doing proxy arp.
At best it would be to flag this situation so that it doesn't report that the IP address is changing?
I have 1 device which is an Ethernet device and in order to connect it to my network, I have a portable Zyxel Wifi client bridging Wifi to Ethernet for it.
This causes an interesting problem since it (the Zyxel Wifi client) is proxy arping for Ethernet-only device it is bridging for.
The result is that you see the Zyxel's MAC address regularly flip between its own IP address (used for web management) and that of the Ethernet-only device.
Not too sure how to solve this. Maybe a way to indicate that a particular MAC address belong to WiFi client proxy arping?
The text was updated successfully, but these errors were encountered: