Losing access to devies when adding VLAN tag

I am trying to migrate from TPLink ex820 router to the route 10.

When ever I set up the WAN1 port with a VLAN tag I instantly loose all my devices in my local controller.

This means I can’t debug the the issue.

As far as I can see all ports are on VLAN 1.

It seems I have to have a working internet connection to access my local controller?

@mikedidthis My first question is whether your ISP actually requires a VLAN tag in order to operate. Most ISPs do not. Are you trying to create another local VLAN, or can you describe what you are trying to accomplish first?

Yes my IP requires the following:

Dynamic IP
VLAN 911
DNS 8.8.8.8 and 1.1.1.1

I want to use the WAN1 to access fibre internet via an ont box.

We do have a local controller option with our Control hardware appliance, if you want to be able to configure locally.

I’d like to double check what you are saying though. You have Internet access while you are setting up Route10 (i.e. via 192.168.1.1 or mobile app), but then you lose connectivity after you set it up on VLAN911? If that is true, can you set it up using the standard VLAN1 first, and then invite me to understand why VLAN911 isn’t allowing access?

I have tried this with both the local and cloud based controller.

I currently have an ISP provided router that I am connecting the route 10 to (as I can’t set it up without internet access)

Once the route 10 is setup and I have access I want to remove the ISP provided router. I update the WAN1 vlan id to 911 and swap the cables.

Once I do this I lose access as there is no active internet connection.

I guess more than half of Europe do Jeff - so please keep that on your guys’ radar!
Also, PPPoE is very common here.

Do you know if your ISP also requires the MAC address of the Route10 to match your current router?

If they don’t, can you follow these steps:

  1. Set Route10 up behind your normal router
  2. If you don’t have an SFP RJ45 module, set one of your LAN ports up as a WAN port. To do this, click on the port, set its mode to WAN, and select WAN2 for the WAN. We will use this WAN connection later when VLAN911 causes connectivity to fail.
  3. Shift-click the Route10 name in the Network tab to open the terminal
  4. Run command: touch /cfg/.persistent.log
  5. Run command: sync
  6. Run command: reboot
  7. Configure the Route10’s WAN for VLAN911 and wait 30 seconds
  8. Swap WAN cables to your Route10 and power cycle the Route10
  9. Wait 2 minutes
  10. Plug WAN cable back into your existing router, and plug the Route10 LAN port that you configured as a WAN connection into your main network.
  11. Route10 should come back online in manage.alta.inc
  12. Shift-click the Route10 name again
  13. cat /var/log/messages* and copy/paste the output via direct message to me.
  14. You can also use ssh to download these logs, if that works better for you
1 Like

@TeWe Don’t worry, we fully support VLANs on WANs, and many others are using them successfully.

1 Like

Sent logs via message. Thanks again for the help