All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Eastep <teastep@shorewall.net>
To: "Anthony R. Vallario" <avallario@tecmasters.com>,
	netfilter@lists.netfilter.org
Subject: Re: Strange NAT Behavior
Date: Fri, 14 Jul 2006 07:29:26 -0700	[thread overview]
Message-ID: <44B7AA46.7080105@shorewall.net> (raw)
In-Reply-To: <005a01c6a750$847a7d00$e30da8c0@tmilawton.com>

[-- Attachment #1: Type: text/plain, Size: 830 bytes --]

Anthony R. Vallario wrote:
> Sure enough, there are logged events
> from when one of the LAN pc's was blocked from going to say yahoo, adobe
> or google. Weird thing is, it's random. Ports are random to.I can't make
> heads or tales out of a pattern or reason why. So why on earth would a
> nat firewall with no outgoing drop rules all of a sudden block these lan
> pc's?

Check the DROP log messages -- is the IN= interface your LAN interface or your
WAN interface? If it is the WAN interface, check your cabling to be sure that
you haven't bridged the LAN and WAN sides of your firewall.

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net
PGP Public Key   \ https://lists.shorewall.net/teastep.pgp.key


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

  reply	other threads:[~2006-07-14 14:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-14 14:19 Strange NAT Behavior Anthony R. Vallario
2006-07-14 14:29 ` Tom Eastep [this message]
2006-07-15 10:44 ` Sietse van Zanen

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=44B7AA46.7080105@shorewall.net \
    --to=teastep@shorewall.net \
    --cc=avallario@tecmasters.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.