|
|
johnny bobby bee <useraddshine_eh@xxxxxxxx> wrote in news:GpZge.107711
$3V3.18106@edtnps89:
> an option might be to use iptables-save to save the iptables rules that
> firestarter created. then user iptables-restore (something like cat
> /etc/iptables-save | iptables-restore -c) to bring them back up at
boot.
> add the iptables-restore command to something like rc.local or some
> other runlevel. then stop firestarter from coming up at boot.
>
> it's dirty, but it might work. no gui needed.
Heh heh, yeah, I know, sometimes you gotta do the dirty job just to get
it done in time. I opted for another "dirty" solution, I restart
firestarter from rc.local...
#Restart firestarter filewall to apply rules after booting
/etc/init.d/firestarter restart
It works, I get the firestarter rules message at boot now, NAT is back,
firewall runs properly.
I thought about your idea but want to retain the simplicity of the
firestarter GUI for when I need it. I use it to setup port forwarding and
it makes things easier to block errant IPs, poke holes for services, etc.
iptables are pretty darned frightening for me, I am just awe stricken by
anyone that really understands it all. Your idea would work but then I
would have to save new rules every time I changed anything in the GUI. It
would have worked, though. Thanks.
--
~Ohmster
ohmster at newsguy dot com
|
|