1
23.1 Legacy Series / No Internet Connection After Updating to 23.1.10
« on: June 25, 2023, 09:52:30 am »
Hi there,
I initially updated my OPNsense (running in a Proxmox VM) when the 23 release was made. I was either running 23.0.X or 23.1.1. I don't exactly remember the release I had prior to the update currently. Regardless, since it's been a while since I updated my OPNsense and I was performing maintenance on my homelab, updating other stuff, I decided to update OPNsense as well. The update installed a new kernel and required a reboot, which happened automatically. However, upon reboot, I lost all internet connectivity in my household.
I can verify my ISP router has internet. I have connected to it via Ethernet and removed the routing/DNS setting to my OPNsense and I am able to access the internet. When reverted, and all traffic is going back to my OPNsense, my devices can get an internal IP address, thus I am able to reach my servers etc. but I cannot ping 1.1.1.1 or google.com. When pinging Google, I do not get any messages etc. presumably because I am not able to translate the domain to an IP address. When I ping 1.1.1.1, I get no route to host.
I tried downgrading to whatever I had (presumably 23.1.1) using opnsense-update -kr 23.1.1, however, since I have no internet, I cannot get the kernel/packages.
I have read that several people faced issues with the 23.1.6 update, due to the AdGuard Home plugin being broken for a bit. I have AdGuard Home in my network, but not on OPNsense as a plugin. It's on a separate VM/container (i.e. independent), and it was fully functional before the update, as I've updated it 2-3 days before I decided to update OPNsense.
I am trying to figure out what is the problem, i.e. why am I not getting any internet on my WAN, and how to fix it, but I can't seem to figure out what the problem is or what the solution is. As a result, I am curious how can I downgrade/revert the update, before I try something drastic, such as spinning up a new OPNsense VM, and migrating the traffic there using a backup of my configuration etc.
Does anyone know how can I fix this, or if they've experienced such an issue?
Thanks!
I initially updated my OPNsense (running in a Proxmox VM) when the 23 release was made. I was either running 23.0.X or 23.1.1. I don't exactly remember the release I had prior to the update currently. Regardless, since it's been a while since I updated my OPNsense and I was performing maintenance on my homelab, updating other stuff, I decided to update OPNsense as well. The update installed a new kernel and required a reboot, which happened automatically. However, upon reboot, I lost all internet connectivity in my household.
I can verify my ISP router has internet. I have connected to it via Ethernet and removed the routing/DNS setting to my OPNsense and I am able to access the internet. When reverted, and all traffic is going back to my OPNsense, my devices can get an internal IP address, thus I am able to reach my servers etc. but I cannot ping 1.1.1.1 or google.com. When pinging Google, I do not get any messages etc. presumably because I am not able to translate the domain to an IP address. When I ping 1.1.1.1, I get no route to host.
I tried downgrading to whatever I had (presumably 23.1.1) using opnsense-update -kr 23.1.1, however, since I have no internet, I cannot get the kernel/packages.
I have read that several people faced issues with the 23.1.6 update, due to the AdGuard Home plugin being broken for a bit. I have AdGuard Home in my network, but not on OPNsense as a plugin. It's on a separate VM/container (i.e. independent), and it was fully functional before the update, as I've updated it 2-3 days before I decided to update OPNsense.
I am trying to figure out what is the problem, i.e. why am I not getting any internet on my WAN, and how to fix it, but I can't seem to figure out what the problem is or what the solution is. As a result, I am curious how can I downgrade/revert the update, before I try something drastic, such as spinning up a new OPNsense VM, and migrating the traffic there using a backup of my configuration etc.
Does anyone know how can I fix this, or if they've experienced such an issue?
Thanks!