All of lore.kernel.org
 help / color / mirror / Atom feed
From: gui <whereisgui@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Protecting multiple webservers
Date: Wed, 19 Jan 2005 14:35:00 -0800	[thread overview]
Message-ID: <48be50bb050119143595e54d2@mail.gmail.com> (raw)

>uh--where are the "allow incoming connections to my web servers" lines?

> -A FORWARD -i eth0 -o eth1 -p tcp --syn -d 192.168.0.2 --dport 80 \
>   -j ACCEPT
>
>-A FORWARD -i eth0 -o eth1 -p tcp --syn -d 192.168.0.3 --dport 80 \
>   -j ACCEPT
>
>make sure you also enabled IP forwarding:
>
> sysctl -w net.ipv4.ip_forward=1

The iptables start up script enables forwarding, but you were right I
was missing the  "allow incoming connections to my web servers" lines.
 Thanks James!

>are these webservers goingto be part of a cluster or do they need to
have there own resolved >hostnames?
>are they to be part of virtual hosting scenario ?

No, they are not in a cluster or anything fancy like that. These are
just stand alone web servers serving their own content that need to be
isolated from the rest of our network, but need to have their own
(current) hostnames resolved. I don't see what more information I can
provide.

The set up seems to be working fine after I added the lines suggested
by James. I'll report back if I encounter problems.

piranha,
Would you mind telling what are the other ways to do this?  Keep in
mind that I can't touch the DNS server.

Thanks again.

-gui


             reply	other threads:[~2005-01-19 22:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19 22:35 gui [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-19 21:07 Protecting multiple webservers Hudson Delbert J Contr 61 CS/SCBN
2005-01-19 20:37 gui
2005-01-19 20:58 ` Jason Opperisano
     [not found] <15069645.1105491740310.JavaMail.rct@kale>
2005-01-12  4:01 ` Bob Tellefson
2005-01-12 15:14   ` Maxime Ducharme
2005-01-12 15:37     ` Samuel Jean
2005-01-12 19:57   ` John A. Sullivan III
2005-01-12  1:01 gui

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=48be50bb050119143595e54d2@mail.gmail.com \
    --to=whereisgui@gmail.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.