<div dir="ltr">What do you guys think about this issue? I want to say that it's pressing, but:<div><br></div><div>1. This is the only remaining problematic protocol for me. SSH works perfectly, and git works just as well over HTTP nowadays, if I'm not mistaken.</div>
<div>2. It seems unnecessary, in my opinion, for this protocol to exist - it should just be done over HTTP.</div><div><br></div><div>However, network neutrality is always important, and Bezeq International's claims of "we don't block any ports" become problematic (albeit technically true). Is there anything that can be done about this?<br>
<br><div class="gmail_quote">On Mon, Oct 18, 2010 at 1:38 AM, Kohn Emil Dan <span dir="ltr"><<a href="mailto:emild@cs.technion.ac.il">emild@cs.technion.ac.il</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<br>
I am also connected to Bezeq Beinleumi (actually 'upgraded' to it after Actcom's demise). I have tried your gpg command, and I found IMO some interesting results.<br>
<br>
Doing an nslookup on <a href="http://subkeys.pgp.net" target="_blank">subkeys.pgp.net</a> reveals that this host has a number of IP addresses:<br>
<br>
$ nslookup<br>
Note: nslookup is deprecated and may be removed from future releases.<br>
Consider using the `dig' or `host' programs instead. Run nslookup with<br>
the `-sil[ent]' option to prevent this message from appearing.<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<a href="http://subkeys.pgp.net" target="_blank">subkeys.pgp.net</a><br>
</blockquote>
Server: 10.71.0.138<br>
Address: 10.71.0.138#53<br>
<br>
Non-authoritative answer:<br>
Name: <a href="http://subkeys.pgp.net" target="_blank">subkeys.pgp.net</a><br>
Address: 114.31.78.196<br>
Name: <a href="http://subkeys.pgp.net" target="_blank">subkeys.pgp.net</a><br>
Address: 208.72.157.55<br>
Name: <a href="http://subkeys.pgp.net" target="_blank">subkeys.pgp.net</a><br>
Address: 195.113.19.83<br>
Name: <a href="http://subkeys.pgp.net" target="_blank">subkeys.pgp.net</a><br>
Address: 213.239.206.174<br>
Name: <a href="http://subkeys.pgp.net" target="_blank">subkeys.pgp.net</a><br>
Address: 213.239.212.133<br>
Name: <a href="http://subkeys.pgp.net" target="_blank">subkeys.pgp.net</a><br>
Address: 64.71.173.107<br>
<br>
<br>
I tried your gpg command using the host name <a href="http://subkeys.pgp.net" target="_blank">subkeys.pgp.net</a> and then with each IP address instead of the host name.<br>
<br>
Using the host name <a href="http://subkeys.pgp.net" target="_blank">subkeys.pgp.net</a> causes the command to hang (I guess because the command tries only the first IP address).<br>
The command succeeds if using the IP addresses 208.72.157.55 and 195.113.19.83 while it fails for the rest of the addresses. For the last IP address (i.e. 64.71.173.107) causes the command to fail with "No route to host", while with the rest of the "problematic" addresses it just hangs<br>
<br>
<br>
Regards,<br><font color="#888888">
Emil</font><div><div></div><div class="h5"><br>
On Sat, 16 Oct 2010, Ohad Lutzky wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello everyone,<br>
I have a Linksys DSL-2760u router/DSL modem, using a Wow (Bezeq) connection<br>
to the Bezeq International ISP. It seems that various outgoing ports are<br>
blocked - HTTP, HTTPS, bittorrent and SSH work well enough, but - for<br>
example - I can't download Android apps from the Market. Easier to test, I<br>
can't download PGP public keys. For example:<br>
<br>
gpg -v -v --keyserver <a href="http://subkeys.pgp.net" target="_blank">subkeys.pgp.net</a> --recv F120156012B83718<br>
gpg: requesting key 12B83718 from hkp server <a href="http://subkeys.pgp.net" target="_blank">subkeys.pgp.net</a><br>
<br>
This hangs indefinitely. So does this:<br>
telnet <a href="http://subkeys.pgp.net" target="_blank">subkeys.pgp.net</a> 11371<br>
Trying 195.113.19.83...<br>
<br>
The same occurs for other keyservers, git-protocol, and various other<br>
"unconventional" high-port usage. I've gone over the router settings,<br>
disabled its firewall (but not NAT, which I need), added my machine to the<br>
DMZ (this actually seems to help, sometimes, for git - and even then, only<br>
once), tried port triggering... I can't get a consistent result.<br>
<br>
I should note that this issue only exists for *outgoing* ports. I have no<br>
problem mapping *incoming* ports (such as my openssh server or bittorrent<br>
web interface).<br>
<br>
--<br>
Man is the only animal that laughs and weeps, for he is the only animal that<br>
is struck with the difference between what things are and what they ought to<br>
be.<br>
- William Hazlitt<br>
<br>
Ohad Lutzky<br>
<br>
</blockquote>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Man is the only animal that laughs and weeps, for he is the only animal that is struck with the difference between what things are and what they ought to be.<br>
- William Hazlitt<br><br>Ohad Lutzky<br>
</div></div>