James MacLachlan

To change your Verizon FIOS PTR record do the following steps:

Send and email with the a record and the ip you wish to update requesting the PTR be changed to the following email address:

mmvbtsatverizondotcom

The email should look like the following 2 lines:

Please update the reverse DNS PTR record for the following:

pcmsite.net -> 71.179.174.40

Then call 888-427-1405 options 1,1,3.

Ask about changing your reverse DNS PTR record, tell them you sent an email to the above address.

Our FIOS has been great at the office until tonight. It appears that it isn’t directly related to our local connection, but rather their routers. Below is the traceroute between a few computers and our server.

This from Verizon’s DSL network:

ibook-g4:~ james$ traceroute pcmsite.net
traceroute to pcmsite.net (71.179.174.40), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 20.169 ms 2.725 ms 1.996 ms
2 10.4.31.1 (10.4.31.1) 10.855 ms 9.940 ms 23.280 ms
3 so-0-2-0-0.core-rtr2.balt2.verizon-gni.net (130.81.9.41) 10.599 ms 11.177 ms 11.117 ms
4 so-7-0-0-0.core-rtr1.balt2.verizon-gni.net (130.81.18.184) 11.455 ms 26.586 ms 14.164 ms
5 130.81.20.8 (130.81.20.8) 20.290 ms 29.312 ms 15.005 ms
6 so-7-0-0-0.bb-rtr2.res.verizon-gni.net (130.81.19.51) 12.942 ms 13.359 ms 48.985 ms
7 p14-3.lcr-03.bltmmd.verizon-gni.net (130.81.29.129) 57.082 ms * *
8 p14-0.lcr-04.bltmmd.verizon-gni.net (130.81.27.143) 54.705 ms * 67.077 ms
9 l1.vfttp-07.bltmmd.verizon-gni.net (130.81.242.211) 56.000 ms 66.653 ms 57.566 ms
10 * * static-71-179-174-40.bltmmd.fios.verizon.net (71.179.174.40) 59.737 ms !<10>
11 static-71-179-174-40.bltmmd.fios.verizon.net (71.179.174.40) 60.139 ms !<10> 77.297 ms !<10> 59.648 ms !<10>

This is from Comcast:

3 ge-1-21-ur01.whitemarsh.md.bad.comcast.net (68.87.130.129) 41.327 ms 42.431 ms 45.402 ms
4 te-8-2-ur02.whitemarsh.md.bad.comcast.net (68.87.129.170) 48.877 ms 50.730 ms 51.950 ms
5 te-9-3-ar01.whitemarsh.md.bad.comcast.net (68.87.129.165) 49.555 ms 51.408 ms 55.131 ms
6 po-90-ar02.whitemarsh.md.bad.comcast.net (68.86.252.218) 55.735 ms 24.925 ms 31.538 ms
7 68.86.85.9 (68.86.85.9) 36.636 ms 41.361 ms 41.826 ms
8 COMCAST-IP.edge1.NewYork2.Level3.net (4.78.169.50) 48.176 ms 51.903 ms 53.506 ms
9 xe-10-2-0.edge1.NewYork2.Level3.net (4.78.169.49) 46.989 ms 47.448 ms 54.047 ms
10 (204.255.173.53) 55.642 ms 56.244 ms mci-level3-ge.NewYork1.Level3.net (4.68.110.234) 35.489 ms
11 0.ge-5-0-0.XL4.NYC4.ALTER.NET (152.63.3.117) 29.646 ms 36.547 ms 32.439 ms
12 0.so-6-0-0.XL4.IAD8.ALTER.NET (152.63.0.130) 33.564 ms 0.so-4-0-3.XT1.DCA6.ALTER.NET (152.63.1.117) 33.180 ms 0.so-6-0-0.XL4.IAD8.ALTER.NET (152.63.0.130) 33.314 ms
13 0.so-4-0-0.RES-BB-RTR1.verizon-gni.net (152.63.39.170) 37.060 ms 36.439 ms 35.313 ms
14 P14-3.LCR-03.BLTMMD.verizon-gni.net (130.81.29.129) 71.166 ms 74.161 ms so-7-0-0-0.BB-RTR2.RES.verizon-gni.net (130.81.19.51) 36.814 ms
15 P14-3.LCR-03.BLTMMD.verizon-gni.net (130.81.29.129) 88.653 ms P14-0.LCR-04.BLTMMD.verizon-gni.net (130.81.27.143) 94.024 ms *
16 P14-0.LCR-04.BLTMMD.verizon-gni.net (130.81.27.143) 79.912 ms 83.905 ms L1.VFTTP-07.BLTMMD.verizon-gni.net (130.81.242.211) 81.657 ms
17 L1.VFTTP-07.BLTMMD.verizon-gni.net (130.81.242.211) 80.536 ms static-71-179-174-40.bltmmd.fios.verizon.net (71.179.174.40) 77.285 ms !X 77.662 ms !X


We can really see where the issue is, maybe they will see it too…

I am not sure how anyone else feels about the documentation on Mozilla’s API is but the stuff on http://www.xulplanet.com/ is geared to javascript development and sucks for C++ because it doesn’t fully describe how stuff works.  I wrote an entire plugin in C++ without any other documentation and it was unpleasant.  I got Doxygen working with the source tree by excluding a couple of files and figured that I didn’t want it to go to waste, here it is: Firefox Doxygen Config File.  I will in the future make a website for the documentation I plan to have automatic builds and have part with just the usable API visible.  We will see how it goes, but for now there it is.

I upgraded from Adobe Flash Player 7 to 9 the other day, it was really nice because I was able to play a lot more content. Flash Player has never been easy on my computer, to run a single instance it makes Firefox run about 20% more CPU utilization. The new version ran like that for a while then one day my computer seemed to be frozen, I had been using Pandora and just let it run for hours. When I finally got to top I saw that softirqd was going nuts along with X11, through elimination I determined that it was the Flash Player. After searching Google I found that softirqd issues generally occur because of network related issues, this fits the Pandora problem to a “T”. I uninstalled Flash Player 9 and put back in 7 and sure enough no more weird 100% CPU times. I later found a thread on the kernel mailing list that had a guy describing it as a possible kernel bug and one of the kernel developers stating that it was a Flash 9 bug. I would think that the kernel would protect from an application gathering too many soft requests and over loading the system.

I have been using VMware for a while to emulate windows machines for development.  When the VMware tools are installed it allows you to take clipboard contents from one system to the next.  It works great except that if you enter windows with something in your Klippy clipboard and then go back to X11 the 2nd Klippy item becomes active.  I would assume that this is a VMware issue but it doesn’t appear to have been fixed in the beta version of Workstation 6.

Another strange thing, when using the tools to auto capture the cursor for a Linux machine the cursor virtually cycles around in a very odd fashion on entering the emulator.  You have to try it to understand what I mean.