| To: | Martin Bene <martin.bene@icomedias.com> |
|---|---|
| Subject: | Re: AW: [LARTC] qos inside ipsec tunnel |
| From: | Mohan Sundaram <mohan.tux@gmail.com> |
| Date: | Sat, 04 Nov 2006 06:55:51 +0530 |
| Cc: | lartc@mailman.ds9a.nl, Marco Berizzi <pupilla@hotmail.com> |
| Delivered-to: | sp-com-lists@consult.net |
| Delivered-to: | lartc-list@securepoint.com |
| Delivered-to: | lartc@outpost.ds9a.nl |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:reply-to:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:from; b=chyDu7q+KKXlaKGZwpTc0oam9kBlU1s2Vp8sH+iHlfKRZ2PXIflEK7MgGkktkr/k9tovB7HaNIChRZT9PWUCBjfYuBRbTOFkS7Q+yNiXfSfZj200eN2d90XbMYedm/eejyyamiXGzJvPxajdz/y1ivmmNIxyzjI6CE68zZziHBM= |
| In-reply-to: | <FA095C015271B64E99B197937712FD020F1F252B@freedom.grz.icomedias.com> |
| List-archive: | <http://mailman.ds9a.nl/pipermail/lartc> |
| List-help: | <mailto:lartc-request@mailman.ds9a.nl?subject=help> |
| List-id: | "Mailinglist of the Linux Advanced Routing & Traffic Control project" <lartc.mailman.ds9a.nl> |
| List-post: | <mailto:lartc@mailman.ds9a.nl> |
| List-subscribe: | <http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc>, <mailto:lartc-request@mailman.ds9a.nl?subject=subscribe> |
| List-unsubscribe: | <http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc>, <mailto:lartc-request@mailman.ds9a.nl?subject=unsubscribe> |
| References: | <FA095C015271B64E99B197937712FD020F1F252B@freedom.grz.icomedias.com> |
| Reply-to: | smohan@vsnl.com |
| Sender: | lartc-bounces@mailman.ds9a.nl |
| User-agent: | Thunderbird 1.5.0.7 (Windows/20060909) |
Martin Bene wrote: Has anyone tested this? Does the mark get carried across encapsulations or is the packet context a new one on encapsulation? I know that IPSec RFC says inner packet headers have to be copied to the outer header. Does that include the TOS byte too? Do not know what OpenSWAN does. If that were the case, assigning TOS prior to encapsulation and classifying by TOS at the device will work.Hi Marco,Hello everybody. I would like to do some kind of shaping inside an ipsec tunnel implemented by Openswan and linux 2.6.18.x with xfrm (no KLIPS): for example, to limit outbound smtp traffic inside the tunnel. Question: where should I attach the qdisc to? Eth0? I'm asking this, because tcpdump only see the ESP packet on the eth0 and not the 'clear' packet.Heh - just subscribed to LARC list because I'm working on a similarproblem.Yes, you'll have to attach your classes to eth0 device. However, by the time qos gets to see the packets, they'll be encrypted, so you won't be able to just use tc filter with u32 classifier to select on port 25. What should work is to mark the packets in PREROUTING in the mangle table and assign them to the classes you want based on the fwmark: iptables -t mangle -A PREROUTING -d <private ip vpn remote side>/24 -p tcp -m multiport --port 25 -j MARK --set-mark 102 tc filter add dev eth0 protocol ip parent 1:0 prio 1 handle 102 fw flowid 1:20 Hope this helps, Martin Mohan _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [LARTC] Strategy for penalising IPs with too many simultaneous sessions, Stephen Hemminger |
|---|---|
| Next by Date: | Re: [LARTC] Strategy for penalising IPs with too many simultaneous sessions, Mohan Sundaram |
| Previous by Thread: | [LARTC] Strategy for penalising IPs with too many simultaneous sessions, Graham Leggett |
| Next by Thread: | AW: AW: [LARTC] qos inside ipsec tunnel, Martin Bene |
| Indexes: | [Date] [Thread] [Top] [All Lists] |