All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Wayne" <wayne@fengshuifont.com>
To: lartc@vger.kernel.org
Subject: [LARTC] FTP Connection Tracking in a Bridge
Date: Wed, 20 Aug 2003 08:48:00 +0000	[thread overview]
Message-ID: <marc-lartc-106136953432545@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 949 bytes --]

Hello,

I have a box running as a bridge and am trying to track the passive FTP sessions by marking them with iptables (CONNMARK option installed) and then trying to pick up the mark using tc filter fwmark. This is not working.

I have checked the marking of the packets and this is working fine because I can see the marks when I cat /proc/net/ip_conntrack.

Having setup my queues and using the following command:

tc filter add dev eth1 parent 1:2 protocol ip prio 1 handle 2 fw classid 1:2a

I do not get any traffic going in to this queue. I am running kernel 2.4.21. 

My question is whether the packet that I have marked is actually every getting to the tc filter. As I am running a bridge, does the packet get marked in iptables PREROUTING, and then go straight to the FORWARD rule and then out.

What is the sequence in which iptables processes the packet and then the tc filter processes the packet.

Many thanks

Wayne

[-- Attachment #2: Type: text/html, Size: 1352 bytes --]

             reply	other threads:[~2003-08-20  8:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-20  8:48 Wayne [this message]
2003-08-20  9:02 ` [LARTC] FTP Connection Tracking in a Bridge Eric Leblond
2003-08-20  9:56 ` S Mohan
2003-08-20 10:06 ` Wayne
2003-08-20 12:24 ` Stef Coene
2003-08-20 12:26 ` Stef Coene
2003-08-20 12:38 ` Eric Leblond
2003-08-20 12:39 ` Wayne
2003-08-20 13:26 ` S Mohan
2003-08-20 15:17 ` Stef Coene
2003-08-21  7:28 ` Wayne
2003-08-22 19:12 ` Bart De Schuymer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-106136953432545@msgid-missing \
    --to=wayne@fengshuifont.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.