From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: ipsec nat and iptables
Date: Fri, 26 Aug 2005 08:03:39 -0500 [thread overview]
Message-ID: <200508260803.39600.rob0@gmx.co.uk> (raw)
In-Reply-To: <430DE371.7020206@datacenter1.com>
On Thursday 2005-August-25 10:27, Info DataCenter1.com wrote:
> Network A
> eth0= conected to internet
> eth1= conected to private lan 192.168.1.1
>
> Network B
> eth0 conected to Internet
> eth1= conected to private lan 192.168.2.1
>
> >From server A I'm able to ping 192.168.2.1 and viceversa but
> > computers in the private lan can't see the other side
snip
> iptables -A FORWARD -i eth1 -o eth0
> iptables -A FORWARD -i eth0 -o eth1
These rules do nothing.
> iptables -P FORWARD DROP
And then your policy drops that traffic.
--
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: header
next prev parent reply other threads:[~2005-08-26 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 15:27 ipsec nat and iptables Info DataCenter1.com
2005-08-26 13:03 ` /dev/rob0 [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-25 15:31 Guillermo Calvo
2005-08-25 15:45 Gary W. Smith
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=200508260803.39600.rob0@gmx.co.uk \
--to=rob0@gmx.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox