Changing ISP - Route10 configuration

Alta Control
,
1

Hi all,

I’ve been using the Route10 with the cloud controller since late last year and it has been working fine for my needs. However I need to change ISPs in the next week or so and am wondering how I would re-configure the Route10 without an internet connection? Is this something that would require a full reset like this post suggests?

In the past I’ve used a basic ISP supplied router and was able to login via the local gateway e.g. 192.168.0.1, to change ISP login details and such during the changeover. But I can’t seem to find how to do the same through the cloud controller. I could learn what to do via SSH but I’d rather a simpler solution. Would setting up a local controller be useful in this case?

2

What I’ve generally done is entered in the new ISP settings into the cloud controller right before switching over. That’s assuming the new ISP is making their service available while you still have connectivity with the old ISP.

So for example, if there was a static IP being assigned by the ISP and that was changing with the new ISP, I’d enter in the new IP just before the switch. This would allow the new setting to propagate to the router and be ready for connecting to the new ISP. This, of course, would prevent the router from working with the old ISP but that hopefully shouldn’t be a big deal assuming the new ISP’s equipment is setup and ready to go while you’re still getting service from the old ISP.

Otherwise that is a case where the local controller should be handy. The other option is resetting the Route10 and adding it back to the same site with the new settings. After a reset there’s a web interface available on the Route10 for entering in ISP settings for initial setup or it can be done through the mobile app. You’d want to make sure the new ISP settings are already set in the cloud controller in that second scenario as you would run the risk of getting the router online and then it dropping back offline because it pulled in the old ISP settings again from the cloud controller.

3

In my case it’ll likely be the second scenario, not having a concurrent connection with the two ISPs. I’ve managed to locate the WANs section in the cloud controller. It appears my current ISP connection is via DHCP which doesn’t seem to require a username and password? Does this mean if my next ISP also uses DHCP I should be ok with not changing anything and it’ll automatically switch over?

Screenshot 2025-09-16 at 23.27.42
Screenshot 2025-09-16 at 23.27.42690×910 38.1 KB

I think in the past I have had ISPs who have given me PPPoE username and passwords which I’ve had to enter manually. I presume I’ll have to use reset method if that is the case this time around.

W.r.t. a local controller I could try to get one up and running but I’ve read that the Docker container is not persistent and the migration process isn’t easy? I have some VLAN, firewall rules, and static IPs set-up that I’d rather not do again manually. Does anyone have experience they could share? Or an update on the transfer process?

4

Get your SSH key and access operational posthaste before then.

5

On top of what @Beaker said as a just in case, I’d recommend reaching out to your new ISP to confirm what they’re looking for. If it’s DHCP then it should just be as simple and connecting the Route10 to their equipment and it obtaining an IP address.

6

Just confirming this is what I insert into /etc/config/network? As per ChatGPT:

config interface 'wan'
    option ifname 'eth0'
    option proto 'pppoe'
    option username 'your_pppoe_username'
    option password 'your_pppoe_password'
    option mtu '1492'

But examining my /etc/config/network the current config seems to be:

config interface 'wan'
        option ifname 'eth3'
        option metric '200'
        option dns_metric '200'
        option proto 'dhcp'
        option norelease '1'
        option ipaddr '114.XXX.XXX.XXX'
        option peerdns '1'

Does that mean I should use eth3 instead? I am using WAN1 as my WAN port so am I correct to assume WAN1 = eth3? Thus:

config interface 'wan'
    option ifname 'eth3'
    option proto 'pppoe'
    option username 'your_pppoe_username'
    option password 'your_pppoe_password'
    option mtu '1492'
7

Ordered by ethX, I believe it is:

From the rightmost RJ45 going left, for RJ45 ports:

  • eth0: L3
  • eth1: L2
  • eth2: L1
  • eth3: W1

and then start over from the SFP port to the right and going left, for SFP+ ports:

  • eth4: W2
  • eth5: L4

Or, from left to right on the switch:

RJ45 ports:

  • W1: eth3
  • L1: eth2
  • L2: eth1
  • L3: eth0

SFP+: ports:

  • L4: eth5
  • W2: eth4

So, yes, should be correct:

Edit: Adding a more compact lists for reference. From left to right:

  • W1: eth3, RJ45
  • L1: eth2, RJ45
  • L2: eth1, RJ45
  • L3: eth0, RJ45
  • L4: eth5, SFP+
  • W2: eth4, SFP+
8

In the end my new ISP was using DHCP after all. So I did not have to break out the SSH / change config. Changeover went very smoothly. Didn’t notice it at all. Thanks for the help everyone.