Sorry for being such a noob. My networking is not very strong, thought I’d ask the fine folks here.

Let’s say I have a Linux box working as a router and a dumb switch (I.e. L2 only). I have 2 PCs that I would like to keep separated and not let them talk to each other.

Can I plug these two PCs into the switch, configure their interfaces with IPs from different subnets, and configure the relevant sub-interfaces and ACLs (to prevent inter-subnet communication through the router) on the Linux router?

What I’m asking is; do I really need VLANs? I do need to segregate networks but I do not trust the operating systems running on these switches which can do L3 routing.

If you have a better solution than what I described which can scale with the number of computers, please let me know. Unfortunately, networking below L3 is still fuzzy in my head.

Thanks!

  • neidu3@sh.itjust.worksEnglish
    2·
    1 day ago

    As others have said: It will work as you’ve planned it. The subnetting will keep these two PCs separated (If they still need internet, just add a second IP in your router-PC to allow for communication with this subnet).

    VLANs aren’t required, but are more relevant when you want to force network segregation based on individual ports. If you really want to, you can add tagged virtual interfaces on these two separated hosts so that the others hosts aren’t able to simply change the address to reach these. The switch should ignore the VLAN tag and pass it through anyway. But again, it’s not really needed, just something you can do if you really want to play with tagged VLAN interfaces

    • marauding_gibberish142@lemmy.dbzer0.comOPEnglish
      2·
      1 day ago

      Thank you. In theory, is there a mechanism which will prevent other hosts from tagging the interface with a VLAN ID common with another host and spoof traffic that way? Sorry, I need to study more about this stuff

      • neidu3@sh.itjust.worksEnglish
        2·
        21 hours ago

        Yes, but that’s done on the switch. Basically VLAN tags are applied in one of two ways:

        Untagged (sometimes called Access) is something you apply on a switch port. For example, if you assign a port to Untagged VLAN 32, anything connected to that port will only be able to see traffic assigned to VLAN 32.

        Tagged (sometimesreferred to as Trunk), on the other hand, is for traffic that is already assigned a VLAN tag. For example Tagged 32 means that it will allow traffic that already has a VLAN tag of 32. It is possible to assign multiple VLANs to a Tagged port. Whatever is connected to that port will need to be able to talk to the associated VLAN(s).

        In your particular case, the best practice would be to assign two ports (One for each host, obviously) to Untagged 32 (arbitrarily chosen number, any VLAN ID will do, as long as you’re consistent), and all the other ports as Untagged to a different VLAN ID. That way the switch will effectively contain two segments that cannot talk to each other.

        • marauding_gibberish142@lemmy.dbzer0.comOPEnglish
          2·
          21 hours ago

          Thank you so much for the explanation. I followed everything but:

          Untagged (sometimes called Access) is something you apply on a switch port. For example, if you assign a port to Untagged VLAN 32, anything connected to that port will only be able to connect to port 32.

          I couldn’t really understand what you meant here. Did you mean VLAN 32 in the last line?

          • neidu3@sh.itjust.worksEnglish
            1·
            21 hours ago

            Derp, yes. Corrected. VLAN numbers are obviously not related to port numbers in any way.