Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Mike Wright <mike.wright@mailinator.com>
To: David J Craigon <david@craigon.co.uk>
Cc: netfilter@vger.kernel.org
Subject: Re: Conntrack not recording packets going through a firewall
Date: Wed, 21 Jan 2009 10:36:26 -0800	[thread overview]
Message-ID: <49776B2A.4070005@mailinator.com> (raw)
In-Reply-To: <c1ace6860901210937m375a8f38g87a86e6264ff6023@mail.gmail.com>

David J Craigon wrote:
> Think I might of misunderstood your email. What I want to happen is
> for all traffic to go through the firewall. Customer 1 and Customer 5
> are on separate VLANs. I want Customer 5 to be able to access Customer
> 1's server as if it was any other host on the internet.
> 
> Does that make more sense?
> 
> 2009/1/21 David J Craigon <david@craigon.co.uk>:
> 
>>No, the routing is definitely working 8-). Otherwise how could all
>>traffic go from the internet to these servers? They have no other
>>internet connection than through the firewall.

Not too sure about VLANs but I have a 3-legged firewall/router with 
discrete network cards.

I just removed the route to my DMZ and now I can't reach it.  Hosts on 
my DMZ can still see my LAN and the internet because 1)net is on default 
route and 2)route to LAN still exists.

Ping a DMZ host from a LAN host and I see 100% packet loss.

I re-added the route:  ip route add DMZ/24 dev eth1

Voila', ping starts to work.

:m)

  reply	other threads:[~2009-01-21 18:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 14:32 Conntrack not recording packets going through a firewall David J Craigon
2009-01-21 16:49 ` Mike Wright
2009-01-21 17:20   ` David J Craigon
2009-01-21 17:37     ` David J Craigon
2009-01-21 18:36       ` Mike Wright [this message]
2009-01-21 20:33         ` David J Craigon
2009-01-21 21:22           ` Mike Wright
2009-01-21 22:23             ` David J Craigon

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=49776B2A.4070005@mailinator.com \
    --to=mike.wright@mailinator.com \
    --cc=david@craigon.co.uk \
    --cc=netfilter@vger.kernel.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