I need help with IP Tunnling, willing to Pay for it.

Discussion in 'Mail Chat' started by Kumar, Mar 6, 2016.

  1. Kumar

    Kumar New Member

    Joined:
    Sep 7, 2015
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    1
    I have already tried tutorials available in this forum and in google. Also, tried the installation on multiple servers but some how I am not able to do it successfully.

    I am willing to pay someone who can help me to do it. I have already wasted lot of time on it but no success. I need to do it ASAP.

    Plz PM me. Thanks
     
  2. SuperGenii

    SuperGenii www.DataMCP.com

    Joined:
    Apr 9, 2011
    Messages:
    135
    Likes Received:
    16
    Trophy Points:
    63
    Location:
    Southern California
    without revealing your IPs, paste your commands.

    SG
     
  3. Kumar

    Kumar New Member

    Joined:
    Sep 7, 2015
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    1
    Here is the commands I used for the tunneling:

    ============================
    Master Server main IP: 43.52.151.156 nic eth0
    Slave Server:107.14.42.87/27, Usable IPs: 87-115, main IP: 107.14.42.87 nic eth0

    Note: All actual IPs are changed.
    --------------------------------------------------
    On Slave Server:

    Code:
    chkconfig iptables off
    service iptables stop
    
    sysctl -w net.ipv4.ip_forward=1
    sysctl -w net.ipv4.conf.all.forwarding=1
    sysctl -w net.ipv4.conf.proxy_arp=1
    sysctl -w net.ipv4.conf.all.proxy_arp=1
    sysctl -w net.ipv4.conf.eth0.rp_filter=0
    sysctl -w net.ipv4.conf.default.rp_filter=0
    
    modprobe ip_gre
    ip tunnel add tunx mode gre remote 43.52.151.156  local 107.14.42.87 ttl 255
    ip addr add 10.0.250.2/30 dev tunx
    ip link set tunx up
    ip route add 107.14.42.87/27 via 10.0.250.2
    ip route add 107.14.42.87/27 dev tunx
    ---------------------------------------------------------------
    On Master Server:

    Code:
    chkconfig iptables off
    service iptables stop
    sysctl -w net.ipv4.conf.default.rp_filter=0
    
    modprobe ip_gre
    ip tunnel add tun1 mode gre remote 107.14.42.87 local 43.52.151.156 ttl 255
    ip addr add 10.0.250.1/30 dev tun1
    ip link set dev tun1 up
    ip addr add 107.14.42.87/27 dev eth0
    ip addr add 107.14.42.88/27 dev eth0
    ip addr add 107.14.42.90/27 dev eth0
    =========================================

    After doing the above steps, I tried below test on master server to test slave server IPs. My test shows below result:

    Test 1: nc -s 107.14.42.87 mx1.biz.mail.yahoo.com 25

    Result: No response (no error either)

    Test 2: curl --verbose --interface 107.14.42.87 http://www.google.com

    Result:
    * About to connect() to www.google.com port 80 (#0)
    * Trying 2a00:1450:400f:804::2004... getaddrinfo(3) failed for 107.14.42.87:0
    * Couldn't bind to '107.14.42.87'
    * Trying 216.58.209.132... Name '107.14.42.87' family 2 resolved to '107.14.42.87' family 2
    * Local port: 0
    * About to connect() to www.google.com port 80 (#0)
    * Trying 2a00:1450:400f:804::2004... getaddrinfo(3) failed for 107.14.42.87:0
    * Couldn't bind to '107.14.42.87'
    * Trying 216.58.209.132... Name '107.14.42.87' family 2 resolved to '107.14.42.87' family 2
    * Local port: 0

    ---------------------------
    Plz help me to make this working.

    Thanks
     
  4. nickphx

    nickphx VIP

    Joined:
    Apr 2, 2011
    Messages:
    1,139
    Likes Received:
    363
    Trophy Points:
    83
    Gender:
    Male
    Location:
    guadalajara, chiuhuahua
    You can't bind the main IP of the source server to the target server....
     
  5. SuperGenii

    SuperGenii www.DataMCP.com

    Joined:
    Apr 9, 2011
    Messages:
    135
    Likes Received:
    16
    Trophy Points:
    63
    Location:
    Southern California
    First, I like to add a device to the initial tunnel command:

    ip tunnel add tunx mode gre remote 43.52.151.156 local 107.14.42.87 ttl 255 dev eth0

    Next, I like the next line to look peer to peer format (reversed on other server):

    ip addr add dev tunx 10.0.250.2 peer 10.0.250.1/32;

    Also, when you route the IPs, you should use the remote peer address, not the local one:

    ip route add 107.14.42.88 via 10.0.250.1

    ip route add 107.14.42.87/27 dev tunx <- delete this line

    You may need to disable selinux. To test, you should be able to ping through the tunnel to confirm the tunnel is up. But you need to use an external third party to ping the IP to confirm it is public. Traceroute tool helps trouble shoot routing issues too. And in the future, don't post your real IPs, for your own protection..

    SG
     
  6. SuperGenii

    SuperGenii www.DataMCP.com

    Joined:
    Apr 9, 2011
    Messages:
    135
    Likes Received:
    16
    Trophy Points:
    63
    Location:
    Southern California
    Yeah that too ^
     
  7. Kumar

    Kumar New Member

    Joined:
    Sep 7, 2015
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    1
    Thanks, I am trying it out and will update it here shortly :)
     

Share This Page