[Techtalk] LinkedIn Ubuntu connection weirdness

Mon Mar 29 01:43:49 UTC 2010

MLL:  I posed it as a question on LinkedIn.  This is what I got:

On 03/14/10 9:06 PM, Bernard Gore wrote:
--------------------
There is a long standing problem with some wireless routers that exactly
meets your description. LinkedIn have known about it for 2 years that I know
of, but keep denying it's a problem with their site - even though as you say
it doesn't affect any other site that I've been able to find.

There is no fix, other than changing the router (which isn't an option
unless you are a very good customer of that coffee shop!).

--------------------
--------------------

MLL: I also noticed that Windows and Linux seem to think that LinkedIn have
different IP addresses, but from home each of these work fine for me
(64.74.98.80 & 64.74.98.86).

Windows Traceroute from Laughing Ladies to LinkedIn  (MLL: connection
successful)
Tracing route to www.linkedin.com [64.74.98.80]
over a maximum of 30 hops:

  1     4 ms     3 ms     2 ms  192.168.1.1
  2     3 ms     1 ms     2 ms  67-134-197-169.dia.static.qwest.net
[67.134.197.169]
  3     7 ms     7 ms     8 ms  363.s10-1-0.sttl-cust.sttl.uswest.net
[206.81.193.125]
  4    10 ms     7 ms     7 ms  tuk-core-01.inet.qwest.net [205.171.11.37]
  5     8 ms     7 ms     7 ms  sea-core-01.inet.qwest.net [67.14.1.194]
  6     7 ms     8 ms     7 ms  sea-brdr-01.inet.qwest.net [205.171.26.54]
  7     8 ms     7 ms     7 ms  POS2-3.BR1.SEA1.ALTER.NET [204.255.169.29]
  8     8 ms     9 ms     7 ms  0.so-4-2-0.XT1.SEA1.ALTER.NET
[152.63.105.82]
  9   104 ms    65 ms    65 ms  0.ge-5-2-0.XL3.CHI13.ALTER.NET
[152.63.64.217]
 10    66 ms    66 ms    66 ms  TenGigE0-6-2-0.GW2.CHI13.ALTER.NET
[152.63.65.137]
 11    67 ms    65 ms    65 ms  internap-gw.customer.alter.net
[63.84.96.162]
 12    67 ms    66 ms    67 ms  border2.te7-1-bbnet1.chg004.pnap.net
[64.94.32.19]
 13    67 ms    66 ms    66 ms  64.94.34.154
 14    68 ms    67 ms     *     www.linkedin.com [64.74.98.80]
 15    70 ms    67 ms    67 ms  www.linkedin.com [64.74.98.80]

Trace complete.

Linux Traceroute from Laughing Ladies to LinkedIn (MLL: connection
unsuccessful) 
traceroute to linkedin.com (64.74.98.86), 30 hops max, 40 byte packets
 1  192.168.1.1 (192.168.1.1)  11.774 ms  13.473 ms  16.999 ms
 2  67-134-197-169.dia.static.qwest.net (67.134.197.169)  22.873 ms  23.756
ms  24.715 ms
 3  tuk-edge-04.inet.qwest.net (206.81.193.125)  24.988 ms  25.183 ms
25.803 ms
 4  tuk-core-02.inet.qwest.net (205.171.11.41)  27.199 ms  27.375 ms  27.669
ms
 5  sea-core-01.inet.qwest.net (67.14.1.194)  27.851 ms  28.729 ms  29.375
ms
 6  sea-brdr-01.inet.qwest.net (205.171.26.54)  30.199 ms  15.675 ms  22.636
ms
 7  POS2-3.BR1.SEA1.ALTER.NET (204.255.169.29)  23.263 ms  26.276 ms  26.423
ms
 8  0.so-7-3-0.XT2.SEA1.ALTER.NET (152.63.105.22)  26.550 ms  26.704 ms
26.975 ms
 9  0.so-7-1-0.XL4.CHI13.ALTER.NET (152.63.64.14)  80.858 ms  80.992 ms
81.829 ms
10  TenGigE0-7-2-0.GW2.CHI13.ALTER.NET (152.63.65.149)  84.717 ms
TenGigE0-7-0-0.GW2.CHI13.ALTER.NET (152.63.65.13)  84.947 ms  85.181 ms
11  internap-gw.customer.alter.net (63.84.96.162)  85.414 ms  85.547 ms
85.553 ms
12  border2.te8-1-bbnet2.chg004.pnap.net (64.94.32.83)  75.915 ms  74.017 ms
71.835 ms
13  64.94.34.154 (64.94.34.154)  72.782 ms  74.127 ms  74.326 ms
14  * * *
15  * * *
  -  deleted for brevity - all ***
30  * * * 

MLL:  My successful connection from home - same laptop (where I start with
my own router and then go to Verizon)

traceroute to linkedin.com (64.74.98.86), 30 hops max, 40 byte packets
 1  192.168.1.1 (192.168.1.1)  0.868 ms  1.246 ms  2.234 ms
....  stuff in here deleted for brevity ....
 7  tge2-2.fr3.sjc.llnw.net (69.28.171.145) 45.998 ms 48.080 ms 50.833 ms
 8  tge9-4.fr4.ord.llnw.net (69.28.172.78) 98.811 ms 101.568 ms 114.831 ms
 9  linkedin.tge3-2.fr4.ord.llnw.net (208.111.156.74) 109.410 ms 112.220 ms
114.831 ms
10  * * *
11  * * *
  -  deleted for brevity - all ***
30  * * * 

MLL:  Eventhough I reach LinkedIn fine from home, I'm puzzled that the last
entry in Traceroute doesn't match the destination (64.74.98.86).

MLL:  when I put http://208.111.156.74 into my browser, it times out.
      when I put http://64.74.98.86  or http://64.74.98.80 into my browser
from home, I get connected to LinkedIn.

 Wim De Smet wrote:
> This is still bothering me cause I can't figure it out. Perhaps it is
> a DNS problem after all? Perhaps try using google's DNS servers while
> there (8.8.8.8 and 8.8.4.4), see what happens.

MLL: I'll try that later this week.  Thanks.

Meryll