Flashing red lights

Also, looking back at your first post here, the red lights after performing a power-on-reset (holding reset while powering up) indicates that the Route10 cannot get an Internet connection on the WAN port while attempting to download the factory firmware. Can you confirm that the connection you are giving the Route10 in this mode offers valid DHCP + Internet?

Following the video for method 2 and 3, I am unable to setup the Route10.

Yes.

Hardware configurations attempted:

A) ISP → Arris SB8200 → WAN → pfSense → LAN(10.11.11.X/24)
No issues, household has internet connection.

B) ISP → Arris SB8200 → WAN → pfSense → LAN(10.11.11.X/24) → Asus RT-AX86U → LAN(192.168.1.X/24)
No issues, household has internet connection on both subnets.

C) ISP → Arris SB8200 → WAN → pfSense → LAN(10.11.11.X/24) → Route10
Connection on 10.11.11.X. Route10 LAN no connection.

D) ISP → Arris SB8200 → WAN → Route10 → LAN(192.168.1.X/24)
No connection.

All use WAN1 on Route10, single client on LAN3.

What I am currently able to consistently replicate in all hardware configurations with Route10:
Scenario 1) Route10 powered off, plug in power. Port lights active, logo “breathing” for a moment. Logo goes white. Device is accessible on 192.168.1.1, load setup page in Firefox/edge/chrome. WAN1, DHCP/Auto, No tagging, No MAC, No link speed. “Taking longer than usual” message. No connection even if left for 12+ hours.

Scenario 2) Route10 powered on, hold reset ~10seconds. Logo flash blue, then “breathing.” No port lights, orange PoE lights on LAN1/2 active. Flashing red logo after some time. Not accessible on 192.168.1.1.

Scenario 3) Route10 powered off, hold reset while plugging in. Release reset when logo starts "breathing "blue. No port lights, orange PoE lights on LAN1/2 active. Flashing red logo after some time. Not accessible on 192.168.1.1.

@ZamorakWasRight Can you please plug the Route10 WAN into your PfSense LAN network and hold the reset button down while turning it on? If you’d like to update the Route10 before using it (which appears to be the case) then you will need to have a working Internet connection that the Route10 can use to update first. As long as you do not get a red flashing light, then you can assume that the Route10 is on the latest factory firmware.

After that, there are some ISP idiosyncrasies that you will likely need to deal with, the most common being that many cable ISPs will not allow a new router MAC unless you give them a call. Or you can clone the WAN MAC address of your PfSense on the Route10, so that it can get an Internet connection from your ISP.

Yes. Scenario 3, with hardware configuration C has been attempted.

I am able to access Internet through 3 separate routers, all have unique MAC addresses. None of which I’ve had to call my ISP for. To my knowledge that was only required when I set up the modem.

Edit - Also to note, the Route10 has ran at the head of my network previously, also without interacting with the ISP.

Any chance you can use a less custom router (or less custom config, etc.) as the uplink for the Route10, to make sure that it is getting an internet connection? Do you have any metrics on your PfSense that shows how far the Route10 is getting? To be clear, when resetting the firmware to factory firmware (holding reset at boot) it will:

  1. Obtain DHCP from its WAN1 interface.
  2. Sync with NTP servers (0.openwrt.pool.ntp.org), so that SSL works.
  3. Download and install the latest firmware from dl.alta.inc.

If any of these fails, you will get the red blinking light.

We’ve tested Route10’s recovery on dozens of different routers, but it looks like there is something in your PfSense config that may be incompatible. It would also be great if you can bring it online on some other connection first, make sure that it is updated to the latest 1.3u, and then try to swap it out for your main router.

I am unsure how I can be any more clear than what I have posted already. Even with pfSense removed from the configuration, I am able to consistently reproduce each scenario stated above. Route10 was working perfectly with only my Arris SB8200 modem(no advanced features or routing) in front of it previously. This is no longer working.

We cannot reproduce the issue you’re seeing anywhere, thus I am asking for more information.

Based on your ARP table, are you expecting the Route10 to show up as 192.168.1.1 there? If connected as expected, it should show up as a DHCP client in the DHCP client table on your router. You’ll also need to make sure that your LAN subnet (that you connect the Route10 WAN into) is not 192.168.1.x. I guess it’s possible there’s something actually wrong with your specific device, but you would need to reach out to support for help with that.

Yes, as that should be the out of box experience of the Route10 attempting to setup, correct?

I’m left scratching my head here, and maybe I just need to be set straight. To my understanding, in regards to a scenario where pfSense is utilized, the DHCP client table is only going to show devices that are being served DHCP. The ARP table will show devices will show IPv4 hosts trying to communicate to/through the firewall. As we are hoping for Route10 to host DHCP to its own subnet, I assumed we would would not want pfSense involved in that.

Interestingly, when pfSense hosts DHCP for the subnet 192.168.1.x we do see a different outcome. First, the Route10 shows in the DHCP client table @ 192.168.1.1, with a MAC address this time. I can pull up the setup page in the browser, eventually leading to “taking longer than usual.” Second, the Route10 creates another subnet 192.168.0.1. The PC connection on LAN3 instantly grabs 192.168.0.10, with access out to internet, no setup page needed. Going through the setup page to verify, the process is successful within seconds. Control grabs 192.168.0.11, with all setup pages being reachable. I ran out of time here to keep investigating, but I will have some time later this weekend.

Very interested in anyone’s thoughts here.

I’m trying to break up this process into two steps:

  1. Ensuring that Route10 is on the latest firmware
  2. Proceeding through the normal Route10 setup process

From your description, it looks like Route10 is on a recent enough firmware that it is resetting its LAN subnet to 192.168.0.x, so you should be able to skip step 1.

One difference from previous Route10 releases is the use of the 192.168.0.x subnet instead of 192.168.1.x (if the Route10 detects 192.168.1.x on its WAN). Have you tried visiting 192.168.0.1 or setup.lan / setup.localdomain when you are behind the Route10 in its unconfigured state, and can you ping through it in that state? If so, the Route10 has an Internet connection in that state, and so whatever configuration you are making in the wizard must be different than the standard VLAN1/DHCP/auto-negotiation config that gave the Route10 its connection in the first place.

Is this not verification of that? Yes it can ping.

In regards to the setup pages for Route10? I selected the same prompts every time.

Have you tried just adding it to a site in manage.alta.inc or the app without going through the wizard? Does it go disconnected in that case?

At this point I am stumped.

With pfSense serving DHCP on 192.168.1.0/24, I was able to access the Route10 on 192.168.0.1, controller on 192.168.0.11 just like stated above. I set it up as normal, attached the local controller as normal. Control was on 1.0h, Route10 on 1.3p. Updated to 1.0t and 1.3u respectively. I changed the subnet to 192.168.1.0, and stopped pfsense from serving DHCP. Rebooted and everything is on the 192.168.1.0 subnet working just fine.

I am now able to use the Route10 at the head of the network, as well as behind pfSense without issue. The only thing I’m noticing is that it’s running about 10C hotter than I’ve seen it run before. <1% CPU load, 7-8% memory usage, essentially idle.

Power-on-resetting immediately reproduces all issues stated in the thread. No real resolution, sorry for anyone else having these issues. Maybe a help if someone else runs into this specific issue.