Monthly Archives: January 2008

ThreadAbortException – Response.Redirect

If you have ever seen this exception while debugging a web application:

A first chance exception of type ‘System.Threading.ThreadAbortException’ occurred in mscorlib.dll
An exception of type ‘System.Threading.ThreadAbortException’ occurred in mscorlib.dll but was not handled in user code

To cut down on exceptions in your ASP.NET applications with Response.Redirect, you need to use the overloaded redirect method.  Under the hood, the CLR will throw an exception to ensure the page execution is halted.

private void SomeEvent(object sender, System.EventArgs e)
{
   
//This will throw an exception so that the CLR ensures the end of execution.
   
Response.Redirect(“http://www.threadabort.com“);

    //This performs better when this overload function’s second arg is set to false
   
//because an exception will not be thrown.
   
Response.Redirect(“http://www.threadabort.com“, false);
}

 The only issue is that the page continues to execute.  This may not be desired.

FiOS vs Cable (Cox Communications) part 2 – Install Day

Today is the day.  FiOS is now installed.  Here are a few tips that I gathered from reading about everyone else experiences.  Ask the guy to do ethernet from the ONT box.  They can and will do it only if you ask.  Otherwise you will get Coax cable to your supplied Actiontec MI424 Router.  Now, I can not confirm or deny this, but I think there is a lag if you use the Coax method of an additional 5 ms or so.  If anyone can confirm this, please let me know.

Here is my tracert (trace route) for FiOS to this site (residing on a gigabit fiber network on Level3′s backbone).

Tracing route to threadabort.com [4.79.230.85]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms  myrouter [192.168.49.1]
2     3 ms     2 ms     2 ms  l100.vfttp-07.nrflva.verizon-gni.net [72.84.94.1]
3     2 ms     2 ms     2 ms  p4-3.lcr-01.nrflva.verizon-gni.net [130.81.58.64]
4     9 ms     9 ms     8 ms  so-6-3-0-0.BB-RTR2.RES.verizon-gni.net [130.81.29.92]
5     9 ms     9 ms     9 ms  0.so-7-1-0.xl4.iad8.alter.net [152.63.39.165]
6     9 ms     9 ms     9 ms  0.ge-7-0-0.br2.iad8.alter.net [152.63.41.157]
7     *        9 ms     9 ms  4.68.63.165
8    10 ms    10 ms    10 ms  ae-22-79.car2.washington1.level3.net [4.68.17.68]
9    10 ms    11 ms    11 ms  bandwidthco.car2.washington1.level3.net [4.79.19.110]
10    10 ms    10 ms    10 ms  4.79.230.85

Well, a 2 ms drop is very acceptable compared to Cox’s 6-8 ms drop.

Here is the new speakeasy.net speed test:

As you can see I get pretty close to the 30/15 number I signed up for.  The upstream test doesn’t seem to be that fair anyways since it happens so quick.  But, Verizon Fios is not fudging any numbers here.

Since I have a very specialized WRT-54gs router, I installed that after the tech guy left.  I love to use DD-WRT on my Linksys router, so I wanted that back.  It performs just as well as the ActionTec router as far as I can tell.

If you want to use your own router here are some tips:

  1. You must have Ethernet to the ONT (The box outside that the fiber goes into).  You can ask for it later, but it is not as easy to install.  You will have to call Verizon to switch it if you wait.
  2. Make sure you use MAC Clone on your router and set it to the MAC address listed on the ActionTech router.
  3. Turn off STP if you have an option to.  I couldn’t get the router to pick up DHCP until this was off.
  4. If you have FiOS TV, check out Verizon_FIOS_setup_with_dd-wrt_as_primary_router

 

UPDATE (1/12/2008) : I switched back to the ActionTec Router.  It is far faster than my Linksys WRT-54GS.  The Linksys would have trouble at 30mbps.

FiOS vs Cable (Cox Communications) part 1

Check out Part 2 for the final results.

Tomorrow I will have FIOS installed.  30 down / 15 up.  One thing that is always bothered me about Cable is that I seem to drop 6-10 ms just from my cable modem to Cox’s.

Here is my current tracert (traceroute) to this site.  This site is connected on Level3′s backbone via fiber and a gigabit connection.

Tracing route to threadabort.com [4.79.230.85] over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms  192.168.49.1
2     8 ms     7 ms     7 ms  10.2.204.1
3     7 ms     8 ms     8 ms  68.10.8.57
4     7 ms     6 ms     9 ms  172.22.48.65
5     8 ms     7 ms     7 ms  172.22.48.5
6     8 ms     7 ms     7 ms  172.22.48.129
7     7 ms     7 ms    11 ms  nrfkdsrj02-ge703.rd.hr.cox.net [68.10.14.17]
8     7 ms     7 ms     7 ms  nrfkdsrj01-so010.rd.hr.cox.net [68.10.15.1]
9    15 ms    15 ms    15 ms  tbr2.wswdc.ip.att.net [12.123.8.30]
10    14 ms    13 ms    13 ms  ar4.wswdc.ip.att.net [12.123.8.101]
11     *       15 ms    14 ms  so-8-0-0.car3.washington1.level3.net [4.68.127.153]
12    15 ms    17 ms    17 ms  ae-42-99.car2.washington1.level3.net [4.68.17.196]
13    16 ms    15 ms    15 ms  bandwidthco.car2.washington1.level3.net [4.79.19.110]
14    15 ms    15 ms    13 ms  4.79.230.85

As you can see, 6-8 of the ms drop is from my cable modem to cox.  I am hoping that fiber to my home should allow for a smaller drop.  My Cox Connection is a business class connection and offers me 15 down / 2 up.

I will continue this with Part 2 by the end of the week with details and tips for a FIOS install.