From: Nikolay Nikolaev <nnn@vsu.by>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Layer-7 don't work
Date: Thu, 24 Aug 2006 06:03:12 +0000 [thread overview]
Message-ID: <44ED4120.3040404@vsu.by> (raw)
Szymon Mroofka пишет:
> Hi,
>
> I have simple question about Skype. What are the methods of selecting packets
> which belongs to Skype??
> I know about 7layer but I don't belive that is only way.
> Is 7layer realy good and stable solution for routers which must handle more
> than 1000 users ?
>
Hi everybody!
I use Layer-7 filter for hook packets like this :
$ipt -t mangle -N SKYPE
$ipt -t mangle -A SKYPE -j MARK --set-mark 41
$ipt -t mangle -A SKYPE -j LOG --log-prefix "IPT. SKYPE: " --log-ip-options
$ipt -t mangle -A SKYPE -j IMQ
....
....
....
$ipt -t mangle -A PREROUTING -m layer7 --l7dir /etc/l7-protocols
--l7proto dns -j DNS
...
$ipt -t mangle -A PREROUTING -m layer7 --l7dir /etc/l7-protocols
--l7proto skypetoskype -j SKYPE
...
$ipt -t mangle -A PREROUTING -j OTHER
the iptables -t mangle -L PREROUTING -n -v show it's correct,
but I see in LOG and see this:
Aug 23 10:57:16 gate kernel: IPT. SKYPE: IN=eth0 OUT= MAC=xx:xx:...xx
SRC\x10.10.0.114 DST\x10.10.0.1 LEN\x140 TOS=0x04 PREC=0x00 TTLd ID=0
PROTO=UDP SPT\x162 DPT\x162 LEN\x120
etc...
grep 162 /etc/services
snmp-trap 162/tcp snmptrap # Traps for SNMP
snmp-trap 162/udp snmptrap # Traps for SNMP
it's not SKYPE, i think .... it is normal?
my kernel 2.6.15, iptables v 1.3.5 all pathced, all modules is load.
thx.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2006-08-24 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 6:03 Nikolay Nikolaev [this message]
2006-08-24 16:34 ` [LARTC] Layer-7 don't work Jason Boxman
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=44ED4120.3040404@vsu.by \
--to=nnn@vsu.by \
--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.