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

[WamuuWasAwaken]

ok i managed to install traceroute on the first vm and here's what happens when i traceroute 8.8.8.8:

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  _gateway (192.168.3.1)  0.293 ms  0.264 ms  0.257 ms
 2  192.168.1.1 (192.168.1.1)  2.248 ms  2.717 ms  2.947 ms
 3  151.7.206.36 (151.7.206.36)  12.447 ms  12.516 ms  12.826 ms
 4  151.7.51.168 (151.7.51.168)  12.429 ms  12.423 ms  12.943 ms
 5  151.6.1.168 (151.6.1.168)  13.780 ms  13.775 ms 151.6.3.180 (151.6.3.180)  14.432 ms
 6  151.6.7.181 (151.6.7.181)  13.677 ms 151.6.7.239 (151.6.7.239)  13.608 ms  13.904 ms
 7  74.125.32.80 (74.125.32.80)  13.986 ms  13.390 ms  15.355 ms
 8  * * *
 9  8.8.8.8 (8.8.8.8)  10.239 ms  10.442 ms  9.955 ms

 

[jeenam]

ok i managed to install traceroute on the first vm and here's what happens when i traceroute 8.8.8.8:

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  _gateway (192.168.3.1)  0.293 ms  0.264 ms  0.257 ms
 2  192.168.1.1 (192.168.1.1)  2.248 ms  2.717 ms  2.947 ms
 3  151.7.206.36 (151.7.206.36)  12.447 ms  12.516 ms  12.826 ms
 4  151.7.51.168 (151.7.51.168)  12.429 ms  12.423 ms  12.943 ms
 5  151.6.1.168 (151.6.1.168)  13.780 ms  13.775 ms 151.6.3.180 (151.6.3.180)  14.432 ms
 6  151.6.7.181 (151.6.7.181)  13.677 ms 151.6.7.239 (151.6.7.239)  13.608 ms  13.904 ms
 7  74.125.32.80 (74.125.32.80)  13.986 ms  13.390 ms  15.355 ms
 8  * * *
 9  8.8.8.8 (8.8.8.8)  10.239 ms  10.442 ms  9.955 ms

The traceroute output you reported indicates the networking configuration is set up properly and your VM can reach the internet. If you want to route to hosts on the 192.168.3.0 network from hosts on the 192.168.1.0 network you will need to add static routes on hosts that reside on the 192.168.1.0 network. I included instructions in my post on how to add static routes for MacOS, and links to instructions for WIndows and Linux. The instructions are at the end of the first post.

 

[WamuuWasAwaken]

ok but there's still a problem: i can ping ip addresses fine but i can't apt update or ping any domain

$ ping google.com
ping: google.com: Temporary failure in name resolution

$ ping youtube.com
ping: youtube.com: Temporary failure in name resolution

 

[jeenam]

What does the command dig @1.1.1.1 google.com show? If it resolves properly then all you need to do is properly configure your VM to point to a valid DNS server for name resolution. You can use 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) for DNS servers.

 

[WamuuWasAwaken]

it seems to be working

$ dig @1.1.1.1 google.com

; <<>> DiG 9.18.12-0ubuntu0.22.04.2-Ubuntu <<>> @1.1.1.1 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26635
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             215     IN      A       142.251.209.14

;; Query time: 4 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Wed Jul 03 05:35:09 UTC 2024
;; MSG SIZE  rcvd: 44

 

[jeenam]

it seems to be working

$ dig @1.1.1.1 google.com

; <<>> DiG 9.18.12-0ubuntu0.22.04.2-Ubuntu <<>> @1.1.1.1 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26635
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             215     IN      A       142.251.209.14

;; Query time: 4 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Wed Jul 03 05:35:09 UTC 2024
;; MSG SIZE  rcvd: 44

The Wifi configuration with routed configured is working 100% as expected and is fully functional. Your problem now is that your VM is not properly configured for DNS resolution.

https://www.pdq.com/blog/change-dns-server-settings-in-windows/

https://www.tecmint.com/set-permanent-dns-nameservers-in-ubuntu-debian/

https://www.cyberciti.biz/faq/change-dns-ip-address-rhel-redhat-linux/

https://support.apple.com/guide/mac-help/change-dns-settings-on-mac-mh14127/mac

You can use 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) for DNS servers.

 

[WamuuWasAwaken]

The Wifi configuration with routed configured is working 100% as expected and is fully functional. Your problem now is that your VM is not properly configured for DNS resolution.

https://www.pdq.com/blog/change-dns-server-settings-in-windows/

https://www.tecmint.com/set-permanent-dns-nameservers-in-ubuntu-debian/

https://www.cyberciti.biz/faq/change-dns-ip-address-rhel-redhat-linux/

https://support.apple.com/guide/mac-help/change-dns-settings-on-mac-mh14127/mac

You can use 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) for DNS servers.

it works perfectly now, thank you

 

[jeenam]

I recently discovered there was a typo in the /etc/network/interfaces config posted in step 14. At some point spellcheck kicked in and changed 'o' to '0' by mistake for the FORWARD -o rules. The error has no effect on functionality as far as I can tell. Here is the proper config since I can't edit my original post.

auto lo
iface lo inet loopback

iface enp1s0 inet manual

auto wlp4s0
iface wlp4s0 inet manual
               address 192.168.1.100/24
               gateway 192.168.1.1

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

auto vnet1
iface vnet1 inet static
               address 192.168.3.1/24
               bridge-ports none
               bridge-stp off
               bridge-fd 0
               hwaddress f6:c7:43:09:0b:45
               post-up echo 1 > /proc/sys/net/ipv4/ip_forward
               post-up iptables -A FORWARD -i wlp4s0 -j ACCEPT
               post-up iptables -A FORWARD -o wlp4s0 -j ACCEPT
               post-up iptables -A FORWARD -i vnet1 -j ACCEPT
               post-up iptables -A FORWARD -o vnet1 -j ACCEPT


source /etc/network/interfaces.d/*