[TUTORIAL] HOWTO - Proxmox VE 8-x.x Wifi with routed configuration

news said:
please show your config, /etc/network/interfaces and /etc/network.d/
and also iptable -L -t nat

# https://pve.proxmox.com/wiki/Network_Configuration
Click to expand...

Code: 
root@pve:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp2s0 inet manual

auto wlo1
iface wlo1 inet manual
        address 192.168.50.20/24
        gateway 192.168.50.1

auto vmbr0
iface vmbr0 inet static
    address 192.168.51.1/24
    bridge-ports none
    bridge-stp off
    bridge-fd 0

auto vnet1
iface vnet1 inet static
    address 192.168.52.1/24
    bridge-ports none
    bridge-stp off
    bridge-fd 0
    hwaddress 6e:08:e2:74:e7:61
    post-up echo 1 > /proc/sys/net/ipv4/ip_forward
    post-up iptables -A FORWARD -i wlo1 -j ACCEPT
    post-up iptables -A FORWARD -o wlo1 -j ACCEPT
    post-up iptables -A FORWARD -i vnet1 -j ACCEPT
    post-up iptables -A FORWARD -o vnet1 -j ACCEPT

Code: 
root@pve:~# cat /etc/network.d
cat: cannot access '/etc/network.d': No such file or directory

I have network and networks in /etc though.

Code: 
root@pve:~# iptables -L -t nat
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination        

Chain INPUT (policy ACCEPT)
target     prot opt source               destination        

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination        

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination
 
Last edited:
sittingduck said:
Thanks - traceroute to another host gives:

Code: 
user@debian:~$ traceroute 192.168.50.246
traceroute to 192.168.50.246 (192.168.50.246), 30 hops max, 60 byte packets
1 debian (169.254.11.14) 3077.298 ms !H 3077.283 ms !H 3077.278 ms !H

vnet1 is 192.168.52.1, pinging just hangs (no message, blinking cursor):

Code: 
user@debian:~$ ping 192.168.52.1
PING 192.168.52.1 (192.168.52.1) 56(84) bytes of data.
_

Router gateway 192.168.50.1 is unreachable:

Code: 
user@debian:~$ ping 192.168.50.1
PING 192.168.50.1 (192.168.50.1) 56(84) bytes of data.
From 169.254.11.14 icmp_seq=1 Destination Host Unreachable
From 169.254.11.14 icmp_seq=2 Destination Host Unreachable
From 169.254.11.14 icmp_seq=3 Destination Host Unreachable
Click to expand...

Ping is failing from the VM to the vnet1 interface 192.168.52.1. Check your VM Hardware configuration. Check the Network Device and ensure it is bridged to vnet1. My guess is the Network Device is bridged to vmbr0, which is a network blackhole.
 
jeenam said:
Yes, the "Bridge" for the virtual network interface for VM's and containers should be set to vnet1 based on the example that I posted. The vnet1 is essentially a virtual switch. In SDN terms, it's referred to as a Bridge even though the wireless interface doesn't bridge to a physical adapter.
Click to expand...
Can I use the default vmbr0 to replace vnet1 as the bridge, I have tried this, but it doesn't work, I wonder why it doesn't work, but vnet1 can work, thank you very much
 
wanxingge said:
Can I use the default vmbr0 to replace vnet1 as the bridge, I have tried this, but it doesn't work, I wonder why it doesn't work, but vnet1 can work, thank you very much
Click to expand...

No. You can't bridge the physical wifi adapter (unless your wifi access point supports WDS mode). That's why I wrote the Tutorial.
 
You must log in or register to reply here.
Top Bottom