From: "Mardaga Stephan" <smardaga@brutele.be>
To: netfilter@lists.netfilter.org
Subject: Re: Masquerade don't masquerade
Date: Wed, 25 Aug 2004 21:36:47 +0200 [thread overview]
Message-ID: <004c01c48adb$5b3cf910$c6ea44d4@famille> (raw)
In-Reply-To: 3063e5040825121849d03e03@mail.gmail.com
Here are :
> The -L output is not enough,
> try iptables-save -t nat
# Generated by iptables-save v1.2.6a on Wed Aug 25 21:28:05 2004
*nat
:PREROUTING ACCEPT [631:81365]
:POSTROUTING ACCEPT [60:18132]
:OUTPUT ACCEPT [60:18132]
-A POSTROUTING -j LOG
-A POSTROUTING -s 192.168.1.0/255.255.255.0 -o eth0 -j MASQUERADE
-A POSTROUTING -j LOG
COMMIT
# Completed on Wed Aug 25 21:28:05 2004
> Also make sure you don't filter stuff in -t filter chain FORWARD
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
> And, did you echo 1 > /proc/sys/net/ipv4/ip_forward ? :D
yes
>
> On Wed, 25 Aug 2004 21:05:07 +0200, Mardaga Stephan <smardaga@brutele.be>
wrote:
> > Hello,
> >
> > I'm new on this forum and hope you will help me.
> >
> > I'm building a Debian server and it is the basic stage.
> > I wish to run Iptables with masquerade.
> >
> > detailed problem report could be find @ this address :
> > http://homeusers.brutele.be/smardaga/masquerade/
> >
> > resume :
> >
> > PC1 Debian Serveur PC2
> > | Eth0 Eth1 |
> > |.1 .50| |.1 .2|
> > | | | |
> > | | | |
> > --------------------------- -------------------------
> > 192.168.0.x/24 192.168.1.x/24
> >
> > Masquerade don't work when pinging from PC2 (192.168.1.2) to PC1
> > (192.168.0.1). PC1 receives icmp packet with IP source address
192.168.1.2.
> >
> > tcpdump on eth0 :
> >
> > 20:30:25.472725 192.168.1.2 > 192.168.0.1: icmp: echo request
> > 20:30:30.972679 192.168.1.2 > 192.168.0.1: icmp: echo request
> > 20:30:36.472321 192.168.1.2 > 192.168.0.1: icmp: echo request
> > 20:30:41.972217 192.168.1.2 > 192.168.0.1: icmp: echo request
> > 20:30:47.472049 192.168.1.2 > 192.168.0.1: icmp: echo request
> > 20:30:52.972084 192.168.1.2 > 192.168.0.1: icmp: echo request
> >
> > iptables release 1.2.6a
> > Linux 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 unknown
> >
> > Chain PREROUTING (policy ACCEPT)
> > target prot opt source destination
> >
> > Chain POSTROUTING (policy ACCEPT)
> > target prot opt source destination
> > LOG all -- anywhere anywhere LOG level
> > warning
> > MASQUERADE all -- 192.168.1.0/24 anywhere
> > LOG all -- anywhere anywhere LOG level
> > warning
> >
> > Chain OUTPUT (policy ACCEPT)
> > target prot opt source destination
> >
> > Any help and/or suggestions will be accepted gratefully.
> >
> > Thanks in advance,
> >
> > Stephan Mardaga
> >
> >
>
>
> --
> Bla bla
>
next prev parent reply other threads:[~2004-08-25 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 19:05 Masquerade don't masquerade Mardaga Stephan
2004-08-25 19:18 ` George Alexandru Dragoi
2004-08-25 19:36 ` Mardaga Stephan [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-25 19:18 Jason Opperisano
2004-08-25 19:40 ` Mardaga Stephan
2004-08-29 11:47 ` Mardaga Stephan
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='004c01c48adb$5b3cf910$c6ea44d4@famille' \
--to=smardaga@brutele.be \
--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