I am having issues with ssh (or scp) between OSX devices, only on my eero network
I have three macbook pro devices. 2008 model on 10.11.6, 2015 on 10.13.6, and new 2019 on 10.14.6.
While trying to setup the newest device I wanted to scp files from the 2015 to the 2019. But I couldn't get scp or ssh to work on my home eero network not mater what I tried.
So I tried at work and they connect just fine.
More testing on home network finds that this seems to be an eero issue. I have a second network at home (independent network with it's own external WAN IP). It's on a zyxel router and connecting to that device works fine. I can ssh between any of these devices.
Once I return them to the eero network they start failing again.
I also find they can't ping each other.
Each Mac can see the rest of my network. I have several Raspberry Pi devices. Each can be seen, each can be pinged and I can ssh to any of them from any of my OSX macbooks. I can even ssh from one mac to the other if I go through any of the pi devices. SSH to PI and then SSH any of the other macs. No problem. I can also ping the macbooks from any of the pi devices.
So for some reason my eero network is causing issues for peer to peer connections between OSX devices specifically.
I can ssh from any pi to any other pi as well. So it is a OSX specific issue.
Actually it seems to be an apple specific issue. Because I have a terminal app on my iphone which lets me ssh. I can ssh into any pi, but once again I can NOT ssh into my macbooks from my iphone.
I have heard about issues with Apple devices on eero network but they mostly involve issues with connecting to a closer (stronger signal) eero or loss of connection when you roam. I have this issue as well with my iphones, macbooks and ipads. But a simple wifi off/wifi on fixes this issue. I can't find a solution to fix my ability to ssh (or more specifically scp) from one macbook to another on an eero network.
Has anyone else experienced this issue?
Is there a solution?
I'm having a very similar issue, I'm unable to ping from devices connected to the eero network toward devices on the wired segment, but the wired devices seem to be able to talk to one another just fine.
I can even ping a wireless device and get a response. Pinging from that same wireless device to the same wired device yields no response.
Some wired devices are experiencing connectivity issues out to the internet.
Now I have quite a few IP reservations and port mappings, so with no advanced features on the eero like backup and restore... yes, it's 2020 and we're still calling backup and restore an advanced feature, FML... I'm not just going to delete the network and start provisioning again.
In a dollars to dissatisfaction ratio, this eero bundle is likely the worst purchase I've ever made.
Ok, so thinking about it.. I did make a "Family Profile" for my daughter's phone to see what that was like - I only added her phone and tablet to it, nothing to do with these devices that can't talk to each other. It has a schedule on it that is supposed to stop internet access at bed time and these other features that never really seemed to work right so I just stopped using the profile and removed it.... This got me thinking that maybe there is some kind of configuration remnant left behind after deleting/removing... something that was wreaking havoc on my network...
I started running some continuous pings to some devices.... I reloaded the error pro and for just a few intervals at start up I was able to ping my devices. The plot thickens, this new bit of information fuels my suspicion that some configuration remnant that I can't see because... advanced features?... is to blame.
Quickly I create a profile "default" and add all 46 devices to it. I pause the profile and then enable it.... the next few pings fail. Dejected I turn to my phone to dig further into the app when in the corner of my eye it's brighter that it was a moment ago... there's more white against my black background, my pings are echoed back?! It's working?! Was it really the fix? I try another address quickly as if I'm racing against some unseen force coming to steal away my packets. Success! Another, also successful.
Ok, so I don't really want to add a device to this profile every time I onboard something new... can I remove it now and delete it? will everyone still like each other? Slowly, taking special care not to spook the newly domesticated packets I begin removing each device one by one from the profile, the idea here not to leave anything behind with the nuclear option of deleting the profile. With the number of devices left assigned to the profile at 0, it was time to say goodbye. So I deleted the "default" profile scattering its data to the ether with a confirmed "yes."
Sitting back at the create your first profile screen I knew what I had to do. Pausing briefly from typing this I had to switch over to the continuous ping that was still running in the background and make sure that my connectivity was still there. A knot grew in the pit of my stomach, what if this wasn't the fix? What if this $315 hunk of absolute garbage was somehow that much trashier still.... It was time to find out...
It's still there! It's still working I thought to myself amazed and bewildered. I immediately thought of the surprised Airman Doughtery from WarGames after surviving Joshua's simulated nuclear missile strike from the USSR, "Yeah, we're here! Jesus H. Christ! We're still here!"
So, I guess the moral of this story is, don't use Family Profiles. They're half baked and can really jack up your network. If you're having some flaky problems after having created one of these god forsaken things try my steps above, maybe you'll have a positive outcome. Me, I'm moving to an Orbi deployment ASAP. I don't like walking away from something I spent this much money on, but at the end of the day it can't be a guessing game of if the network is going to work or not.
Deuces eero, I'm out. See ya never.
Nope, no double NAT. Wired is just a dumb switch with PoE. All the devices get DHCP from Eero. It's just a terrible product. It was a very strange issue. I'm not sure what mechanism the profiles use, the inability to communicate makes me think it might be some type of vlan mechanism. Anyway, if someone was having some strange issue, it's a troubleshooting step they could try.