16again wrote:It's way beyond broadcast filtering.
An ARP sent from .45 to 192.168.1.127 might be answered directly by Asus device. If the Asus device already knows IP/MAC mapping cached, there's no need to consult the client, just answer from cache.
Moreover, the ARP for .127 might be answered by Asus itself, with a different MAC address than the .127 is having!
This would make perfect sense, but .45 never receives a response to its ARP request.
redfive wrote:All devices need to belong to the same L2 ? If not, maybe using the wireless interface of the asus as WAN (with no NAT) and adding a static route on the ER, for the 'new' network behind the asus ....
When there is more than one client behind a wireless bridge, is always a challange
Cheers,
jonatha
I understand what you mean, but I have absolutely no idea how to set that up on the ASUS firmware.... Maybe I'll try DD-WRT. If I have network behind the bridge as say 192.168.10.1/24, I should have the static route to that subnet pointing to the IP address of the Wireless Bridge, correct?
Also, would setting the ASUS in router mode interfere with mDNS? I have a Chromecast behind the wireless bridge that I need to cast to.
