Issue: Bridge not working

[ManucrackYT]

Hi, I recently installed Proxmox on a Dedicated Server and bought a subnet/29 for it. When I tried to create a CT Container, there were no Bridges on the Network Section so I make one on my node manually



Then I could create a CT but now the LXC container cant ping or do apt update correctly, what can I do?

 

[Dunuin]

You didn't specify a gateway (and maybe no DNS?) for that LXC.

 

[ManucrackYT]

You didn't specify a gateway (and maybe no DNS?) for that LXC.

On the Linux Bridge?

 

[Dunuin]

On your LXC. The screenshot shows your IPv4 Gatway field is empty, so the LXCs OS doesn't know where to send packets to access the internet.
It needs an IP, gateway and DNS server like any OS.

 

[ManucrackYT]

On your LXC. The screenshot shows your IPv4 Gatway field is empty, so the LXCs OS doesn't know where to send packets to access the internet.

And what should I put there?

 

[Dunuin]

And what should I put there?

Only you can know that. The IP of the device that is doing the routing in that subnet.
what gateway did you set up for your PVE host so the host can access the internet?

 

[ManucrackYT]

Theres no PVE Gateway, as you can see on the first screenshot because if you put something there, you get the following error:

 

[Dunuin]

You usually don't set IP or gateway on the NIC but on the bridge instead.

 

[wahmed]

Hi, I recently installed Proxmox on a Dedicated Server and bought a subnet/29 for it. When I tried to create a CT Container, there were no Bridges on the Network Section so I make one on my node manually

View attachment 65942

Then I could create a CT but now the LXC container cant ping or do apt update correctly, what can I do?


View attachment 65943

From your post, it seems like you have the dedicated server hosted with a provider which comes with a dedicated IP. On top of that, you have another subnet /29 apart from the main subnet allocated. If it is correct, then you are facing the common issue of multiple IPs on a single MAC. It can be solved by having all subnets use the same MAC address when exiting your network into the provider's environment.

Here is a sample configuration may work in your situation with 2 subnets. In this example, the IP 10.0.0.1/30 is the main subnet and 10.10.1.1/29 is the additional subnet:

auto enps0f0
iface enps0f0 inet static
        address  10.0.0.1/30
        gateway  10.0.0.254
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        post-up echo 1 > /proc/sys/net/ipv4/conf/eno0/proxy_arp

auto vmbr0
iface vmbr0 inet static
        address  10.10.1.1/29
        bridge-ports none
        bridge-stp off
        bridge-fd 0

 

[ManucrackYT]

From your post, it seems like you have the dedicated server hosted with a provider which comes with a dedicated IP. On top of that, you have another subnet /29 apart from the main subnet allocated. If it is correct, then you are facing the common issue of multiple IPs on a single MAC. It can be solved by having all subnets use the same MAC address when exiting your network into the provider's environment.

Here is a sample configuration may work in your situation with 2 subnets. In this example, the IP 10.0.0.1/30 is the main subnet and 10.10.1.1/29 is the additional subnet:

auto enps0f0
iface enps0f0 inet static
        address  10.0.0.1/30
        gateway  10.0.0.254
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        post-up echo 1 > /proc/sys/net/ipv4/conf/eno0/proxy_arp

auto vmbr0
iface vmbr0 inet static
        address  10.10.1.1/29
        bridge-ports none
        bridge-stp off
        bridge-fd 0

I think you're not correct, I have a dedicated IP but it doesnt mention its from a subnet

 

[ManucrackYT]

Hi, good news, I have fixed it, thanks for the help!