[Bug 259782] ipfw problem during upgrade

From: <bugzilla-noreply_at_freebsd.org>
Date: Thu, 11 Nov 2021 18:39:15 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259782

            Bug ID: 259782
           Summary: ipfw problem during upgrade
           Product: Base System
           Version: 13.0-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: lg@spirale-ingenierie.com

I upgraded my remote server from version 12.2 to 13-RELEASE.
IPFW+IPDIVERT+NAT are activated. IOCAGE is installed too (5 jails).

After the first reboot (upgrade, install), I can no longer connect to my server
in SSH but the computer responds to the ping.
I have access to a FREEBSD-11 rescue console to check the server : everything
is fine in the log files. (ps : My next server will have an IP KVM access).

I was in panic mode... My provider seems to no longer support FREEBSD for the
new installations, so I cannot reinstall my server !

I disabled many services (rc.conf) but the ssh access didn't work, sometimes
the ping works sometimes not.

After the latest test (no service except basic network config) the server seems
to be down (no ping, remote hard reboot not working), the support team of my
provider put my server in rescue mode and gave me an important message : << the
login prompt is displayed >> and the server is frozen. 
I then got the idea that that the problem came from the firewall even though
the service is disabled, so the only custom settings left were in the kernel
configuration file (loader.conf).

I take back the control of my server in rescue mode and remove IPFW_LOAD and
IPDIVERT_LOAD options in the KERNEL configuration file (loader.conf) : the
server starts and the SSH access is working again. 

Now I am trying to finish the upgrade and then I will try to activate all the
necessary services one by one.

-- 
You are receiving this mail because:
You are the assignee for the bug.