Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Alistair Tonner <Alistair@nerdnet.ca>
To: netfilter@lists.netfilter.org
Subject: Re: pop3 and dns
Date: Wed, 5 May 2004 08:30:34 -0400	[thread overview]
Message-ID: <200405050830.34905.Alistair@nerdnet.ca> (raw)
In-Reply-To: <F22386C3FEB012449238672E38ED61E706C2D6@overlord.overturemedia.com>

On May 5, 2004 12:58 am, Fritz Mesedilla wrote:
> > These look fine as they are, however you will need a rule to
> > allow the reply
> > packets, and perhaps one to SNAT your Internet-bound packets
> > if you are using
> > private addresses on your network.
>
> Oh... How do I do that? Can you give me a sample rule?
>
> > Questions:
> > 1. Can clients access anything by IP address rather than hostname?
> > 2. Do any other services work, such as web browsing (assuming
> > you have rules
> > to allow other servies)?
>
> Clients cannot access anything except web browsing through the Squid proxy.
>
> > Suggestions:
> > 1. Describe your network setup to us.
> > 2. Show us all your netfilter rules.
>
> We have public ips on the outside while we have private ips on the inside
> doing nat through iptables and not through the router as we do not have
> control of the router.
>
> For example,
>
> 202.78.90.166 <-> iptables <-> 192.168.247.11
> 202.78.90.166 <-> iptables <-> 192.168.247.12
>
> For web browsing I have squid proxy. So normally, clients do not have to
> resolve domain names as squid proxy does it for them. Now I need to allow
> clients to resolve domain names to be able to retrieve pop3 from their
> other mail servers.
>
> Thanks again!
>

	Looking at your included ruleset I don't see any NAT of the (already) allowed 
DNS and POP3 requests -- You have forward rules that will allow the DNS 
requests out the forward chain, but you are only MASQUERADING the port 80 
requests.

      Try adding a duplicate of the MASQUERADE rule to TCP and UDP port 53.
       If the pop3 is in the routable internet space, you need to MASQUERADE 
that as well.

	Alistair

	


>


	<much snippage for Brevity  >


  parent reply	other threads:[~2004-05-05 12:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-05  4:58 pop3 and dns Fritz Mesedilla
2004-05-05 10:24 ` Antony Stone
2004-05-05 12:30 ` Alistair Tonner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-13  1:40 cldavis
2004-05-13 23:49 ` Mark E. Donaldson
2004-05-07  5:21 Fritz Mesedilla
2004-05-05  4:42 Fritz Mesedilla
2004-05-04  9:40 Fritz Mesedilla
2004-05-04  9:40 ` Ray Leach
2004-05-04 10:09 ` Antony Stone
2004-05-11 13:37 ` Peter Marshall
2004-05-12  4:22   ` Alexander Samad
2004-05-12  7:15     ` Ray Leach
2004-05-12 19:14       ` Dana Bourgeois
2004-05-12 19:34         ` Cedric Blancher
2004-05-12 21:21           ` Dick St.Peters

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=200405050830.34905.Alistair@nerdnet.ca \
    --to=alistair@nerdnet.ca \
    --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