similar to: rp_filter and fib_validate_source sequence in KPTD

Greetings, I''ve been experiencing problems with HTB where the whole machine locks up. This usually happens when the whole qdisc is being removed and occasionally when a leaf is being removed. Common is that it always happens when some sort of removal is in progress. Console output I have captured is at the end of this message. The same behavior exists from vanilla 2.6.19.7 and above.

Hi all, Our kernel is 2.6.32-358.14.1.x86_64, recently dozens of them panicked, since it's been OK for a long time and the problem emerged all of a sudden, I'm not sure if an upgrade caused this problem. Here's what I got from backtracing: PID: 8136 TASK: ffff8803341aead0 CPU: 2 COMMAND: "" #0 [ffff880028283610] panic at ffffffff815286b8 #1 [ffff880028283690]

http://bugzilla.netfilter.org/show_bug.cgi?id=714 Summary: Kernel panics in same_src() Product: netfilter/iptables Version: linux-2.6.x Platform: x86_64 OS/Version: All Status: NEW Severity: normal Priority: P5 Component: NAT AssignedTo: netfilter-buglog at lists.netfilter.org ReportedBy:

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=42 Summary: Kernel panic in PSD Product: netfilter/iptables Version: patch-o-matic Platform: i386 OS/Version: other Status: NEW Severity: major Priority: P2 Component: ip_tables (kernel) AssignedTo: laforge@netfilter.org

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=22 laforge@netfilter.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bowles@ambisys.com Component|unknown |ip_tables (kernel) OS/Version|other

I see this ocasionally on one of my CentOS 6.3 x64 systems: Oct 18 03:10:52 backup kernel: swapper: page allocation failure. order:1, mode:0x20 Oct 18 03:10:52 backup kernel: Pid: 0, comm: swapper Not tainted 2.6.32-279.9.1.el6.x86_64 #1 Oct 18 03:10:52 backup kernel: Call Trace: Oct 18 03:10:52 backup kernel: <IRQ> [<ffffffff8112789f>] ? __alloc_pages_nodemask+0x77f/0x940 Oct 18

https://bugzilla.netfilter.org/show_bug.cgi?id=1247 Bug ID: 1247 Summary: Module crash due to broken count Product: netfilter/iptables Version: unspecified Hardware: other OS: other Status: NEW Severity: blocker Priority: P5 Component: unknown Assignee: netfilter-buglog at

Hi all, I''m having a hell of a time getting tc and IFBs to co-operate. I''ve copied the following from http://linux-net.osdl.org/index.php/IFB: -- export TC="/sbin/tc" $TC qdisc add dev ifb0 root handle 1: prio $TC qdisc add dev ifb0 parent 1:1 handle 10: sfq $TC qdisc add dev ifb0 parent 1:2 handle 20: tbf rate 20kbit buffer 1600 limit 3000 $TC qdisc add dev ifb0

http://bugzilla.netfilter.org/show_bug.cgi?id=800 Summary: sk_buff.transport_header set incorrectly for NF_IP_PRE_ROUTING hook Product: netfilter/iptables Version: linux-2.6.x Platform: x86_64 OS/Version: Ubuntu Status: NEW Severity: normal Priority: P5 Component: netfilter hooks

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=48 laforge@netfilter.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From laforge@netfilter.org 2003-02-14 09:02 ------- This is a really hard

I am using kernel 2.6.9 (gentoo,AMD64 version) + routes-2.6.9-11.diff If compile kernel with gcc 3.4.3, then the similar error comes out: ------------------ net/ipv4/fib_frontend.c: In function `fib_validate_source'': include/net/ip_fib.h:181: sorry, unimplemented: inlining failed in call to ''fib_result_table'': function body not available net/ipv4/fib_frontend.c:204:

With 2.4.28 and Julian Anastasov''s http://www.ssi.bg/~ja/routes-2.4.27-9.diff patch, I get the following when I attempt to build my kernel. Any ideas? Thanks! gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -fno-unit-at-a-time -nostdinc

We have here an knfs fileserver running ext3 on 2.4.18 kernel with three filesystems: <CLIP> Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda3 10080520 3609632 6368476 37% / /dev/hda4 16437332 12295408 3974932 76% /home /dev/md1 1024872060 409906136 614441636 41% /fs </CLIP> The /fs filesystem lives on a

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.netfilter.org/) that require attention. All of these bugs are in the NEW or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You

Hello I have a server with a dsl connection on eth1 and local interface eth0. Because of the NAT i cannot direct traffic to IMQ device in PREROUTING chain but have to use INPUT and FORWARD. So i use rules. iptables -t mangle -A INPUT -i eth1 -j IMQ --todev 0 iptables -t mangle -A FORWARD -i eth1 -j IMQ --todev 0 And now the strange thing: FORWARD traffic gets directed nicely to the IMQ, but

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.netfilter.org/) that require attention. All of these bugs are in the NEW or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You

Hello, We're having an issue with our distributed gluster filesystem: * gluster 3.3.1 servers and clients * distributed volume -- 69 bricks (4.6T each) split evenly across 3 nodes * xfs backend * nfs clients * nfs.enable-ino32: On * servers: CentOS 6.3, 2.6.32-279.14.1.el6.centos.plus.x86_64 * cleints: CentOS 5.7, 2.6.18-274.12.1.el5 We have a directory containing 3,343 subdirectories. On

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.netfilter.org/) that require attention. All of these bugs are in the NEW or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You

>From netdev@oss.sgi.com: ----- Forwarded message from jamal <hadi@cyberus.ca> ----- X-Original-To: sebek@localhost X-Received-Date: Mon, 12 Apr 2004 03:25:37 +0200 (CEST) Subject: (Long) ANNOUNCE: IMQ replacement WAS(Re: [RFC/PATCH] IMQ port to 2.6 From: jamal <hadi@cyberus.ca> Reply-To: hadi@cyberus.ca To: "Vladimir B. Savkin" <master@sectorb.msk.ru> Cc:

Is there a flow diagram as to where tc actions take place with respect to NAT and other iptables functions on a multihomed box (private & public NICs) ? Are tc filter rules consulted before or after NATing? My real interest is in basic understanding first, and then solving a real problem second. Example: Firewall Public NIC 123.123.123.1 Firewall Private NIC 192.168.168.1 Dedicated Video