I build a new whiterussian firmware to fix a problem as discussed here but some of you could find it useful for other situations, so I post it here for review and comment.
Kamikaze have all this resolved plus is a lot better, this is just a bandage to whiterussian (which is obsolete), please if you can, use Kamikaze instead.
Latest source patch (Version 5).
Version 5 - May/20/2007 - Changes:
Decouple netfilter (specially ip_conntrack) from the kernel to external loadable modules in kmod_iptables package.
Fix selects and depends for kmod_iptables.
Fix iptables list of builtin extensions.
Version 4 - May/20/2007 - Changes:
Resync with svn.
Revert back gcc, kernel, wlcompat, switch, iptables and squashfs versions in order to keep binary/source compatibility and minimum differences with upstream Whiterussian.
Port Kamikaze's bcm47xx arch to kernel 2.4.30 so latest wl driver works with this kernel.
Version 3 - May/4/2007 - Changes:
wl driver from 184.108.40.206 to 220.127.116.11
wificonf patched to recognize wl?_spect nvram variable, if not present disable spectrum management (802.11h & 802.11d) at wifi setup.
netconsole dropped (instability with wl driver).
Version 2 - May/2/2007 - Changes:
Version 1 - April/25/2007 - Original changes to whiterussian (svn):
gcc from 3.4.4 to 3.4.6
kernel from 2.4.30 to 18.104.22.168
wl driver from 22.214.171.124 to packaged 126.96.36.199
wlcompat driver from kamikaze
diag driver from kamikaze
switch driver from kamikaze
iptables from 1.3.3 to 1.3.5
squashfs from 2.1r2 to 3.0
(Last edited by solca on 20 May 2007, 22:34)