Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Help with Proxmox Networking (US Dedicated/IP Aliasing)

Go to solution Solved by iCoExist,
28 minutes ago, Windows7ge said:

It appears all the NICs are in the same IOMMU group...which is bad. However, they do say they support SR-IOV. Now how one goes about setting that up on Proxmox...going to have to read the documentation.

I think I'm onto something here. I yeeted all of the primary:x devices, and just defined one interface. Now my config looks like this:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

auto primary
iface primary inet manual

auto vmbr0
iface vmbr0 inet static
        address 66.23.201.178
        netmask 255.255.255.255
        gateway 66.23.201.177
        bridge_ports primary
        bridge_stp off
        bridge_fd 0

I was going off the thought that I needed to define an IP on the "primary" interface, so I went with static. It turns out, to use this as a bridged device, I need to use manual on this interface instead. Then define the first usable address in the vmbr0 interface. From there, I just add a network device to the CT/VM, and use the next available IP that was assigned to me. So far, it seems to be working!!

Hey everyone! I was hoping to get some assistance with a Proxmox server I've spun up with US Dedicated. This server provider assigns IPs to machines a bit differently than I'm used to. I'm used to how OVH handles failover IPs. So here's the rundown: I have managed to get Proxmox installed on top of Debian Buster. I can access it via the IP address, but when I go to the networking tab, I see a whole bunch of entries that I'm not familiar with. This is also what I see in /etc/network/interfaces. The IP block I have assigned is 66.23.201.176/29, the gateway being 66.23.201.177.

 

I can't seem to figure out how to properly assign IP addresses here. I also don't understand what is going on in /etc/network/interfaces. I've never seen adapters with what I assume is IP aliasing. I've only ever worked with individual interfaces, not what is going on here. If I make any changes, it seems like the network breaks and I cannot access the server anymore. I also can't get networking going inside of any containers/VMs.

 

If anyone need more information, please just let me know what you might need, and I'll try to get that back as soon as possible. I was hoping to roll out my website and forum, but seeing as I can't even get containers started, I seem to be at a bit of a standstill.

Link to post
Share on other sites
10 minutes ago, iCoExist said:

I can't seem to figure out how to properly assign IP addresses here.

I don't understand why you think you need to assign IP-addresses. Those interfaces already have an IP assigned.

Hand, n. A singular instrument worn at the end of the human arm and commonly thrust into somebody’s pocket.

Link to post
Share on other sites
Just now, WereCatf said:

I don't understand why you think you need to assign IP-addresses. Those interfaces already have an IP assigned.

Sorry for not clarifying, I meant to say something along the lines of assigning an IP address to a VM/container, or how am I supposed to create a bridge for the VMs/containers to use. If I create a VM/container, I cannot seem to get them to communicate with the outside world. I've been piecing things together from various places, and decided to do the following in /etc/network/interfaces:

auto lo
iface lo inet loopback

auto primary
iface primary inet static
        address 66.23.201.178/29
        gateway 66.23.201.177
        dns-nameservers 8.8.8.8

auto vmbr0
iface vmbr0 inet static
        address 66.23.201.178/29
        netmask 255.255.255.255
        bridge_ports none
        bridge_stp off
        bridge_fd 0
        bridge_maxwait 0
        pre-up brctl addbr vmbr0
        up ip route add 66.23.201.179/32 dev vmbr0
        up ip route add 66.23.201.180/32 dev vmbr0
        up ip route add 66.23.201.181/32 dev vmbr0
        up ip route add 66.23.201.182/32 dev vmbr0

 

This makes the most sense to me right now, but it still doesn't allow VMs/containers to talk to the world.

 

root@test:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 66.23.201.179 icmp_seq=1 Destination Host Unreachable
From 66.23.201.179 icmp_seq=2 Destination Host Unreachable
From 66.23.201.179 icmp_seq=3 Destination Host Unreachable
^C
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4092ms

 

Link to post
Share on other sites
4 minutes ago, iCoExist said:

Sorry for not clarifying, I meant to say something along the lines of assigning an IP address to a VM/container, or how am I supposed to create a bridge for the VMs/containers to use

You should have been able to just simply assign one of the extra interfaces to the VM as-is. You were given 66.23.201.176/29, ie. 66.23.201.176 - 66.23.201.183 and it seems to me like they just simply set up a couple of interfaces by default for such use.

Hand, n. A singular instrument worn at the end of the human arm and commonly thrust into somebody’s pocket.

Link to post
Share on other sites

The problem with a Linux Bridge here is it passes network packets from a virtual interface assigned to the CT/VM to the physical NIC on what would normally be a LAN.

 

So by setting the network adapter of a given CT/VM to the Linux Bridge it's effectively connected to the open Internet but the issue is it will send out a DHCP request which will be quickly dropped as there is no server to hand out an address on the WAN.

 

You would need to assign the interface itself to the VM. That, or setup a DHCP/Firewall server and run everything behind NAT.

 

Assigning the hardware NIC itself to the VM should be possible with SR-IOV. I'm not sure how to do it otherwise on PROXMOX.

Guides & Tutorials:

Testing for RAM Errors w/ MemTest86

How To: Remotely Access a Computer, Server, or NAS

How To: Access Remote Systems at Home/Work Securely from Anywhere with Pritunl

How to Format Storage Devices in Windows 10

A How-To: Drive Sharing in Windows 10

VFIO GPU Pass-though w/ Looking Glass KVM on Ubuntu 19.04

A How-To Guide: Building a Rudimentary Disk Enclosure

Three Methods to Resetting a Windows Login Password

 

Guide/Tutorial in Progress:

iPXE Network Booting to an iSCSI Target

 

In the Queue:

 

 

Don't see what you need? Check the Full List or *PM me, if I haven't made it I'll add it to the list.

*NOTE: I'll only add it to the list if the request is something I know I can do.

Link to post
Share on other sites
1 hour ago, Windows7ge said:

The problem with a Linux Bridge here is it passes network packets from a virtual interface assigned to the CT/VM to the physical NIC on what would normally be a LAN.

 

So by setting the network adapter of a given CT/VM to the Linux Bridge it's effectively connected to the open Internet but the issue is it will send out a DHCP request which will be quickly dropped as there is no server to hand out an address on the WAN.

 

You would need to assign the interface itself to the VM. That, or setup a DHCP/Firewall server and run everything behind NAT.

 

Assigning the hardware NIC itself to the VM should be possible with SR-IOV. I'm not sure how to do it otherwise on PROXMOX.

I referenced this post on Reddit and was hoping I was onto something. Unfortunately I don't quite understand that either. I'm getting mixed responses as well -- the server provider mentioned that I need to reference Proxmox' manual and use a Bridged interface. This makes me believe I just need to remove all the primary:x aliases? I really just don't understand what's going on here.

Link to post
Share on other sites
1 hour ago, WereCatf said:

You should have been able to just simply assign one of the extra interfaces to the VM as-is. You were given 66.23.201.176/29, ie. 66.23.201.176 - 66.23.201.183 and it seems to me like they just simply set up a couple of interfaces by default for such use.

Provider said something along the lines of this, but then also mentioned the use of a bridge. Not sure if they're understanding what I'm asking. How would I go about assigning these interfaces to a CT/VM? I feel like if this is the case, I'm missing something somewhere.

Link to post
Share on other sites
23 minutes ago, iCoExist said:

I referenced this post on Reddit and was hoping I was onto something. Unfortunately I don't quite understand that either. I'm getting mixed responses as well -- the server provider mentioned that I need to reference Proxmox' manual and use a Bridged interface. This makes me believe I just need to remove all the primary:x aliases? I really just don't understand what's going on here.

You can try this if you like but I have no confidence it'll work. Create a Linux Bridge going to one of the NICs (preferably not the one you're using for Web Management). Assign that bridge to a CT/VM then configure that CT/VM with the same Static IP assigned to the physical interface.

 

This might work. This also might break things. 😅

Guides & Tutorials:

Testing for RAM Errors w/ MemTest86

How To: Remotely Access a Computer, Server, or NAS

How To: Access Remote Systems at Home/Work Securely from Anywhere with Pritunl

How to Format Storage Devices in Windows 10

A How-To: Drive Sharing in Windows 10

VFIO GPU Pass-though w/ Looking Glass KVM on Ubuntu 19.04

A How-To Guide: Building a Rudimentary Disk Enclosure

Three Methods to Resetting a Windows Login Password

 

Guide/Tutorial in Progress:

iPXE Network Booting to an iSCSI Target

 

In the Queue:

 

 

Don't see what you need? Check the Full List or *PM me, if I haven't made it I'll add it to the list.

*NOTE: I'll only add it to the list if the request is something I know I can do.

Link to post
Share on other sites
9 minutes ago, Windows7ge said:

You can try this if you like but I have no confidence it'll work. Create a Linux Bridge going to one of the NICs (preferably not the one you're using for Web Management). Assign that bridge to a CT/VM then configure that CT/VM with the same Static IP assigned to the physical interface.

 

This might work. This also might break things. 😅

Ah well, I tried this route, but then I get "iface primary:1 - ip address can't be set on interface if bridged in vmbr0 (500)". At this rate, I'd have better luck just spinning up another server from a different provider, but I don't want to give up on something just because I can't figure it out. I've been trying to figure this out for two days but to no avail yet. There's also a third interface showing up, enp1s0f1, but its set to manual. From what I understand, that's to create a device with no defined IP address, possibly for use with a bridge.

 

Have you got any other ideas? In the meantime, I'm going to look into SR-IOV. There doesn't seem to be a way to just attach a interface directly to a CT/VM in Proxmox from what I can gather.

Link to post
Share on other sites

Given this is a rental server you may not be able to utilise SR-IOV. Also the suggestion I have here would only work for VMs to my knowledge.

 

If you go into the proxmox terminal and run the command:

lspci -vnn

And find the four network adapters in the list do they all appear in different IOMMU groups? You may be able to pass each NIC to a different VM.

Guides & Tutorials:

Testing for RAM Errors w/ MemTest86

How To: Remotely Access a Computer, Server, or NAS

How To: Access Remote Systems at Home/Work Securely from Anywhere with Pritunl

How to Format Storage Devices in Windows 10

A How-To: Drive Sharing in Windows 10

VFIO GPU Pass-though w/ Looking Glass KVM on Ubuntu 19.04

A How-To Guide: Building a Rudimentary Disk Enclosure

Three Methods to Resetting a Windows Login Password

 

Guide/Tutorial in Progress:

iPXE Network Booting to an iSCSI Target

 

In the Queue:

 

 

Don't see what you need? Check the Full List or *PM me, if I haven't made it I'll add it to the list.

*NOTE: I'll only add it to the list if the request is something I know I can do.

Link to post
Share on other sites
4 minutes ago, Windows7ge said:

Given this is a rental server you may not be able to utilise SR-IOV. Also the suggestion I have here would only work for VMs to my knowledge.

 

If you go into the proxmox terminal and run the command:



lspci -vnn

And find the four network adapters in the list do they all appear in different IOMMU groups? You may be able to pass each NIC to a different VM.

00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:1918] (rev 07)
        Subsystem: Super Micro Computer Inc Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [15d9:0898]
        Flags: bus master, fast devsel, latency 0
        Capabilities: [e0] Vendor Specific Information: Len=10 <?>
        Kernel driver in use: skl_uncore
        Kernel modules: ie31200_edac

00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 25
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 0000e000-0000efff
        Memory behind bridge: 88400000-886fffff
        Capabilities: [88] Subsystem: Super Micro Computer Inc Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) [15d9:0898]
        Capabilities: [80] Power Management version 3
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [a0] Express Root Port (Slot+), MSI 00
        Capabilities: [100] Virtual Channel
        Capabilities: [140] Root Complex Link
        Capabilities: [1c0] Advanced Error Reporting
        Capabilities: [d94] #19
        Kernel driver in use: pcieport

00:13.0 Non-VGA unclassified device [0000]: Intel Corporation Sunrise Point-H Integrated Sensor Hub [8086:a135] (rev 31)
        Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family Integrated Sensor Hub [15d9:0898]
        Flags: fast devsel, IRQ 20
        Memory at df322000 (64-bit, non-prefetchable) [size=4K]
        Capabilities: [80] Power Management version 3
        Kernel modules: intel_ish_ipc

00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31) (prog-if 30 [XHCI])
        Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [15d9:0898]
        Flags: bus master, medium devsel, latency 0, IRQ 38
        Memory at df300000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [70] Power Management version 2
        Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
        
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31)
        Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family Thermal Subsystem [15d9:0898]
        Flags: bus master, fast devsel, latency 0, IRQ 18
        Memory at df321000 (64-bit, non-prefetchable) [size=4K]
        Capabilities: [50] Power Management version 3
        Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
        Kernel driver in use: intel_pch_thermal
        Kernel modules: intel_pch_thermal

00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31)
        Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family MEI Controller [15d9:0898]
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at df320000 (64-bit, non-prefetchable) [size=4K]
        Capabilities: [50] Power Management version 3
        Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+
        Kernel modules: mei_me

00:16.1 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #2 [8086:a13b] (rev 31)
        Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family MEI Controller [15d9:0898]
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at df31f000 (64-bit, non-prefetchable) [size=4K]
        Capabilities: [50] Power Management version 3
        Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+
        Kernel modules: mei_me

00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] [8086:a102] (rev 31) (prog-if 01 [AHCI 1.0])
        Subsystem: Super Micro Computer Inc Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] [15d9:0898]
        Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 37
        Memory at df310000 (32-bit, non-prefetchable) [size=8K]
        Memory at df31e000 (32-bit, non-prefetchable) [size=256]
        I/O ports at f050 [size=8]
        I/O ports at f040 [size=4]
        I/O ports at f020 [size=32]
        Memory at df31d000 (32-bit, non-prefetchable) [size=2K]
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [70] Power Management version 3
        Capabilities: [a8] SATA HBA v1.0
        Kernel driver in use: ahci
        Kernel modules: ahci

00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #9 [8086:a118] (rev f1) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 26
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
        Capabilities: [40] Express Root Port (Slot-), MSI 00
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [90] Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family PCI Express Root Port [15d9:0898]
        Capabilities: [a0] Power Management version 3
        Kernel driver in use: pcieport

00:1d.5 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #14 [8086:a11d] (rev f1) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0, IRQ 27
        Bus: primary=00, secondary=03, subordinate=04, sec-latency=0
        I/O behind bridge: 0000d000-0000dfff
        Memory behind bridge: de000000-df0fffff
        Capabilities: [40] Express Root Port (Slot+), MSI 00
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [90] Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family PCI Express Root Port [15d9:0898]
        Capabilities: [a0] Power Management version 3
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Access Control Services
        Capabilities: [220] #19
        Kernel driver in use: pcieport

00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a149] (rev 31)
        Subsystem: Super Micro Computer Inc C236 Chipset LPC/eSPI Controller [15d9:0898]
        Flags: bus master, medium devsel, latency 0

00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31)
        Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family Power Management Controller [15d9:0898]
        Flags: bus master, fast devsel, latency 0
        Memory at df318000 (32-bit, non-prefetchable) [size=16K]

00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31)
        Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family SMBus [15d9:0898]
        Flags: medium devsel, IRQ 16
        Memory at df31c000 (64-bit, non-prefetchable) [size=256]
        I/O ports at f000 [size=32]
        Kernel driver in use: i801_smbus
        Kernel modules: i2c_i801

01:00.0 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)
        Subsystem: Super Micro Computer Inc Dual Port i350 GbE MicroLP [AOC-CGP-i2] [15d9:0652]
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at 88400000 (32-bit, non-prefetchable) [size=512K]
        I/O ports at e020 [size=32]
        Memory at 88580000 (32-bit, non-prefetchable) [size=16K]
        Expansion ROM at 88500000 [disabled] [size=256K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
        Capabilities: [70] MSI-X: Enable+ Count=10 Masked-
        Capabilities: [a0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 0c-c4-7a-ff-ff-b2-96-6a
        Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
        Capabilities: [1a0] Transaction Processing Hints
        Capabilities: [1c0] Latency Tolerance Reporting
        Capabilities: [1d0] Access Control Services
        Kernel driver in use: igb
        Kernel modules: igb

01:00.1 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)
        Subsystem: Super Micro Computer Inc Dual Port i350 GbE MicroLP [AOC-CGP-i2] [15d9:0652]
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at 88480000 (32-bit, non-prefetchable) [size=512K]
        I/O ports at e000 [size=32]
        Memory at 885c4000 (32-bit, non-prefetchable) [size=16K]
        Expansion ROM at 88540000 [disabled] [size=256K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
        Capabilities: [70] MSI-X: Enable+ Count=10 Masked-
        Capabilities: [a0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 0c-c4-7a-ff-ff-b2-96-6a
        Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
        Capabilities: [1a0] Transaction Processing Hints
        Capabilities: [1d0] Access Control Services
        Kernel driver in use: igb
        Kernel modules: igb
        
03:00.0 PCI bridge [0604]: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge [1a03:1150] (rev 03) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=03, secondary=04, subordinate=04, sec-latency=32
        I/O behind bridge: 0000d000-0000dfff
        Memory behind bridge: de000000-df0fffff
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [78] Power Management version 3
        Capabilities: [80] Express PCI-Express to PCI/PCI-X Bridge, MSI 00
        Capabilities: [a4] Subsystem: Super Micro Computer Inc AST1150 PCI-to-PCI Bridge [15d9:0898]
        Capabilities: [100] Virtual Channel
        Capabilities: [800] Advanced Error Reporting

04:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 00 [VGA controller])
        Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:0898]
        Flags: medium devsel, IRQ 17
        Memory at de000000 (32-bit, non-prefetchable) [size=16M]
        Memory at df000000 (32-bit, non-prefetchable) [size=128K]
        I/O ports at d000 [size=128]
        [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/4 Maskable- 64bit+
        Kernel driver in use: ast
        Kernel modules: ast



Haven't worked with IOMMU stuff yet. 😅

Edited by iCoExist
Fixed copy/paste
Link to post
Share on other sites

It appears all the NICs are in the same IOMMU group...which is bad. However, they do say they support SR-IOV. Now how one goes about setting that up on Proxmox...going to have to read the documentation.

Guides & Tutorials:

Testing for RAM Errors w/ MemTest86

How To: Remotely Access a Computer, Server, or NAS

How To: Access Remote Systems at Home/Work Securely from Anywhere with Pritunl

How to Format Storage Devices in Windows 10

A How-To: Drive Sharing in Windows 10

VFIO GPU Pass-though w/ Looking Glass KVM on Ubuntu 19.04

A How-To Guide: Building a Rudimentary Disk Enclosure

Three Methods to Resetting a Windows Login Password

 

Guide/Tutorial in Progress:

iPXE Network Booting to an iSCSI Target

 

In the Queue:

 

 

Don't see what you need? Check the Full List or *PM me, if I haven't made it I'll add it to the list.

*NOTE: I'll only add it to the list if the request is something I know I can do.

Link to post
Share on other sites
28 minutes ago, Windows7ge said:

It appears all the NICs are in the same IOMMU group...which is bad. However, they do say they support SR-IOV. Now how one goes about setting that up on Proxmox...going to have to read the documentation.

I think I'm onto something here. I yeeted all of the primary:x devices, and just defined one interface. Now my config looks like this:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

auto primary
iface primary inet manual

auto vmbr0
iface vmbr0 inet static
        address 66.23.201.178
        netmask 255.255.255.255
        gateway 66.23.201.177
        bridge_ports primary
        bridge_stp off
        bridge_fd 0

I was going off the thought that I needed to define an IP on the "primary" interface, so I went with static. It turns out, to use this as a bridged device, I need to use manual on this interface instead. Then define the first usable address in the vmbr0 interface. From there, I just add a network device to the CT/VM, and use the next available IP that was assigned to me. So far, it seems to be working!!

Link to post
Share on other sites
11 hours ago, iCoExist said:

I think I'm onto something here. I yeeted all of the primary:x devices, and just defined one interface. Now my config looks like this:


source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

auto primary
iface primary inet manual

auto vmbr0
iface vmbr0 inet static
        address 66.23.201.178
        netmask 255.255.255.255
        gateway 66.23.201.177
        bridge_ports primary
        bridge_stp off
        bridge_fd 0

I was going off the thought that I needed to define an IP on the "primary" interface, so I went with static. It turns out, to use this as a bridged device, I need to use manual on this interface instead. Then define the first usable address in the vmbr0 interface. From there, I just add a network device to the CT/VM, and use the next available IP that was assigned to me. So far, it seems to be working!!

This makes sense. Under normal circumstances though you wouldn't do this with PROXMOX. Most people keep there servers on a LAN behind a router. This way when you create your Linux Bridge for vmbr0, 1, 2, 3 all the CT/VMs just have direct access to those respective LANs and a DHCP server. Then it'd be up to you to setup Port Forwarding in the router.

 

I take it you didn't like the idea of self-hosting? Did you consider a web service like Squarespace to build and host your site/forum? Would have been easier. Don't know if it would have been cheaper though.

Guides & Tutorials:

Testing for RAM Errors w/ MemTest86

How To: Remotely Access a Computer, Server, or NAS

How To: Access Remote Systems at Home/Work Securely from Anywhere with Pritunl

How to Format Storage Devices in Windows 10

A How-To: Drive Sharing in Windows 10

VFIO GPU Pass-though w/ Looking Glass KVM on Ubuntu 19.04

A How-To Guide: Building a Rudimentary Disk Enclosure

Three Methods to Resetting a Windows Login Password

 

Guide/Tutorial in Progress:

iPXE Network Booting to an iSCSI Target

 

In the Queue:

 

 

Don't see what you need? Check the Full List or *PM me, if I haven't made it I'll add it to the list.

*NOTE: I'll only add it to the list if the request is something I know I can do.

Link to post
Share on other sites
21 hours ago, Windows7ge said:

This makes sense. Under normal circumstances though you wouldn't do this with PROXMOX. Most people keep there servers on a LAN behind a router. This way when you create your Linux Bridge for vmbr0, 1, 2, 3 all the CT/VMs just have direct access to those respective LANs and a DHCP server. Then it'd be up to you to setup Port Forwarding in the router.

 

I take it you didn't like the idea of self-hosting? Did you consider a web service like Squarespace to build and host your site/forum? Would have been easier. Don't know if it would have been cheaper though.

I have always preferred using a dedicated server and slicing it up vs. something like Squarespace. Could self-host, but don't get that SLA. 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×