Oh no, you!

  • 3 Posts
  • 185 Comments
Joined 5 months ago
cake
Cake day: November 3rd, 2024

help-circle
  • Not really approaching religion in any way, but Bill Bryson - “A Short History of Nearly Everything” is a neat book if your knowledge about the world is grounded in religious teachings.

    Basically it goes through a lot of the scientific knowledge we have today and tells the story of how it was discovered, focusing on giving answers to “how we know what you know”. It’s a bit oversimplified in many areas, but it’s still pretty educational, entertaining, and at times funny.




  • I just replaced my car, mostly due to upkeep costs. But while I can manage the car loan as it stands right now, once my grandparents’ house is sold, almost all of my share will go into the car loan.

    The severance obviously won’t last forever (6 months-ish), but I live in a “socialist hellscape scandinavian country” (Glenn Beck told me so, I didn’t know how awful I had it until I accidentally watched Fox News in 2008), so even if it takes me a while to land a job I’m not too worried. Plus I have plenty ty of c9ntacts in my current field of work, so even if things were to go to hell, I’m sure I’ll land on my feet.








  • 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.


  • 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