|
@Home is blocking a port! I get the same
response from @home here. I'm thinking of the following solution:
I have a network at home (my ISP is @home, over the
coaxial TV-cable with a cable-modem), so do two of my friends. One is living
nearby (only 1 block away) the other lives at the other side of town. I
cannot reach (ping, ftp, ssh, whatever) my friend A nearby. The other, friend B,
however, I can reach and he can reach me and my friend A.
I could tell ipchains to route all network traffic
from my own network 192.168.0.0 destined to a subnet 192.168.1.0 (A) to leave my
network over the Inet-if to the B-network (192.168.2.0) with a tunnel over a
non-blocked port (?can I?). The gateway at network B then has to be tought that
all traffic coming over the tunnel from me has to be relayed through another
tunnel to A where it will be forwarded to that LAN.
Note: friend A and me use the same gateway, friend
B uses another gateway. The gateways of @Home in my region have been programmed
to NAT/relay all "sub-local" traffic to the Internet and vice-versa but to block
all traffic that wants to go through the gateway back into the same "sub-local"
network. Beside this problem, @Home told me that VPN is not supported, ie they
blocked some ports (?). We do have real Internet-IP's I think: ping me at the IP
you can find in this mail to make sure. (I would like to know if someone from
the US or Down-Under can actually ping me...)
I think my humble idea might work but it sure as
hell will be slooooowww. So: anyone knows a route2 solution or a faster
tunnel-solution? Maybe something like firewall-piercing (whatever that may be,
haven't read that HOWTO yet)?
greetz, Mythiq.
|