Skip to contentSkip to conversation

Limit bandwidth for ipsec vpns

LARTC Emmanuel Lacour 3 participants 4 messages Aug 19, 2002 – Aug 20, 2002

lore
Share & tools
lore
#0 lore raw

Hi everybody,

Is there anyone having an idea on how to limit bandwidth on a linux gw doing vpns with freeswan, I.E. for a 1Mbit line with 1 ipsec tunnel on interface ppp0, limiting vpn traffic (esp) to 512kbit and internet traffic (non vpn) to 512kbit.

Thanks in advance!

Manu.

Signature · 7 lines
Easter-eggs                                Spécialiste GNU/Linux
44-46 rue de l'Ouest  -  75014 Paris   -   France -  Métro Gaité
Phone: +33 (0) 1 43 35 00 37    -     Fax: +33 (0) 1 41 35 00 76
mailto:[email protected]   -    http://www.easter-eggs.com
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#1 lore raw
Quoted 10 lines · Emmanuel Lacour

Hi everybody,

Is there anyone having an idea on how to limit bandwidth on a linux gw doing vpns with freeswan, I.E. for a 1Mbit line with 1 ipsec tunnel on interface ppp0, limiting vpn traffic (esp) to 512kbit and internet traffic (non vpn) to 512kbit.

Thanks in advance!

More info about shaping can be found on www.lartc.org. And I have some extra information on www.docum.org.

You have to add a cbq or htb qdisc to your interfaces and create 2 classes. One for vpn traffic and one for non vpn traffic. I hope that you use fixed ports for the vpn traffic so you can use the dst/src port as a filter key. You can share the same 1mbit or you can limit each class to 512kbit.

Stef

Signature · 7 lines
[email protected]
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#2 lore raw
In reply to Emmanuel Lacour
Quoted 11 lines · Stef Coene
Quoted 4 lines

Is there anyone having an idea on how to limit bandwidth on a linux gw doing vpns with freeswan, I.E. for a 1Mbit line with 1 ipsec tunnel on interface ppp0, limiting vpn traffic (esp) to 512kbit and internet traffic (non vpn) to 512kbit.

More info about shaping can be found on www.lartc.org. And I have some extra information on www.docum.org.

You have to add a cbq or htb qdisc to your interfaces and create 2 classes. One for vpn traffic and one for non vpn traffic. I hope that you use fixed ports for the vpn traffic so you can use the dst/src port as a filter key. You can share the same 1mbit or you can limit each class to 512kbit.

If FreeS/WAN is used, adding a pair of classes to the external interface for 'normal' and 'VPN' traffic should suffice. VPN traffic is identifiable as traffic over UDP port 500 and protocols 50 or 51, although you may wish to give them their own class with high priority as they do key exchanges.

If you gave each 512kbps, then add a root class to ipsec0 of 512kbps and work from there on it.

Signature · 6 lines
Michael T. Babcock
CTO, FibreSpeed Ltd.     (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#3 lore raw
In reply to Emmanuel Lacour
Quoted 13 lines · Michael T. Babcock
Quoted 11 lines · Stef Coene
Quoted 4 lines

Is there anyone having an idea on how to limit bandwidth on a linux gw doing vpns with freeswan, I.E. for a 1Mbit line with 1 ipsec tunnel on interface ppp0, limiting vpn traffic (esp) to 512kbit and internet traffic (non vpn) to 512kbit.

More info about shaping can be found on www.lartc.org. And I have some extra information on www.docum.org.

You have to add a cbq or htb qdisc to your interfaces and create 2 classes. One for vpn traffic and one for non vpn traffic. I hope that you use fixed ports for the vpn traffic so you can use the dst/src port as a filter key. You can share the same 1mbit or you can limit each class to 512kbit.

Quoted 4 lines

If FreeS/WAN is used, adding a pair of classes to the external interface for 'normal' and 'VPN' traffic should suffice. VPN traffic is identifiable as traffic over UDP port 500 and protocols 50 or 51, although you may wish to give them their own class with high priority as they do key exchanges.

Thanks, I tried with marking packet with netfilter, but here is one of my pbms, I can mark esp proto but not non-esp proto:

# This works
# Marking outgoing vpn packets
iptables -t mangle -A OUTPUT -o $IFEXT -p esp -j MARK --set-mark 29 iptables -t mangle -A OUTPUT -o $IFEXT -p udp --dport 500 -j MARK --set-mark 29

# This doesn't works!!
# Marking outgoing non-vpn packets
iptables -t mangle -A OUTPUT -o $IFEXT -p ! esp -j MARK --set-mark 39

Any Idea??

Quoted 10 lines

If you gave each 512kbps, then add a root class to ipsec0 of 512kbps and work from there on it.

Signature · 6 lines
Michael T. Babcock
CTO, FibreSpeed Ltd.     (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Signature · 7 lines
Easter-eggs                                Spécialiste GNU/Linux
44-46 rue de l'Ouest  -  75014 Paris   -   France -  Métro Gaité
Phone: +33 (0) 1 43 35 00 37    -     Fax: +33 (0) 1 41 35 00 76
mailto:[email protected]   -    http://www.easter-eggs.com
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/