i have a ccr2004-1G-12S+2Xs as router to replace my isp router (orange livebox).
I have follow instruction available on french forum lafibre.info.
there are no vlan on the lan dedicated port.
At this point, without vlan all work fine.
i have installed a crs309 with 2 vlan:
vlan 1 is the default vlan untagged on all port
vlan 10 is the vlan for some vm tagged on 2 port dedicated to my vmware server. (where i have several vm some on vlan 1, other on vlan 10)
here the config:
i have configured port sfpplus1 as tagged vlan 10 and untagged vlan 1 to ma other switch aruba and that work, the on lan 10 could ping the aruba ip on vlan 10.
But i don’t understand how configure vlan between crr2004 and crs309 so that all vlan could reach internet
Side of the crr2004 i have add vlan 1 and vlan 2 on the interface dedicated to the lan and side of the crs 309 i have tried several things such as admit only tagged vlan but withour result.
i would like that the 2 vlan reach internet but don’t communicated together.
I don’t see any IP setup on vlan10 interface on CCR … you’ll definitely need some if you want CCR to communicate with devices in that subnet (and you want if it’s supposed to be gateway for that subnet).
There are interfaces (L3 entities, essentially anything carrying IP address) and there are ports (L2 entities). When something is set as member of bridge, it becomes a port. And it should not be used as interface. Ever. Bridge has a few personalities, one of them being an interface which allows communication between router’s CPU (software stack) and bridged network.
In short: whenever bridge is used and device needs to communicate with (any of) bridged network, it’s bridge interface which has to be used to setup such connectivity.
In your particular case: if you want switch IP to belong to some VLAN, then create vlan interface, anchored to bridge (not to some of member ports), and then use that vlan interface to set IP address. If VLANs are not in the mix, then set IP address directly on bridge interface.
Yes, in most setups involving VLAN interface (created under /interfacw/vlan), vlan interfaces should be used exclusively to support L3 operations (routing, providing services such as DNS). Using vlan interfaces in L2 operations (such as tagging/untagging frames) is highly likely an abuse (and should be reported to nearest capable MTCNA) exactly for this reason - it’s relying on CPU to do the task.
If a device doesn’t perform L3 operations in certain VLAN (e.g. it’s used as VLAN-enabled switch), then corresponding vlan interface is not needed (and for security reasons it should not be present, bridge (CPU-facing) port should not be member of that VLAN either.
i’m a bit lost.
in my case i use the crs309 as VLAN-enabled switch, the the general routing is made by the crr2004, and the inter vlan too.
it’s the right way, yes?
I use 2 vlan,the default id 1 (i will change this) untagged on all port and id 10 tagged on the port for the vmware server and the trunk port to crr2004.
So the management ip will be at least in the default vlan (not vlan id 1).
If have follow your explanation,in my case (use of vlan) i need to create a vlan interface anchored on bridge and set an ip for the management.
But the switch don’t perform L3 opération, so , according your last post vlan interface is not needed and bridge (CPU-facing) port should not be member of that VLAN either.
Before the crs309, i used an l2 switch aruba 1930 instant on.The management ip was reachable on one particular vlan.
So, with what i have understood, that functionning will be the same with crs309 in the case of vlan interface anchored on bridge and an ip set in for the management.
I have in mind that using l3 with the crs309 will generate bad performance because that use cpu
Sorry but i’m not really sure to understand what’s the best practice to configure management ip.
Maybe i just over thinking for nothing.
I will sleep on it tonight , maybe my ideas will be clearer tomorrow.
all SFP+ ports (and ether1 port) will members of bridge with per-port vlan settings as needed (port connecting to CCR will be tagged-only, other ports might be untagged access ports for a particular VLAN with pvid set appropriately)
bridge port will be set as tagged member of mgmt VLAN (and will not be nember of other VLANs)
there will be single vlan interface anchored to bridge interface with vlan-id set to mgmt VLAN ID
vlan interface will have IP address set
Bullet #2 makes sure that management access (even non-IP using winbox) is possible only through mgmt VLAN. Bullet #3 makes sure that switch won’t route anything as it will only be able to “talk to” management VLAN. Bullet #1 will make L2 HW offload possible (multiple bridges can’t be offloaded).
I suggest you to leave ether1 out of bridge while configuring switch, it’s only too easy to screw L2 config and loose management access in which case device has to be reset and configuring restarted from scratch. If you leave ether1 aside, you can use it to connect using winbox and fix config.