[clug] ssl and https

[dylan porter]

On 02/26/2011 06:13 PM, Peter Barker wrote:
> On Sat, 26 Feb 2011, dylan porter wrote:
>
>>>> packets Tracing the path to live.com (65.55.206.154) on TCP port 22
>>>> (ssh),
>>>> 30 hops max
>>> I think I understand part of the problem.
>>> So running tcptraceroute to port 22 isn't the same as running to
>>> port 443
>>> (which is the usual SSL/TLS port).
>>> Brad
>> yeah i kind of saw that just now so i guess its a problem with ssh
>> not ssl
>
> Hmm,.
>
> Your problem as originally stated was:
>> My problem is that i cannot connect to some websites that have ssl and
>> https, like facebook and sourceforge and it wont connect to instant
>> messengers.
>
>
> Which means you have a problem with ssl, not ssh.  Port 22 is
> typically used by programs communicating using the "ssh" protocol. 
> That's useful for using machines remotely - usually for an interactive
> shell, sometimes for other things.  ssl is the "secure sockets
> layer".  This protocol is sometimes used by internet servers and
> clients to communicate - all sorts of *other* protocols are spoken on
> top of ssl-secured connections.  The *most* used [citation needed] is
> "secure http", "https" - and is almost always [no citation needed]
> spoken on port 443 (from the server's persepective).
>
> So.  Since you are having problems with *some* websites - we should
> get the diagnostics for those websites.
>
> My firewalls on this machine prevent me from presenting tcptraceroutes
> at the moment.  Could you present the results of "tcptraceroute
> www.facebook.com 443", and "tcptraceroute google.com 443", please?
>
>> dylan porter
>
> Yours,
dylan at dylan-netbook ~ $ sudo tcptraceroute www.facebook.com 443
Password:
Selected device wlan0, address 192.168.0.10, port 40028 for outgoing packets
Tracing the path to www.facebook.com (66.220.149.25) on TCP port 443
(https), 30 hops max
 1  192.168.0.1  7.126 ms  5.207 ms  0.957 ms
 2  * * *
 3  core-32-25.grapevine.net.au (203.129.32.25)  10.445 ms  10.886 ms 
14.695 ms
 4  gigabitethernet1-4.core01.eqnx.transact.net.au (202.55.149.209) 
24.137 ms  10.789 ms  19.999 ms
 5  gigabitethernet14-17.core01.gate.transact.net.au (202.55.144.193) 
15.678 ms  12.916 ms  13.067 ms
 6  10gigabitethernet4-1.core01.eqnx.transact.net.au (202.55.144.198) 
19.766 ms  16.523 ms  12.557 ms
 7  ten-0-2-0-639.bdr01.syd03.nsw.VOCUS.net.au (114.31.200.201)  19.778
ms  16.576 ms  20.677 ms
 8  ge-0-1-2.cor01.syd03.nsw.VOCUS.net.au (114.31.192.58)  176.266 ms 
182.082 ms  175.029 ms
 9  ge-0-1-3-126.bdr01.sjc01.ca.VOCUS.net.au (114.31.192.101)  171.464
ms  172.114 ms  171.934 ms
10  ten-1-1-0.bdr02.sjc01.ca.VOCUS.net.au (114.31.199.117)  173.423 ms 
172.608 ms  172.057 ms
11  facebook.com.any2ix.coresite.com (206.223.143.161)  179.063 ms 
180.485 ms  198.232 ms
12  xe-1-1-0.bb02.sjc1.tfbnw.net (204.15.21.162)  204.439 ms  179.855
ms  181.378 ms
13  * ae2.dr01.snc5.tfbnw.net (74.119.77.184) 257.223 ms  298.033 ms
14  po510.csw02a.snc5.tfbnw.net (74.119.78.22)  183.895 ms  206.505 ms 
176.563 ms
15  www-12-02-snc5.facebook.com (66.220.149.25) [open]  201.217 ms 
184.269 ms  199.256 ms
dylan at dylan-netbook ~ $ sudo tcptraceroute www.google.com 443
Selected device wlan0, address 192.168.0.10, port 46503 for outgoing packets
Tracing the path to www.google.com (74.125.237.18) on TCP port 443
(https), 30 hops max
 1  192.168.0.1  1.550 ms  4.513 ms  0.983 ms
 2  * * *
 3  core-32-25.grapevine.net.au (203.129.32.25)  10.521 ms  17.614 ms 
8.323 ms
 4  gigabitethernet1-4.core01.eqnx.transact.net.au (202.55.149.209) 
16.475 ms  20.671 ms  10.124 ms
 5  gigabitethernet14-17.core01.gate.transact.net.au (202.55.144.193) 
9.618 ms  38.359 ms  11.697 ms
 6  10gigabitethernet4-1.core01.eqnx.transact.net.au (202.55.144.198) 
39.183 ms  14.193 ms  12.436 ms
 7  202.167.228.73  14.530 ms  17.368 ms  52.129 ms
 8  66.249.95.232  14.881 ms  13.818 ms  15.100 ms
 9  * * *
10  74.125.237.18 [open]  180.866 ms  33.496 ms  19.894 ms

thats the 2 you wanted

-- 
dylan porter