All of lore.kernel.org
 help / color / mirror / Atom feed
From: Magnus Sundberg <Magnus.Sundberg@dican.se>
To: Rob Sterenborg <rsterenborg@xs4all.nl>, netfilter@lists.netfilter.org
Subject: Re: Non host resident proxies
Date: Tue, 21 Jan 2003 13:14:52 +0100	[thread overview]
Message-ID: <3E2D39BC.1060302@dican.se> (raw)
In-Reply-To: FD8F124A387AD6119F7900A0D218B321019AED@hslex01.hslbz.local

Hi,
Thanks for your answer.
It will not work, since NAT rewrites the destination header, which is 
used by the pop3vscan proxy to find out the actual host.

But I found out later
iptaples -t mangling -p tcp --dport 110 -s ! <ip_host> -j ROUTE --gw 
<ip_host>

According to Cédric, the author of the ROUTE target, you need to use CVS 
for p-o-m and source, since there are some compatibility issues between 
the new patch-o-matic-20030107 with the old iptables-1.2.7a.

/Magnus

Rob Sterenborg wrote:
>>I want to redirect all POP3 requests back to my main server. POP3 
>>requests from the main server is forwarded to the internet. 
>>Something like this.
>>
>>------------          -------------------
>>!          !          !                 !
>>! Client   !--------->! router/firewall !
>>!          !      ----!                 !
>>------------      ! ->! - - - - - - - - ! ---->(Internet)
>>                   ! ! !                 !
>>                   ! ! -------------------
>>-------------     ! !
>>!           !<----- !
>>! Server    !--------
>>!           !
>>-------------
>>
>>I can scan all pop3 traffic for viruses by this method.
>>I believe this setup would be correct for proxying other 
>>protocols to. I would preferably be interested in also being 
>>able to redirect the 
>>protocol port too.
>>Is it possible to do this with the current netfilter release?
>>I am aware that there is good chance of unwanted loops with this setup
> 
> 
> You mean to just DNAT port 110/tcp (pop3) to <ip_server> ?
> 
> I assume :
> eth0 : inet
> eth1 : lan
> eth2 : dmz
> 
> iptables -i eth0 [-o eth2] -d <ip_server> -p tcp --dport 110 -j ACCEPT
> itables -t nat -A PREROUTING -i eth0 -p tcp --dport 110 --to-destination
> <ip_server>
> 
> 
> Rob
> 
> 






       reply	other threads:[~2003-01-21 12:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <FD8F124A387AD6119F7900A0D218B321019AED@hslex01.hslbz.local>
2003-01-21 12:14 ` Magnus Sundberg [this message]
2003-01-17 17:50 Non host resident proxies Magnus Sundberg

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=3E2D39BC.1060302@dican.se \
    --to=magnus.sundberg@dican.se \
    --cc=netfilter@lists.netfilter.org \
    --cc=rsterenborg@xs4all.nl \
    /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.