Sunday, November 28, 2010

Thanks Given

"for Grace of God through my bride, and for this body, and the way you've shown love to us. And for Larry Trotter " [pastor]

"for Christ, who has allowed me to do my thing -- but this year for the last three weeks, has been roundhouse kicking me. Sometimes like Jonah you get tired of running. For a wife, and beautiful kids. For a church family loving on me. For a pastor teaching God's words."

"for this Service"

"for a church praying, and for pregnancy support services, and a daughter in church this morning"

"for God showing me that I need to follow Him, even if there aren't big miracles and mountains falling. And for softening my heart."

"for Jesus dying on the cross for our sins"

"for a roof over my head and clothes to keep me warm"

"after a rough year, with my husband having two heart attacks in eight days, for a church being there for us and praying for us."

"for the Lord directing my steps through all of you, the body of Christ"

"for God, though He doesn't do things the way you think He's going to do things, he's always faithful. For my daughter and grandson all here and doing well. For your prayers."

"for my family, especially my Dad."

"for a home to live in."

"for a pastor, who was once my student requiring much supervision."

Thanks given in the 10:45 am meeting at North Wake Church, Wake Forest, NC.

Tuesday, November 23, 2010

How do they deliver files so fast?

TomTom emailed me this morning to say a new map was available for my GPS Receiver. Since we're just about to go on a trip, I jumped at the chance for a shiny new map. I use a TomTom Go 720.

1. The download rate was impressive. My TimeWarner Business Class service in the Raleigh NC area provides 8 Mbps download capacity. At 8:22 am, this transfer was running at 8 Mbps. That suggests the bottleneck was really my access link.

2. The time-to-live on received packets was 57. That's a fairly close server, at only 8 hops away.


# 2010-11-23 08:25:50 mark@nabla ~$ ping -m 7 209.18.41.26
PING 209.18.41.26 (209.18.41.26): 56 data bytes
36 bytes from ae-1-0.pr0.dca20.tbone.rr.com (66.109.6.183): Time to live exceeded
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 40 5400 8fbd 0 0000 01 01 0464 172.24.127.3 209.18.41.26

Request timeout for icmp_seq 0
36 bytes from ae-1-0.pr0.dca20.tbone.rr.com (66.109.6.183): Time to live exceeded
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 40 5400 afa8 0 0000 01 01 e478 172.24.127.3 209.18.41.26

^C
--- 209.18.41.26 ping statistics ---
2 packets transmitted, 0 packets received, 100.0% packet loss

# 2010-11-23 08:25:55 mark@nabla ~$ ping -m 8 209.18.41.26
PING 209.18.41.26 (209.18.41.26): 56 data bytes
64 bytes from 209.18.41.26: icmp_seq=0 ttl=57 time=271.677 ms
64 bytes from 209.18.41.26: icmp_seq=1 ttl=57 time=281.295 ms
^C
--- 209.18.41.26 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 271.677/276.486/281.295/4.809 ms


3. TimeWarner / RoadRunner does such a nice job naming their point-to-point router IPs, we can guess about the network technology used.


traceroute to 209.18.41.26 (209.18.41.26), 64 hops max, 52 byte packets
1 172.24.127.1 (172.24.127.1) 0.813 ms 0.595 ms 0.586 ms
2 10.123.128.1 (10.123.128.1) 231.388 ms 268.237 ms 268.356 ms
3 gig9-1-4.rlghncg-rtr1.nc.rr.com (24.25.1.73) 260.497 ms 279.656 ms 253.422 ms
4 pos1-0.rlghnca-rtr1.nc.rr.com (24.25.20.17) 254.433 ms 258.332 ms 264.331 ms
5 ge-6-0-0.rlghncpop-rtr1.southeast.rr.com (24.93.64.66) 257.150 ms 274.931 ms 265.894 ms
6 ae-3-0.cr0.dca10.tbone.rr.com (66.109.6.80) 259.336 ms 317.687 ms 286.754 ms
7 ae-1-0.pr0.dca20.tbone.rr.com (66.109.6.183) 290.598 ms 274.169 ms 280.447 ms
8 209-18-42-26.dca20.tbone.rr.com (209.18.41.26) 287.974 ms 254.063 ms 230.003 ms


They use the term "ae", which is a Juniper term for "Aggregate Ethernet". So I'd guess TimeWarner is using Juniper routers, at least in the "dca" area. (Washington DC?)

The third-hop interface is GigabitEhternet 9/1/4 on Raleigh NC "G" Router 1.

The fourth-hop interface is Packet-over-Sonet 1/0 on Raleigh NC "A" Router 4.

The fifth-hop interface is Gigabit Ethernet 6/0/0 on Raleigh NC "POP" router 1.

The sixth-hop interface is AggregateEthernet 3/0 on "cr0" in "dca10". I'm guessing that's "core router 0" in Washington DC area 10, but I really don't know. The router naming scheme changed when we left the Raleigh NC area.

The seventh-hop interface is Aggregate Ethernet 1/0 on "pr0" in "dca20". That sounds like a peering router, and it'd make sense, since that's the router that is apparently connected to the file server.

4. The bulk of the data came from came from 209.18.41.26, aka "209-18-42-26.dca20.tbone.rr.com.".

According to ARIN, somebody named that network "COUDERSPORTBB-1". Coudersport PA was the location of Telcove and Adelphia Communications, and currently an Operations Center for Level(3).

5. The Ethernet frames, as they arrive, are 1514 bytes. They have 1488 bytes of TCP payload in each packet. That's making full use of 1514 byte frames, and it's as efficient as they could be without special tricks.

6. The IP datagrams sent have the "Don't Fragment" bit set. That suggests they used Path MTU discovery to optimize the right packet size.


What's the point? The file server sending me this file is directly connected to the RoadRunner / TimeWarner network. And it's likely that at this hour, the TimeWarner network is not saturated.

Thursday, November 18, 2010

How to pair a Apple Wireless (Aluminum) Keyboard

I have an Apple Wireless Keyboard that I switch between computers occasionally. Today trouble struck: it wouldn't pair with one of the computers, even after I deleted it on the previous computer it had been paired with.

I could find no documented method to have the Apple Wireless (Aluminum) Keyboard actually become discoverable and start searching for a mate. My online compatriots seemed to have one idea: remove the batteries, and put them back in. Once that fails, they're out of ideas.

But this procedure seemed to work immediately:

1. Remove the screw-on cover.

2. Press and hold the power button.

3. Screw on the cover.

The keyboard was immediately discoverable, blinking furiously for a mate.

I have a hunch that this problem occurs when the losing device is one of certain bluetooth implementations, such as the one in a 2006-era 2.1 GHz MacBook Pro.