0

Eero in Bridge Mode not allowing connection to hardwired LAN devices

I am using an Eero Pro 6e as a wireless AP in my network. This is my topology:

 

  • Modem
    • Router/DHCP server
      • Switch
        • Eero in Bridge Mode (AP) 
        • LAN Devices
        • NAS
        • Laptop
        • Switch
          • Additional LAN devices
          • Sonos running SonosNet 

I started noticing issues accessing web services hosted on my NAS, but only for wireless devices.

 

Wired devices have full communication both with LAN hardwired devices branching off my Switch, and they can also ping any wireless devices on my network.

However, wireless devices connected to my Eero cannot ping any of the wired devices on my network. If I restart any of the LAN devices connected to my first switch (including the NAS), they show up in the Eero app for a few hours and drop off silently. If I pull up my Eero app after a day, it shows them all as "recently connected".

 

If my Eero is in bridge mode, shouldn't my router be the authority on what is currently connected to my network? I find it strange that I can ping LAN -> Wireless but not the other way around. Also interestingly, my local DNS server has no problem sending the correct IP address for my lan domain, which suggests DNS requests are making it to my router, but the device can't connect to the resolved LAN IP. If I unplug the wired device and plug it back in, I can access it from a wireless device for a few hours. 

 

I am on the latest software 6.13.4-21 although I started seeing this behavior an update ago. I originally thought it was an issue with my router, and after a lot of digging I was able to reproduce the issue by pinging the LAN device while hardwired, and the pings failing once switching to WiFi (also, not seeing the wired devices in my Eero app).

 

Any help is appreciated!

10 replies

null
    • Michael_eero_support
    • 7 mths ago
    • Reported - view

    Hi c_c

    The topology looks correct for a single eero.  if you have multiple eero you will need to have one between the DHCP router and the switch.   One eero must be upstream of all other hardwired eero in the topology to be the gateway eero.

    From the behavior it sounds like the eero isn't bridged.  If the eero is bridged, yes, your router is the authority.  The switch might also be doing something odd or unexpected.

    You may want to call support so we can take a look and see what we can see: https://support.eero.com/hc/en-us/articles/207376426-How-do-I-contact-eero-support-

    • c_c
    • 7 mths ago
    • Reported - view

    Thank you for the reply, Michael.
     

    The Eero is definitely bridged, and I do have a single Eero setup (no mesh). The switch is unmanaged, and is allowing traffic between lan and wireless devices, and doesn’t seem to be an issue. 

     

    I tried calling support before asking here, but was left on hold for a very long time. I’ll try calling back today if that is the best way to get support. 
     

    Thanks. 

      • Michael_eero_support
      • 7 mths ago
      • Reported - view

      c_c that certainly looks right.  You might try going router->eero->switch just to see what affect that has.  That would be the first thing I would try in this circumstance if it was my own network.

      • c_c
      • 7 mths ago
      • Reported - view

      Michael_eero_support I appreciate the reply but unfortunately that didn’t help in my case. I redid my network by going directly from my router -> Eero -> switch and rebooted my entire infrastructure (NAS/switches/router) and the issue still occurs after a few hours. 
       

      Another annoying consequence of this topology is that my Apple TV (hardwired) running Plex cannot stream my Plex content directly from my NAS. Before, the tv and server lived on the same switch but adding Eero in between the router and switch causes the devices to lose communication with each other on the Ethernet LAN side as well as the wireless side. 
       

      Eero seems to be messing with my routing even in bridge mode. 

      • c_c
      • 7 mths ago
      • Reported - view

      c_c 

      To clarify, the TV and NAS still exist on the same switch, but adding the Eero between the switch and the router causes them to not be able to communicate with each other (which is the same behavior I saw on wireless before redoing my network)

      • c_c
      • 7 mths ago
      • Reported - view

      Hey Michael_eero_support ,

       

      I stumbled upon this thread on the TrueNAS forums, and this is exactly the issue I'm running into. https://www.truenas.com/community/threads/jails-eero.59477/

       

      Clearing the ARP cache allows me to instantly connect to my jails (Plex is running on one as well). This seems to be a long-standing issue on the Eero side as this thread is from a few years ago. Another example: https://www.truenas.com/community/threads/yet-another-lost-connection-to-a-jail-gui-ip-its-only-1-of-2-computers-though-appears-to-be-an-eero-mesh-bridge-issue.85332/

    • gavin_corbett
    • 1 mth ago
    • Reported - view

    I have this exact same issue so would like to know if there is a resolution to this.

    I have a simple LAN, with a single switch for connected devices, and the Eero 6 mesh, in bridge mode with a base connected to that switch and the other meshed eero somewhere else in the house.

    For some reason i can ping and see all devices connected on wried and wireless except the Synology NAS.

    These devices also show up as connected devices in Eero, except the Synology.

    If i enable the wifi on my old a non mesh wifi AP and connect to it from my wifi devices (non specific, as ive tried a windows pc, a mac, and an iphone) none will ping the Nas if connected to Eero Mesh.

    Once i connect to the old wifi the arp -a shows the Synology mac address, and when i reconnect to the new eero 6 mesh, the arp entry is still there but i cannot ping it.

    ive ruled out the devices connecting to the wifi, and the nas as they all work when on the old wifi, its definitely something with the Eero so really keen to see if anyone has resolved this.

      • c_c
      • 1 mth ago
      • Reported - view

      gavin. corbett 

       

      Gavin, have you tried clearing the arp route with the -d flag? While it’s not a permanent fix, when I had this issue, that temporarily allowed me to access my device. 
       

      I’ve since moved to TrueNas Scale, which uses docker networking on my device’s ethernet adapter IP rather than virtual IPs, which has solved this issue for me since there is no arp mapping going on (I’m sure the issue still exists on Eero APs, though). 

      • gavin_corbett
      • 1 mth ago
      • Reported - view

       it removes the arp entry on that one device but that doesn’t fix why no other wifi connected device cannot see the synology. Almost like it doesn’t recognize it and drops it at the wifi level. 
      As I said if I connect my pc to the old wifi then it all works fine. 
      I hope eero know what’s going on with their shit…

    • korrind3
    • 1 mth ago
    • Reported - view

    Verify that there are no routing or VLAN configurations on your switch that might be causing the separation between wired and wireless devices. Incorrect VLAN configurations can lead to devices not being able to communicate across segments. 

Login to reply

Content aside

  • 1 mth agoLast active
  • 10Replies
  • 842Views
  • 4 Following