From: Patrick McHardy <kaber@trash.net>
To: "Eliot, Wireless and Server Administrator,
Great Lakes Internet" <support8@greatlakes.net>
Cc: lartc@mailman.ds9a.nl,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: [LARTC] iptables CLASSIFY and MARK not working?
Date: Thu, 01 Jun 2006 19:44:12 +0000 [thread overview]
Message-ID: <447F438C.4080606@trash.net> (raw)
In-Reply-To: <0633E0EDB4F25F43A2D7179CA11FAFAB255419@xavier.staff.greatlakes.net>
Eliot, Wireless and Server Administrator, Great Lakes Internet wrote:
> Both devices (br1 and wivl4) are bridged interfaces with spanning tree
> turned on. They also do VLANs. Specifically, vconfig was used to create
> a VLAN (in this case, VLAN 4) on two interfaces: eth2 and eth3. These
> two VLAN interfaces were called e2v4 and e3v4. Then, brctl was used to
> bridge the two VLAN interfaces (e2v4 and e3v4) into a new interface
> called wivl4. Spanning tree was then enabled on wivl4. The MTU size was
> then adjusted -4 bytes to accommodate the VLAN tagging.
Any chance you got bridge netfilter enabled? If so please disable
it and try again (or set the bridge-nf-call-iptables sysctl to 0).
> Also, did you happen to try my specific rules (under different devices)
> to see if they work?
No, just tried CLASSIFY with my own HFSC setup, which is pretty
similar.
> If possible, could you try creating a VLAN interface and test on that
> interface? Then try a bridged interface. And finally, a bridged VLAN
> interface.
>
> I will try to set this all up on a different machine without the bridged
> VLANs and see if it works there.
I checked the code, neither VLAN nor bridge should matter.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: "Eliot, Wireless and Server Administrator,
Great Lakes Internet" <support8@greatlakes.net>
Cc: lartc@mailman.ds9a.nl,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: iptables CLASSIFY and MARK not working?
Date: Thu, 01 Jun 2006 21:44:12 +0200 [thread overview]
Message-ID: <447F438C.4080606@trash.net> (raw)
In-Reply-To: <0633E0EDB4F25F43A2D7179CA11FAFAB255419@xavier.staff.greatlakes.net>
Eliot, Wireless and Server Administrator, Great Lakes Internet wrote:
> Both devices (br1 and wivl4) are bridged interfaces with spanning tree
> turned on. They also do VLANs. Specifically, vconfig was used to create
> a VLAN (in this case, VLAN 4) on two interfaces: eth2 and eth3. These
> two VLAN interfaces were called e2v4 and e3v4. Then, brctl was used to
> bridge the two VLAN interfaces (e2v4 and e3v4) into a new interface
> called wivl4. Spanning tree was then enabled on wivl4. The MTU size was
> then adjusted -4 bytes to accommodate the VLAN tagging.
Any chance you got bridge netfilter enabled? If so please disable
it and try again (or set the bridge-nf-call-iptables sysctl to 0).
> Also, did you happen to try my specific rules (under different devices)
> to see if they work?
No, just tried CLASSIFY with my own HFSC setup, which is pretty
similar.
> If possible, could you try creating a VLAN interface and test on that
> interface? Then try a bridged interface. And finally, a bridged VLAN
> interface.
>
> I will try to set this all up on a different machine without the bridged
> VLANs and see if it works there.
I checked the code, neither VLAN nor bridge should matter.
next prev parent reply other threads:[~2006-06-01 19:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 14:31 [LARTC] iptables CLASSIFY and MARK not working? Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-05-19 17:31 ` Andreas Unterkircher
2006-05-19 19:26 ` Jody Shumaker
2006-05-22 21:56 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-05-23 4:32 ` Jody Shumaker
2006-05-30 19:25 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-05-30 19:49 ` Jason Boxman
2006-05-30 20:12 ` Luciano Ruete
2006-05-30 20:13 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-05-30 20:19 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-05-30 20:25 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-06-01 18:13 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-06-01 18:22 ` Patrick McHardy
2006-06-01 18:22 ` Patrick McHardy
2006-06-01 18:49 ` [LARTC] " Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-06-01 18:49 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-06-01 19:09 ` [LARTC] " Patrick McHardy
2006-06-01 19:09 ` Patrick McHardy
2006-06-01 19:38 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-06-01 19:38 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-06-01 19:44 ` Patrick McHardy [this message]
2006-06-01 19:44 ` Patrick McHardy
2006-06-01 19:58 ` [LARTC] " Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-06-01 19:58 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-06-01 20:01 ` [LARTC] " Patrick McHardy
2006-06-01 20:01 ` Patrick McHardy
2006-06-01 20:09 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-06-01 20:09 ` Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-06-01 20:10 ` Patrick McHardy
2006-06-01 20:10 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2006-06-03 16:43 Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-06-08 7:41 ` Patrick McHardy
2006-06-08 7:41 ` Patrick McHardy
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=447F438C.4080606@trash.net \
--to=kaber@trash.net \
--cc=lartc@mailman.ds9a.nl \
--cc=netfilter-devel@lists.netfilter.org \
--cc=support8@greatlakes.net \
/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.