Route10 connects to ISP but all other devices offline

Routers
1

Received my Route10 from Amazon today. I have been unable to setup this device and am on the verge of returning. Asking for help here before I give up.

Current setup:

  • pfSense (192.168.2.x subnet)
  • Alta AP6-PRO (has been solid)
  • TP-Link POE switch
  • AT&T Fiber Modem (Arris BGW320-500 on 192.168.1.x subnet) - requires IP Passthrough to allow for downstream router to get ISP IP address. This has been working without any issues with pfSense. I added the WAN1 port MAC address in modem for IP Passthrough configuration:

Screenshot From 2024-10-23 23-11-55
Screenshot From 2024-10-23 23-11-55974Ă—600 116 KB

I followed all 3 methods described in this video.

  • Bluetooth setup simply does not work. App never sees the Route10.
  • I connected to the route10 via ethernet and accessed the setup page on 192.168.1.1. Connected to ISP successfully. Route10 becomes visible in controller and shows “connected” and performed a firmware update.

This is where trouble begins. the Alta AP6-PRO will now show as disconnected and never receives an IP address. Confusingly, the same applies to some devices connected via ethernet but not others . I’ve tried factory reset and have repeated the setup multiple times with no success. On some occasions, after successful ISP connection, the Route10 itself will go offline and display “disconnected”. I’ve attempted to change the subnet on the Route LAN1 port to 192.168.2.x to match my previous setup to no avail.

Reverting back to pfSense (and updating fiber modem IP Passthrough) and AP6-PRO immediately connects and all is normal again. Feedback on what I may be doing wrong is greatly appreciated.

2

Are you able to confirm that the route10 is indeed getting the public IP from the Arris BGW and not a 192.168.1.x address?

3

Have you had any luck vaheh? If not it might be worth reaching directly out to support.

4

Yes, I’m able to get a public IP address from ISP.

5

Can you share a screenshot of your Route10 interface layout? Do you get an APIPA (169.254.x.x) if you plug a laptop directly into the LAN port of the Route10?

1 Like
6

Just throwing this out there, is it possible you have multiple DHCP ranges being given out? The devices offline are grabbing a scope that’s not working…and would account for why some devices are working and others aren’t.

1 Like
7

I think this may have been the issue. I factory reset both the Route10 and the AP. Deleted my site from the controller and started fresh. Connected the Route10 to existing LAN via the LAN1 port. Configured the WAN port and changed the DHCP settings on LAN1 to 192.168.2.x. The AT&T modem (I really hate this thing) requires DHCP or fixed IP allocation for IP Passthrough and it already has 192.168.1.x subnet to itself (the Route10 is assigned an IP Address in this subnet which the modem then uses for public IP Passthrough). After this config change, I replaced pfSense with the Route10 on the network an all seems to function correctly.

EDIT: Spoke too soon. While things seemed to work initially, devices (both wired and wireless) are behaving in strange ways:

  • Controller displays IP address but device is not accessible
  • Controller displays no IP address but device has connection
  • Controller displays a normal 192.168.2.x ip address but device shows 10.188.94.179 with a gateway address of 10.188.0.1 and still has a connection.
  • Devices (like Nest Thermostat) connect initially and have an IP but lose internet access after a short period of time and are no longer able to connect to wifi (device continues to display “invalid password”).
1 Like
8

It seems the Fallback Upon Failure feature was tripped (which is where the 10.188.x.x addresses are coming from).

I’d like to get invited to the site so I can review your settings. I’ll DM you the email address to invite.

9

@vaheh are you still having issues? We’d really like to take a look, if possible.