Leigh Sharpe wrote:
Try protocol 8021q or whatever its number is -
Thanks Andy, this did the trick. And now for the next question.
802.1q is protocol number 0x8100. Therefore my filter lines look like this:
Tc filter add dev eth3 parent : protocol 0x8100 prio 10 u32 match u32 0 0
Leigh Sharpe wrote:
Nup. Well, not directly. This is going on our backbone, so I'm not taking traffic straight off the wireless. Ultimately, it will be delivered to a customer over a wireless link, but there's lots of ethernet between the QOS box and the wireless.
By the way, wireless !=
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 29, 2007 12:33 PM
To: Leigh Sharpe
Cc: lartc
Subject: Re: [LARTC] RE: IFB setup was no subject
Leigh Sharpe wrote:
Seems that the example I gave actually works, but not the way I'm using it.
I am bridging
Leigh Sharpe wrote:
Hi all,
I'm having a hell of a time getting my IFB to work. I know I've done
this before, so I'm missing something stupid. Can anybody tell me what
it might be?
Configs as follows:
#!/bin/sh
modprobe ifb numifbs=1000
modprobe act_mirred
modprobe 8021q
brctl
:[EMAIL PROTECTED]
Sent: Thursday, March 29, 2007 2:59 AM
To: Leigh Sharpe
Cc: lartc
Subject: Re: IFB setup was no subject
Leigh Sharpe wrote:
Hi all,
I'm having a hell of a time getting my IFB to work. I know I've done
this before, so I'm missing something stupid. Can anybody tell me what
Leigh Sharpe wrote:
Seems that the example I gave actually works, but not the way I'm using it.
I am bridging VLAN tagged packets,
Try protocol 8021q or whatever its number is - if there are other
protocol filters you will need a different prio or you will get an error.
but for some
, 2007 12:33 PM
To: Leigh Sharpe
Cc: lartc
Subject: Re: [LARTC] RE: IFB setup was no subject
Leigh Sharpe wrote:
Seems that the example I gave actually works, but not the way I'm using it.
I am bridging VLAN tagged packets,
Try protocol 8021q or whatever its number is - if there are other
protocol
