No internet access on Proxmox VM due to hardcoded ethernet interface

[NuclearKitty]

Ive got HAOS running inside a VM on my Proxmox Server which is connected to my router via ethernet (Interface reads: enp6s18)

I am running the AP with a dedicated Intel 9260 WiFi Card (Interface reads: wlp1s0) via PCIe passthrough. I can connect to it and open the home assistant page, but thats it. Android reports "No Internet Access" and I cant connect to the net or even to any other devices on my LAN.

Digging through other issues and further versions the issue seems to me that the addon is hardcoded to assume "eth0" as the ethernet interface and wont work with anything else?

---

This is my config:

ssid: Cyberkitty
wpa_passphrase: ********
channel: "6"
address: 192.168.99.1
netmask: 255.255.255.0
broadcast: 192.168.99.255
interface: wlp1s0
hide_ssid: "0"
dhcp: "1"
dhcp_start_addr: 192.168.99.10
dhcp_end_addr: 192.168.99.254
allow_mac_addresses: []
deny_mac_addresses: []
debug: 1
hostapd_config_override: []
client_internet_access: "1"
client_dns_override:

• 8.8.8.8
• 1.1.1.1

dnsmasq_config_override: []

---

And this is my Log:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Starting Hass.io Access Point Addon
-# Setup interface:
Add to /etc/network/interfaces: iface wlp1s0 inet static
Run command: nmcli dev set wlp1s0 managed no
Run command: ip link set wlp1s0 down
Add to /etc/network/interfaces: address 192.168.99.1
Add to /etc/network/interfaces: netmask 255.255.255.0
Add to /etc/network/interfaces: broadcast 192.168.99.255
Run command: ip link set wlp1s0 up
-# Setup hostapd:
Add to hostapd.conf: ssid=Cyberkitty
Add to hostapd.conf: wpa_passphrase=********
Add to hostapd.conf: channel=6
Add to hostapd.conf: ignore_broadcast_ssid=0
Add to hostapd.conf: macaddr_acl=0
Add to hostapd.conf: interface=wlp1s0
-# DHCP enabled. Setup dnsmasq:
Add to dnsmasq.conf: dhcp-range=192.168.99.10,192.168.99.254,12h
Add to dnsmasq.conf: interface=wlp1s0
Add custom DNS: dhcp-option=6,8.8.8.8,1.1.1.1
-## Starting dnsmasq daemon
-## Starting hostapd daemon
rfkill: Cannot open RFKILL control device
wlp1s0: interface state UNINITIALIZED->ENABLED
wlp1s0: AP-ENABLED
wlp1s0: STA 00:0a:f5:ab:3c:ba IEEE 802.11: authenticated
wlp1s0: STA 00:0a:f5:ab:3c:ba IEEE 802.11: associated (aid 1)
wlp1s0: AP-STA-CONNECTED 00:0a:f5:ab:3c:ba
wlp1s0: STA 00:0a:f5:ab:3c:ba RADIUS: starting accounting session F3EDA9AEBFF1DA5F
wlp1s0: STA 00:0a:f5:ab:3c:ba WPA: pairwise key handshake completed (RSN)
wlp1s0: EAPOL-4WAY-HS-COMPLETED 00:0a:f5:ab:3c:ba

---

[NuclearKitty]

Add:

Can confirm, downloading the repo, modifying the "run.sh" to default to "enp6s18" instead of "eth0" and installing the addon locally makes it work like a charm.

Is it possible to bring back the ethernet interface option that was removed in 0.4.6?

[mattlongman]

Hi @NuclearKitty - yes, I'll re-apply those changes as soon as I'm able. I had some (unrelated) issues during testing so rolled back, and no feedback after that so I left it.

If you want to compare the difference in the 0.4.5 pre-release and current main branch, and submit a PR in the meantime, I can probably review it sooner.

[mezen]

@mattlongman still an issue...

Need to update 14 Shelly devices, dont want to switch all of them to a other wlan with inet and back :(

[mattlongman]

@mezen - can you check to see if v0.4.8 solves this? If not, I'll take a look from scratch.

[ROBOT0-VT]

Heyo, anyone still having this issue?

[mezen]

@mezen - can you check to see if v0.4.8 solves this? If not, I'll take a look from scratch.

Looks like it is fixed with the current version.