Openspot3, and EEro, and/or Mesh routers?

jbradshoemaker

Brian,

As you can see from below - Eero wants to explore bringing OpenSpot3 to the most recent update and ruling it out will get us to the place where I'll need to bring the mesh network back to factory defaults and start again (a major pain). After that, according to below, Brandon is out of ideas so I'll buy google nest (a major expense and pain) and if that doesn't work its back to SharkRF.

Surely there must be a log file that can be created which displays the glitch. I did download wireshark for mac but do not know how to get you the info you need. I am returning to you because you have been innovative in your approach.

Just out of curiosity the other fellow from SharkRF said he'd send me the file to update OS3 but never did, and my follow up requests appear to have been ignored. Are you able to send me the manual update with instructions, or is it not possible and the other fellow simply misspoke?

Brad
-------------------------------------------------------------------------------------------------------------------------------

Brandon (eero Customer Support)
Mar 15, 2021, 1:39 PM CDT

Hi Brad,

As far as I can see there is nothing in the eero network that would be blocking the OpenSpots internet access, I believe that we need to try and get that device updated. Sometimes if there are updates available for devices, those devices will have random issues and sometimes certain features stop working when the device is not updated to the latest firmware.

I would suggest that we try to get in touch with their support again and see if there is a way for them to assist you in getting your device updated.

Best,
Brandon | eero Support

HA2NON

We'll send you the manual firmware upgrade instructions if you contact us at info@sharkrf.com

Tyrbiter

Hi again all, sorry I missed this but I would agree that as a first step send a request to info@sharkrf.com for the file that will get you to v53 firmware. This just went stable today I think.

Once that's done then please feel free to request more help, I would be quite happy to try and get you sorted out.

jbradshoemaker

Hi Brian,

As per Norbert's request I have sent an email to info requesting the newest stable update. As an afterthought, I do not expect a 'cleansing' of the eero system to have success because others have been having the same problem. (Yes - some can share the same glitch but the probability is low). Changing to another Mesh network probably would solve the problem, but I own 6 of these Eero routers (due to the size, materials and odd layout of my property) so buying 6 more from a competitor is a significant cost.

I'll let you know when the update to OS3 has been installed and if it makes a difference.

Brad

jbradshoemaker

Hi Brian,

I have updated to the most recent update. Booted up. The LEDs are flashing red and blue alternately - seems to be 2 flashes for each colour.

Using my Eero app I can see that it has connected at 2.4 GHz to my kitchen Eero which is the same as my computer.

Using http://192.168.7.210/#status . I can see that it is connected too but "● internet connection error". On the log it shows retrying e.g. AmericaLink.

On the status page it shows firmware version V53.

So everything seems to be in order

Maybe there is a way to send you all of my OS3 settings - while is unlikely to be the problem as others with Eero are also experiencing it, but ...maybe there is a setting somewhere that is not proper.

Otherwise I have wireshark at the ready

Thx again for looking at it.

Brad

Tyrbiter

If you can see the IP address that the AmericaLink server uses, try a ping and a traceroute from your laptop to that address. I think you should be able to see it on the connectors page.

If that works on the laptop then see if the gateway address on the OS3 network page is correct.

We can then see if you need to try Wireshark.

jbradshoemaker

Hi Brian,

It does not give me an IP but instead a website net: americalink.radiotechnology.xyz

Checking on the IP for the website and pinging that reveals

64 bytes from 192.64.119.254: icmp_seq=2 ttl=55 time=97.640 ms
64 bytes from 192.64.119.254: icmp_seq=3 ttl=55 time=103.027 ms
64 bytes from 192.64.119.254: icmp_seq=4 ttl=55 time=132.309 ms
64 bytes from 192.64.119.254: icmp_seq=5 ttl=55 time=136.855 ms
64 bytes from 192.64.119.254: icmp_seq=6 ttl=55 time=296.822 ms
64 bytes from 192.64.119.254: icmp_seq=7 ttl=55 time=161.493 ms
64 bytes from 192.64.119.254: icmp_seq=8 ttl=55 time=233.139 ms
64 bytes from 192.64.119.254: icmp_seq=9 ttl=55 time=135.070 ms
64 bytes from 192.64.119.254: icmp_seq=10 ttl=55 time=246.874 ms
64 bytes from 192.64.119.254: icmp_seq=11 ttl=55 time=107.660 ms
64 bytes from 192.64.119.254: icmp_seq=12 ttl=55 time=101.666 ms
64 bytes from 192.64.119.254: icmp_seq=13 ttl=55 time=92.789 ms
64 bytes from 192.64.119.254: icmp_seq=14 ttl=55 time=94.932 ms
64 bytes from 192... etc.

I previously (and regularly) test this in a different way by connecting through my cellular system and changing to a different but active reflector. E.G. REF001C and REF030C. When I reconnect via wifi it uses last settings and gives me the same result. It is not therefore likely to be an issue with the site that OS3 is attempting to reach but instead...something in the middle.
This method also shows that it is not a crosstalk issue as I have both a Dstar HT and a C4FM HT and I am crossing (or not crossing) between these and AmericaLink (C4FM) and REF (Dstar)

Tyrbiter

Right, well there is something really odd going on.

I can ping and traceroute to 192.64.119.254 but a dig -x 192.64.119.254 does not resolve to an A record.

If I traceroute to americalink.radiotechnology.xyz then that resolves to 104.245.34.107 and a traceroute to that peters out somewhere in Dallas but ping works.

So, given this, I think it would be useful to know what IP address your OS3 thinks it ought to be connecting to.

A bit more looking and I see that the http:// response from americalink.radiotechnology.xyz sends you to the America Link Facebook group home page. It's entirely possible that UDP port 42000 is redirecting to the other IP address but I don't know because it's not obvious what is happening. In any case I can't see why your OS3 would decide to change an IP address for a UDP connection that's something that would happen at the server end.

jbradshoemaker

Hi Brian,

I alternated between my cell (so I can change reflectors) and my wifi (turned off autoscroll and limit lines) so I could capture the beginning of each.

Americalink, REF001C, REF030C

08:10:15 httpsrv[0]: websocket opened with token e8da18ec
08:10:16 net: americalink.radiotechnology.xyz resolve error
08:10:16 net-connector: connect retry in 209 ms
08:10:16 ysfref: uninitialized
08:10:16 net: americalink.radiotechnology.xyz resolve error, retrying
08:10:16 net: americalink.radiotechnology.xyz resolve error, retrying
08:10:16 net: americalink.radiotechnology.xyz resolve error, retrying
08:10:16 net: americalink.radiotechnology.xyz resolve error
08:10:16 net-connector: connect retry in 171 ms
08:10:16 ysfref: uninitialized
08:10:16 net: americalink.radiotechnology.xyz resolve error, retrying
08:10:17 net: americalink.radiotechnology.xyz resolve error, retrying
08:10:17 net: americalink.radiotechnology.xyz resolve error, retrying

08:16:30 httpsrv[0]: websocket opened with token 0c62426e
08:16:30 net: ccs002.xreflector.net resolve error
08:16:30 a3k: reset req.
08:16:30 net-connector: connect retry in 168 ms
08:16:30 net: connectivitycheck.gstatic.com resolve error, retrying
08:16:30 a3k-receive: init ok
08:16:30 ref: uninitialized
08:16:30 net: ccs002.xreflector.net resolve error, retrying
08:16:30 net: connectivitycheck.gstatic.com resolve error
08:16:30 nvmm: net check retry 1/2
08:16:31 batt: stat: dischargenvmm: net ip report
08:16:31 , 90% (new) (3970mV 25C est. 8h58m)
08:16:31 net: sharkrf.link resolve error, retrying
08:16:31 net: ccs002.xreflector.net resolve error, retrying
08:16:31 net: sharkrf.link resolve error, retrying
08:16:31 net: ccs002.xreflector.net resolve error, retrying
08:16:31 net: sharkrf.link resolve error, retrying
08:16:31 net: ccs002.xreflector.net resolve error
08:16:31 a3k: reset req.
08:16:31 net: sharkrf.link resolve error
08:16:31 nvmm: net ip address report retry 2/10
08:16:31 net-connector: connect retry in 103 ms
08:16:31 a3k-receive: init ok
08:16:31 ref: uninitialized
08:16:31 net: ccs002.xreflector.net resolve error, retrying
08:16:32 net: ccs002.xreflector.net resolve error, retrying
08:16:32 net: ccs002.xreflector.net resolve error, retrying
08:16:32 nvmm: downloading verinfo
08:16:32 net: img.sharkrf.com resolve error, retrying
08:16:32 net: ccs002.xreflector.net resolve error
08:16:32 a3k: reset req.
08:16:32 net: img.sharkrf.

08:20:35 net: ccs002.xreflector.net resolve error
08:20:35 a3k: reset req.
08:20:35 net-connector: connect retry in 173 ms
08:20:35 a3k-receive: init ok
08:20:36 ref: uninitialized
08:20:36 nvmm: net check
08:20:36 net: ccs002.xreflector.net resolve error, retrying
08:20:36 net: connectivitycheck.gstatic.com resolve error, retrying
08:20:36 net: ccs002.xreflector.net resolve error, retrying
08:20:36 net: connectivitycheck.gstatic.com resolve error, retrying
08:20:36 net: ccs002.xreflector.net resolve error, retrying
08:20:36 net: connectivitycheck.gstatic.com resolve error, retrying
08:20:36 net: ccs002.xreflector.net resolve error
08:20:36 a3k: reset req.
08:20:36 net: connectivitycheck.gstatic.com resolve error
08:20:36 nvmm: net check failed
08:20:36 nvmm: net ip report
08:20:36 net-connector: connect retry in 173 ms
08:20:36 a3k-receive: init ok
08:20:36 net: sharkrf.link resolve error, retrying
08:20:37 ref: uninitialized
08:20:37 net: ccs002.xreflector.net resolve error, retrying
08:20:37 net: sharkrf.link resolve error, retrying
08:20:37 net: ccs002.xreflector.net resolve error, retrying
08:20:37 net: sharkrf.link resolve error, retrying
08:20:37 net: ccs002.xreflector.net resolve error, retrying
08:20:37 net: sharkrf.link resolve error
08:20:37 nvmm: net ip address report retry 3/10
08:

I'll address your last communication shortly

jbradshoemaker

Hi Brian,

Hopefully that was of some help. Your statement seems to be a stream of consciousness ending in a need to bring in the ISP.

Given this has occurred with others geopolitically separated (and thus using different ISPs), all using the Eero mesh network it would seem to not be the ISPs unless Eero somehow operates differently with them...and this still ends up being an Eero/OS3 issue.

If you emailed Brandon and possibly worked with one of their programmers the two of you could likely troubleshoot this better.

Regardless, Let me know what I need to do next and thanks for your continued help.

Brad

Tyrbiter

What I see in your log output is that every attempt to lookup an IP address fails with:

net: resolve error

or

net: resolve error, retrying

From your previous post where you used your laptop to look up americalink.radiotechnology.xyz and it gave you a totally different IP address from what I see using Google's DNS servers, I have to say that I think something is wrong with the DNS setup on your Eero system, even when you set a different DNS it seems that something within your network is intercepting port 53 and then returns IP addresses that make no sense.

For instance, when I look up ccs002.xreflector.net I see this:

;; ANSWER SECTION:
ccs002.xreflector.net. 21578 IN A 176.10.105.246

sharkrf.link gives:

;; ANSWER SECTION:
sharkrf.link. 3599 IN A 216.239.38.21
sharkrf.link. 3599 IN A 216.239.34.21
sharkrf.link. 3599 IN A 216.239.36.21
sharkrf.link. 3599 IN A 216.239.32.21

img.sharkrf.com gives:

;; ANSWER SECTION:
img.sharkrf.com. 2308 IN CNAME ghs.googlehosted.com.
ghs.googlehosted.com. 45 IN A 216.58.213.115

connectivitycheck.gstatic.com gives:

;; ANSWER SECTION:
connectivitycheck.gstatic.com. 128 IN A 172.217.169.35

whereas your setup never resolves any of these hostnames.

If Eero are claiming that they can see nothing wrong then I have to say that I don't see how their technical support can call itself that.

I'm really trying to help here, but I have little to work with. What I do see is a lot of Google hits for a search for "eero dns lookup failure" and to my mind that isn't a good sign.

At this stage I can't help much with Wireshark because it will take time to set up and isolate the OS3's traffic but the log you sent points pretty conclusively towards there being no configured DNS server that can resolve pretty much anything at all.

HTH

jbradshoemaker

Tyrbiter

Brian,

Thanks for unpacking your comments. I'll go back to Brandon (Eero) who has been reading the notes on this site periodically.

Not being an IT guy I only partially understand even your clearer version.

You had suggested I override the DNS servers and this didn't make a difference. I have also changed DNS servers at home a few times. All roads end up unresolved.

Maybe the extra notes will be of some help to Eero. Maybe. Earlier you showed me the settings page for your network, it showed the DNS server as being inside your network, the same IP address as the router/AP/Eero I assume. That means that the DNS packets should be forwarded somewhere by the device at that IP address, normally DNS requests are sent to either your ISP's DNS servers or Google or OpenDNS (according to your choices) and the only thing that happens is there is an address translation from your LAN to the WAN address (your external IP address as seen by the outside world) because internal addresses are unroutable on the wider internet by design. So what I think is happening is that the DNS proxy or cache on your local network is not passing on the request, instead it is either blackholing it or is only looking in its cache which appears to be empty of anything outside your LAN.

I really feel for you on this, for some reason Eero appear to have a DNS setup that behaves strangely and as I don't have personal experience of their products I can't really offer any further assistance.

jbradshoemaker

Thank you for your efforts - If it is resolved, a further post will be made. As for now it remains unresolved (for others encountering similar problems with a mesh network)

jbradshoemaker

Hi Brian,

They have escalated support to a tier 2 person and he, Matt, is asking the following.

"The information we're looking for is this:
What URLs is the device trying to resolve in order to establish and confirm internet connectivity?
e.g. ccs002.xreflector.net from your forum post
Expected DNS record results for the above URLs
for instance, A records, cnames, etc
This information will help us isolate where the breakdown in communication is occuring. At the eero-device level, at the eero gateway level, or at the eero-ISP level."

Frankly I have no idea how to respond, and if you do it might help move this forward.

Thanks again,

Brad

Tyrbiter

OK, so I have chopped out all except the resolution failures in the log you posted.

You can see that some servers that don't resolve are those needed for radio purposes and others are for checking connectivity (connectivitycheck.gstatic.com) or for providing a link to the OS3's IP address (sharkrf.link)

08:10:16 net: americalink.radiotechnology.xyz resolve error
08:10:16 net: americalink.radiotechnology.xyz resolve error, retrying
08:10:16 net: americalink.radiotechnology.xyz resolve error, retrying
08:10:16 net: americalink.radiotechnology.xyz resolve error, retrying
08:10:16 net: americalink.radiotechnology.xyz resolve error
08:10:16 net: americalink.radiotechnology.xyz resolve error, retrying
08:10:17 net: americalink.radiotechnology.xyz resolve error, retrying
08:10:17 net: americalink.radiotechnology.xyz resolve error, retrying

08:16:30 net: ccs002.xreflector.net resolve error
08:16:30 net: connectivitycheck.gstatic.com resolve error, retrying
08:16:30 net: ccs002.xreflector.net resolve error, retrying
08:16:30 net: connectivitycheck.gstatic.com resolve error
08:16:31 net: sharkrf.link resolve error, retrying
08:16:31 net: ccs002.xreflector.net resolve error, retrying
08:16:31 net: sharkrf.link resolve error, retrying
08:16:31 net: ccs002.xreflector.net resolve error, retrying
08:16:31 net: sharkrf.link resolve error, retrying
08:16:31 net: ccs002.xreflector.net resolve error
08:16:31 net: sharkrf.link resolve error
08:16:31 net: ccs002.xreflector.net resolve error, retrying
08:16:32 net: ccs002.xreflector.net resolve error, retrying
08:16:32 net: ccs002.xreflector.net resolve error, retrying
08:16:32 net: img.sharkrf.com resolve error, retrying
08:16:32 net: ccs002.xreflector.net resolve error

08:20:35 net: ccs002.xreflector.net resolve error

08:20:36 net: ccs002.xreflector.net resolve error, retrying
08:20:36 net: connectivitycheck.gstatic.com resolve error, retrying
08:20:36 net: ccs002.xreflector.net resolve error, retrying
08:20:36 net: connectivitycheck.gstatic.com resolve error, retrying
08:20:36 net: ccs002.xreflector.net resolve error, retrying
08:20:36 net: connectivitycheck.gstatic.com resolve error, retrying
08:20:36 net: ccs002.xreflector.net resolve error
08:20:36 net: connectivitycheck.gstatic.com resolve error
08:20:36 net: sharkrf.link resolve error, retrying
08:20:37 net: ccs002.xreflector.net resolve error, retrying
08:20:37 net: sharkrf.link resolve error, retrying
08:20:37 net: ccs002.xreflector.net resolve error, retrying
08:20:37 net: sharkrf.link resolve error, retrying
08:20:37 net: ccs002.xreflector.net resolve error, retrying
08:20:37 net: sharkrf.link resolve error

All of the hostnames shown above resolve to IP addresses using Google's DNS servers, someone in L2 support at Eero should be able to find this out quite easily.

Hope this helps you to get an answer.

HamScanMan

Just upgraded to Eero (7 devices). I got 43 other devices connected, got to my Openspots (3 x V2 and 1 x V3) - Nothing. Cannot connect.

This is the final BS I am going to put up with. OS2 WiFi was crap at best. OS3, not much better.

If these device cannot work with a new Wi-Fi - They are gone. Back to good old Pi-Star.

HamScanMan

Did anyone ever find a solution to Open Spot 2 and 3 connected to Eero Mesh Wifi?

I just brought up my Yeasu Wires-X node, added the required ports forwards..... No go with Eero either!

HamScanMan

Circling back.... After installing the Eero system, my ISP made a change which I did not know. I replaced all the older routers and networking equipment this morning and still could not get the OpenSpots working.

That is when I dug a little deeper, the ISP had be on a super fast but incorrectly provisioned link. I got that changed and my OpenSpots (at least two of them) are on-line and seem to work.

Equally, my Wires-X node is now also working. It apparently requires a Public IP address and the ISP network segment I was on, did not have that.

At this point, the Eero system is staying, as are the OpenSpots

w9fyi@me.com

Hi folks, I've still had issues with my OS3 not being able to connect to my Eero system. I can get it to connect to my t-mobile home wifi router which is also a mesh system, but I'd like it to be on my Eero system, as the ISP that it is linked to has better latency etc. Is there anyway I can get logs, and other data to send to Eero support from the device? I'm sure they are going to want to see what kind of errors the OS3 gets when it tries to get out to the internet, and why traffic is being blocked. I'd love to have some logs to upload if possible. thanks for any help,
justin-ai5os

« Previous Page Next Page »