Openspot3, and EEro, and/or Mesh routers?

w9fyi@me.com

Hi there,

I'm trying to get my Openspot 3 to properly connect to my Eero mesh wi-fi router, and am not having much luck with getting the device to actually see it's way to the internet. I've taken the following steps:
•Created an ip reservation for the Openspot 3 so that it will have a specific place to connect so that necessary ports can be opened..
•Gone to the connectors page, and tried to find all relevant ports that are used and setup these ports to stay open in the Eero router.
•enabled a 2.4 GhZ only network so that the Openspot 3 can connect.

The Openspot 3 does connect to my mesh network, but I continue to get an internet unreachable message regardless of what connector I use. Happy to send any logs/diagnostic information if needed.
Thanks,
Justin

HA2NON

Try turning off any firewalls. If the status LED is blue/red then it means that the openSPOT3 is connected to a Wi-Fi network, trying to connect to the selected server, but it can't because there's a problem with the internet connection. This error can be caused if the router, network, or the internet service provider is using a proxy or some kind of traffic filtering which blocks the openSPOT3 from connecting.

w9fyi@me.com

OK... we'll try and see if we can make some firewall changes. Thanks for your help...

jbradshoemaker

Norbert,

Justin (the other respondent on this thread) and I still cannot access the internet through our home wifi. We see that we are connected to the Eero Wi-Fi network - but cannot access the internet with the OpenSpot3.

In addition to my previous attempts outlined in the email included below, I have done many additional hard resets - annoying - I have overrode the DNS servers and changed to 3 different ones. I can access through mobile but only download 28% of each file (firmware and callsign). The notion that the ISP cuts it off due to overtime is likely incorrect as the firmware file is 1.56mb and the callsign is about 8. 25% of 8 is 2 which would therefore be sufficient to download the whole firmware file.

I have read as much Eero info as possible - Also note that I have previously had it working using the same ISP - so it is unlikely to be them as the one thing in common between Justin, I and the FB people is Eero.

Could you please contact Eero as you have the information they would need to jointly resolve it. Your clients cannot do this on our own.

If you believe that your current firmware update will resolve this issue please email me jbradshoemaker@yahoo.ca - and Justin w9fyi@me.com the file with instructions on how to manually install. You may want to look at the Facebook group for others in need of support.

As a reminder - I emailed you the following on Jan 17th with your response included
-------------------------------------------------------------------------------------------
"Was using my OS3 w/o issue and then one day it wouldn’t connect to the internet - most of the time.
Did a factory reset - no change after setting up. Also won’t upgrade firmware or callsigns- immediately.

I am using an Eero mesh network and figured they added security so I messed around with the firewall for a bit - I ‘allowed’ sharkrf.com - I disabled advanced security and ad blocking. I read a shark forum saying port opening/ forwarding was not required.

So I went in a different direction to test if it was the router/isp or their settings that was the problem.

Ran it via my mobile and - good news - it worked. But when trying to upgrade firmware (hoping a patch would resolve it) or callsigns - even though both are significantly different in size, they fail at 27%. Retried several several, several times in different ways w/o success."

Response "Note that updates are downloaded from a CDN, and not from sharkrf.com. Your firewall/router (or ISP with a proxy) is probably does not allow long duration connections. Try using a different internet connection to update your openSPOT3. We can also send you a firmware file for manual upgrade if you want."

HamScanMan

Did this get resolved and if so, how?

Its generally common courtesy to follow-up on a thread with the closure details so others can learn from it.

jbradshoemaker

No - It was completely ignored - thought I was polite - I and Justin cannot conect through our mesh networks.

Seemed like a simple request - IE. you have the information about how Openspot3 works (I don't), please contact Eero as they have the information about what might be stopping it from connecting.

I suspect the next step is for me to contact eero and ask them to contact SharkRF - they seem professional.

I still can't update to the most recent firmware nor add the new callsign database - even though he said he's send us the link to do it directly. - SharkRF doesn't seem interested in providing support.

Btw - If I ever resolve this I promise you that I will return with the solution - Agree that leaving things hanging helps no one.

HA2NON

Sorry, but we don't know what causes your issue with your router/ISP.

Tyrbiter

Given that the update process uses a completely standard http or https connection then it makes no sense that a home network would not allow it unless the correct gateway address is not being given out by the DHCP service on your router/AP.

Does the EERO unit allow you to see which wireless devices are connected? Does it use a separate router or is this all part of the mesh system?

If you can connect to the internet from a laptop via a WiFi network then posting the details of the ipconfig might help us to understand why things don't work for the OS3.

jbradshoemaker

Hi Brian,

Eero does allow me to see which devices are connected. Openspot3 is connected to my kitchen hub 2.4 Ghz (at the moment as is my iMac 5Ghz ]& iPhone 5Ghz) - a few months ago it worked flawlessly - something has changed in the interim. Using http://192.168.7.210/#net I can see the status and make changes to OpenSpot3. The one constant is, the status reads "internet connection error".

Hope this helps,

iMac:~ jbradshoemaker$ ifconfig
lo0: flags=8049 mtu 16384
options=1203
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=201
gif0: flags=8010 mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863 mtu 1500
options=50b
ether 10:dd:b1:e2:b7:39
inet6 fe80::47e:731:df26:16ff%en0 prefixlen 64 secured scopeid 0x4
inet 192.168.7.54 netmask 0xfffffc00 broadcast 192.168.7.255
inet6 fdad:50f7:a6d3:1 :1891: 8d53:ed05:f076 prefixlen 64 autoconf secured
inet6 fdad:50f7:a6d3:1 :207b: 3a8d:547e:443b prefixlen 64 autoconf temporary
inet6 2607:f2c0:eda6:361 :1404: 2c5a :1343: 92df prefixlen 64 detached autoconf secured
inet6 2607:f2c0:eda6:361:9885:65ea:f217:48e3 prefixlen 64 detached autoconf temporary
inet6 2607:f2c0:eda6:369 :1c71: f89a:eeeb:3637 prefixlen 64 autoconf secured
inet6 2607:f2c0:eda6:369:fc87:80c3:8cb:4b9c prefixlen 64 autoconf temporary [/b]
nd6 options=201
media: autoselect (1000baseT )
status: active
en1: flags=8863 mtu 1500
options=400
ether ec:35:86:4a:4f:b8
inet6 fe80: :106c: 684e:56fc:404b%en1 prefixlen 64 secured scopeid 0x5
inet 192.168.7.58 netmask 0xfffffc00 broadcast 192.168.7.255
inet6 fdad:50f7:a6d3:1:bd :17be: ef70:b225 prefixlen 64 autoconf secured
inet6 fdad:50f7:a6d3:1:e12c:b2e4:bb4b:483d prefixlen 64 autoconf temporary
inet6 2607:f2c0:eda6:369 :149a: 8e91 :2771: 39f1 prefixlen 64 autoconf secured
inet6 2607:f2c0:eda6:369:9007:6c50 :1d90: 171 prefixlen 64 autoconf temporary
nd6 options=201
media: autoselect
status: active
p2p0: flags=8843 mtu 2304
options=400
ether 0e:35:86:4a:4f:b8
media: autoselect
status: inactive
awdl0: flags=8943 mtu 1484
options=400
ether 0e:d9:1c:c4:09:a5
inet6 fe80::cd9 :1cff: fec4:9a5%awdl0 prefixlen 64 scopeid 0x7
nd6 options=201
media: autoselect
status: active
en2: flags=8963 mtu 1500
options=460
ether 82:0d:62:58:53:00
media: autoselect
status: inactive
en3: flags=8963 mtu 1500
options=460
ether 82:0d:62:58:53:01
media: autoselect
status: inactive
bridge0: flags=8863 mtu 1500
options=63
ether 82:0d:62:58:53:00
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x0
member: en2 flags=3
ifmaxaddr 0 port 8 priority 0 path cost 0
member: en3 flags=3
ifmaxaddr 0 port 9 priority 0 path cost 0
nd6 options=201
media:
status: inactive
utun0: flags=8051 mtu 1380
inet6 fe80::7343:9252 :168d: 997f%utun0 prefixlen 64 scopeid 0xb
nd6 options=201
utun1: flags=8051 mtu 2000
inet6 fe80: :2e6d: f1be:bb56:9455%utun1 prefixlen 64 scopeid 0xc
nd6 options=201
utun2: flags=8051 mtu 1380
inet6 fe80::a20a:fd72:d42b:cec%utun2 prefixlen 64 scopeid 0xd
nd6 options=201
utun3: flags=8051 mtu 1380
inet6 fe80: :24d5: 90fc:7b02:2b75%utun3 prefixlen 64 scopeid 0xe
nd6 options=201
utun4: flags=8051 mtu 1380
inet6 fe80::4bdf:86a4:fe4a:2a97%utun4 prefixlen 64 scopeid 0xf
nd6 options=201
utun5: flags=8051 mtu 1380
inet6 fe80::a90c:819d:6aea:2e95%utun5 prefixlen 64 scopeid 0x10
nd6 options=201

I can also connect via my cellular hotspot which is fine but does run up my data which is limited in this country. I have been unable to update the firmware or the callsigns using this system as they both crash around 27% complete - odd considering they are substantially different sizes and both quite small. My current firmware is V29 and the stable version is 48.

I use WPA2 which I believe has not changed over the longer period. WPA3 is available.

Thx Brian for exploring this - if there is any other logs I can provide let me know. OS3 logs while on my home network simply say

15:33:01 ysfref: uninitialized
15:33:01 ysfref: getaddrinfo americalink.radiotechnology.xyz error
15:33:01 net-connector: connect retry in 959 ms
15:33:02 ysfref: uninitialized
15:33:02 ysfref: getaddrinfo americalink.radiotechnology.xyz error
15:33:02 net-connector: connect retry in 959 ms
15:33:03 batt: stat: discharge, 79% (3882mV (new) 29C est. 3h50m)
15:33:03 ysfref: uninitialized

Changing reflectors doesn't effect the outcome.

Tyrbiter

Can you post a screenshot of the OS3 network page please, I want to see the current configuration section of the Network status page.

I assume you can get to it with http://192.168.7.210/#net in your network.

jbradshoemaker

As requested

Tyrbiter

OK, so you have a /22 CIDR LAN with addresses between 192.168.4.0 and 192.168.7.254 usable, broadcast address is at 192.168.7.255

I notice that you don't have a DNS override enabled on the OS3, but your only DNS server is 192.168.4.1 which is the same address as the gateway. If the gateway is not forwarding DNS to your ISP's servers then unless it actually runs a DNS resolver it won't see any addresses outside your network.

Try enabling DNS override, this will set 8.8.8.8 and 4.4.4.4 as DNS servers for the OS3 DHCP client. Alternatively look at the EERO setup and see if the network setup is somehow not passing DNS settings or only sends them to certain clients. I think that the EERO expects the router to be in bridge mode so it won't see any servers on the router, which is where DNS might well have been served in the past. I am not a Mac expert or indeed know anything much about EERO.

HTH

jbradshoemaker

Hi Brian,

I tried overriding the DNS settings before as it was an option suggested in the manual. My home DNS settings have also been changed from MyIspDNS to OPENDNS to Google and now to CISCO. At your suggestion I over-road again in the hopes that something has changed. Unfortunately it's still not a go.

Nevertheless, as we have gone through log files and looked at some settings, I now feel satisfied that we tried.

I too am not an expert at Eero and am not sure how to complete your most recent request - at least without getting tech support from Eero - probably my next step.

If you have any other suggestions or areas to consider let me know otherwise let's call it closed. If I find a solution I'll return and post it for others.

jbradshoemaker

Addendum - it appears that the DNS you meant was 8.8.8.8, 8.8.4.4 as that is googlesDNS - I tried this too and it also did not result in a connection.

I also have a windows computer that is used as a standalone for wiresX - might try acceessing Eero and OS3 through this to see if it provides any more usable data. Let me know if ifconfig from this PC notebook would be any more helpful to you.

Tyrbiter

The only other thing I can think of is to install Wireshark on your Windows machine and use that to sniff all the traffic to/from the OS3 over the 2.4GHz WiFi, it's fairly easy to do this as you know its IP address.

Sorry I couldn't be more help, this really should just work.

A quick Google reveals someone suggesting turning off local DNS caching in the EERO settings, you may need to restart the network and the OS3. The person reporting the problem is seeing exactly the same problem you are with the entered DNS servers being ignored and 192.168.4.1 being passed as DNS from DHCP. There is more to it as well, see here:

https://community.eero.com/t/g9hymxk/eero-wont-let-me-set-my-own-dns-servers

HTH

jbradshoemaker

Awesome - I wasn't using DNS caching - but will try turning it off and on. Also will download wireshark and read the thread from the link you provided.

I have put a request into Eero and directed them to these threads as well.

jbradshoemaker

Sooo - now I am befuddled.

Read the article to the end and it seems HomeKit security via Eero was a source of the problem. Since I now recall this issue beginning around the time of this new 'feature' -> I disconnected it. At the same time I turned on DNS Caching - so it could be turned off later. Both required a reboot.

I was not able to connect to the reflector BUT ...the callsign database downloaded in entirety. Thinking we were getting close, I turned off the DNS caching.

Now it won't connect to my home wifi at all (in truth it connects to wifi, then disconnects - never gets internet...repeat)- still connects to my cell.

At the end of the article in the link you sent, the guy spoke to Eero who temporarily disabled their security features on their end (presumably for him alone) and then he was able to operate it. It may be that I have made so many changes, the software may think I am up to no good. Hopefully that solution will work for me.

We must be close,

Thx again.

jbradshoemaker

One more thing.

I set up a guest network on eero which isolates devices and still gives them internet access. Tada - worked like a (broken) charm. OS3 was able to connect to the internet, I just couldn't access the device to change reflectors and such.

So now it is very clearly in the realm of Eero. This information should help them pinpoint the issue.

Thanks again,

Brad

Tyrbiter

Good to hear that you are making progress, these things are rarely simple.

The problem from my perspective is that systems like EERO are designed for the majority but when you want something a little different then they don't support it out of the box. To be honest I don't think openSPOTs are actually even a little different.

Hope you get this fixed soon.

jbradshoemaker

Hi Brian,

Still working son it. One of the suggestions was to update OS3 to the most recent stable firmware.

Is this something that can be done manually and if so could you send me the file and instructions.

I am not able to download it using my cell as it restarts at 27% and while I have been to a couple of hotels and made the attempt, so far it has been unsuccessful
.

Thank you