Okay ..
I am currently quite content with iptables as it stands on my
system..
kernel 2.4.13, and iptables 1.2.4 meets our needs quite
happily..
However, I've recently moved to an Athlon on the (questionable)
Via
chipset, and I've been given to understand that there is a fix
in 2.4.17
kernel for this....
Me being slightly mad and not having to worry too much about
production
quality (my desktop PC, and our firewall/gateway for a 5 pc
home network)
I've decided to see just what all I can get into the system,
thus for some
insane reason I am trying to put CVS iptables in ...
Here be my situation... per Harald's (offlist) suggestion I'm
now working
at getting iptables CVS onto 2.4.18rc2 (actually Harald
suggested rc1 --
but the few diffs are likely worth it considering my original
point..the
Athlon/Via situation)
If I put in the rc2 patch, I cannot apply newnat7 from patch o
matic
if I put in newnat7 on 2.4.17, part of the patch for
/net/ipv4/netfilter/ip_conntrack_irc.c out of the 2.4.18rc2
patch
will not apply. (see attatched .rej file) -- I cannot see where
this might
be in that target, and am not sure if this causes a disastrous
break.
Should I even be trying this? -- or do I just need another cup
of coffee and a
few valium....
*grin*
Alistair Tonner
ip_conntrack_irc.c.rej
Description: application/reject
