From: Raffaele Brancaleoni <s940195@student.ulg.ac.be>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to recognize a IPSEC packet ?
Date: Mon, 09 Jul 2001 18:26:47 +0000 [thread overview]
Message-ID: <marc-lartc-99470323915796@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99469143401463@msgid-missing>
Franck BALAZOT wrote:
> Hi all,
>
> I want to make bandwidth management with CBQ (iproute2)
> There is no problem to manage service like FTP, HTTP,...
> We have an IPSEC VPN here, and I don't know how to reconignize IPSEC
> packets to manage the VPN bandwith.
> Is there a special port or something in the IP packet header that tells
> "here is an IPSEC packet" ?
>
> Thanks,
> ------------------------------------------------
> Franck BALAZOT (fbalazot@aeta.fr)
> AETA.COM
> 361, Avenue du Général De Gaulle
> 92140 CLAMART
> FRANCE
> Tél:01.41.36.12.93
> ------------------------------------------------
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
Hi,
From what I remember, IPSec use port 500 TCP for IKE & protocol-ids for IPSec
trafic are
50 (ESP) / 51 (AH) (stored in IP Header). This should allow you to recognize the
IPSec
traffic with u32 filters.
Hope this help !
Later,
Raffaele.
--
____________________________________________________________________________
Raffaele Brancaleoni Email : s940195@student.ulg.ac.be
Licence en Informatique
Université de Liège - Belgique
____________________________________________________________________________
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-07-09 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 14:30 [LARTC] How to recognize a IPSEC packet ? Franck BALAZOT
2001-07-09 17:37 ` Mike Fedyk
2001-07-09 18:26 ` Raffaele Brancaleoni [this message]
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=marc-lartc-99470323915796@msgid-missing \
--to=s940195@student.ulg.ac.be \
--cc=lartc@vger.kernel.org \
/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.