Warn people that ipchains and ipfwadm are going away.
Quoted 9 lines · Andi Kleen
Quoted 1 line · Martin Josefsson
Ever heard of iptables?
Except that it doesn't have usable 32bit emulation on x86-64. 32bit userland on x86-64 kernel cannot use iptables, they have to use ipchains.
I would ask for to not drop ipchains until this is fixed.
Who is doing a 32-bit userland on x86-64, and WTF for? Why do they not also run a 32-bit kernel?
Quoted 2 lines · Albert Cahalan
Who is doing a 32-bit userland on x86-64, and WTF for? Why do they not also run a 32-bit kernel?
Backwards compatibility? Desire to run binary-only 32-bit software as well as 64-bit software on the same kernel?
Chris
Quoted 7 lines · Chris Friesen
Quoted 2 lines · Albert Cahalan
Who is doing a 32-bit userland on x86-64, and WTF for? Why do they not also run a 32-bit kernel?
Backwards compatibility? Desire to run binary-only 32-bit software as well as 64-bit software on the same kernel?
Nope. For that, you run 99% 64-bit, including iptables. That's what is typically done. So you'd have a 32-bit OpenOffice maybe, and everything else is 64-bit.
I'm still not seeing a need to run an x86-64 kernel with an i386 iptables.
Quoted 11 lines · Albert Cahalan
Quoted 7 lines · Chris Friesen
Quoted 2 lines · Albert Cahalan
Who is doing a 32-bit userland on x86-64, and WTF for? Why do they not also run a 32-bit kernel?
Backwards compatibility? Desire to run binary-only 32-bit software as well as 64-bit software on the same kernel?
Quoted 8 lines
Nope. For that, you run 99% 64-bit, including iptables. That's what is typically done. So you'd have a 32-bit OpenOffice maybe, and everything else is 64-bit.
I'm still not seeing a need to run an x86-64 kernel with an i386 iptables.
Easy migration: take your fully-set-up server image, throw in an Opteron with 16GB RAM, and boot a 64-bit kernel. As long as you don't need more than 4GB/program, you're set. Except your firewall is broken.
--Andy
Quoted 2 lines · On 23 Sep 2004 15:36:34 -0400 Albert Cahalan <[email protected]> wrote:
I'm still not seeing a need to run an x86-64 kernel with an i386 iptables.
Me neither. And it's not like the netfilter tools have any interesting library dependencies either, ldd on iptables for example is merely:
libdl.so.2 => /lib/ultra3/libdl.so.2 (0x7002c000)
libnsl.so.1 => /lib/ultra3/libnsl.so.1 (0x70040000)
libc.so.6 => /lib/ultra3/libc.so.6 (0x70068000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x70000000)And that's just libc.
If Andi would code on kernel bug fixes for these problems as much as he complained about them, he wouldn't have anything to complain about :-)
I would like to see a netfilter compat layer translater engine of some sort, none the less. With the right design it won't be hard to implement things properly.
Quoted 2 lines · Albert Cahalan
Who is doing a 32-bit userland on x86-64, and WTF for? Why do they not also run a 32-bit kernel?
Debian will be shipping a 32-bit userland with a 64-bit kernel. The reasons are long, awkward, and mostly uninteresting. The reason for shipping a 64-bit kernel is that it makes it easier for users who require large quantities of VM to obtain it.
Signature · 1 line
Matthew Garrett | [email protected]
Quoted 9 lines · On Fri, 24 Sep 2004 00:08:13 +0100 Matthew Garrett…
Quoted 2 lines · Albert Cahalan
Who is doing a 32-bit userland on x86-64, and WTF for? Why do they not also run a 32-bit kernel?
Debian will be shipping a 32-bit userland with a 64-bit kernel. The reasons are long, awkward, and mostly uninteresting. The reason for shipping a 64-bit kernel is that it makes it easier for users who require large quantities of VM to obtain it.
But just like the sparc64 port, there is a 64-bit userland compilation environment available, and debian has the means to ship 64-bit specific packages on top of a mostly 32-bit userland. So it is very easy for them to ship a 64-bit netfilter utility package if they wanted to.