All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB and Openvpn
Date: Wed, 06 Oct 2004 13:30:47 +0000	[thread overview]
Message-ID: <4163F387.3080807@metamorpher.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0410061153510.2239-100000@george.eliot.priv.at>

Peter Huetmannsberger wrote:
> I have changed my setup accordingly now, however there are still packets 
> showing up on the default qdisc when I go through the tunnel, about half 
> the packets don't seem to match. 

If there really only is udp traffic on port 5001, I don't see why your 
rules should match that only partially. If they were wrong, they'd 
either match everything or nothing at all, wouldn't they?

> Did you see anything wrong with the filter rules. Openvpn uses port 5001 
> on both ends, and tcpdump -i eth0 shows udp packets going back and forth 
> on port 5001 and no other traffic, yet the default counter goes up along 
> with the 1:10 qdisc.

I don't know tcpdump - when debugging filter rules, I usually adapt 
these rules to iptables and use iptables log with different prefixes to 
distinct which packets matched which rules (and which didn't match at 
all). If nothing shows up this way, then I too am clueless as to what 
might be wrong. Maybe someone else has a suggestion. :)

I don't have any experience with OpenVPN myself, so I don't know what's 
the best way to match OpenVPN traffic. Using port criteria alone, might 
not be waterproof enough, as long as anyone can use these ports for 
anything. Matching both IP and Port would probably be more reliable.

Andreas
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2004-10-06 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06 10:01 [LARTC] HTB and Openvpn Peter Huetmannsberger
2004-10-06 10:55 ` Andreas Klauer
2004-10-06 11:09 ` Peter Huetmannsberger
2004-10-06 13:30 ` Andreas Klauer [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=4163F387.3080807@metamorpher.de \
    --to=andreas.klauer@metamorpher.de \
    --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.