Author Topic: Network not working can only ping localhost (Solved)  (Read 293 times)

pksings

  • Zen Apprentice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Network not working can only ping localhost (Solved)
« on: September 29, 2021, 01:06:15 am »
Hello everyone, I have exhausted my resources on this.  My mail VM, Zentyal, has stopped talking on the network. It is a VirtualBox VM using a Bridged adapter on the only NIC active in my Linux server.  It worked for months, and after updates hasn't worked since.

I cannot ping it, it cannot ping anything. Nic (eth0) shows up, has link. It is an Intel I211-AT chipset built into my motherboard. Working fine in the base os, Linux.
 5.10.0-1045-oem kernel which I am using to get accurate CPU temps, I have also tried 5.4.0-88-generic which does not provide them.  Does not work with either of them.  All the services are running according to the Admin screen, it seems like it's fine. But it isn't.
No changes have been made other than updates for about 3 months.

Any help is very much appreciated.
Thanks.

Paul
« Last Edit: October 21, 2021, 02:06:54 am by pksings »

pksings

  • Zen Apprentice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Re: Network not working can only ping localhost [Resolved by deletion]
« Reply #1 on: October 04, 2021, 04:42:13 pm »
Well, since I got no help I am left with no other options but to remove it. Which I have done.  Not a single bit of help came from the community.
« Last Edit: October 04, 2021, 04:44:17 pm by pksings »

pksings

  • Zen Apprentice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Re: Network not working can only ping localhost (SOLVED by fixing IDS/IPS)
« Reply #2 on: October 21, 2021, 02:01:16 am »
Replying to my own post because I found the fix. The symptoms are DNS fails. Dig further and no working network.  The real problem is the IDS/IPS is not working. A config file has a critical error in it. In my case that is why it failed after an update, the previous file did not have this error apparently.

The fix is https://github.com/zentyal/zentyal/issues/2037 . long story short is this.
After some hours of research we found that in file "/etc/init.d/suricata" (date of 2nd March 2021) the line 68 was as following:
LISTEN_OPTIONS=" $NFQUEUE"
but it has to be
LISTEN_OPTIONS=" -q $NFQUEUE"
After correcting this and restarting the system, the module behaves as expected as far as we can see.

Fixed mine.....