From: Michael Gale <michael.gale@utilitran.com>
To: netfilter@lists.netfilter.org
Subject: Re: Help with Access Point firewalling
Date: Wed, 18 Aug 2004 06:03:17 -0600 [thread overview]
Message-ID: <20040818060317.322ec47e@mgalepc.utilitran.com> (raw)
In-Reply-To: <41234202.6040903@4Dllc.com>
Hello,
I have never used a wireless interface yet but as long as you have ip_forwarding enabled it should forward the packets
across the interfaces, the clients must be setup to route packets to the wireless interface either by a default route or
a routing table entry.
If you want the packets to be MASQUERADE that should be as simple as adding a rule for packets leaving the interface.
Michael.
On Wed, 18 Aug 2004 13:48:18 +0200
Steve Comfort <steve@4Dllc.com> wrote:
> Hi all,
>
> I'm working on an embedded scenario that has got me a bit stumped, and
> thought maybe one of the guru's here could help out.
>
> The device is based around an IXP processor and has an ethernet and a
> wireless interface. When the wireless interface is configured as managed
> (ie its a client) I have no problem and am happily using a modification
> of Oskar Andreaason's firewall script to do the firewalling. Everything
> works fine.
>
> However, what should I be doing if the device is configured as an Access
> Point? I figured I need to allow in NEW TCP connections, but don't know
> whether I will be able to use iptables to masquerading between the wlan
> port and the eth port, (ie will the MASQUERADE target forward packets
> received on the WLAN to the ETH interface ?) or whether I will have to
> add a bridge and use ebtables?
>
> Any advice would be appreciated!
>
> Best regards
> Steve
>
>
>
>
>
>
--
Michael Gale
Network Administrator
Utilitran Corporation
prev parent reply other threads:[~2004-08-18 12:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 11:48 Help with Access Point firewalling Steve Comfort
2004-08-18 12:03 ` Michael Gale [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=20040818060317.322ec47e@mgalepc.utilitran.com \
--to=michael.gale@utilitran.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.