Hi folks, hope your weekend is going well.

So I have put myself into a situation. I have a home server with docker installed running fine so far. In my home network I have multiple networks for different purposes. The whole network stack looks like this OPNSense — Switch — Ubuntu Server

The server is connected to a switch port with pvid 100, and runs on vlan0.100 Now my goal is to move some docker containers to other vlans. To accomplish that I have set vlan0.101 and vlan0.102 on my server as interfaces with their own IP and default gateway on that subnet (e.g. 192.168.101.10) Next step I set up macvlans for my docker containers Then I set the port to also allow tagged traffic, but kept it on pvid 100. Now on my OPNSense I changed the host ip of my server from 192.168.100.10 to include all 3 IPs so homeserver 192.168.100.10, 192.168.101.10, 192.168.102.10

This setup seems to work fine for internal network, however no services are reachable from the outside (internet) anymore.

My first question is: Am I thinking correctly about this? Or is this over-engineered bs at this point and there is a better way to put docker containers on different subnets.

Second question is: Any ideas what’s breaking the internet access?

Thanks for the help in advance :D

EDIT: i have not changed the vlan of any container yet

  • zo0OPEnglish
    1·
    19 天前

    Yes can confirm, the physical devices on those subnets work fine, it’s the server ‘after the changes’ that becomes confused

    • al@lighthouse.co.im
      1·
      19 天前

      @zo0 “Check OPNsense: do you have VLAN interface definitions for vlan0.101 and vlan0.102? Are there NAT rules for those subnets? Are there firewall rules allowing them to reach the WAN?”
      If all three are there and correct, the problem is elsewhere (switch config, trunk port tagging). If any are missing, that’s the culprit.