http://dlsvr01.asus.com/pub/ASUS/wireless/WL-600g/GPL_WL600g_1028A.zip

[bcm963xx.git] / targets / fs.src / etc / l7-protocols / protocols / h323.pat

diff --git a/targets/fs.src/etc/l7-protocols/protocols/h323.pat b/targets/fs.src/etc/l7-protocols/protocols/h323.pat
new file mode 100755 (executable)
index 0000000..0cbdd7d
--- /dev/null
+++ b/targets/fs.src/etc/l7-protocols/protocols/h323.pat
@@ -0,0 +1,38 @@
+# H.323 - Voice over IP.
+# Pattern quality: ok veryfast
+# Protocol groups: voip
+#
+# This pattern is written without knowledge of the principles of H.323.
+# It has only been tested with gnomemeeting and may not work for other
+# clients. 
+#
+# Also, it has been reported that:
+# "the pattern ... match[es] only first H.323 stream (conntrack for H.323 was 
+# enabled).  Also the major chunk of traffic was of RTP which went untracked."
+#
+# Also, it may very well match other things that use TPKT and
+# Q.931. 
+
+# To get or provide more information about this protocol and/or pattern:
+# http://www.protocolinfo.org/wiki/H.323
+# http://lists.sourceforge.net/lists/listinfo/l7-filter-developers
+
+# Note that to take full advantage of this pattern, you will need to
+# have connection tracking of H.323 support in your kernel.  This
+# support is not in the stock kernel.  A patch can be found at
+# http://netfilter.org
+
+h323
+# TPKT format: http://www.ietf.org/rfc/rfc1006.txt
+# \x03 = TPKT version.  It was 3 in May 1987 and gnomemeeting still uses 3.
+# ..? = null reserved byte and packet length field.
+# Q.931 format: http://www.freesoft.org/CIE/Topics/126.htm
+# \x08  = Q.931
+# . = length of call reference
+# The next byte was: \x18 = message sent from originating side.
+# But based on experimentation, it seems that just . is better. 
+# .?.?.?.?.?.?.?.?.?.?.?.?.?.?.? = call reference (0-15 bytes (0 for nulls))
+# \x05 = setup message
+#
+# Yup, it doesn't actually include any H.323 protocol information.
+^\x03..?\x08...?.?.?.?.?.?.?.?.?.?.?.?.?.?.?\x05