Hmm. I thought this would be pretty simple. And maybe it is. But all the information is cloudy and unclear.
My home network is set up as my "main LAN" is VLAN 100. These are real routed IPs, and on some physical ports are untagged/retagged at the port (so the device connected is not VLAN aware). Then I have an IOT VLAN on 107 and a Guest VLAN on 666.
My "infrastructure" is VLAN 1 and/or untagged? Is that a sensible thing to say?
My plan was to have my proxmox's web UI on the infrastructure VLAN only, then use VLAN bridging to point (where needed) individual VLANs to specific VMs on the box. And probably to add another VLAN (maybe 123) for "hosting", which is publicly accessible ingress [w/firewalling naturally).
But I cannot get the proxmox to "sit" on VLAN 1 for its admin UI, with VLAN bridging on.
And all the docs just cloudily say "avoid VLAN 1". No further explanation.
I've now gotten access to the ProxMox web UI, by simply forcing
auto vmbr0
iface vmbr0 inet dhcp
and setting that switchport to an access port on my "real IP" VLAN 100.
This has then picked up an address via DHCP successfully. But there seems to be no obvious way of even inspecting network config from within the web interface.
This is, yet again, a pain of "self hosting". And to go back to @neil 's point ... it is never, ever, "*JUST*" self host.
@bloor @neil vlan 1 is almost always advised against for the simple reason that so many devices capable of dot1q assume their default vlan is 1. This makes for all manner of fuckery when adding new devices.
I use 1001 for mgmt, then got caught out by Cisco's reservation is 1002-4 for legacy stuff. Having coded up everything for automation I had to go back and rejig everything manually to 1012,3,4 etc.
I think my home network may be too complicated!
🆎
Greem (Graeme. Not Graham!)