Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 23 May 2021 11:36:47 -0500
From:      Valeri Galtsev <galtsev@kicp.uchicago.edu>
To:        FreeBSD Mailing List <freebsd-questions@freebsd.org>
Subject:   After upgrade to 13.0-RELEASE ipfw locks the boxes
Message-ID:  <72162DBE-737D-42BA-8010-AA28DA6F2A5F@kicp.uchicago.edu>

Next in thread | Raw E-Mail | Index | Archive | Help
Dear All,

as a lazy person, before I start rewriting all my ipfw scripts I decided =
to ask somebody=E2=80=99s else wisdom. It is possible that I missed =
something I have to do related to ipfw in this particular upgrade: from =
12.2-RELEASE to 13.0-RELEASE

I have a bunch of boxes that I have rather similar (though not =
identical) ipfw scripts on, these were written a while back (around =
8.x-RELEASE), and were just slightly modified on some occasions. None of =
previous upgrades 8 =E2=80=94> 9; 9 =E2=80=94> 10,.. 11 =E2=80=94> 12 =
led to any problems as far as ipfw is concerned. I was just rebooting =
the machine after kernel upgrade, and after userland upgrade and all pkg =
reinstallation, I was testing things as usually, no problem with ipfw.

After this upgrade: to 13.0-RELEASE, ipfw effectively locks any remote =
access to the box (except for ping). My first guess was I just missed =
relevant part in release notes (which I must confess I rarely read =
carefully), but I don=E2=80=99t find anything special related to ipfw.

I hope, someone points me too obvious =E2=80=9Cpilot error=E2=80=9D I =
made. Before I start re-creating ipfw scripts, and testing every line in =
them as did when I was learning it when first started playing with ipfw.

Thanks in advance for all your answers.

Valeri

++++++++++++++++++++++++++++++++++++++++
Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247
++++++++++++++++++++++++++++++++++++++++=



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?72162DBE-737D-42BA-8010-AA28DA6F2A5F>