I upgraded to opnsense 26.1.7 yesterday and for some reason the internet just completely stopped working through both wifi and wired. I only had a backup from 25.7 so I did a fresh install of 25.7 and now the internet works but I've lost all my dhcp mappings.
My unraid server IP address has been given to another device. How do I kick this device off the address and give it to my unraid server? Sorry if my question seems silly, I'm still new to opnsense
Quote from: rama3124 on May 01, 2026, 11:30:40 PMI upgraded to opnsense 26.1.7 yesterday and for some reason the internet just completely stopped working through both wifi and wired. I only had a backup from 25.7 so I did a fresh install of 25.7 and now the internet works but I've lost all my dhcp mappings.
My unraid server IP address has been given to another device. How do I kick this device off the address and give it to my unraid server? Sorry if my question seems silly, I'm still new to opnsense
Go to Services / Dnsmasq DNS & DHCP / Hosts and create DHCP static mappings so that IP addresses get tied to MAC addresses.
Quote from: rama3124 on May 01, 2026, 11:30:40 PMI've lost all my dhcp mappings.
Why didn't you export them into a .CSV file ?!
You can do it from the webGUI directly :)
QuoteMy unraid server IP address has been given to another device.
How do I kick this device off the address and give it to my unraid server?
Your UNRAID Server should have a Static IP Address configured in it's OS and only use the Static DHCP Mapping based on the MAC Address as a backup solution in case some OS update/upgrade does something weird to your network's configuration !!
I would put the device that has "stolen" the IP Address offline now and configure your UNRAID Server correctly first.
Then when the "bad device" goes online again it should get a new IP Address :)
And last but not least :
Make sure all your Clients that connect to the UNRAID Server use host.domain.tld to connect to it instead of the IP Address.
So for example unraid.athome.lan or simply use the new .internal domain for private use : unraid.internal
This way you can just change the IP Address of the DNS Record and solve the issue too if something like this happens again in the future...