From: Steve Comfort <steve@4Dllc.com>
To: Joel Newkirk <firewalldude@newkirk.us>
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Very newB questions
Date: Fri, 25 Jun 2004 09:51:36 +0200 [thread overview]
Message-ID: <40DBD988.7040502@4Dllc.com> (raw)
In-Reply-To: 40DB26F4.8000808@newkirk.us
Hi John, gents,
> Have you bookmarked and printed Oscar Andreasson's tutorial at
> http://iptables-tutorial.frozentux.net ? I think it's the hands-down
> best document around regarding iptables.
First off John, thanks for all your suggestions: I won't comment yet,
'cos its early in the morning here and my braincells are still chugging
into life. I started looking at Netfilter yesterday :) Yes, I found the
tutorial and have downloaded it and am busy trying to absorb as much as
I can.
> Out of curiosity, is this an embedded system you are making into a
> firewall/router, or what? I've compiled and used iptables and ip
> commands for ARM-based Sharp Zaurus handhelds. (I actually used one
> of mine as a wireless->GPRS gateway for a few days of DSL outage,
> feeding my LAN traffic and newkirk.us domain traffic over 802.11b to
> the Zaurus, then via IRDA over my cellphone GPRS tunnelled to my
> office, an ISP)
(You must have really needed to be connected :) Yes, the CPU is an
IXP425, with an Atheros wireless chipset and ethernet PHY on the other
side. Obviously the product is a broadband wifi thingy. I've just
finished getting netSNMP working on it, as well as PPPOE, so the
firewalling is about the last piece of the puzzle that needs to be
placed before it can take its first steps into the big bad world out
there :)
> Yep. As Mr Stone mentioned, ACCEPT is a target, NOT a chain.
> However, the way iptables rules work, if the target is NOT a valid
> target (ACCEPT,REJECT,DROP,SNAT,DNAT,MASQUERADE, that sort of thing)
> then it assumes it's the name of a custom rule chain, named ACC in
> this case, and then fails when it can't find said chain. I also
> notice that it seems to be truncating the iptables version number?
> Very odd.
Indeed :) Hopefully I will be able to enlighten myself as to why sooner
rather than later...
Best regards
Steve
prev parent reply other threads:[~2004-06-25 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 12:33 Very newB questions Steve Comfort
2004-06-24 13:31 ` Antony Stone
2004-06-24 20:29 ` John A. Sullivan III
[not found] ` <40DB26F4.8000808@newkirk.us>
2004-06-25 7:51 ` Steve Comfort [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=40DBD988.7040502@4Dllc.com \
--to=steve@4dllc.com \
--cc=firewalldude@newkirk.us \
--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.