I'm cut off from my router, requesting help triaging

Started by wbk, Today at 03:22:52 PM

Previous topic - Next topic
Hi all,

TL;DR/WR: I don't have physical access to my router and upgraded in a hurry over a crappy connection. OPNsense won't come back online. Is 'power cycle' a sound approach for coming back online?

I'm not sure whether I'm in the right subforum, as I don't know on which version I am now. Sorry for that.

Longer version: I'm on holiday on the other side of the world. My last upgrade has been on or around 20th of June, to one of the 26.4 releases. Everything has been running stably until my VPN did not work this morning (Asia time).

I was able to contact someone to pull the power on the machine that runs OPNsense on Proxmox, after which all came back online. Before getting the connection back, my speculation in descending order of probability were:
* power loss (thunderstorm/surge breaker)
* random hang in the stack
* exploited vulnerability in the stack
* overheating

It was no power loss issue, nor was the room warm. Random hang is just... random; an exploit would probably have been fixed with a hotfix.

So my first step was to have the firmware upgraded over a crappy internet connection. With the connection as it is, while opening forum announcements here (OPNsense) and there (rest of the stack), I started the upgrade for OPNsense without carefully reading the release notes.

I noticed the required reboot, which did give me pause for a moment, but not long enough to call it off (I never had it not get back after an upgrade).

It did not get back, or at least, I can't connect to the router or the services behind it.

Thanks for reading so far!

The situation now:
* unsure on which version I am
* I did not change release channel from what it was at the start of the year
* I have no recollection of the upgrade progress, the page became unavailable upon refresh when I expected the upgrade to be done.
* The machine has remote management, but only accessible via the LAN side. With OPNsense down (no DHCP available) I can't ask someone to connect to it.

I have no 'boots on the ground' near the router, but I can arrange a power cycle. I'm fairly sure Proxmox will weather a power cycle. It would autostart the VM with OPNsense, and under normal circumstances OPNsense would boot and just pick up the configuration as if nothing happened.

With the upgrade to a (for me) unknown version in an unknown state, is there an other option than power cycle and hope for the best?

THanks in advance for your suggestions!

Quote from: wbk on Today at 03:22:52 PMSo my first step was to have the firmware upgraded over a crappy internet connection.
Then why do it via the webGUI ?!
(Or at all to be honest...)

Next time SSH to it and use something like screen or tmux ;)

QuoteI started the upgrade for OPNsense without carefully reading the release notes.
Well... now you know...

QuoteI noticed the required reboot, which did give me pause for a moment, but not long enough to call it off (I never had it not get back after an upgrade).
That's something that has always bothered me a bit :

I want more control over the update process and not have things done for me after a step has been completed.

Quote* The machine has remote management, but only accessible via the LAN side. With OPNsense down (no DHCP available) I can't ask someone to connect to it.
You don't need DHCP to connect directly to it ?!

Just ask someone you trust to assign a Laptop the right IP Address in the same subnet and connect P2P to it :)

QuoteWith the upgrade to a (for me) unknown version in an unknown state, is there an other option than power cycle and hope for the best?
I would ignore that option for now and try the stuff mentioned above!
Weird guy who likes everything Linux and *BSD on PC/Laptop/Tablet/Mobile and funny little ARM based boards :)