All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Vassilev <mv-lists@net-surf.net>
To: netfilter@lists.netfilter.org
Subject: Re: Problem with transparent proxing if catching traffic on vlan interface
Date: Fri, 13 May 2005 16:28:07 +0300	[thread overview]
Message-ID: <200505131628.07118.mv-lists@net-surf.net> (raw)
In-Reply-To: <200505121650.j4CGovrs010826@mont.net-surf.net>

On Thursday 12 May 2005 19:50, netfilter-request@lists.netfilter.org wrote:
> On Thu, May 12, 2005 at 02:52:38PM +0300, Martin Vassilev wrote:
> > Hello , first of all sorry for poor english.
> >
> > Have some trouble with transparent proxing    
> >
> > Configuration is simple:
> >
> > ------------                            ----------
> >
> > |CLIENT| ---- eth/vlans ---- | GATE|
> >
> > ------------                            ----------
> >                                       transparent proxy
> >
> >
> > ------------------test1---------------------
> > GATE:/#iptables  -t nat -I PREROUTING -p TCP -s `CLIENT`  \
> > --destination-port 80 -i vlan8 -j REDIRECT --to-ports 3128
> >
> > CLIENT:/# telnet www.netfilter.org 80
> > Trying 213.95.27.115...
> > telnet: connect to address 213.95.27.115: Connection refused
> > (thats the problem ;))
> >
> > GATE:/# tcpdump  -n -i vlan8 -f "net `CLIENT`"
> > tcpdump: listening on vlan8
> > 11:43:28.336226 `CLIENT`.38842 > 213.95.27.115.80: S
> > 1057989664:1057989664(0) win 5840 <mss 1412,sackOK,timestamp 1881955228
> > 0,nop,wscale 2> (DF) [tos 0x10]
> >
> > GATE:/# iptables -t nat -n -L -v
> > Chain PREROUTING (policy ACCEPT 32M packets, 1991M bytes)
> >  pkts bytes target     prot opt in     out     source              
> > destination
> >     1    60 REDIRECT   tcp  --  vlan8  *       `CLIENT`      0.0.0.0/0  
> >         tcp dpt:80 redir ports 3128
> >
> > nothing appear in squid´s access.log
> >
> >
> > ----------------test2------------------------
> > After some rerouting to reach the gate through eth0
> >
> > GATE:/#iptables  -t nat -I PREROUTING -p TCP -s `CLIENT`  \
> > --destination-port 80 -i eth0 -j REDIRECT --to-ports 3128
> >
> > and all works fine.
> > ---------------------------------------------
> >
> > Is there any differents for netfilter if catching traffic on eth or vlan
> > interface ?
>
> does vlan8 have an IP address?  REDIRECT rewrites the packet's dst IP to
> be the IP of the interface the packet was received on, i'd imagine it
> would get confused if the interface didn't have an IP address.
>
> alternatively, you may have some funky routing going on--i wouldn't be
> surprised if you tcpdumped the other interfaces and saw the SYN/ACK from
> the first example going out an interface other than vlan8--does:
>
>   ip route get $CLIENT_IP
>
> show that the packet is routed via dev vlan8?
>
> just some things to consider.
>
> -j
Thanks for repply Jason.
Binding squid on 0.0.0.0:3128 instead of $GATE_IP:3128 fix the problem.
Not work on $VLAN8_IP:3128 ?

-- 
Best Regards,
Martin Vassilev
NetSurf.net Ltd.



       reply	other threads:[~2005-05-13 13:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200505121650.j4CGovrs010826@mont.net-surf.net>
2005-05-13 13:28 ` Martin Vassilev [this message]
2005-05-12 11:52 Problem with transparent proxing if catching traffic on vlan interface Martin Vassilev
2005-05-12 12:47 ` Jason Opperisano

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=200505131628.07118.mv-lists@net-surf.net \
    --to=mv-lists@net-surf.net \
    --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.