Hi,
Installed HA using this procedure - but I have a problem with the IP address assignment. Once I installed Debian 11, IP is being assigned by my modem without any issues (tried host restart too), but once I install HA and restart the host, it is not being assigned an IP address.
Then I configured a static IP address using the following:
root@NUC01:/home/# cd /etc/network
root@NUC01:/home/# vi interfaces
source /etc/network/interfaces.d/*
auto lo
iface lo inet loopback
auto enp0s25
iface enp0s25 inet static
address 192.168.1.230
netmask 255.255.255.0
gateway 192.168.1.254
dns-nameservers 192.168.1.254
IP configured is being assigned by I the machine is not able to resolve DNS queries.
Once I add the following DNS works fine, but this entry is removed on host restart
root@NUC01:/home/# cat /etc/resolv.conf
#Generated by NetworkManager
nameserver 8.8.8.8
Is there a particular reason why IP is not being assigned (never had issues with Debian 10)
Now check whether the resolvconf service has started correctly: sudo systemctl status resolvconf.service
If it has started correctly add the nameserver IP addresses of your choice to the resolvconf configuration file “head” : sudo nano /etc/resolvconf/resolv.conf.d/head
Prepend valid nameservers of your choice below the comments, i.e.:
nameserver 192.168.1.254
nameserver 8.8.8.8
Now run resolv.conf update: sudo resolvconf --enable-updates sudo resolvconf -u
Make sure the new nameserver addresses have been added by displaying the contents of /etc/resolv.conf : sudo cat /etc/resolv.conf
Whenever you want to change or add nameservers just change the file “head” (as above) and re-run: sudo resolvconf -u
thanks for the detailed info … followed this procedure but now the contents of resolv.conf is empty. Do I need to reboot the machine for changes to take effect?
root@NUC01:/# more /etc/resolvconf/resolv.conf.d/head
nameserver 192.168.1.254
nameserver 8.8.8.8
EDIT: after the reboot resolve.conf contains the following
root@NUC01:/home# more /etc/resolv.conf #Generated by NetworkManager
root@NUC01:/home#
root@NUC01:/home#
root@NUC01:/home#
i wouldnt be surprised if i messed it up but i installed everything from scratch three times following the procedure to the letter.
will return the output this evening because i currently out and i removed port forwarding from my modem and cannot access it remotely. btw thanks for the follow up!
root@NUC01:/home/# ip -c link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether b8:ae:ed:72:73:e2 brd ff:ff:ff:ff:ff:ff
3: hassio: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 02:42:af:c5:3b:e9 brd ff:ff:ff:ff:ff:ff
4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 02:42:34:d2:5b:e3 brd ff:ff:ff:ff:ff:ff
6: vetheea252d@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP mode DEFAULT group default
link/ether 82:82:62:a5:15:8e brd ff:ff:ff:ff:ff:ff link-netnsid 0
8: vethb5237aa@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT group default
link/ether b6:ef:e2:e3:52:61 brd ff:ff:ff:ff:ff:ff link-netnsid 1
10: vethfc7f4e6@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP mode DEFAULT group default
link/ether 8a:8f:30:b6:24:5d brd ff:ff:ff:ff:ff:ff link-netnsid 1
12: veth526c9de@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP mode DEFAULT group default
link/ether fe:f9:fd:16:ec:a4 brd ff:ff:ff:ff:ff:ff link-netnsid 2
14: veth5bbd3e0@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP mode DEFAULT group default
link/ether 52:8c:05:62:6b:57 brd ff:ff:ff:ff:ff:ff link-netnsid 3
16: veth165cafa@if15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master hassio state UP mode DEFAULT group default
link/ether 92:07:fd:6d:3f:ac brd ff:ff:ff:ff:ff:ff link-netnsid 4
yeah this is very strange … in my opinion it is not accepting any IP assignment through DHCP once Supervisor is installed… had no issues when installed same setup on Debian 10
I did the same install 3-4 months ago on Debian 11.3 and had no issues. I’ve tried multiple fresh installs, different hypervisors, tried different ways and as soon as I install supervisor, no IP.
hi again Tamsy, if it will help you i kept a copy of the CLI and output of the commands executed during the last install. if interested to take a look drop me a DM
I’m having the same issue here, I just reinstall HA supervise and after the first reboot after the installation I loose connectivity, my network adapter lose its IP. If I uninstall HA, I regain connectivity. I reinstall it and lose again. I don’t know what todo.
Having a similar issue for Supervised on Debian 11 not giving IP’s after reboot. Base on my understanding it will replace /etc/network/interface which make the IP disappears. In my case restoring the original interface did revive the IP’s however that machine will inquire a 2nd IP’s which is really strange. I have been trying to remove the 2nd IP’s without any success.
but i installed everything from scratch three times following the procedure to the letter.