Skip to main content

iptables - (dnat|redirect) with masquerade doesn't work

I have a problem, till a bit ago it was working just fine.
but now, it doesn't work, but on another testing server it works just
fine



I force all traffic to tor, and this part
works just fine.
Problem is on masquerade I think as it not change the
dnat/redirect port 9040 to the origin port 80/443 back after receive response




  • href="http://ipinfo.io:9040" rel="nofollow
    noreferrer">http://ipinfo.io:9040



  • Software:




    • 1.6.1-2ubuntu2

    • ubuntu
      16.04/18.04 the same result

    • tor
      0.3.2.9-1build1


  • Networking





    • virbr1
      - 192.168.2.0/24 - host only

    • eno1 - 192.168.1.0/24 -
      internet


  • Iptables:




    • /sbin/iptables
      -t nat -A POSTROUTING -o virbr1 -j
      MASQUERADE

    • /sbin/iptables -t nat -A POSTROUTING -o eno1
      -j MASQUERADE # on another server works without that, this was just for
      testing

    • /sbin/iptables -t nat -A PREROUTING -p udp
      --source 192.168.2.6 ! --destination 192.168.2.1 -j DNAT --to-destination
      192.168.2.1:9040 # tested REDIRECT --to-ports 9040, the
      same







*filter
:INPUT ACCEPT [174876:86417485]
:FORWARD DROP
[0:0]
:OUTPUT ACCEPT [170612:89138010]
:DOCKER - [0:0]

:DOCKER-ISOLATION - [0:0]
:DOCKER-USER - [0:0]

-A
FORWARD -d 192.168.2.8/32 -i virbr1 -o virbr1 -j ACCEPT
-A FORWARD -s
192.168.2.8/32 -i virbr1 -o virbr1 -j ACCEPT
-A FORWARD -d 192.168.2.0/24 -o
virbr1 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -s
192.168.2.0/24 -i virbr1 -j ACCEPT
-A FORWARD -i virbr1 -o virbr1 -j
ACCEPT
-A OUTPUT -s 192.168.2.8/32 -j DROP
COMMIT
#
Completed on Tue Feb 20 09:32:11 2018
# Generated by iptables-save v1.6.1 on
Tue Feb 20 09:32:11 2018
*nat

:PREROUTING ACCEPT
[193:19723]
:INPUT ACCEPT [193:19723]
:OUTPUT ACCEPT
[129:12889]
:POSTROUTING ACCEPT [124:11792]
:DOCKER -
[0:0]
-A PREROUTING -s 192.168.2.8/32 -p tcp -m tcp --dport 53 -j DNAT
--to-destination 192.168.2.1:5353
-A PREROUTING -s 192.168.2.8/32 -p udp -m
udp --dport 53 -j DNAT --to-destination 192.168.2.1:5353
-A PREROUTING -s
192.168.2.8/32 ! -d 192.168.2.1/32 -p tcp -j DNAT --to-destination
192.168.2.1:9040
-A PREROUTING -s 192.168.2.8/32 ! -d 192.168.2.1/32 -p udp
-j DNAT --to-destination 192.168.2.1:9040
-A POSTROUTING -o tun5 -j
MASQUERADE

-A POSTROUTING -o virbr1 -j MASQUERADE

COMMIT
# Completed on Tue Feb 20 09:32:11 2018
# Generated by
iptables-save v1.6.1 on Tue Feb 20 09:32:11 2018
*mangle

:PREROUTING ACCEPT [3538365:1832890486]
:INPUT ACCEPT
[3538362:1832890258]
:FORWARD ACCEPT [3:228]
:OUTPUT ACCEPT
[3495644:1711746305]
:POSTROUTING ACCEPT
[3496898:1711973811]

-A POSTROUTING -o virbr1 -p udp -m udp
--dport 68 -j CHECKSUM --checksum-fill
-A POSTROUTING -o virbr0 -p udp -m udp
--dport 68 -j CHECKSUM --checksum-fill
-A POSTROUTING -o virbr1 -p udp -m udp
--dport 68 -j CHECKSUM --checksum-fill

COMMIT




  • /proc/sys/net/ipv4/ip_forward
    is set to
    1


  • Monitoring
    with conntrack
    -L





    • tcp
      6 431973 ESTABLISHED src=192.168.2.6 dst=172.217.16.4 sport=49215 dport=443
      src=192.168.2.1 dst=192.168.2.6 sport=9040 dport=49215 [ASSURED] mark=0
      use=1

    • tcp 6 431983 ESTABLISHED src=192.168.2.6
      dst=104.81.60.33 sport=49226 dport=80 src=192.168.2.1 dst=192.168.2.6 sport=9040
      dport=49226 [ASSURED] mark=0 use=1

    • tcp 6 431972
      ESTABLISHED src=192.168.2.6 dst=64.233.184.154 sport=49211 dport=443 src=192.168.2.1
      dst=192.168.2.6 sport=9040 dport=49211 [ASSURED] mark=0
      use=1

    • tcp 6 431972 ESTABLISHED src=192.168.2.6
      dst=54.192.185.106 sport=49216 dport=80 src=192.168.2.1 dst=192.168.2.6 sport=9040
      dport=49216 [ASSURED] mark=0 use=1

    • tcp 6 431973
      ESTABLISHED src=192.168.2.6 dst=216.58.208.46 sport=49194 dport=80 src=192.168.2.1
      dst=192.168.2.6 sport=9040 dport=49194 [ASSURED] mark=0
      use=1

    • tcp 6 74 TIME_WAIT src=192.168.2.6 dst=178.255.83.1
      sport=49190 dport=80 src=192.168.2.1 dst=192.168.2.6 sport=9040 dport=49190 [ASSURED]
      mark=0
      use=1





PS
on another server with the same OS, iptables version, iptables rules it works just
fine



Thanks in advance

Comments

Post a Comment

Popular posts from this blog

linux - Awstats - outputting stats for merged Access_logs only producing stats for one server's log

I've been attempting this for two weeks and I've accessed countless number of sites on this issue and it seems there is something I'm not getting here and I'm at a lost. I manged to figure out how to merge logs from two servers together. (Taking care to only merge the matching domains together) The logs from the first server span from 15 Dec 2012 to 8 April 2014 The logs from the second server span from 2 Mar 2014 to 9 April 2014 I was able to successfully merge them using the logresolvemerge.pl script simply enermerating each log and > out_putting_it_to_file Looking at the two logs from each server the format seems exactly the same. The problem I'm having is producing the stats page for the logs. The command I've boiled it down to is /usr/share/awstats/tools/awstats_buildstaticpages.pl -configdir=/home/User/Documents/conf/ -config=example.com awstatsprog=/usr/share/awstats/wwwroot/cgi-bin/awstats.pl dir=/home/User/Documents/parced -month=all -year=all...
Post a Comment
Read more

iLO 3 Firmware Update (HP Proliant DL380 G7)

The iLO web interface allows me to upload a .bin file ( Obtain the firmware image (.bin) file from the Online ROM Flash Component for HP Integrated Lights-Out. ) The iLO web interface redirects me to a page in the HP support website ( http://www.hp.com/go/iLO ) where I am supposed to find this .bin firmware, but no luck for me. The support website is a mess and very slow, badly categorized and generally unusable. Where can I find this .bin file? The only related link I am able to find asks me about my server operating system (what does this have to do with the iLO?!) and lets me download an .iso with no .bin file And also a related question: what is the latest iLO 3 version? (for Proliant DL380 G7, not sure if the iLO is tied to the server model)
Post a Comment
Read more

hp proliant - Smart Array P822 with HBA Mode?

We get an HP DL360 G8 with an Smart Array P822 controller. On that controller will come a HP StorageWorks D2700 . Does anybody know, that it is possible to run the Smart Array P822 in HBA mode? I found only information about the P410i, who can run HBA. If this is not supported, what you think about the LSI 9207-8e controller? Will this fit good in that setup? The Hardware we get is used but all original from HP. The StorageWorks has 25 x 900 GB SAS 10K disks. Because the disks are not new I would like to use only 22 for raid6, and the rest for spare (I need to see if the disk count is optimal or not for zfs). It would be nice if I'm not stick to SAS in future. As OS I would like to install debian stretch with zfs 0.71 as file system and software raid. I have see that hp has an page for debian to. I would like to use hba mode because it is recommend, that zfs know at most as possible about the disk, and I'm independent from the raid controller. For us zfs have many benefits, ...
Post a Comment
Read more