Description of problem: Shorewall fails when applying traffic control rules with the following error: RTNETLINK answers: No such file or directory This is due to some missing kernel modules that have been moved to kernel-modules-extra package. After Shorewall failure, the system network connectivity is correctly (in my opinion) blocked. Of course, for a network only device is not acceptable. How reproducible: Always Steps to Reproduce: 1. Yum upgrade a working F16 device with a boot generated firewall by Shorewall to F17 2. Reboot 3. Enjoy remote brick Actual results: No network connectivity. Expected results: Working device. Additional info: Modules used by Shorewall that have moved to kernel-modules-extra: # find /usr/share/shorewall/* -type f -exec grep 'loadmodule ' \{} \; | awk '{print $2}' | sort -u > shorewall.txt # rpm -ql kernel-modules-extra | egrep -e '\.ko' | xargs -l basename | awk -F"." '{print $1}' >> shorewall.txt # sort shorewall.txt | uniq -d Result : sch_hfsc sch_ingress sch_prio sch_sfq sch_tbf
(In reply to comment #0) > sch_hfsc > sch_ingress > sch_prio > sch_sfq > sch_tbf These should be back in the main kernel package in tomorrow's rawhide and in the next F17 kernel build.
If the next kernel package for f17 is: kernel-3.5.0-2.fc17 http://koji.fedoraproject.org/koji/buildinfo?buildID=344970 then these modules still available only into the kernel-modules-extra package.
(In reply to comment #2) > If the next kernel package for f17 is: > > kernel-3.5.0-2.fc17 Nope. I said the next kernel build. It hasn't been built yet. Bodhi will leave a comment here when it's available.
This was fixed in 3.5.0-4 (and newer).