But the eero is processing all of hte packets on the LAN side and then natting it through to the modem..
you need to do a packet trace on both the LAN side and the WAN side of the eero and see what’s being generated.. by hte time the packet has been processed/sanitised and sent onto the hub, all the hub it seeing is a tcp stream (or a bunch of udp packets) it’s not seeing any wireless frames or anything like that - it’s all standard stuff and the source shouldn’t be relevant.
an interesting problem for sure, but without some more data on what packet(s) are causing the hub to fail we’re gonna be none-the-wiser..
@golec83 wrote:There is no vlans so technically a packet from the laptop can hit the router still (again, assuming the two ports on eero work like a switch).
I don’t know anything about eero’s, but in theory(in my simple brain anyways) the eero should have a WAN and LAN interface (might not matter which you use, but it should designate one for each network) so any packets hitting the LAN interface with a destination outside of your network should be sent off to the processor that handles NAT/routing and then back down to the WAN port.. it shouldn’t be possible for a LAN packet to hit the eero’s WAN interface without first being processed (i.e. NAT’d)
Edit: are you able to disable the AX radio in the eero? So that clients can only connect via the older standards?