| To: | hadi@xxxxxxxxxx |
|---|---|
| Subject: | Re: IMQ / new Dummy device post. |
| From: | syrius.ml@xxxxxxxxxx |
| Date: | Mon, 19 Apr 2004 14:33:16 +0200 |
| Cc: | Andy Furniss <andy.furniss@xxxxxxxxxxxxx>, netdev@xxxxxxxxxxx |
| In-reply-to: | <1082203795.1043.18.camel@xxxxxxxxxxxxxxxx> (hadi@xxxxxxxxxx's message of "17 Apr 2004 08:09:55 -0400") |
| References: | <407E5905.9070108@xxxxxxxxxxxxx> <1082031313.1039.13.camel@xxxxxxxxxxxxxxxx> <407EE3E5.8060200@xxxxxxxxxxxxx> <1082087553.1035.287.camel@xxxxxxxxxxxxxxxx> <4080356F.4020609@xxxxxxxxxxxxx> <1082145341.1026.125.camel@xxxxxxxxxxxxxxxx> <40810957.6030209@xxxxxxxxxxxxx> <1082203795.1043.18.camel@xxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux) |
[...] > - packets from local Lan can be marked at ingress and redirect to a > dummy if needed. Infact you can do this on the egress at ppp0 as well > using the new tc -i <inputdev> that i introduced. So this is easy. Hmm I don't see -i option in the patches. what's the point of having a -i <inputdev> option ? does it mean I can work on egress at ppp0 and use -i eth0 to match packets that were originaly from eth0 ? I personnaly use netfilter to mark packets and 'handle $mark fw' to filter them. (that may explain why i don't see the point :-) -- |
| Previous by Date: | [RFC] Store inner MTU in dst_pmtu for IPsec, Herbert Xu |
|---|---|
| Next by Date: | Re: IMQ / new Dummy device post., syrius . ml |
| Previous by Thread: | Re: IMQ / new Dummy device post., Martin Josefsson |
| Next by Thread: | Re: IMQ / new Dummy device post., syrius . ml |
| Indexes: | [Date] [Thread] [Top] [All Lists] |