Just a quick note so I don’t forget all this stuff. I used DiGi OCS and D’Chat today to ask why I couldn’t access www.w3.org from my DiGi USB EDGE adapter. See the ping output below:<\/p>\n
root@box0045:\/home\/sean# ping www.w3.org
\nPING www.w3.org (128.30.52.166) 56(84) bytes of data.
\nFrom crusher.w3.org (128.30.52.166) icmp_seq=1 Dest Unreachable, Bad Code: 10
\nFrom crusher.w3.org (128.30.52.166) icmp_seq=2 Dest Unreachable, Bad Code: 10
\nFrom crusher.w3.org (128.30.52.166) icmp_seq=3 Dest Unreachable, Bad Code: 10
\nFrom crusher.w3.org (128.30.52.166) icmp_seq=4 Dest Unreachable, Bad Code: 10
\nFrom crusher.w3.org (128.30.52.166) icmp_seq=5 Dest Unreachable, Bad Code: 10
\n^C
\n— www.w3.org ping statistics —
\n5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 4021ms
\n, pipe 2<\/small><\/p>\n
Pinging some sites is as reliable as ever, but I also get problems when I ping wikipedia:<\/p>\n
root@box0045:\/home\/sean# ping en.wikipedia.org
\nPING rr.pmtpa.wikimedia.org (208.80.152.2) 56(84) bytes of data.
\n^C
\n— rr.pmtpa.wikimedia.org ping statistics —
\n9 packets transmitted, 0 received, 100% packet loss, time 8046ms<\/small><\/p>\n
And when I ping www.tm.com.my:<\/p>\n
root@box0045:\/home\/sean# ping www.tm.com.my
\nPING www.tm.com.my (202.71.108.103) 56(84) bytes of data.
\n64 bytes from 202.71.108.103: icmp_seq=1 ttl=115 time=884 ms
\n64 bytes from 202.71.108.103: icmp_seq=1 ttl=115 time=900 ms (DUP!)
\n64 bytes from 202.71.108.103: icmp_seq=2 ttl=115 time=662 ms
\n64 bytes from 202.71.108.103: icmp_seq=2 ttl=115 time=678 ms (DUP!)
\n64 bytes from 202.71.108.103: icmp_seq=3 ttl=115 time=214 ms
\n64 bytes from 202.71.108.103: icmp_seq=3 ttl=115 time=413 ms (DUP!)
\n64 bytes from 202.71.108.103: icmp_seq=4 ttl=115 time=370 ms
\n64 bytes from 202.71.108.103: icmp_seq=4 ttl=115 time=391 ms (DUP!)
\n^C
\n— www.tm.com.my ping statistics —
\n4 packets transmitted, 4 received, +4 duplicates, 0% packet loss, time 3010ms
\nrtt min\/avg\/max\/mdev = 214.117\/564.192\/900.255\/237.384 ms<\/small><\/p>\n
A ping to bbcnews.com (for example) is as good as ever. Ping is not a reliable friend on DiGi’s network – I think they must have many network features clamped down for security and reliability, so I’m not convinced these commands would work reliably any other time. What I would expect though, is to be able to browse a web page at one of these sites. I get No Route To Host for w3.org:<\/p>\n
root@box0045:\/home\/sean# curl -s -v www.w3.org
\n* About to connect() to www.w3.org port 80 (#0)
\n*\u00a0\u00a0 Trying 128.30.52.52… No route to host
\n*\u00a0\u00a0 Trying 128.30.52.51… No route to host
\n*\u00a0\u00a0 Trying 128.30.52.38… ^C<\/small><\/p>\n
And SocketTimeout for wikipedia:<\/p>\n
root@box0045:\/home\/sean# curl -s -v en.wikipedia.org
\n* About to connect() to en.wikipedia.org port 80 (#0)
\n*\u00a0\u00a0 Trying 208.80.152.2… Connection timed out
\n* couldn’t connect to host
\n* Closing connection #0<\/small><\/p>\n
And for www.daemon.be:<\/p>\n
root@box0045:\/home\/sean# curl -s -v www.daemon.be
\n* About to connect() to www.daemon.be port 80 (#0)
\n* Trying 78.47.186.210… Connection timed out
\n* couldn’t connect to host
\n* Closing connection #0<\/small><\/p>\n
I forget the exact wording, but the nice person at DiGi tells me they’ll get a ‘data specialist’ (I think) to call me today or tomorrow. It’s 10pm now, so I guess tomorrow…<\/p>\n
The funny thing is… when I called earlier, I could browse www.w3.org from my old Siemens MC60 using DiGi’s GPRS and a ‘digiwap’ APN, but it also failed from my wife’s posh smartphone using DiGi EDGE and ‘diginet’ APN. The DiGi D’Chat agent asked me what APN I was using for the USB adapter, and I couldn’t tell them! It’s not set anywhere in my pppd config files. I remember seeing how to discover it with an extended AT command, but it wasn’t until I got off the chat thing that I hunted it down:<\/p>\n
OK<\/p>\n So my USB adapter is using the diginet APN, because I send the dial string “atd*99***1#” – I think!<\/p>\n I just tried plugging that USB EDGE adapter into my laptop and could fetch the robots.txt for en.wikipedia.org and www.dameon.be, but still the same problem with www.w3.org! With the USB EDGE adapter back in the server it is usually attached to, I still get the problem with www.w3.org, but can fetch the robots.txt from en.wikipedia.org and from www.daemon.be …?<\/p>\n Time to stop fiddling with this, for all I know there’s a guy in a DiGi uniform up my local radio mast, tongue sticking out of the corner of his mouth, plugging and unplugging a cable.<\/p>\n Update 28th April 2009 – Paka (see comment) reminds me this problem still exists. Here are today’s output from various utilites:<\/span><\/p>\n First ifconfig ppp0, just to prove we’re on DiGi’s network:<\/strong><\/p>\n root@box0045:\/home\/sean# ifconfig ppp0 Lynx, a text-based browser (there’s no GUI on this machine):<\/strong><\/p>\n sean@box0045:~$ lynx http:\/\/www.w3.org<\/p>\n Looking up www.w3.org lynx: Can’t access startfile http:\/\/www.w3.org\/<\/p><\/blockquote>\n ping (I suspect DiGi have made some changes to ICMP on their network recently, ping usually says “100% packet loss”):<\/strong><\/p>\n sean@box0045:~$ ping www.w3.org and curl (“see URL”, a swiss-army knife of a utility, I use it usually to check headers from hosts):<\/strong><\/p>\n sean@box0045:~$ curl -s -v http:\/\/www.w3.org\/ But anything else seems to work just fine:<\/strong><\/p>\n sean@box0045:~$ curl –head www.digi.com.my Time for D’Chat!<\/p>\n","protected":false},"excerpt":{"rendered":" Just a quick note so I don’t forget all this stuff. I used DiGi OCS and D’Chat today to ask why I couldn’t access www.w3.org from my DiGi USB EDGE adapter. See the ping output below: root@box0045:\/home\/sean# ping www.w3.org PING www.w3.org (128.30.52.166) 56(84) bytes of data. From crusher.w3.org (128.30.52.166) icmp_seq=1 Dest Unreachable, Bad Code: 10 […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14],"tags":[107,42,19,34],"class_list":["post-297","post","type-post","status-publish","format-standard","hentry","category-broken","tag-broken","tag-digi","tag-malaysia","tag-network"],"_links":{"self":[{"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/posts\/297","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/comments?post=297"}],"version-history":[{"count":6,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/posts\/297\/revisions"}],"predecessor-version":[{"id":301,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/posts\/297\/revisions\/301"}],"wp:attachment":[{"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/media?parent=297"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/categories?post=297"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/tags?post=297"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}at+cgdcont?
\n+CGDCONT: 1,\"IP\",\"diginet\",\"0.0.0.0\",0,0
\n+CGDCONT: 3,\"IP\",\"\",\"0.0.0.0\",0,0<\/code><\/p>\n
\nppp0\u00a0\u00a0\u00a0\u00a0\u00a0 Link encap:Point-to-Point Protocol
\ninet addr:10.32.64.240\u00a0 P-t-P:192.200.1.21\u00a0 Mask:255.255.255.255
\nUP POINTOPOINT RUNNING NOARP MULTICAST\u00a0 MTU:1500\u00a0 Metric:1
\nRX packets:123 errors:0 dropped:0 overruns:0 frame:0
\nTX packets:153 errors:0 dropped:0 overruns:0 carrier:0
\ncollisions:0 txqueuelen:3
\nRX bytes:42772 (41.7 KiB)\u00a0 TX bytes:17530 (17.1 KiB)<\/p><\/blockquote>\n
\nMaking HTTP connection to www.w3.org
\nAlert!: Unable to connect to remote host.<\/p>\n
\nPING www.w3.org (128.30.52.53) 56(84) bytes of data.
\nFrom 210.48.192.158 icmp_seq=2 Packet filtered
\nFrom 210.48.192.158 icmp_seq=9 Packet filtered
\nFrom 210.48.192.158 icmp_seq=10 Packet filtered
\nFrom 210.48.192.158 icmp_seq=11 Packet filtered
\nFrom 210.48.192.158 icmp_seq=12 Packet filtered
\nFrom 210.48.192.158 icmp_seq=13 Packet filtered
\n^C
\n— www.w3.org ping statistics —
\n15 packets transmitted, 0 received, +6 errors, 100% packet loss, time 14023ms<\/p><\/blockquote>\n
\n* About to connect() to www.w3.org port 80 (#0)
\n*\u00a0\u00a0 Trying 128.30.52.54… No route to host
\n*\u00a0\u00a0 Trying 128.30.52.166… No route to host
\n*\u00a0\u00a0 Trying 128.30.52.168… No route to host
\n*\u00a0\u00a0 Trying 128.30.52.170… No route to host
\n*\u00a0\u00a0 Trying 128.30.52.38… No route to host
\n*\u00a0\u00a0 Trying 128.30.52.51… No route to host
\n*\u00a0\u00a0 Trying 128.30.52.52… No route to host
\n*\u00a0\u00a0 Trying 128.30.52.53… No route to host
\n* couldn’t connect to host
\n* Closing connection #0<\/p><\/blockquote>\n
\nHTTP\/1.1 200 OK
\nDate: Tue, 28 Apr 2009 08:44:43 GMT
\nServer: Apache-Coyote\/1.1
\nContent-Type: text\/html;charset=ISO-8859-1
\nSet-Cookie: JSESSIONID=C58F88B5A8B39C5C5CF05C9C39B25EBF; Path=\/
\nConnection: close<\/p><\/blockquote>\n