Page 2 of 2 FirstFirst 12
Results 11 to 12 of 12

Thread: iptables routing - host inaccessible publicly

  1. #11
    Join Date
    Jul 2008
    Beans
    51

    Re: iptables routing - host inaccessible publicly

    so im sorry to say but the problem isnt the vpn server configuration, nor iptables, nor my router... IT IS MY ******* ISP

    http://www.dslreports.com/faq/7288
    http://community.spiceworks.com/topi...-ports-blocked [best answer reply]

    immense frustration

    i can probably host it over Tor
    Last edited by NetSkay; January 6th, 2012 at 02:07 AM.

  2. #12
    Join Date
    Aug 2011
    Beans
    26

    Re: iptables routing - host inaccessible publicly

    forgive me here as I am very new to this.

    let's say that I am connecting a home server to an EC2 instance via OpenVPN. I want the EC2 elastic IP to resolve to the home server --effectively making my home server (blocked by ISP NAT) public. Doing this should be a matter of assigning public IP traffic to resolve to the private IP of my server registered on the OpenVPN, but I can't for the life of me figure this out. Where to start? Apache? iptables? something else entirely?

Page 2 of 2 FirstFirst 12

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •