bridge-utils-1.0.6 doesn't compile succesfully on hardened-sources-2.4.31 with linux-headers-2.4.22, installs some files (docs), but not brctl and brctld masking >bridge-utils-1.0.0 solve this problem libbridge_private.h:39.2 #error Using wrong kernel headers if_bridge.h is out of date same about sockios.h and about undeclared SYSFS_BRIDGE_ATTR SYSFS_BRIDGE_PORT_ATTR SYSFS_BRIDGE_FDB Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: cant't set up a bridge - there is no brctl
you need 2.6 headers for the new bridge-utils. I'll update the DEPENDS to show this.
(In reply to comment #1) > you need 2.6 headers for the new bridge-utils. > I'll update the DEPENDS to show this. Is that safe using a 2.4 kernel and profile (which masks >=linux-headers-2.6)?
well that will mask all of the new versions for your profile then, which is the only way to make them work. Given that upstream recommends everybody use the new version, I'd like to suggest you move to 2.6-hardened kernels. I use with without any problems (the full selinux even).
Is it really necessary to move to 2.6 kernels? Compilation of any package on my server/router takes twice or more time on 2.6 kernel than on 2.4. It doesn't matter which version of 2.6 kernel is. It is pentium-mmx 200MHz with only 32MB of RAM. Is there any solution for this?
if you want the new bridge-utils, 2.6 is required, as the new bridge-utils uses sysfs. If you're content with bridge-utils-0.9*, then 2.4 is fine. Is the double time with the same minimal kernel config?
All kernels on this machine were compiled with only necessary drivers. 2.6 series uses too much swap / swaps too much. IMHO it is irrelevant to this bug. If you know how to solve issue with swapping in 2.6 please write to my personal email address: capsel@gmail.com
for a box with so little memory, uclibc might also be something to look at later on, instead of the overhead of glibc.
yo. solar presented an alterative idea, that I've implemented now in 1.0.6-r3, so you should be good to use the latest bridge-utils again.