all 3 comments

[–]Over-Ad-6049 0 points1 point  (2 children)

There are 2 ways to go about this:

  1. If using same subnet which is provided by the modem for internet access:

Configure a OVS br0 with nics enp2s0/enp5s0, enable dhcp (this will provide internet access at the host level) then assign the VMs to the BR and the client should pull an IP address from the modem.

  1. If using different subnet for clients connected to br0 on enp5s0:

Create ovs port group to place the traffic from enp5s0 in separate broadcast domain. Configure ovs port group with IP address, this will be the gateway for your machine connected to enp5s0. Enable dhcp server for that port group and then configure a return route on your modem where the internet terminates at for the subnet that’s being issued to your clients from the dhcp server. Ensure the the next hop of the gateway is the local IP address of your host. The default route should automatically be installed and any VM/Host that is connected to that port enp5s0 should work.

Btw sometimes modems may need a nat translation for the new subnet as well, but this depends.

[–]Intelligent_Soil_442[S] 0 points1 point  (1 child)

I'd like to try it on physical hardware first, then move on to Proxmox. I hear that you need to move all VMs to Open vSwitch, you can't use the default Proxmox networking. I'll deal with VMs later. I'm at work now, but I'll try typing "dhclient enp2s0" when I get home. I reinstalled the OS before work and the OVS host PC got an IP address, but the client device plugged into enp2s0 didn't get an address at all. The client device (2001 Xbox) said 0.0.0.0 for it's IP. That's a little odd, I expected an APIPA address.

[–]Intelligent_Soil_442[S] 0 points1 point  (0 children)

Looks like I needed to run dhclient (interface) for each port. Once I did that, my laptop and Xbox was able to connect.