From: Jack Bowling <jbinpg@shaw.ca>
To: netfilter@lists.samba.org
Subject: Re: simple, but not for me.
Date: Sat, 29 Jun 2002 22:25:42 -0700 [thread overview]
Message-ID: <0GYI00CJJ72YLS@l-daemon> (raw)
In-Reply-To: <00a701c21feb$30bea010$0200a8c0@SILVERBEAST>
** Reply to message from outspoken <outspoken@gru.net> on Sun, 30 Jun 2002 00:04:09 -0400
> ok, ill lay out a simple plan of what i need done. of course ive tried a lot of the options listed in this listeserv, and cant seem to get them working properly. also read some howtos and other various things but just came seem to get things working. there was one post that i thought was going to be helpful recently, but all they talked about was how its a security risk and they should really look into a dmz. well i cant right now since i don't have another ethernet card so please someone post simple iptables examples for me to use. =)
>
>
> i have a machine = 192.168.0.8 which is behind the firewall = 192.168.0.1
> what i need to do is have 192.168.0.8 be visible to the public for web serving, ssh, mysql.
> that is all.
>
> my nat setup currently works fine with 3 machines behind the firewall.
>
> modules loaded:
<snip>
Just an aside - we are not likely to be much help unless you post your whole ruleset. We do not know your default chain policies for one which will determine a lot.
jb
next prev parent reply other threads:[~2002-06-30 5:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-30 4:04 simple, but not for me outspoken
2002-06-30 5:25 ` Jack Bowling [this message]
[not found] <20020630053506.43C3143FD@lists.samba.org>
2002-06-30 5:54 ` outspoken
2002-06-30 8:04 ` Jack Bowling
[not found] <20020630132725.896984212@lists.samba.org>
2002-06-30 16:48 ` Marc Carter
-- strict thread matches above, loose matches on Subject: below --
2002-06-30 19:35 j davis
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=0GYI00CJJ72YLS@l-daemon \
--to=jbinpg@shaw.ca \
--cc=netfilter@lists.samba.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.