Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Running iptables behind router
Date: Tue, 24 Feb 2004 11:06:41 +0000	[thread overview]
Message-ID: <200402241106.41715.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <20040224001308.GA10127@zaklinux.zakarun>

On Tuesday 24 February 2004 12:13 am, Kean Pedersen wrote:

> My network right now is:
>
> Hardware router(192.168.1.1), the only access to Internet.
> Desktop (192.168.1.42)
> Server/NAT box (eth0:192.168.1.3 and eth1:192.168.2.1)
> Laptop (192.168.2.101)
>
> The hardware router, desktop and server:eth0 are on one switch, while
> laptop and server:eth1 are on another switch.
>
> I then try a ping from my laptop (192.168.2.101) to my desktop
> (192.168.1.42), but all packes are lost. The packet count on iptables -L -v
> goes up for postrouting/masquerade and forward/accept.

What's the routing table on 192.168.1.42?   Can the reply packets find their 
way back to 192.168.2.101 again?

Antony.

-- 
Success is a lousy teacher.  It seduces smart people into thinking they can't 
lose.

 - William H Gates III

                                                     Please reply to the list;
                                                           please don't CC me.



  parent reply	other threads:[~2004-02-24 11:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 23:55 Running iptables behind router Kean Pedersen
2004-02-17 12:39 ` Alexis
2004-02-24  0:13   ` Kean Pedersen
2004-02-24  4:31     ` John A. Sullivan III
2004-02-24 12:07       ` Kean Pedersen
2004-02-25 18:40         ` John A. Sullivan III
2004-02-25 19:41           ` Kean Pedersen
2004-02-24 11:06     ` Antony Stone [this message]
2004-02-24 14:13     ` Jeffrey Laramie

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=200402241106.41715.Antony@Soft-Solutions.co.uk \
    --to=antony@soft-solutions.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