Haven’t had a great experience thus far, but reaching out to the community in hopes someone else has had a similar enough issue that I can get this resolved.
Background story:
I’ve had the Route10 set up in an extremely basic configuration and running the home network previously. I was not pleased with the Alta labs collecting telemetry data, with no option to opt out. I switched back to my pfSense setup so the household could continue to have an internet connection, in hopes this would be addressed. Unsurprisingly, the post about this was removed with only a comment that it would be addressed in the near future, which I’ve yet to see.
After the pfSense box was put back into commission, I set up a test network for the purpose of restricting what content was farmed from me. This also allowed me a playground where I wouldn’t disturb the rest of the household while I learned this new platform. I took some time away from the Route10 until I seen the features were more fleshed out. I see now Wireguard has been added, along with IDS/IPS capabilities, and wanted to test those features out. The Route10 sat on a shelf in the closet until recently.
Issue at hand:
Upon recommissioning the Route10, it would not connect to the internet. I was able to access it on 192.168.1.1 but after going through the setup prompts, I was left at the final screen telling me it was “Taking longer than usual.” At first I assumed it would be some double NAT issue, but after connecting a third router I was able to confirm this was not the case. I performed a power-on-reset assuming it must be hanging on to some of my configuration from when this device was at the head of my network. After this reset, I only get flashing red lights with no access to the device on 192.168.1.1. I have also tried again putting this device at the head of the network. Flashing red lights. I performed another power-on-reset with nothing connected but the WAN raw off the modem. Flashing red lights, no ports are lit.
We can do our best here to help, but if you are stuck you can also call into support during the week.
The telemetry thing is a tough one… Alta is first and foremost designed to be an easily cloud managed system.
Can you elaborate on that one? Literally everything except the DDNS address creation is local when using the local controller. Even your account you create is local to the controller. Are you seeing something different with Wireshark or something similar?
Which mentions the telemetry, sadly when trying to have discussion about this, along with @ZamorakWasRight I too had my posts deleted and the thread locked.
I also have been waiting with baited breath for the Trust Site.
Additionally, along with what Hefty has linked, if you pay close attention to the login screen for the cloud controller prior to making an account it will say that account doesn’t exist. Simply making an account only for the local controller, that message will disappear on the cloud login, saying the information provided is incorrect. They are absolutely not separating the two.
Other things discussed were just the dependency on Alta, for DDNS/Email Notifications/Dumps being shipped to Jeff’s private domain with no opt-in or notifications too.
Thanks for linking the trust site, I hadn’t seen that.
Thanks for linking that, I don’t think it applies to me though.
Note: These firewall changes are only necessary if you’re using the free cloud controller. If the Alta Control Appliance or self-hosted options are in use, these changes are not necessary.
Understood. Has any explicit blocks of the domains listed in the other thread been attempted? I could understand why it would be there by default for first setup.
Out of interest if you stick your connection back up via pfsense, and go back to double NATing (plug ALTA WAN into your LAN), do you see the ALTA device get a DHCP lease ?
After leaving it powered down for about 20 minutes, I plugged it back in. Port lights are back, logo is white at first but goes flashing red after a while. 192.168.1.1 shows in pfSense ARP Table, but incomplete for the MAC
From my experience, flashing red light means the device thinks it has set up properly and it is trying to reach the internet to perform a firmware upgrade and it is unable to perform one. The red light blinking is specifically related to inability of the device to either check for a firmware upgrade or not able to do a firmware upgrade.
Also I documented pain points I had during setup process and what I did to fix them. It is posted in this forum.
Yes, thank you. I’ve actually been following your posts. Specifically here. Many of the issues you (and I) have with the platform are outlined articulately, not only for the community, but for the Alta team as well. It is off-putting seeing you still get generic responses like “others aren’t having that issue” and “it’s for user experience.” As if we aren’t the users having a bad experience. That aside…
I’ve followed Jeff’s response in the post linked above. I cannot get past step 3.
If you are still hung up, can you please share a video of what problem you are seeing? I only mention that “others aren’t having that issue” because we’ve seen rapid adoption of the product, but we’re happy to look into any gotchas that might slow anyone down. It is a new product type, which is why we’ve provided Youtube videos and a built-in setup wizard to make it as painless as possible.
