From: Joel Newkirk <firewalldude@newkirk.us>
To: tedkaz@optonline.net
Cc: netfilter@lists.netfilter.org
Subject: Re: udp/tcp port range rules for forward/input chains
Date: Thu, 16 Oct 2003 17:49:52 -0400 [thread overview]
Message-ID: <1066340992.2300.249.camel@alpha.newkirk.us> (raw)
In-Reply-To: <1066340042.6368.21.camel@tarkus>
On Thu, 2003-10-16 at 17:34, Ted Kaczmarek wrote:
> As it turned out their was a hidden character in one of my logging rules
> which was totally messing with my head :-)
> > > If anyone has a link that or info that can steer me in the right
> > > direction the beers are on me at the Javits Center Linux show.
> > >
> > > Thanks,
> > > Ted
So no beer? ;^)
j
prev parent reply other threads:[~2003-10-16 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 3:10 udp/tcp port range rules for forward/input chains Ted Kaczmarek
2003-10-15 6:27 ` Joel Newkirk
2003-10-16 21:34 ` Ted Kaczmarek
2003-10-16 21:49 ` Joel Newkirk [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=1066340992.2300.249.camel@alpha.newkirk.us \
--to=firewalldude@newkirk.us \
--cc=netfilter@lists.netfilter.org \
--cc=tedkaz@optonline.net \
/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.