OPNsense Forum

Archive => 17.1 Legacy Series => Topic started by: akashkaveti on April 20, 2017, 10:54:32 am

Title: OPNsense unresponsive-Network down but WAN working
Post by: akashkaveti on April 20, 2017, 10:54:32 am

Hello,

we are facing a strange situation, where network is down but the WAN connection seems to be working fine.
after the reboot of opnsense the network works normally.

I tried checking the logs but couldn't find any.

Thanks

Title: Re: OPNsense unresponsive-Network down but WAN working
Post by: bringha on April 20, 2017, 12:47:38 pm

Hi,

can you still access GUI or ssh the opnsense?

Br br

Title: Re: OPNsense unresponsive-Network down but WAN working
Post by: akashkaveti on April 20, 2017, 12:49:45 pm

No I cant access both.

Title: Re: OPNsense unresponsive-Network down but WAN working
Post by: bringha on April 20, 2017, 06:45:39 pm

Can you login on console directly ?

(serial, vga,....)

Title: Re: OPNsense unresponsive-Network down but WAN working
Post by: akashkaveti on April 21, 2017, 10:56:22 am

I have disabled the console access as we were using the ssh.

Title: Re: OPNsense unresponsive-Network down but WAN working
Post by: bringha on April 21, 2017, 12:04:15 pm

Hmmmm - I assume that your system does not show any life sign anymore (e.g. flashing disk LED or so?!) - then only a hard reboot helps.

BTW: I face a similar problem: after a few weeks of stable operation, my systems completely halts out of the sudden. Have this since upgrade to 17.1, meanwhile 4 times in the last three months. No hint in the logs after reboot, no access over NICs or even the BMC console possible - system is simply dead.

I have now activated the physical console again to see whether some hints/messages are shown after the crash there. Even booting with the -v option does not show any additional information. Have also run a diagnose tool to check hardware, no findings...  :-\. Am a little lost how to analyze this further ...

br br

Could you perhaps check after the reboot whether you can see something in the logs? (system.log. dmesg.today, dmesg.yesterday, ....)

Br br