To rephrase your question, based on one of your later comments, you want to
access [website] from a server that hasn't access to that URL using a personal computer with no open ports as tunnel - Helio
At first glance, what you are asking for seems impossible. Upon closer inspection, what you need is some highly advanced networking voodoo. Specifically:
- A VPN server running on your personal computer (let's call it herpyderp)
- An SSH server running on the remote server (call it.... megatron. why not?)
- A VPN client on megatron.
Set up the VPN server
The process of setting up a VPN server is... quite complex, and well beyond the scope of this answer. I'll put some resource links at the end for you.
Anyway, set it up to listen on 127.0.0.1
, and disable pushing a default route. (You also may need to set it to use tcp; I'm not sure how udp will react in this... odd situation.)
Forward the port over SSH
For the sake of simplicity, I'm going to assume you have an OpenVPN server on herpyderp properly set up and listening on 127.0.0.1:1194
. Connect to megatron and forward the appropriate port back to herpyderp (on localhost
):
ssh -R 8088:localhost:1194 awesomeuser@megatron
Connect VPN
Again, for simplicity, I will assume you have a config file for the OpenVPN client on megatron
. Ensure that it is configured to not set a default route, and to connect to the server at address 127.0.0.1:8088
.
Note that if megatron
has something already listening on 8088, you will need to use a different port number.
Add routes
Finally, you will need to route requests to the blocked IP through the VPN with the ip route add
command. Use ifconfig
to get the ip address of the VPN adapter and its destination address. Use ping
or nslookup
to obtain the ip address of the site in question. Then, armed with this information, add the route:
ip route add <SITE_IP_ADDR> via <VPN_DEST_ADDR> dev <VPN_ADAPTER>
If everything goes just right, you should be able to access the blocked IP from megatron
via herpyderp
's internet connection.
But...
That being said, I'm fairly sure that any network admin that's made it this far into the answer is either weeping or in shock by now. There is nothing... right... with this setup. I feel as if I've committed a sin for even suggesting it.
Also, I wouldn't expect any significant throughput. And just... astronomical latency.
Final disclaimer: I have no idea whether this will actually work. It should, but due to the sheer amount of work involved with this setup, I haven't actually tested it. There are about a million things that could go wrong. Good luck, and godspeed.
Resources
EDIT: A word of caution
This absolutely has the potential to make your server completely unreachable over the network. The ip
commands especially; the wrong route can block all network activity.