{"id":272,"date":"2006-08-15T19:42:19","date_gmt":"2006-08-15T08:42:19","guid":{"rendered":"http:\/\/www.somethinkodd.com\/oddthinking\/2006\/08\/15\/bloglines-networking-issue\/"},"modified":"2007-03-17T15:32:59","modified_gmt":"2007-03-17T04:32:59","slug":"bloglines-networking-issue","status":"publish","type":"post","link":"https:\/\/www.somethinkodd.com\/oddthinking\/2006\/08\/15\/bloglines-networking-issue\/","title":{"rendered":"Bloglines Networking Issue"},"content":{"rendered":"
STOP PRESS:<\/strong> See the comments near the end that suggest that perhaps this isn’t really a Bloglines issue.<\/div>\n

I am encountering a weird networking problem with Bloglines.<\/p>\n

The Bloglines web-site appears to be up, but it doesn’t seem to want to talk to me. Did I say something too nasty last time I was freedbacking<\/a>?<\/p>\n

The web-site is working fine (including responding to web-requests and to pings) when I contact it from:<\/p>\n

    \n
  1. another machine on another ISP,<\/li>\n
  2. via an anonymous proxy on my machine,<\/li>\n
  3. on my machine, as long as I VPN into another network.<\/li>\n<\/ol>\n

    However, when I contact it directly, my packets disappear somewhere on the other side of the Earth.<\/p>\n

    Here’s an example:<\/p>\n

    Ping result from Nwtools.com<\/a>:<\/h4>\n

    Ping 65.214.39.152
    \n[bloglines.com]<\/p>\n

    Round trip time to 65.214.39.152: 57 ms
    \nRound trip time to 65.214.39.152: 56 ms
    \nRound trip time to 65.214.39.152: 57 ms
    \nRound trip time to 65.214.39.152: 55 ms
    \nRound trip time to 65.214.39.152: 56 ms
    \nRound trip time to 65.214.39.152: 57 ms
    \nRound trip time to 65.214.39.152: 56 ms
    \nRound trip time to 65.214.39.152: 57 ms
    \nRound trip time to 65.214.39.152: 57 ms
    \nRound trip time to 65.214.39.152: 55 ms<\/p>\n

    Average time over 10 pings: 56.3 ms
    \n<\/code><\/p><\/blockquote>\n

    Ping result from my machine:<\/h4>\n

    >ping bloglines.com<\/p>\n

    Pinging bloglines.com [65.214.39.152] with 32 bytes of data:<\/p>\n

    Request timed out.
    \nRequest timed out.
    \nRequest timed out.
    \nRequest timed out.<\/p>\n

    Ping statistics for 65.214.39.152:
    \n Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
    \n<\/code><\/p><\/blockquote>\n

    Now check this out:<\/p>\n

    Traceroute result from Nwtools.com<\/a>:<\/h4>\n

    TraceRoute to 65.214.39.152 [bloglines.com]<\/p>\n

    Hop (ms) (ms) (ms) IP Address Host name
    \n1 0 0 0 66.98.244.1 gphou-66-98-244-1.ev1.net
    \n2 0 0 0 66.98.241.16 gphou-66-98-241-16.ev1.net
    \n3 0 0 0 66.98.240.5 gphou-66-98-240-5.ev1.net
    \n4 1 3 1 129.250.10.189 ge-2-0-0.r02.hstntx01.us.bb.gin.ntt.net
    \n5 24 10 9 129.250.5.30 as-0.r20.dllstx09.us.bb.gin.ntt.net
    \n6 10 9 9 129.250.3.21 p16-0-0-0.r00.dllstx09.us.bb.gin.ntt.net
    \n7 11 10 61 204.255.174.229 0.so-0-1-0.br6.dfw9.alter.net
    \n8 12 10 11 152.63.103.77 0.so-3-3-0.xt2.dfw9.alter.net
    \n9 54 54 55 152.63.21.73 0.so-6-1-0.xl2.bos4.alter.net
    \n10 54 55 55 152.63.16.134 0.so-7-0-0.xr2.bos4.alter.net
    \n11 69 55 57 152.63.29.221 0.so-7-0-0.wr2.bos6.alter.net
    \n12 55 57 57 63.111.123.34 so-1-0-0.ur2.bos6.web.wcom.net
    \n13 57 56 56 208.254.32.53 -
    \n14 57 56 57 65.214.32.81 -
    \n15 57 56 57 65.214.39.152 web.bloglines.com <\/p>\n

    Trace complete
    \n<\/code><\/p><\/blockquote>\n

    Expurgated Traceroute result from my machine:<\/h4>\n

    >tracert bloglines.com<\/p>\n

    Tracing route to bloglines.com [65.214.39.152]
    \nover a maximum of 30 hops:<\/p>\n

    1 <1 ms <1 ms <1 ms You don't<\/b>
    \n 2 14 ms 13 ms 12 ms need to<\/b>
    \n 3 11 ms 13 ms 12 ms know this part<\/b>
    \n 4 175 ms 172 ms 173 ms gi0-0.bdr1.syd6.agile.on.net [150.101.199.232]
    \n 5 174 ms 171 ms 173 ms pos2-0.bdr1.lax1.agile.on.net [203.16.213.177]
    \n 6 172 ms 172 ms 171 ms GigabitEthernet3-2.GW1.LAX15.ALTER.NET [208.222.8.93]
    \n 7 173 ms 172 ms 173 ms 0.so-2-0-0.CL1.LAX15.ALTER.NET [152.63.115.210]
    \n 8 253 ms 253 ms 251 ms 0.so-6-0-0.XL1.BOS4.ALTER.NET [152.63.16.129]
    \n 9 265 ms 252 ms 250 ms 0.so-7-0-0.XR1.BOS4.ALTER.NET [152.63.16.122]
    \n 10 253 ms 253 ms 254 ms 0.so-7-0-0.WR1.BOS6.ALTER.NET [152.63.29.217]
    \n 11 255 ms 253 ms 255 ms so-1-0-0.ur1.bos6.web.wcom.net [63.111.123.30]
    \n 12 255 ms 253 ms 255 ms 208.254.32.37
    \n 13 252 ms 252 ms 252 ms 65.214.32.81
    \n 14 * * * Request timed out.
    \n 15 * * * Request timed out.
    \n 16 * * * Request timed out.
    \n 17 * * * Request timed out.
    \n 18 * * * Request timed out.
    \n 19 * * * Request timed out.
    \n 20 * * * Request timed out.
    \n 21 * * * Request timed out.
    \n 22 * * * Request timed out.
    \n 23 * * * Request timed out.
    \n 24 * * * Request timed out.
    \n 25 * * * Request timed out.
    \n 26 * * * Request timed out.
    \n 27 * * * Request timed out.
    \n 28 * * * Request timed out.
    \n 29 * * * Request timed out.
    \n 30 * * * Request timed out.<\/p>\n

    Trace complete.
    \n<\/code><\/p><\/blockquote>\n

    It looks like on the last hop in the Bloglines network it either it is blocking stuff from my IP address, or I am blocking stuff from its IP address. <\/p>\n

    I have checked my router configuration, and I can’t see any thing firewally that might be getting in the way. I haven’t installed anything special recently (except Windows patches).<\/p>\n

    I’m sorry, Bloglines, but I have just started a FeedDemon trial because blog-reading is now a mission-critical application for this machine. I haven’t reported this directly to you, because I have no connectivity to you – it’s all too hard.<\/p>\n

    Can anyone get me back onto the straight and narrow before I fork out $US30?<\/p>\n

    Coda<\/h3>\n

    Update 1: When I swap my newish Billion ADSL Router out and put my old D-Link ADSL modem in its place, Bloglines works fine. Swap back and it is broken again. Unfortunately, I just promised earlier this week to give away my unneeded D-Link modem to a friend!<\/p>\n

    Update 2: I have made my home machine a DMZ Host within the Billion router, as suggested by Alastair in a private communication. That has fixed the problem (at the cost of making my Windows machine less stealthy) but I still don’t really know why, nor what Bloglines is doing that is different to other sites. Thanks, Alastair.<\/p>\n","protected":false},"excerpt":{"rendered":"

    I am encountering a weird networking problem.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_s2mail":"","footnotes":""},"categories":[23,28],"tags":[],"class_list":["post-272","post","type-post","status-publish","format-standard","hentry","category-based-on-a-true-story","category-doubleplus-geek"],"_links":{"self":[{"href":"https:\/\/www.somethinkodd.com\/oddthinking\/wp-json\/wp\/v2\/posts\/272","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.somethinkodd.com\/oddthinking\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.somethinkodd.com\/oddthinking\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.somethinkodd.com\/oddthinking\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.somethinkodd.com\/oddthinking\/wp-json\/wp\/v2\/comments?post=272"}],"version-history":[{"count":0,"href":"https:\/\/www.somethinkodd.com\/oddthinking\/wp-json\/wp\/v2\/posts\/272\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.somethinkodd.com\/oddthinking\/wp-json\/wp\/v2\/media?parent=272"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.somethinkodd.com\/oddthinking\/wp-json\/wp\/v2\/categories?post=272"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.somethinkodd.com\/oddthinking\/wp-json\/wp\/v2\/tags?post=272"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}