[TriLUG] SOLVED: OpenWRT Firewall Persistence

[bak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just as a follow-up on the topic of OpenWRT: for god's sake don't use
'ipkg upgrade'.  Chances are you will suffer a non-functional
configuration, either from having your config files overwritten or from
a full squashfs partition.  It's so useless and dangerous that I really
have to wonder why it's even in there.

Feeling the pain so you won't have to,

- --bak

Randy Barlow wrote:
> Randy Barlow wrote:
>> Hi all, I have OpenWRT on a Linksys 54g (v2.0) and I like it, but
>> there's one small problem.  I have some firewall rules set up to do some
>> port forwarding, and I've noticed that when the router is rebooted that
>> the firewall doesn't start by itself.  I have to ssh and run
>> /etc/init.d/S35firewall to get it going.  How do I make this part of the
>> boot sequence?  Thanks!
> 
> So I figured out the problem.  /etc/init.d/S35firewall was indeed
> getting executed at startup, but *before* /etc/init.d/S40network which
> is why it wasn't seeming to have any effect.  Why the openwrt devs
> thought the default numbering of these was appropriate is beyond me, but
> I renamed the firewall script to /etc/init.d/S41firewall and all is
> happy now!
> 
> R
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)

iD8DBQFGRoILOazs9hveao0RAslpAJ4rAr03TGcMrh0Dz97L9RNbwx7PKACZAYB7
5AUr1zJ6K5OPnwwGye3WrH0=
=a+jP
-----END PGP SIGNATURE-----