- tproxy - lists.balabit.hu

tproxy in Ubuntu
by Tristram Cheer 08 Mar '10

08 Mar '10

Hey Guys, I'm looking at setting up Squid 3.1 with tproxy on ubuntu 9.10 server edition and was wanting to know from the list if anyone has had any luck with this? I'm aware I might have to do a kernel/iptables recompile, Is there a recommended version's to do this with? Are the patchs still needed? Regards Tristram

1 0

Deployment TPROXY
by V. Feitoza 13 Feb '10

13 Feb '10

Good staff I have the following architecture: Arch Linux kernel: 2.6.30 iptables: 1.4.6 ebtables: 2.0.9 squid: 3.1.0.14 Network: eth1: 0.0.0.0 eth2: 0.0.0.0 br0: 172.16.2.3/12 route: 172.16.0.1 Firewall rules: cd /proc/sys/net/bridge/ for i in * do echo 0 > $i done unset i iptables -t mangle -N DIVERT iptables -t mangle -A DIVERT -j MARK --set-mark 1 iptables -t mangle -A DIVERT -j ACCEPT iptables -t mangle -A PREROUTING -p tcp -m socket -j DIVERT iptables -t mangle -A PREROUTING -p tcp --dport 80 -j TPROXY --tproxy-mark 0x1/0x1 --on-port 3129 ebtables -t broute -A BROUTING -i eth1 -p ipv4 --ip-proto tcp --ip-dport 80 -j redirect --redirect-target DROP ebtables -t broute -A BROUTING -i eth2 -p ipv4 --ip-proto tcp --ip-dport 80 -j redirect --redirect-target DROP ip rule add fwmark 1 lookup 100 ip route add local 0.0.0.0/0 dev lo table 100 Sysctl: net.ipv4.conf.default.rp_filter=0 net.ipv4.conf.default.forwarding=1 net.ipv4.conf.all.forwarding=1 net.ipv4.ip_nonlocal_bind=1 net.ipv4.ip_forward=1 Squid.conf acl all src all acl manager proto cache_object acl localhost src 127.0.0.1/32 acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 acl localnet src 10.0.0.0/8 # RFC1918 possible internal network acl localnet src 172.16.0.0/12 # RFC1918 possible internal network acl localnet src 192.168.0.0/16 # RFC1918 possible internal network acl SSL_ports port 443 acl Safe_ports port 80 # http acl Safe_ports port 21 # ftp acl Safe_ports port 443 # https acl Safe_ports port 70 # gopher acl Safe_ports port 210 # wais acl Safe_ports port 1025-65535 # unregistered ports acl Safe_ports port 280 # http-mgmt acl Safe_ports port 488 # gss-http acl Safe_ports port 591 # filemaker acl Safe_ports port 777 # multiling http acl CONNECT method CONNECT http_access allow manager localhost http_access deny manager http_access deny !Safe_ports http_access deny CONNECT !SSL_ports http_access allow localnet http_access deny all icp_access allow localnet icp_access deny all http_port 3128 http_port 3129 tproxy hierarchy_stoplist cgi-bin ? access_log /var/log/squid/access.log squid refresh_pattern ^ftp: 1440 20% 10080 refresh_pattern ^gopher: 1440 0% 1440 refresh_pattern -i (/cgi-bin/|\?) 0 0% 0 refresh_pattern . 0 20% 4320 #acl shoutcast rep_header X-HTTP09-First-Line ^ICY.[0-9] #upgrade_http0.9 deny shoutcast #acl apache rep_header Server ^Apache #broken_vary_encoding allow apache cache_mgr mail(a)mai.com visible_hostname agros.mail.com cache_effective_user proxy cache_effective_group proxy maximum_object_size 10 MB cache_dir aufs /var/cache/squid/cache 80000 16 256 coredump_dir /var/cache/squid/cache/ cache_store_log /var/log/squid/store.log cache_log /var/log/squid/cache.log access_log /var/log/squid/access.log squid pid_filename /var/run/squid.pid tcp_outgoing_address 172.16.2.3 debug_options ALL,1 89,6 Now comes the problem: Sometimes browsing but slowly and in most cases customers do not open anything. Thanks Victor Feitoza.

1 0

Re: [tproxy] iptable_tproxy
by nicolas normand 11 Feb '10

11 Feb '10

I would suggest you use: - iptables 1.4.6: I don't remember if iptables 1.4.2 needs to be patched or not - linux 2.6.31: yes, it has built-in tproxy. You need options "Transparent proxying support (EXPERIMENTAL)", "TPROXY" target support (EXPERIMENTAL) and "socket" match support (EXPERIMENTAL) Don't use the 2.6.32, something changed about rp_filters and I couldn't make tproxy to work with it. Maybe someone else know how to do. The problem was fixed on the 2.6.33 (which is not yet released), but you'll need to set a new sysctl call: sysctl net.ipv4.conf.lo.src_valid_mark=1 For iptables/ebtables rulez, I based my configuration on this post: https://lists.balabit.hu/pipermail/tproxy/2010-January/001211.html Bye, Nicolas 2010/2/11 Alexander Dultsev <alexander.dooltsev(a)gmail.com>: > hi Nicolas, > thanks for the fast reply, and sorry about my spontaneous question - yes, > it's about using iptables 1.4.2 with a patched Debian kernel 2.6.27-wt6 > (tproxy patch) or not patched 2.6.31 (the 2.6.31 has it in-built, am I > correct?) > So, 1) is iptables 1.4.2 + kernel 2.6.31 ok to go for tproxy functionality? > 2) how would you make it working then? > Thanks, > Alex. > > > On Thu, Feb 11, 2010 at 9:14 AM, nicolas normand <doomyster(a)gmail.com> > wrote: >> >> I suppose you are speaking of the tproxy table. It was removed some >> time ago (I don't remember when), now I could make tproxy to work with >> just the mangle table, and a 2.6.31 or 2.6.33 linux kernel. >> >> Bye, >> Nicolas >> >> 2010/2/11 Alexander Dultsev <alexander.dooltsev(a)gmail.com>: >> > Hello, >> > perhaps it's covered in some place here (if so, could you please point >> > to >> > the right direction) - is entry iptables_tproxy.ko missing under tproxy >> > 4.x.x version (so things like 'iptables -F tproxy -L' cannot be called)? >> > I >> > can see, for instance, 'iptables_raw' etc, but not the above in my >> > /lib/modules/... directory. >> > Thanks, >> > Alex. >> > _______________________________________________ >> > tproxy mailing list >> > tproxy(a)lists.balabit.hu >> > https://lists.balabit.hu/mailman/listinfo/tproxy >> > >> > > >

1 0

iptable_tproxy
by Alexander Dultsev 11 Feb '10

11 Feb '10

Hello, perhaps it's covered in some place here (if so, could you please point to the right direction) - is entry iptables_tproxy.ko missing under tproxy 4.x.x version (so things like 'iptables -F tproxy -L' cannot be called)? I can see, for instance, 'iptables_raw' etc, but not the above in my /lib/modules/... directory. Thanks, Alex.

1 0

Need Help
by Adnan Shahzad 04 Feb '10

04 Feb '10

Dear All, I configured Tproxy with squid + NTLM + AD, everything works fine.... My problem is that "HTTPS" .... https request Time out and when I remove only secure portion in Browser setting it work fine.. Kindly help me Access.log: 1264582167.890 3 10.10.0.40 TCP_DENIED/407 7673 CONNECT www.google.com:443<http://www.google.com:443> - NONE/- text/html 1264582167.900 5 10.10.0.40 TCP_DENIED/407 7883 CONNECT www.google.com:443<http://www.google.com:443> - NONE/- text/html 1264582174.569 3 10.10.0.40 TCP_DENIED/407 7673 GET http://mail.yahoo.com/ - NONE/- text/html 1264582174.580 6 10.10.0.40 TCP_DENIED/407 7883 GET http://mail.yahoo.com/ - NONE/- text/html 1264582175.616 1026 10.10.0.40 TCP_MISS/302 700 GET http://mail.yahoo.com/ mydomain\Username DIRECT/69.147.112.160 text/html 1264582175.625 4 10.10.0.40 TCP_DENIED/407 7673 CONNECT login.yahoo.com:443 - NONE/- text/html 1264582175.636 7 10.10.0.40 TCP_DENIED/407 7883 CONNECT login.yahoo.com:443 - NONE/- text/html 1264582177.020 4 10.10.0.40 TCP_DENIED/407 7673 CONNECT login.facebook.com:443 - NONE/- text/html 1264582177.030 5 10.10.0.40 TCP_DENIED/407 7883 CONNECT login.facebook.com:443 - NONE/- text/html 1264582214.286 5 10.10.0.40 TCP_DENIED/403 378 GET http://91.212.226.182/loader.exe - NONE/- text/html 1264582223.319 46277 10.10.0.40 TCP_MISS/000 0 CONNECT login.facebook.com:443 MYDOMAIN\USERNAME NONE/- - 1264582223.338 8 10.10.0.40 TCP_DENIED/407 7673 CONNECT login.facebook.com:443 - NONE/- text/html 1264582223.366 13 10.10.0.40 TCP_DENIED/407 7883 CONNECT login.facebook.com:443 - NONE/- text/html 1264582227.958 60055 10.10.0.40 TCP_MISS/504 0 CONNECT www.google.com:443<http://www.google.com:443> MYDOMAIN\USERNAME DIRECT/216.239.61.104 - 1264582235.984 1 10.10.0.40 TCP_DENIED/407 7673 CONNECT login.facebook.com:443 - NONE/- text/html 1264582235.993 2 10.10.0.40 TCP_DENIED/407 7883 CONNECT login.facebook.com:443 - NONE/- text/html 1264582238.832 2 10.10.0.40 TCP_DENIED/407 7673 GET http://mail.yahoo.com/ - NONE/- text/html 1264582238.842 4 10.10.0.40 TCP_DENIED/407 7883 GET http://mail.yahoo.com/ - NONE/- text/html 1264582240.098 1246 10.10.0.40 TCP_MISS/302 700 GET http://mail.yahoo.com/ MYDOMAIN\USERNAME DIRECT/69.147.112.160 text/html 1264582240.104 2 10.10.0.40 TCP_DENIED/407 7673 CONNECT login.yahoo.com:443 - NONE/- text/html 1264582240.113 4 10.10.0.40 TCP_DENIED/407 7883 CONNECT login.yahoo.com:443 - NONE/- text/html 1264582304.251 1 10.10.0.40 TCP_DENIED/407 7673 GET http://mail.yahoo.com/ - NONE/- text/html 1264582304.262 4 10.10.0.40 TCP_DENIED/407 7883 GET http://mail.yahoo.com/ - NONE/- text/html 1264582305.793 1513 10.10.0.40 TCP_MISS/302 698 GET http://mail.yahoo.com/ MYDOMAIN\USERNAME DIRECT/69.147.112.160 text/html 1264582305.800 4 10.10.0.40 TCP_DENIED/407 7673 CONNECT login.yahoo.com:443 - NONE/- text/html 1264582305.810 4 10.10.0.40 TCP_DENIED/407 7883 CONNECT login.yahoo.com:443 - NONE/- text/html

1 0

Configuration problems
by Stelian Ionescu 29 Jan '10

29 Jan '10

Hello, I'm using kernel 2.6.29 with iptables 1.4.6 and I'm trying to setup a minimal TPROXY. Basically, I've configured another (physical) machine to use my computer as default gateway, then on my machine I've enabled ip_forward and disabled rp_filter everywhere and using these rules: ip rule add fwmark 1 lookup 100 ip route add local 0.0.0.0/0 dev lo table 100 iptables -t mangle -A PREROUTING -p tcp -m tcp --dport 80 -j TPROXY --on-port 9999 --tproxy-mark 0x1/0x1 There are no other iptables rules, and all chains default to ACCEPT Then, on the remote machine I try to telnet google.com 80, but the connection can't be established. Tcpdump shows that SYN packets arrive but then it's as if they were dropped: they aren't getting to the proxy on port 9999. Any ideas ? -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur. http://common-lisp.net/project/iolib

2 2

Tproxy + NTLM + squid
by Adnan Shahzad 29 Jan '10

29 Jan '10

Dear All, I configured Tproxy with squid + NTLM + AD, everything works fine.... My problem is that "HTTPS" .... https request Time out and when I remove only secure portion in Browser setting it work fine.. Kindly help me Access.log: 1264582167.890 3 10.10.0.40 TCP_DENIED/407 7673 CONNECT www.google.com:443 - NONE/- text/html 1264582167.900 5 10.10.0.40 TCP_DENIED/407 7883 CONNECT www.google.com:443 - NONE/- text/html 1264582174.569 3 10.10.0.40 TCP_DENIED/407 7673 GET http://mail.yahoo.com/ - NONE/- text/html 1264582174.580 6 10.10.0.40 TCP_DENIED/407 7883 GET http://mail.yahoo.com/ - NONE/- text/html 1264582175.616 1026 10.10.0.40 TCP_MISS/302 700 GET http://mail.yahoo.com/ mydomain\Username DIRECT/69.147.112.160 text/html 1264582175.625 4 10.10.0.40 TCP_DENIED/407 7673 CONNECT login.yahoo.com:443 - NONE/- text/html 1264582175.636 7 10.10.0.40 TCP_DENIED/407 7883 CONNECT login.yahoo.com:443 - NONE/- text/html 1264582177.020 4 10.10.0.40 TCP_DENIED/407 7673 CONNECT login.facebook.com:443 - NONE/- text/html 1264582177.030 5 10.10.0.40 TCP_DENIED/407 7883 CONNECT login.facebook.com:443 - NONE/- text/html 1264582214.286 5 10.10.0.40 TCP_DENIED/403 378 GET http://91.212.226.182/loader.exe - NONE/- text/html 1264582223.319 46277 10.10.0.40 TCP_MISS/000 0 CONNECT login.facebook.com:443 MYDOMAIN\USERNAME NONE/- - 1264582223.338 8 10.10.0.40 TCP_DENIED/407 7673 CONNECT login.facebook.com:443 - NONE/- text/html 1264582223.366 13 10.10.0.40 TCP_DENIED/407 7883 CONNECT login.facebook.com:443 - NONE/- text/html 1264582227.958 60055 10.10.0.40 TCP_MISS/504 0 CONNECT www.google.com:443 MYDOMAIN\USERNAME DIRECT/216.239.61.104 - 1264582235.984 1 10.10.0.40 TCP_DENIED/407 7673 CONNECT login.facebook.com:443 - NONE/- text/html 1264582235.993 2 10.10.0.40 TCP_DENIED/407 7883 CONNECT login.facebook.com:443 - NONE/- text/html 1264582238.832 2 10.10.0.40 TCP_DENIED/407 7673 GET http://mail.yahoo.com/ - NONE/- text/html 1264582238.842 4 10.10.0.40 TCP_DENIED/407 7883 GET http://mail.yahoo.com/ - NONE/- text/html 1264582240.098 1246 10.10.0.40 TCP_MISS/302 700 GET http://mail.yahoo.com/ MYDOMAIN\USERNAME DIRECT/69.147.112.160 text/html 1264582240.104 2 10.10.0.40 TCP_DENIED/407 7673 CONNECT login.yahoo.com:443 - NONE/- text/html 1264582240.113 4 10.10.0.40 TCP_DENIED/407 7883 CONNECT login.yahoo.com:443 - NONE/- text/html 1264582304.251 1 10.10.0.40 TCP_DENIED/407 7673 GET http://mail.yahoo.com/ - NONE/- text/html 1264582304.262 4 10.10.0.40 TCP_DENIED/407 7883 GET http://mail.yahoo.com/ - NONE/- text/html 1264582305.793 1513 10.10.0.40 TCP_MISS/302 698 GET http://mail.yahoo.com/ MYDOMAIN\USERNAME DIRECT/69.147.112.160 text/html 1264582305.800 4 10.10.0.40 TCP_DENIED/407 7673 CONNECT login.yahoo.com:443 - NONE/- text/html 1264582305.810 4 10.10.0.40 TCP_DENIED/407 7883 CONNECT login.yahoo.com:443 - NONE/- text/html

2 1

Re: [tproxy] tproxy Digest, Vol 55, Issue 6
by Luiz Biazus 13 Jan '10

13 Jan '10

my first configuration was with all disabled : > echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter > echo 0 > /proc/sys/net/ipv4/conf/eth1/rp_filter > echo 0 > /proc/sys/net/ipv4/conf/br0/rp_filter > echo 0 > /proc/sys/net/ipv4/conf/lo/rp_filter i enable it to make the test that u said! so doesn't work :-( Thank you friend Luiz 2010/1/13 <tproxy-request(a)lists.balabit.hu>: > Send tproxy mailing list submissions to > tproxy(a)lists.balabit.hu > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.balabit.hu/mailman/listinfo/tproxy > or, via email, send a message with subject or body 'help' to > tproxy-request(a)lists.balabit.hu > > You can reach the person managing the list at > tproxy-owner(a)lists.balabit.hu > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tproxy digest..." > > > Today's Topics: > > 1. Re: tproxy Digest, Vol 55, Issue 5 (Luiz Biazus) > 2. Re: tproxy Digest, Vol 55, Issue 5 (KOVACS Krisztian) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 12 Jan 2010 09:27:52 -0200 > From: Luiz Biazus <luiz(a)biazus.com> > Subject: Re: [tproxy] tproxy Digest, Vol 55, Issue 5 > To: tproxy(a)lists.balabit.hu > Message-ID: > <8ecc30771001120327t20156525nae58961884b9ea8a(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hello Krisztian! > > is that what i mean! > > follow my full configuration: > > echo 1 > /proc/sys/net/ipv4/ip_forward > echo 1 > /proc/sys/net/ipv4/ip_nonlocal_bind > echo 1 > /proc/sys/net/ipv4/conf/eth0/rp_filter > echo 1 > /proc/sys/net/ipv4/conf/eth1/rp_filter > echo 1 > /proc/sys/net/ipv4/conf/br0/rp_filter > echo 1 > /proc/sys/net/ipv4/conf/lo/rp_filter > echo 1 > /proc/sys/net/ipv4/conf/all/forwarding > echo 1 > /proc/sys/net/ipv4/conf/all/send_redirects > > > cd /proc/sys/net/bridge/ > for i in * > do > echo 0 > $i > done > unset i > > > > iptables -t mangle -N DIVERT > iptables -t mangle -A DIVERT -j MARK --set-mark 1 > iptables -t mangle -A DIVERT -j ACCEPT > iptables -t mangle -A PREROUTING -p tcp -m socket -j DIVERT > iptables -t mangle -A PREROUTING -p tcp --dport 80 -j TPROXY > --tproxy-mark 0x1/0x1 --on-port 8012 > ebtables -t broute -A BROUTING -i eth1 -p ipv4 --ip-proto tcp > --ip-dport 80 -j redirect --redirect-target DROP > ebtables -t broute -A BROUTING -i eth0 -p ipv4 --ip-proto tcp > --ip-sport 80 -j redirect --redirect-target DROP > //eth0 connected to gw and eth1 internal > > > ip rule add dev eth0 fwmark 1 lookup 100 > ip rule add dev eth1 fwmark 1 lookup 100 > ip rule add dev br0 fwmark 1 lookup 100 > > > root@cache:~# ip rule > 0: from all lookup local > 32763: from all fwmark 0x1 iif eth0 lookup 100 > 32764: from all fwmark 0x1 iif eth1 lookup 100 > 32765: from all fwmark 0x1 iif br0 lookup 100 > 32766: from all lookup main > 32767: from all lookup default > > root@thundercache:~# ip route show all > 189.10.205.0/24 dev br0 proto kernel scope link src 189.10.205.3 > default via 189.10.205.1 dev br0 metric 100 > > > > root@thundercache:~# ifconfig > br0 Link encap:Ethernet Endere??o de HW 00:06:4f:5f:b3:1e > inet end.: 189.10.205.3 Bcast:189.10.203.255 Masc:255.255.255.0 > endere??o inet6: fe80::206:4fff:fe5f:b31e/64 Escopo:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 M??trica:1 > pacotes RX:2314056 erros:0 descartados:0 excesso:0 quadro:0 > Pacotes TX:686243 erros:0 descartados:0 excesso:0 portadora:0 > colis??es:0 txqueuelen:0 > RX bytes:640911673 (640.9 MB) TX bytes:499301746 (499.3 MB) > > eth0 Link encap:Ethernet Endere??o de HW 00:06:4f:5f:b3:1e > endere??o inet6: fe80::206:4fff:fe5f:b31e/64 Escopo:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 M??trica:1 > pacotes RX:197138752 erros:0 descartados:0 excesso:0 quadro:0 > Pacotes TX:171287420 erros:0 descartados:0 excesso:0 portadora:0 > colis??es:0 txqueuelen:1000 > RX bytes:1122327687 (1.1 GB) TX bytes:1558614907 (1.5 GB) > IRQ:18 > > eth1 Link encap:Ethernet Endere??o de HW 00:1e:8c:d2:2e:e9 > endere??o inet6: fe80::21e:8cff:fed2:2ee9/64 Escopo:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 M??trica:1 > pacotes RX:171297851 erros:1 descartados:0 excesso:0 quadro:1 > Pacotes TX:197160512 erros:0 descartados:0 excesso:0 portadora:0 > colis??es:0 txqueuelen:1000 > RX bytes:1561386827 (1.5 GB) TX bytes:1915548351 (1.9 GB) > IRQ:25 Endere??o de E/S:0x4000 > > lo Link encap:Loopback Local > inet end.: 127.0.0.1 Masc:255.0.0.0 > endere??o inet6: ::1/128 Escopo:M??quina > UP LOOPBACK RUNNING MTU:16436 M??trica:1 > pacotes RX:40 erros:0 descartados:0 excesso:0 quadro:0 > Pacotes TX:40 erros:0 descartados:0 excesso:0 portadora:0 > colis??es:0 txqueuelen:0 > RX bytes:3690 (3.6 KB) TX bytes:3690 (3.6 KB) > > > > Thank you Friend! > > > Bst Rgds > Luiz > > > > 2010/1/12 <tproxy-request(a)lists.balabit.hu>: >> Send tproxy mailing list submissions to >> ? ? ? ?tproxy(a)lists.balabit.hu >> >> To subscribe or unsubscribe via the World Wide Web, visit >> ? ? ? ?https://lists.balabit.hu/mailman/listinfo/tproxy >> or, via email, send a message with subject or body 'help' to >> ? ? ? ?tproxy-request(a)lists.balabit.hu >> >> You can reach the person managing the list at >> ? ? ? ?tproxy-owner(a)lists.balabit.hu >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of tproxy digest..." >> >> >> Today's Topics: >> >> ? 1. Re: tproxy Digest, Vol 55, Issue 4 (Luiz Biazus) >> ? 2. Re: tproxy Digest, Vol 55, Issue 4 (KOVACS Krisztian) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Mon, 11 Jan 2010 09:05:25 -0200 >> From: Luiz Biazus <luiz(a)biazus.com> >> Subject: Re: [tproxy] tproxy Digest, Vol 55, Issue 4 >> To: tproxy(a)lists.balabit.hu >> Message-ID: >> ? ? ? ?<8ecc30771001110305l2ab305e4h757f48a39fc97d95(a)mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> about this procedures: >> >> ?ip rule add dev eth0 fwmark 1 lookup 100 >> ?ip rule add dev eth1 fwmark 1 lookup 100 >> ?ip rule add dev br0 fwmark 1 lookup 100 >> >> >> It doesnt works >> >> >> Thank you ?Krisztian >> >> >> >> >> >> 2010/1/11 ?<tproxy-request(a)lists.balabit.hu>: >>> Send tproxy mailing list submissions to >>> ? ? ? ?tproxy(a)lists.balabit.hu >>> >>> To subscribe or unsubscribe via the World Wide Web, visit >>> ? ? ? ?https://lists.balabit.hu/mailman/listinfo/tproxy >>> or, via email, send a message with subject or body 'help' to >>> ? ? ? ?tproxy-request(a)lists.balabit.hu >>> >>> You can reach the person managing the list at >>> ? ? ? ?tproxy-owner(a)lists.balabit.hu >>> >>> When replying, please edit your Subject line so it is more specific >>> than "Re: Contents of tproxy digest..." >>> >>> >>> Today's Topics: >>> >>> ? 1. EADDRNOTAVAIL from connect, but only sometimes (Ron Parker) >>> ? 2. Re: Correct kernel version with tproxy (KOVACS Krisztian) >>> >>> >>> ---------------------------------------------------------------------- >>> >>> Message: 1 >>> Date: Sun, 10 Jan 2010 19:46:58 -0500 >>> From: Ron Parker <rparker(a)movik.net> >>> Subject: [tproxy] EADDRNOTAVAIL from connect, but only sometimes >>> To: "tproxy(a)lists.balabit.hu" <tproxy(a)lists.balabit.hu> >>> Message-ID: >>> ? ? ? ?<5D6AFCAC2AD9424D816711D1AF4FE8441BDE791924(a)MAILR014.mail.lan> >>> Content-Type: text/plain; charset="us-ascii" >>> >>> Hi, >>> >>> We are using the tproxy patch for Linux 2.6.24 (Ubuntu 8.0.4). ? When placing outgoing connections, we use the original socket address (4-tuple) ?in the bind and set SO_REUSEADDR on the socket. ? The sequence we are having difficulty with is: >>> >>> >>> * ? ? ? ? Client connects to transparent proxy >>> >>> * ? ? ? ? Transparent proxy connects to remote server >>> >>> * ? ? ? ? Normal data transfer... >>> >>> * ? ? ? ? Remote server closes the connection (but client connection is maintained) >>> >>> * ? ? ? ? Transparent proxy attempts to connect again to remote server using the original 4-tuple (again) >>> >>> o ? Bind succeeds >>> >>> o ? Connect fails with EADDRNOTAVAIL >>> >>> The original socket is probably in TIME_WAIT at this point. ? I thought the SO_REUSEADDR would take care of the problem. ?What am I missing here? >>> >>> Thanks. >>> >>> ? Ron >>>

1 0

Re: [tproxy] tproxy Digest, Vol 55, Issue 5
by Luiz Biazus 12 Jan '10

12 Jan '10

Hello Krisztian! is that what i mean! follow my full configuration: echo 1 > /proc/sys/net/ipv4/ip_forward echo 1 > /proc/sys/net/ipv4/ip_nonlocal_bind echo 1 > /proc/sys/net/ipv4/conf/eth0/rp_filter echo 1 > /proc/sys/net/ipv4/conf/eth1/rp_filter echo 1 > /proc/sys/net/ipv4/conf/br0/rp_filter echo 1 > /proc/sys/net/ipv4/conf/lo/rp_filter echo 1 > /proc/sys/net/ipv4/conf/all/forwarding echo 1 > /proc/sys/net/ipv4/conf/all/send_redirects cd /proc/sys/net/bridge/ for i in * do echo 0 > $i done unset i iptables -t mangle -N DIVERT iptables -t mangle -A DIVERT -j MARK --set-mark 1 iptables -t mangle -A DIVERT -j ACCEPT iptables -t mangle -A PREROUTING -p tcp -m socket -j DIVERT iptables -t mangle -A PREROUTING -p tcp --dport 80 -j TPROXY --tproxy-mark 0x1/0x1 --on-port 8012 ebtables -t broute -A BROUTING -i eth1 -p ipv4 --ip-proto tcp --ip-dport 80 -j redirect --redirect-target DROP ebtables -t broute -A BROUTING -i eth0 -p ipv4 --ip-proto tcp --ip-sport 80 -j redirect --redirect-target DROP //eth0 connected to gw and eth1 internal ip rule add dev eth0 fwmark 1 lookup 100 ip rule add dev eth1 fwmark 1 lookup 100 ip rule add dev br0 fwmark 1 lookup 100 root@cache:~# ip rule 0: from all lookup local 32763: from all fwmark 0x1 iif eth0 lookup 100 32764: from all fwmark 0x1 iif eth1 lookup 100 32765: from all fwmark 0x1 iif br0 lookup 100 32766: from all lookup main 32767: from all lookup default root@thundercache:~# ip route show all 189.10.205.0/24 dev br0 proto kernel scope link src 189.10.205.3 default via 189.10.205.1 dev br0 metric 100 root@thundercache:~# ifconfig br0 Link encap:Ethernet EndereÃ§o de HW 00:06:4f:5f:b3:1e inet end.: 189.10.205.3 Bcast:189.10.203.255 Masc:255.255.255.0 endereÃ§o inet6: fe80::206:4fff:fe5f:b31e/64 Escopo:Link UP BROADCAST RUNNING MULTICAST MTU:1500 MÃ©trica:1 pacotes RX:2314056 erros:0 descartados:0 excesso:0 quadro:0 Pacotes TX:686243 erros:0 descartados:0 excesso:0 portadora:0 colisÃµes:0 txqueuelen:0 RX bytes:640911673 (640.9 MB) TX bytes:499301746 (499.3 MB) eth0 Link encap:Ethernet EndereÃ§o de HW 00:06:4f:5f:b3:1e endereÃ§o inet6: fe80::206:4fff:fe5f:b31e/64 Escopo:Link UP BROADCAST RUNNING MULTICAST MTU:1500 MÃ©trica:1 pacotes RX:197138752 erros:0 descartados:0 excesso:0 quadro:0 Pacotes TX:171287420 erros:0 descartados:0 excesso:0 portadora:0 colisÃµes:0 txqueuelen:1000 RX bytes:1122327687 (1.1 GB) TX bytes:1558614907 (1.5 GB) IRQ:18 eth1 Link encap:Ethernet EndereÃ§o de HW 00:1e:8c:d2:2e:e9 endereÃ§o inet6: fe80::21e:8cff:fed2:2ee9/64 Escopo:Link UP BROADCAST RUNNING MULTICAST MTU:1500 MÃ©trica:1 pacotes RX:171297851 erros:1 descartados:0 excesso:0 quadro:1 Pacotes TX:197160512 erros:0 descartados:0 excesso:0 portadora:0 colisÃµes:0 txqueuelen:1000 RX bytes:1561386827 (1.5 GB) TX bytes:1915548351 (1.9 GB) IRQ:25 EndereÃ§o de E/S:0x4000 lo Link encap:Loopback Local inet end.: 127.0.0.1 Masc:255.0.0.0 endereÃ§o inet6: ::1/128 Escopo:MÃ¡quina UP LOOPBACK RUNNING MTU:16436 MÃ©trica:1 pacotes RX:40 erros:0 descartados:0 excesso:0 quadro:0 Pacotes TX:40 erros:0 descartados:0 excesso:0 portadora:0 colisÃµes:0 txqueuelen:0 RX bytes:3690 (3.6 KB) TX bytes:3690 (3.6 KB) Thank you Friend! Bst Rgds Luiz 2010/1/12 <tproxy-request(a)lists.balabit.hu>: > Send tproxy mailing list submissions to > tproxy(a)lists.balabit.hu > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.balabit.hu/mailman/listinfo/tproxy > or, via email, send a message with subject or body 'help' to > tproxy-request(a)lists.balabit.hu > > You can reach the person managing the list at > tproxy-owner(a)lists.balabit.hu > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tproxy digest..." > > > Today's Topics: > > 1. Re: tproxy Digest, Vol 55, Issue 4 (Luiz Biazus) > 2. Re: tproxy Digest, Vol 55, Issue 4 (KOVACS Krisztian) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 11 Jan 2010 09:05:25 -0200 > From: Luiz Biazus <luiz(a)biazus.com> > Subject: Re: [tproxy] tproxy Digest, Vol 55, Issue 4 > To: tproxy(a)lists.balabit.hu > Message-ID: > <8ecc30771001110305l2ab305e4h757f48a39fc97d95(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > about this procedures: > > ip rule add dev eth0 fwmark 1 lookup 100 > ip rule add dev eth1 fwmark 1 lookup 100 > ip rule add dev br0 fwmark 1 lookup 100 > > > It doesnt works > > > Thank you Krisztian > > > > > > 2010/1/11 <tproxy-request(a)lists.balabit.hu>: >> Send tproxy mailing list submissions to >> ? ? ? ?tproxy(a)lists.balabit.hu >> >> To subscribe or unsubscribe via the World Wide Web, visit >> ? ? ? ?https://lists.balabit.hu/mailman/listinfo/tproxy >> or, via email, send a message with subject or body 'help' to >> ? ? ? ?tproxy-request(a)lists.balabit.hu >> >> You can reach the person managing the list at >> ? ? ? ?tproxy-owner(a)lists.balabit.hu >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of tproxy digest..." >> >> >> Today's Topics: >> >> ? 1. EADDRNOTAVAIL from connect, but only sometimes (Ron Parker) >> ? 2. Re: Correct kernel version with tproxy (KOVACS Krisztian) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sun, 10 Jan 2010 19:46:58 -0500 >> From: Ron Parker <rparker(a)movik.net> >> Subject: [tproxy] EADDRNOTAVAIL from connect, but only sometimes >> To: "tproxy(a)lists.balabit.hu" <tproxy(a)lists.balabit.hu> >> Message-ID: >> ? ? ? ?<5D6AFCAC2AD9424D816711D1AF4FE8441BDE791924(a)MAILR014.mail.lan> >> Content-Type: text/plain; charset="us-ascii" >> >> Hi, >> >> We are using the tproxy patch for Linux 2.6.24 (Ubuntu 8.0.4). ? When placing outgoing connections, we use the original socket address (4-tuple) ?in the bind and set SO_REUSEADDR on the socket. ? The sequence we are having difficulty with is: >> >> >> * ? ? ? ? Client connects to transparent proxy >> >> * ? ? ? ? Transparent proxy connects to remote server >> >> * ? ? ? ? Normal data transfer... >> >> * ? ? ? ? Remote server closes the connection (but client connection is maintained) >> >> * ? ? ? ? Transparent proxy attempts to connect again to remote server using the original 4-tuple (again) >> >> o ? Bind succeeds >> >> o ? Connect fails with EADDRNOTAVAIL >> >> The original socket is probably in TIME_WAIT at this point. ? I thought the SO_REUSEADDR would take care of the problem. ?What am I missing here? >> >> Thanks. >> >> ? Ron >>

2 1

Re: [tproxy] tproxy Digest, Vol 55, Issue 4
by Luiz Biazus 11 Jan '10

11 Jan '10

about this procedures: ip rule add dev eth0 fwmark 1 lookup 100 ip rule add dev eth1 fwmark 1 lookup 100 ip rule add dev br0 fwmark 1 lookup 100 It doesnt works Thank you Krisztian 2010/1/11 <tproxy-request(a)lists.balabit.hu>: > Send tproxy mailing list submissions to > tproxy(a)lists.balabit.hu > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.balabit.hu/mailman/listinfo/tproxy > or, via email, send a message with subject or body 'help' to > tproxy-request(a)lists.balabit.hu > > You can reach the person managing the list at > tproxy-owner(a)lists.balabit.hu > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tproxy digest..." > > > Today's Topics: > > 1. EADDRNOTAVAIL from connect, but only sometimes (Ron Parker) > 2. Re: Correct kernel version with tproxy (KOVACS Krisztian) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 10 Jan 2010 19:46:58 -0500 > From: Ron Parker <rparker(a)movik.net> > Subject: [tproxy] EADDRNOTAVAIL from connect, but only sometimes > To: "tproxy(a)lists.balabit.hu" <tproxy(a)lists.balabit.hu> > Message-ID: > <5D6AFCAC2AD9424D816711D1AF4FE8441BDE791924(a)MAILR014.mail.lan> > Content-Type: text/plain; charset="us-ascii" > > Hi, > > We are using the tproxy patch for Linux 2.6.24 (Ubuntu 8.0.4). When placing outgoing connections, we use the original socket address (4-tuple) in the bind and set SO_REUSEADDR on the socket. The sequence we are having difficulty with is: > > > * Client connects to transparent proxy > > * Transparent proxy connects to remote server > > * Normal data transfer... > > * Remote server closes the connection (but client connection is maintained) > > * Transparent proxy attempts to connect again to remote server using the original 4-tuple (again) > > o Bind succeeds > > o Connect fails with EADDRNOTAVAIL > > The original socket is probably in TIME_WAIT at this point. I thought the SO_REUSEADDR would take care of the problem. What am I missing here? > > Thanks. > > Ron >

2 1