Posted: Sun Nov 03, 2024 17:10 Post subject: package collision on vlan1?
I have an odd problem sending data along eth0.1 between my R9000 and a managed switch on a tagged spf+ 10g line. It works initially but within a few hours stops passing information on the eth0.1 lane of the trunk. The eth0.2 and eth0.10 appear to continue to work fine.
I have a "mostly" working setup in which I have a 2.5G/10G switch passing data between a modem and my R9000. The screenshots below will describe it better than words. Basically if I try to use vlan1 instead of vlan3 as my connection to br0 then the connection becomes increasingly erratic and eventually unusable. I can still connect to vlan1 using one of the switch ports on the router and all the other connections on the network seem to be up and running. I thought I could just remove vlan3 and use vlan1 on the switch as by default it is always there. But apparently that won't work.
Does anyone know why I can't use vlan1 in this case?
Both together are not possible
a port can only have one untagged VLAN and not two
This was the initial reason I was attempting to remove vlan3. I can't remove vlan1 on the switch and as the switch gui is apparently accessed through vlan1, I was concerned about removing all ports from vlan1.
Strangely having both doesn't currently cause any conflict. I wondered about that when I set it up and still can't tell what is really going on in the switch.
ho1Aetoo wrote:
bringing table:
br0 eth0,eth0.1
you should set eth0 to ‘unbridged’ if you are not using it.
this is a guarantee for problems if the physical is bridged with the virtual interfaces
and you don't need STP either if you haven't built any cable loops
I had considered unbridging eth0 but didn't know why it wasn't automatically being removed from br0 when I set up tagging. I'll unbridge it.
simply remove the ‘untagged’ vlan3 ports in the switch.
and use eth0.1/vlan1.
unbridge eth0 in the router (simply set from bridge assignment=default to unbridged - see my vlan stickies)
It is best to deactivate the SFE/NSS stuff in the ‘basic setup’ tab.
As I said, this should also work with vlan1 without any problems. _________________ Quickstart guides:
