For presence detection.

https://www.home-assistant.io/integrations/mikrotik/

All I did was browse MikroTiks website and then started search for reviews from users wether good or bad.

CC: @nprofile1q...

Beans will do that to you. 😉

I know what you mean as I have previously never considered MikroTik before for some reason ? I guess I just listened to the bad rep posts about how hard they were to setup which was my ultimate mistake because I really love this equipment. I might not need an excuse to purchase more and I can hopefully sneak into the home without the other half noticing. 🤣

I'm actually glad to be rid of the US equipment and I did notice that the AP casing had gone sticky for some reason. It's only been ceiling mounted for a good 5 or so years. Oh good riddance and as for the #MikroTik I'm surprised by how good it's range is as I thought it might be a little less than the UniFi AC Pro but no it's better. I'm not sure if I'm going to have an excuse to purchase another for downstairs yet as it works so well ????

So I've got my #Mikrotik cAP ax mounted and the #UniFi equipment removed from my #Homelab successfully. I've also integrated it into #HomeAssistant just because with it's own user and group using the api. So far so good and yes there are a lot of settings in the MikroTik and it takes some understanding but I got there in the end. Even upgraded it and made backups. 😁

Yes re1 is fine on it's own without lagg. It all seems to be working now though thanks.

RESOLVED

After reading Tom's config and adjusting mine this seems to be now working across reboots and I can restart netif without any issues now.

/etc/rc.conf

# WiFi
ifconfig_re1="up"
ifconfig_iwlwifi0="ether *:*:*:*:*:*"
wlans_iwlwifi0="wlan0"
ifconfig_wlan0="WPA"
cloned_interfaces="lagg0"
ifconfig_lagg0="up laggproto failover laggport re1 laggport wlan0 DHCP"
Thanks Tom ! 😉

Thanks Tom but this is what I now have and still if I run doas service netif restart then it toggles network connectivity. On first boot I have no network access but restarting netif gives me network access and the lagg works perfectly switching between re1 and wlan0 if I pull the lan cable. But if I then restart netif if all fails until I restart netif again.

/etc/rc.conf

# WiFi
ifconfig_re1="up"
ifconfig_re1="ether *:*:*:*:*:*"
wlans_iwlwifi0="wlan0"
ifconfig_wlan0="WPA"
cloned_interfaces="lagg0"
ifconfig_lagg0="up laggproto failover laggport re1 laggport wlan0 DHCP"
PS I've hidden re1 MAC address but I have it entered correctly.

It's really strange. I see there is a part that you add a line like ifconfig_re0="ether b8:ee:65:5b:32:59" which is the line in the handbook. I'll try adding that and see what difference it makes.

Some progress I think ? If I change the line in my /etc/rc.conf to the following then the network survives on running doas service netif restart but on reboot the wlan0 gets stuck on the DHCP stuff and I have to ctrl + c to let the boot continue.

#ifconfig_wlan0="WPA SYNCDHCP"
ifconfig_wlan0="WPA DHCP"
#FreeBSD

Yes it's like I run doas service netif restart once and it works but run it again it fails kind of like toggling the network ???