On Tuesday 12 November 2019 21:35:49 Gene Heskett wrote: > On Tuesday 12 November 2019 19:53:15 John Hasler wrote: > > I wrote: > > > Install Shorewall. > > > > Gene writes: > > > Did, spent half an hour reading its man page, but I don't see a > > > command that will extract and save an existing iptables setup, and > > > a later reapply of that saved data. > > > > I meant use it instead of using Iptables directly: the package takes > > care of restoring filter rules on boot and is more user-friendly > > than Iptables. Shorewall-save will save the existing rules. > > > > But why aren't you already using Iptables-save and Iptables-restore? > > I am now,, so that problem is solved.
Except its not apparently setup to restore at bootup. Long story even longer. Motherboard burned up at a usb breakout connection early friday evening, and I have moved 2 of the drives from that machine to an old, slow and memory starved Dell So memory starved that the middle of the night job will probably fail from OOM, so I'll kill the cron job before I hit the rack. It, iptables, did not get restarted on the fresh boot, so obviously the systemd manager hasn't been informed to start iptables, reloading from /etc/iptables/saved-rules. So 1. how do I query systemd to determine if it should have started iptables, and if not, 2. what is the command to set it so it does start iptables at bootup? All new stuff for a new build ordered, but will be later this week arriving. Thanks everyone. > Cheers, Gene Heskett Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
