CSS326-24G-2S+ to CSS326-24G-2S+ Vlan problems on 2nd switch for Linux

[Buckeye]

@comet424

and there is no real video or explanation scenarios on this switch mostly for routeros but not switchos and this specific model.. to get it to work.. so you still gotta be smart at understanding it

I agree you need to understand.

There are some youtube videos, but no high quality professional grade ones that I am aware of.
Wilmer Almazan / The Network Trip has a playlist with a video that was planned but never released. It would have been good. https://www.youtube.com/playlist?list=PLNRJTwfzNNlb-k6D2tYTSVGccfOegWMYO

Mikrotik switchOS configuration: a step-by-step guide | VLAN tagging/port separation is for the switch you have. By TimiGate. It isn't a tutorial; it is more like a show and tell to a friend; a walkthrough without many explanations as to why. For example he doesn't discuss VLAN mode.

I think the best documenation is the what I stated in your other thread

@Buckeye

I highly suggest you spend some time reading CRS3xx and CSS3xx series Manual - SwOS - MikroTik Documentation because if you want your switches to be vlan-aware (and allow things like access ports), you shouldn't be using "optional" or "force VLAN id".

At the very least, read the VLAN and VLANs section, which includes a VLAN Configuration Example section. You want the ports going to the pfsense box and between the two CSS326 switches to be either trunk ports or hybrid ports (depending on how your pfsense box is set up, specifically whether your pfsense box sends any untagged traffic to the directly connected switch.) And then you would set up the ports you want to have access to specific vlans as access ports (for devices that know nothing about vlans, like most PC's).

But you have posted a lot of text, but not given some of the most important info.

How are things connected? Don't expect the people you want help from to spend excessive time to try to figure this out. A diagram is worth a lot in transferring information quickly. Even a photo of a hand drawn sketch is much better than trying to extract it from all the text in your threads. Having the screen shots is nice to be able to verify things, but not a good source of info for the "high level overview" context.

The diagram needs to show any links that need to carry more than one vlan; i.e. any links between the switches (all of them, you mention the two CSS326 switches, but also a 10G switch and a cisco switch). We need to know how these are connected. And if there are any loops, that's where RSTP comes into play. Note that the mesh wifi can act as an alternate path, and lead to loops.

Most importand things to show us on the diagram.

1. How the pfSense router is connected (I think with a trunk link to SW1 port 26 (SFP2). What subnets are defined on the pfSense router? What interfaces are defined? How do the subnets map to the interfaces? How are the vlans defined? Is anything untagged. (If you plug a PC into the pfsense port that is connected to the switch, does it get a dhcp address? Is it consistent?
2. All the connections to the other switches since these probably need to be trunk links.
3. All the connections to AP's (since these may be carrying multiple vlans).
4. An example of a port that works for both Windows dhcp and Linux dhcp.
5. An example of a port that works for Windows dhcp but not linux.
6. Any other thinks that don't work as you expected, and what you expected. Also copies of the errors you get.

Things covered here: https://jdebp.uk/FGA/problem-report-standard-litany.html

Things covered here: https://www.chiark.greenend.org.uk/~sgtatham/bugs.html