From: Norman Zhang <norman.zhang@rd.arkonnetworks.com>
To: netfilter@lists.netfilter.org
Subject: Re: Iptables and Kernel
Date: Sun, 18 Apr 2004 21:34:18 -0700 [thread overview]
Message-ID: <408356CA.4030604@rd.arkonnetworks.com> (raw)
In-Reply-To: <36070.9628942006$1081802745@news.gmane.org>
>I'm running 2.6.3. with iptables 1.2.9 and p-o-m-ng h323 patch -- they work
>for me -- but I'm referring to a home lan ond only one netmeeting seesioon
>from the LAN -- we haven't tried multiple sessions from inside the lan ...
>either to the same netmeeting sessioon or to different ones.
Sorry it is me again. I tried to compile pomng using
# KERNEL_DIR=/usr/src/linux ./runme pending
# KERNEL_DIR=/usr/src/linux ./runme base
# KERNEL_DIR=/usr/src/linux ./runme extend
but couldn't find h323-conntrack-nat patch being offered. I did see
owner-socketlookup mention something about H.323. May I ask how do I
applied h323-conntrack-nat patch to iptables and kernel-2.6.5 alone? I
can see the subfolder h323-conntrack-nat under pomng.
Regards,
Norman
next prev parent reply other threads:[~2004-04-19 4:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 5:22 Iptables and Kernel Norman Zhang
2004-04-12 6:00 ` Unknown, Alistair Tonner
2004-04-12 6:27 ` Norman Zhang
2004-04-12 7:32 ` Unknown, Alistair Tonner
2004-04-12 17:05 ` Norman Zhang
2004-04-12 17:22 ` Antony Stone
2004-04-12 19:07 ` Norman Zhang
2004-04-12 20:16 ` Unknown, Alistair Tonner
2004-04-18 15:53 ` Norman Zhang
2004-04-18 12:06 ` Alistair Tonner
2004-04-18 16:27 ` Norman Zhang
2004-04-18 13:05 ` Alistair Tonner
2004-04-19 4:34 ` Norman Zhang [this message]
2004-04-19 8:48 ` Alistair Tonner
2004-04-19 14:58 ` Norman Zhang
2004-04-19 15:11 ` Geffrey Velasquez
2004-04-21 15:56 ` Norman Zhang
-- strict thread matches above, loose matches on Subject: below --
2004-04-12 5:17 Norman Zhang
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=408356CA.4030604@rd.arkonnetworks.com \
--to=norman.zhang@rd.arkonnetworks.com \
--cc=netfilter@lists.netfilter.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.