Jump to content

Home Assistant on eisy not online

tazman

By tazman
in Home Assistant

Recommended Posts

tazman Advanced

tazman

Posted
  • Author
Posted

I managed to get eisy up and running with something I found online. After eisy is up I was able to get HA running again with the sudo dhclient tap0 sudo dhclient  vm-public Now I just need to be patient and wait to see what @Michel Kohanim's thoughts on how I got it to work.

xKing Advanced

xKing

Posted
Posted

LOL @Michel Kohanim I'm not a guru it just always works for me :D 

@tazman and @rob7419

You don't really need to `dhclient` the `vm-public` nor `tap` devices, those don't need an IP address. Check your rc.conf, there should be no `ifconfig` entries besides these 2: 

ifconfig_re0="DHCP"
ifconfig_re0_ipv6="accept_rtadv"

 

after reboot your `ifconfig -a` should look similar to this (no tap, but vm-bridge is UP): 

re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
	ether 00:21:b9:02:5d:7a
	inet6 fe80::221:b9ff:fe02:5d7a%re0 prefixlen 64 scopeid 0x1
	inet6 fd18:31e5:33f2:844e:221:b9ff:fe02:5d7a prefixlen 64 detached autoconf
	inet 10.0.1.152 netmask 0xffffff00 broadcast 10.0.1.255
	media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
	nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
	inet 127.0.0.1 netmask 0xff000000
	groups: lo
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
vm-public: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	ether 52:14:e6:86:b4:2f
	id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
	maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
	root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
	member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
	        ifmaxaddr 0 port 1 priority 128 path cost 20000
	groups: bridge vm-switch viid-4c918@
	nd6 options=9<PERFORMNUD,IFDISABLED>

 

Start the VM (`sudo vm start homeassistant`) your `ifconfig -a` output should become like this: 

re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=82099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
	ether 00:21:b9:02:5d:7a
	inet6 fe80::221:b9ff:fe02:5d7a%re0 prefixlen 64 scopeid 0x1
	inet6 fd18:31e5:33f2:844e:221:b9ff:fe02:5d7a prefixlen 64 detached autoconf
	inet 10.0.1.152 netmask 0xffffff00 broadcast 10.0.1.255
	media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
	nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
	inet 127.0.0.1 netmask 0xff000000
	groups: lo
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
vm-public: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	ether 52:14:e6:86:b4:2f
	id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
	maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
	root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
	member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
	        ifmaxaddr 0 port 4 priority 128 path cost 2000000
	member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
	        ifmaxaddr 0 port 1 priority 128 path cost 20000
	groups: bridge vm-switch viid-4c918@
	nd6 options=9<PERFORMNUD,IFDISABLED>
tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
	description: vmnet/homeassistant/0/public
	options=80000<LINKSTATE>
	ether 58:9c:fc:10:f8:32
	groups: tap vm-port
	media: Ethernet autoselect
	status: active
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
	Opened by PID 5537

 

`vm-public` has 2 ports `re0` and `tap0` and all interfaces are `UP` 

You should be able to see traffic on `tap0` interface, for example something like this:
  

# just dump on the screen
sudo tcpdump -i tap0 -s0 -vvv

# save a .pcap file
sudo tcpdump -i tap0 -s0 -w trace1.pcap

see if you can capture a minute or two of traffic and attach what you have (or PM me).

For the reference - I'm using pfSense 23.09.1-RELEASE as a router with KEA as DHCP server selected.

tazman Advanced

tazman

Posted
  • Author
Posted
11 minutes ago, xKing said:

LOL @Michel Kohanim I'm not a guru it just always works for me :D 

@tazman and @rob7419 

You don't really need to `dhclient` the `vm-public` nor `tap` devices, those don't need an IP address. Check your rc.conf, there should be no `ifconfig` entries besides these 2: 

ifconfig_re0="DHCP"
ifconfig_re0_ipv6="accept_rtadv"



 

The dhclient was just a way I found to make the vm come online. 

ifconfig_re0="DHCP"



ifconfig_re0_ipv6="inet6 accept_rtadv"

Was already in mine and I placed # in front of the home assistant so it would not start automatically.

11 minutes ago, xKing said:

after reboot your `ifconfig -a` should look similar to this (no tap, but vm-bridge is UP): 

re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
	ether 00:21:b9:02:5d:7a
	inet6 fe80::221:b9ff:fe02:5d7a%re0 prefixlen 64 scopeid 0x1
	inet6 fd18:31e5:33f2:844e:221:b9ff:fe02:5d7a prefixlen 64 detached autoconf
	inet 10.0.1.152 netmask 0xffffff00 broadcast 10.0.1.255
	media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
	nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
	inet 127.0.0.1 netmask 0xff000000
	groups: lo
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
vm-public: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	ether 52:14:e6:86:b4:2f
	id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
	maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
	root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
	member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
	        ifmaxaddr 0 port 1 priority 128 path cost 20000
	groups: bridge vm-switch viid-4c918@
	nd6 options=9<PERFORMNUD,IFDISABLED>

 After restart 

[admin@eisy ~]$ sudo ifconfig -a
Password:
re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether 00:21:b9:02:61:da
        inet6 fe80::221:b9ff:fe02:61da%re0 prefixlen 64 scopeid 0x1
        inet6 2601:500:8801:38a0:221:b9ff:fe02:61da prefixlen 64 autoconf
        inet 10.0.0.66 netmask 0xffffff00 broadcast 10.0.0.255
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
        inet 127.0.0.1 netmask 0xff000000
        groups: lo
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
vm-public: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 96:f8:51:04:43:ae
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000
        groups: bridge vm-switch viid-4c918@
        nd6 options=9<PERFORMNUD,IFDISABLED>
11 minutes ago, xKing said: 
[admin@eisy ~]$ sudo ifconfig -a
Password:
re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether 00:21:b9:02:61:da
        inet6 fe80::221:b9ff:fe02:61da%re0 prefixlen 64 scopeid 0x1
        inet6 2601:500:8801:38a0:221:b9ff:fe02:61da prefixlen 64 autoconf
        inet 10.0.0.66 netmask 0xffffff00 broadcast 10.0.0.255
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
        inet 127.0.0.1 netmask 0xff000000
        groups: lo
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
vm-public: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 96:f8:51:04:43:ae
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000
        groups: bridge vm-switch viid-4c918@
        nd6 options=9<PERFORMNUD,IFDISABLED>

Start the VM (`sudo vm start homeassistant`) your `ifconfig -a` output should become like this: 

re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=82099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
	ether 00:21:b9:02:5d:7a
	inet6 fe80::221:b9ff:fe02:5d7a%re0 prefixlen 64 scopeid 0x1
	inet6 fd18:31e5:33f2:844e:221:b9ff:fe02:5d7a prefixlen 64 detached autoconf
	inet 10.0.1.152 netmask 0xffffff00 broadcast 10.0.1.255
	media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
	nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
	inet 127.0.0.1 netmask 0xff000000
	groups: lo
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
vm-public: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	ether 52:14:e6:86:b4:2f
	id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
	maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
	root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
	member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
	        ifmaxaddr 0 port 4 priority 128 path cost 2000000
	member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
	        ifmaxaddr 0 port 1 priority 128 path cost 20000
	groups: bridge vm-switch viid-4c918@
	nd6 options=9<PERFORMNUD,IFDISABLED>
tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
	description: vmnet/homeassistant/0/public
	options=80000<LINKSTATE>
	ether 58:9c:fc:10:f8:32
	groups: tap vm-port
	media: Ethernet autoselect
	status: active
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
	Opened by PID 5537

 

`vm-public` has 2 ports `re0` and `tap0` and all interfaces are `UP`  

[admin@eisy ~]$ sudo ifconfig -a
re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=82099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether 00:21:b9:02:61:da
        inet6 fe80::221:b9ff:fe02:61da%re0 prefixlen 64 scopeid 0x1
        inet6 2601:500:8801:38a0:221:b9ff:fe02:61da prefixlen 64 autoconf
        inet 10.0.0.66 netmask 0xffffff00 broadcast 10.0.0.255
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
        inet 127.0.0.1 netmask 0xff000000
        groups: lo
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
vm-public: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 96:f8:51:04:43:ae
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 4 priority 128 path cost 2000000
        member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000
        groups: bridge vm-switch viid-4c918@
        nd6 options=9<PERFORMNUD,IFDISABLED>
tap0: flags=8942<BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: vmnet/homeassistant/0/public
        options=80000<LINKSTATE>
        ether 58:9c:fc:10:90:31
        groups: tap vm-port
        media: Ethernet autoselect
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        Opened by PID 8050

 

 After starting home assistant and showing running under vm list but is not available at homeassistant.local:8123 where I find it when it is running. 

[admin@eisy ~]$ sudo ifconfig -a
re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=82099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether 00:21:b9:02:61:da
        inet6 fe80::221:b9ff:fe02:61da%re0 prefixlen 64 scopeid 0x1
        inet6 2601:500:8801:38a0:221:b9ff:fe02:61da prefixlen 64 autoconf
        inet 10.0.0.66 netmask 0xffffff00 broadcast 10.0.0.255
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
        inet 127.0.0.1 netmask 0xff000000
        groups: lo
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
vm-public: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 96:f8:51:04:43:ae
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 4 priority 128 path cost 2000000
        member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000
        groups: bridge vm-switch viid-4c918@
        nd6 options=9<PERFORMNUD,IFDISABLED>
tap0: flags=8942<BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: vmnet/homeassistant/0/public
        options=80000<LINKSTATE>
        ether 58:9c:fc:10:90:31
        groups: tap vm-port
        media: Ethernet autoselect
        status: active
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        Opened by PID 8050
11 minutes ago, xKing said:

You should be able to see traffic on `tap0` interface, for example something like this:
  

# just dump on the screen
sudo tcpdump -i tap0 -s0 -vvv

# save a .pcap file
sudo tcpdump -i tap0 -s0 -w trace1.pcap

see if you can capture a minute or two of traffic and attach what you have (or PM me).

For the reference - I'm using pfSense 23.09.1-RELEASE as a router with KEA as DHCP server selected. 

[admin@eisy ~]$ sudo tcpdump -i tap0 -s0 -vvv
tcpdump: listening on tap0, link-type EN10MB (Ethernet), capture size 262144 bytes

 

 Since home assistant is not running there is no traffic. 

[admin@eisy ~]$ sudo tcpdump -i tap0 -s0 -vvv
tcpdump: listening on tap0, link-type EN10MB (Ethernet), capture size 262144 bytes
tazman Advanced

tazman

Posted
  • Author
Posted

@xKingif it just works for you I think that makes you a guru I appreciate the help and I hope you can follow my previous post ok!

xKing Advanced

xKing

Posted
Posted

So what happens if after you bring the home assistant you do this 

sudo ifconfig vm-public up; sudo ifconfig tap0 up

 

Also try adding this into `/etc/sysctl.conf` and reboot 

net.link.tap.up_on_open=1

 

tazman Advanced

tazman

Posted
  • Author
Posted
3 minutes ago, xKing said:

So what happens if after you bring the home assistant you do this 

sudo ifconfig vm-public up; sudo ifconfig tap0 up

 

@xKingthat brought it up! Now will that carry over on reboot or is there something we need to add somewhere?

tazman Advanced

tazman

Posted
  • Author
Posted
13 minutes ago, xKing said:

Do you have  

vm_enable="YES"

In your `/etc/rc.conf` ?

Yes

 

tazman Advanced

tazman

Posted
  • Author
Posted
52 minutes ago, xKing said:

 

Also try adding this into `/etc/sysctl.conf` and reboot 

net.link.tap.up_on_open=1

 

Added

 

25 minutes ago, xKing said:

Stop home assistant, reboot eisy, do check this 

sysctl -a | grep net.link.tap.up_on_open

 

Output 

[admin@eisy ~]$ sysctl -a | grep net.link.tap.up_on_open
net.link.tap.up_on_open: 1

But if I try to enable vm_list="homeassistant" in rc.conf the virtual switches are not UP any more.

tazman Advanced

tazman

Posted
  • Author
Posted (edited)
On 3/9/2024 at 1:07 PM, KSaccullo01 said:

Restart HA as a CRON job. Have CRON wait 3 minutes before starting HA.

 

@xKingthis was a suggestion that might help now?

Edited by tazman
tazman Advanced

tazman

Posted
  • Author
Posted

@KSaccullo01I tried putting the below line at the bottom of the /etc/crontrab and homeassistant does not start for me. 

@reboot sleep 180 && vm start homeassistant

 

tazman Advanced

tazman

Posted
  • Author
Posted 
###MAINTAINED BY UDX####
###DO NOT MODIFY###

hostname="eisy"
# Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
dumpdev="NO"

zfs_enable="YES"
dbus_enable="YES"
sshd_enable="YES"
moused_nondefault_enable="NO"

sendmail_submit_enable="NO"
sendmail_outbound_enable="NO"
sendmail_msp_queue_enable="NO"

clear_tmp_enable="YES"

#NTP
ntpd_enable="YES"
ntpd_sync_on_start="YES"

#HDMI is disabled by default
#kld_list="i915kms"

#Make sure dhclient is run in the background
background_dhclient="YES"

#make sure we support double stack
ipv6_ipv4mapping="YES"


defaultroute_delay="0"

#Network Interfaces (default)
rtsold_enable="YES"

#for now, do not let iwlwifi/iwm get loaded
devmatch_enable="YES"
devmatch_blocklist="if_iwm if_iwlwifi"



UDX_UPGRADE_STATUS="active"
ifconfig_re0_ipv6="accept_rtadv"



ifconfig_re0="DHCP"



ifconfig_re0_ipv6="inet6 accept_rtadv"
vm_enable="YES"
vm_dir="zfs:storage/vms"
vm_list="homeassistant"
mdnsresponderposix_flags="-f /usr/local/etc/udx.d/static/mdns.services"
~
~
~
~

 

xKing Advanced

xKing

Posted
Posted

Ok, try commenting out just `vm_list` from `/etc/rc.conf` and comment out the line you put in `/etc/sysctl.conf` 
reboot and see what does the `sysctl -a | grep up_on_open`  say?

you also have a duplicate ifconfig_re0_ipv6 in /etc/rc.conf - please delete the second one

tazman Advanced

tazman

Posted
  • Author
Posted

@xKingthe lines are a little different which one should go? 

ifconfig_re0_ipv6="accept_rtadv"

ifconfig_re0_ipv6="inet6 accept_rtadv"

With the 'vm_list' out and '/etc/sysctl.conf' line out 

[admin@eisy ~]$ sysctl -a | grep up_on_open
net.link.tap.up_on_open: 1

 

tazman Advanced

tazman

Posted
  • Author
Posted

@xKingattached is my homeassistant.conf file is there any other VM configuration you know of? 

loader="uefi"
cpu="2"
memory="2G"
network0_type="virtio-net"
network0_switch="public"
disk0_name="disk0"
disk0_dev="sparse-zvol"
disk0_type="virtio-blk"
uuid="EDIT"
network0_mac="EDIT"
#graphics="yes"
#graphics_wait="yes"

 

xKing Advanced

xKing

Posted
Posted

That looks fine, so what happens if you do `sudo vm start homeassistant` now - would tap0 still come up with no “UP” flag and require `sudo ifconfig tap0 up` ?

 

Delete this:  

ifconfig_re0_ipv6="inet6 accept_rtadv"
tazman Advanced

tazman

Posted
  • Author
Posted

@xKingfor this instance everything started fine Tap0 is UP and home assistant became available at homeassistant.local:8123 but I don't know that it would happen all the time unless it is just a matter of starting HA after everything else.

xKing Advanced

xKing

Posted
Posted

Just to clarify - when you say you restarted and interfaces were not up - do you mean that you have vm_list=“homeassistant” uncommented? Or you booted and did `vm start homeassistant` manually?

Guest
This topic is now closed to further replies.
Go to topic listing
×
×
  • Create New...