Just a warning to anyone who is considering using the 2.1.x series since
2.2 is rumoured (I stress that word highly) to be out soon. If you use
IP-Masqing it appears that the 2.1.x kernels break ipfwadm. With a broken
ipfwadm it isn't possible to add/remove IP-Masqing rules like normal.
Steve Lamb wrote:
Just a warning to anyone who is considering using the 2.1.x series since
2.2 is rumoured (I stress that word highly) to be out soon. If you use
IP-Masqing it appears that the 2.1.x kernels break ipfwadm. With a broken
ipfwadm it isn't possible to add/remove IP-Masqing
On Sat, 17 Oct 1998, Steve Lamb wrote:
Just a warning to anyone who is considering using the 2.1.x series since
2.2 is rumoured (I stress that word highly) to be out soon. If you use
IP-Masqing it appears that the 2.1.x kernels break ipfwadm. With a broken
ipfwadm it isn't possible to
Hi,
Nikolai == Nikolai Andreyevich Luzan [EMAIL PROTECTED] writes:
Nikolai This means that you will need to use the ipchains package
Nikolai (not yet debianisedq) to do firewalling/masq'ing.
What do you mean, not yet Debianized? It's in netbase.
manoj
__ type -a ipchains
On 18 Oct 1998, Manoj Srivastava wrote:
Hi,
Nikolai == Nikolai Andreyevich Luzan [EMAIL PROTECTED] writes:
Nikolai This means that you will need to use the ipchains package
Nikolai (not yet debianisedq) to do firewalling/masq'ing.
What do you mean, not yet Debianized? It's in
5 matches
Mail list logo