Hi, i have noticed a problem when I Reboot my router I can’t get a connect back to internet until I reboot the switch. The Switch is connected with 5G CPE to port 5 (DHCP handed IP)
Port 1 Trunk to Mikrotik Router.
Trunkport in router is set to pvid 1. vlan 1= bridge Vlan 1000=Bridge and Trunkport.
My config is:
VLAN 10 LAN
VLAN 1000 WAN
swOS
Port 1 Trunk, Vlan mode strict, only tagged, vlanID 1, vlan header=leave as if
Vlan ID 10 (IVL) add if missing
Vlan ID 1000 (IVL) add if missing
Port 2 Vlan mode strict, only untagged, vlanID 10, vlan header=leave as if (Always strip vlan 10, and not a member vlan 1000 under VLANs)
Port 3 Vlan mode strict, only untagged, vlanID 10, vlan header=leave as if (Always strip vlan 10, and not a member vlan 1000 under VLANs)
Port 4 Vlan mode strict, only untagged, vlanID 10, vlan header=leave as if (Always strip vlan 10, and not a member vlan 1000 under VLANs)
Port 5 Vlan mode strict, any, vlanID 1000, vlan header=leave as if (not a member vlan 10, and always strip vlan 1000 under VLANs)
Is it something I’m missing? It works flawless until router reboots, then I have to reboot switch to make it work again.
Diagram of network please, as your explanation sheds no light.
Config of MT device
/export file=anynameyouwish ( minus router serial number, any public WANIP information, keys)
First, please consider using the “code” tags next time, this makes reading the config a lot easier.
To make sure I understand your config: the router is used to access a tunnel to Mullvad. As it no longer has a dhcp client on ether1 (flagged as the wan port), I gather it no longer provides internet access. Instead it relies on the switch and 5G connection (via vlan1000) to get access to the Internet. The trunk between the switch and router arrives on the router on ether6 (could be ether9 but that makes less sense)
When you have the issue, does the interface vlan1000 have an IP address? Do you see a default route installed in the routing table?
You have set the RSTP priority on your router to 0x6000 (24576). What is the priority on the switch? Do you have the same port-cost-mode on both side (Router is short - what is the switch) - Consider posting a screenshot of the RSTP tab here as well.
Here are my comments. None of that, in isolation, could cause the issue you see, but they are worth fixing, at the very least for the sake of having a clear configuration.
You have 2 bridges defined. Any specific reason? VLAN10 is reused between the 2.
As noted above, it incomprehensible that you assign different subnets to the same vlan…
In other words your requirements have never been clear in your mind. So not quite sure how you expect us to pluck out any logic or approach.
As stated above, I think it would be fair to say, that VLAN1000 is just placeholder vlan to get the cellular traffic to the RB4011 as the WAN IINPUT.
On the same line (trunk port) you need vlan10 with DHCP, for the switch to distribute.
Why do you name ether1 on the ROUTER WAN??? The WAN is coming in on the trunk port on ether6.
Ether9 looks like a trunk port to another smart device not in the picture.
This interface list item makes no sense!!! add interface=lokholmsvagen list=VLAN
Error indications are cropping up… /ppp profile
set *0 bridge=bridge-VLAN
Another contradiction… you seem to have many port forwardings going on??
This is ONLY possible if you have a public IP on the router or are able to forward ports from an upstream router which gets a public IP.
What is the truth???
If that is the case why are you using Back to Home VPN, instead of just normal wireguard with the RB4011 as peer Server Device.
I understand the mullvad, in that you want all users on a specific subnet to go out mullvad for internet.
Too many unknowns and issues to even begin to assist.
You assign an interface to the vLAN that doesnt exist…
I highly suggest to concentrate on one thing at a time.
Disable all wireguard and queuing etc. and just work on getting vlans setup as a first step.
Remove all the extra firewall rules added over defaults and keep the bare minimum required.
Once all the requirements and WAN situation are better understood we could start adding back in functionality, once the vlan network is solid.
The VLAN1000 is converted to VLAN1000 and has DHCP client to get IP from the 5g CPE that is IP Passthrough on. (and is connected to Eth6 on router)
Deafult route gets dynamically associated to vlan 1000 because of the DHCP client on vlan 1000. But when “the issues” is when router reboots (and not the switch) then the IP never gets to DHCP client until I reboot switch.
Bridge-VLAN RSTP is set to 6000, short on router… and 8000, short on switch.
The eth2 on bridge didn’t do the trick, that made no difference.( from old setup I had forgotten to delete, the port is not in use. ) Bridge 2 is used from old setup. Have fixed this now and deleted.
Quite a few addresses?? nooo…It’s dhcp on 10.0.20.1, and then I have I couple of subnets to have when I troubleshoot to set static addresses on that vlan.
For some reason my Mullvad connection on vlan66 don’t work any longer either. I have communication on rx/tx wireguard but no internet when I connect on vlan 66. This problem I got when I converted to vlan 1000 from ordinary Eth1 that was WAN earlier…hmmm…
Ok, sorry for the messup All this is because I have converted it from a normal router setup with wan on eth1. Then I made this setup because I only had one cable to the other side of house where the 5G CPE is. Then the VLAN story came up…
As I said in the other post, more subnets on same vlan is because I use this setup on “work” when I setup other switches and stuff that is delivered with static ip. Then I set the subnet on vlan to get to the device from my network. They are not statically there all the time, I change them from now and then…they are only there for setup… The usual ip is 10.0.20.1 Network.
VLAN1000 is just placeholder vlan as you mentioned…
The ports you name not considered right is port not in use, so this shouldn’t be a problem. But of cause its wrong, I will fix that.
The router gets public ip from vlan 1000 on eth6 through CPE 5G
My recommendations stand, you switched configs many times and went in several different directions.
Start from scratch and do only the basic networking and vlans with basic firewall rules.
Once up and running we can add in layers.