TraceRoute

May 15, 2008

Traceroute is often used for network troubleshooting. By showing a list of routers traversed, it allows the user to identify the path taken to reach a particular destination on the network. This can help identify routing problems that may block or slow access to a web site.In the early days of the Internet such detailed information about the path a packet took was considered acceptable and convenient. However, hackers have exploited this helpful tool in order to acquire sensitive information about a company’s network architecture. By using the traceroute command, a hacker or several hackers can quickly map a company’s network architecture and use that information to launch attacks.

In general traceroute and ping have the lowest priority of all packets. E-mail, web browsing, ftp, etc. data take precedence over traceroute data.

For example if a router is passing secure web data to a customer and another customer starts to ping that router. The router will put a ‘hold’ on the ping packets until it is ready. Because of situations like this, most traceroute programs send 3 different requests. Since one of the requests may be put on ‘hold’ due to higher priority data being sent, the program tests the path 3 times.

Over the past several years network devices have been electronically attacked via the use of ICMP. These attacks have proved to be very effective in the past, and in some situations they still are. Network device (routers, switches, etc) vendors have taken steps to lessen the impact of these attacks destined to their devices. They have done this by limiting the number of ping and traceroute messages received/processed per unit of time. In any given service providing network, multiple devices send/receive ping and traceroute messages on a perpetual basis. Add to this, the number of user/gamer/student/entrepreneurs who continuously run traceroute programs like ping plotter, and the ping and traceroute limits to the devices will be reached very quickly.

How to read traceroute data:

 

Let us do a traceroute to a site we know responds to ICMP packets.

Tracing route to cnn.com [64.236.16.20] over a maximum of 30 hops:

 

1 57 ms 28 ms 50 ms ip68-100-1-97.dc.dc.cox.net

2 341 ms 74 ms 156 ms ip68-100-0-1.dc.dc.cox.net [68.100.0.1]

3 28 ms 207 ms 52 ms mrfddsrj01gex070004.rd.dc.cox.net

4 * ms 274 ms 235 ms mrfdbbrj01-ge020.rd.dc.cox.net

5 73 ms 12 ms 84 ms mrfdbbrj02-ge030.rd.dc.cox.net

6 107 ms 38 ms 47 ms ashbbrj02-so000.r2.as.cox.net

7 35 ms 39 ms 54 ms ashbbbrj01-ae0.0.r2.as.cox.net

8 100 ms 38 ms 51 ms pop1-ash-S0-3-2.atdn.net

9 65 ms 40 ms 20 ms bb1-ash-P0-0.atdn.net [66.185.144.192]

10 40 ms 37 ms 51 ms bb2-vie-P11-0.atdn.net [66.185.152.101]

11 36 ms 35 ms 64 ms bb2-atm-P3-0.atdn.net [66.185.152.33]

12 51 ms 70 ms 45 ms bb2 [66.185.152.3]

 

Looking at this traceroute, one can see that roundtrip times to the site are very good (12 51 ms 70 ms 45

ms bb2 [66.185.152.3]) However looking at #4, one may determine that there is a problem at that device when there is not. When an actual problem occurs with a device that causes latency, that latency is carried on through the other hops.

If the router at #4 was causing latency to the connection at www.cnn.com, one would see increasing times at hop #5, #6, #7 and so on. Since all packets have to traverse the router at #4, any latency created by that device would carry on to the end of the traceroute.

Vendors sometimes limit the amount of ICMP packets that their equipment will respond to. This can produce confusing results. When reading a traceroute, look for latency (high return times) to carry though to the final destination.

 

Here is an example of a traceroute when there is a problem inside a network:

 

1 31 ms 27 ms 28 ms core1-loopback-0.Brisbane.netspace.net.au [203.17.101.6]

2 33 ms 30 ms 28 ms AS7496.brisbane.pipenetworks.com [218.100.0.20]

3 228 ms 329 ms 228 ms fa1-0-6.xr2.wic.server-web.com [203.147.255.118]

4 215 ms 232 ms 228 ms gi2-0.xr2.bne.server-web.com [203.147.255.237]

5 233 ms 229 ms 233 ms core.mls1.bne.server-web.com [203.147.255.246]

6 232 ms 232 ms 233 ms bne606d.server-web.com [202.139.232.71]

As one can see, between hop #2 and #3, the time jumps from 33 ms to 228 ms and the latency continues through to its final destination at #6.

Ingredients:
3 cups cubed peeled potatoes (Idaho or Yukon gold)
1 cup chopped onion
3 pound pork roast, trimmed
4 cloves garlic, minced
1 cup water
1/2 cup ketchup
3 tablespoons red wine vinegar
2 tablespoons light brown sugar (more if you want it sweeter)
2 tablespoons reduced-sodium soy sauce
1 teaspoon Dijon mustard
1/2 teaspoon ground black pepper
Salt

Instructions:

Arrange potatoes and onion in bottom of slow cooker. Place pork on top of potatoes and onion. Spread garlic all over pork.

In a medium bowl, whisk together water, ketchup, vinegar, sugar, soy sauce, mustard, black pepper and salt. Pour mixture over pork.

Cover and cook on LOW for 6 to 8 hours or on HIGH for 3 to 4 hours.

Slice pork crosswise into thin slices and serve 12 ounces for this meal. Serve with all of potatoes, onions, and sauce.

Corn Bread Stuffing

May 4, 2008

Corn Bread
2 cups cornmeal, preferably stone-ground
2 cups all-purpose flour
1 Tbsp. baking powder
2 tsp. salt, plus more to taste
1 large egg, lightly beaten
2 cups skim or low-fat milk
2 Tbsp. canola oil

Stuffing
2 cups chopped onions (2 medium)
2 cups chopped celery (4 large stalks)
1/4 cup chopped fresh parsley
2 1/2 cups reduced-sodium chicken broth 
freshly ground black pepper to taste

1. Preheat oven to 375°F. Lightly oil an 8-inch square baking dish or spray it with nonstick cooking spray. Combine cornmeal, flour, baking powder and 2 tsp. salt in a large bowl and mix well. In a separate bowl, whisk together egg, milk and 1 1/2 Tbsp. of the oil; add to the dry ingredients and stir just until evenly moistened. Turn the batter into the prepared baking dish and bake for 25 to 30 minutes, or until a toothpick inserted in the center comes out clean. Let cool in the pan on a rack. Cut into 1-inch cubes.

2. In a large nonstick skillet, heat the remaining 1/2 Tbsp. oil over medium-high heat. Add onions and celery and cook, stirring often, until softened, about 5 minutes. Transfer to a large bowl and add the cubed corn bread and parsley; toss to mix. Slowly add chicken stock, tossing until the corn bread is well moistened. Season with salt and pepper.

Makes about 12 cups, serves 10.
Per serving: 244 calories; 7 g protein, 5 g fat, 44 g carbohydrate; 58 mg sodium; 22 mg cholesterol.

 

1 cup (2 sticks) butter

1 cup light brown sugar

1 cup white sugar

1 teaspoon vanilla extract

2 eggs

2 cups all-purpose flour

¼ teaspoon salt

¼ teaspoon baking soda

1 (10-ounce) bag toffee candy bits

1 cup oatmeal

1 cup sweetened flake coconut

1 cup chopped whole, skinned almonds

 

Instructions:

 

Preheat oven to 350 degrees F.

 

Cream together the butter, sugar and vanilla. Beat the eggs slightly; then add to the butter mixture and mix well.  Sift flour, salt and baking soda; then add slowly to the moist ingredients and mix thoroughly.  Mix in the toffee bits, oatmeal, coconut and nuts.

 

Drop dough by the teaspoonful onto an ungreased baking sheet and bake for 15 minutes.

Pumpkin Squares

May 4, 2008

 

 

 

*Grease the bottom of a 13 x 9 inch baking dish/pan.  Preheat oven to 350*.

 

Crust 

1 box of yellow cake mix (minus 1 cup – set aside for topping)

½ cup melted butter

1 egg

 

In a medium size bowl combine ingredients  for the crust and press into pan.  Crust should go up the edges of the pan slightly.

 

Filling

1 large can of pumpkin pie MIX 2 eggs

2 tbs vanilla 2/3 cup evaporated milk

1 tsp pumpkin pie spice

 

In a large size bowl combine all ingredients together and pour over crust.

 

Topping

1 cup of yellow cake mix ¼ cup brown sugar

1 tsp pumpkin pie spice (or cinnamon) ¼ cup butter softened

 

In a small size bowl cut all ingredients together with a fork until crumbly .  Sprinkle over top.  Bake for 50-60 minutes.  Let cool, cut into squares, and serve.  Store any leftovers in the refrigerator.

 

 

 

Recipe Summary
Prep Time: 20 minutes 
Inactive Prep Time: 20 minutes 
Cook Time: 3 hours 25 minutes 
Yield: 12 servings 
     

1 cup (2 sticks) unsalted butter, at room temperature 
1/2 bunch fresh sage, leaves finely chopped 
Kosher salt and freshly ground black pepper 
2 large onions, finely chopped 
1 loaf cornbread, cubed (about 6 cups) 
1 large egg, lightly beaten 
1/2 cup heavy cream 
3 cups chicken stock 
1 (12 to 14 pound) fresh turkey 
1 cup pure maple syrup 
1/4 cup hot water 
8 strips smoked bacon 
1/4 cup all-purpose flour 
1/2 lemon, juiced
 

 

Preheat the oven to 350 degrees F and remove the top rack.Combine the butter and sage in a mixing bowl, mash with a fork or spoon until the sage is well incorporated and the butter has flecks of green in it; season with salt and pepper.

In a saute pan, melt 4 tablespoons of the sage butter, add the onions, cook and stir for 15 minutes until soft and golden. Remove from heat. Put the cornbread in a large mixing bowl and scrape the sauteed onion mixture on top. Add the egg, heavy cream, and just enough chicken stock to moisten the stuffing without making it soggy (about 1/2 cup.) Toss well to combine, season with salt and pepper.

Remove the neck and gizzards from the inside of the turkey and discard. Rinse the bird thoroughly inside and out with cold water, pat dry. Sprinkle the cavity and skin liberally with salt and pepper. Using your fingers, gently lift the skin from the breast and legs, and slip pieces of the sage butter underneath; massaging it in as you go. Fill the bird with the cornbread stuffing without packing too tightly; cook the remaining stuffing separately in a buttered baking dish. Truss the turkey; place it on a rack in a large roasting pan, and put into the oven.

Meanwhile, in a small mixing bowl, whisk together the maple syrup and hot water to thin the glaze out a bit; use this to baste the turkey every 30 minutes. The turkey should take about 3 hours to cook (i.e. 15 to 20 minutes per pound.) If the legs or breast brown too quickly, cover with foil. About 2 hours into cooking, shingle the strips of bacon oven the turkey breast to cover; continue to roast and baste for another hour or so. The turkey is done when an instant-read thermometer inserted into the meatiest part of the thigh registers 170 degrees F (the thigh juices will also run clear when pricked with a knife.) Transfer the turkey to a cutting board and let rest for 20 minutes before carving, so the juices can settle back into the meat.

Skim off the excess fat from the pan drippings with a spoon and place the roasting pan over 2 burners set on medium-high heat. Using a wooden spoon, scrape up brown bits stuck to bottom of pan. Whisk the flour into the drippings, stirring as it thickens to prevent lumps. Add the remaining chicken stock and bring to a simmer; season with salt and pepper and hit it with a squeeze of lemon juice to brighten the flavor. Simmer for 5 minutes and then strain to remove any particles. Serve the gravy with the maple-roasted turkey and cornbread stuffing.

 

Effects and explanations  concerning digital/highdef televisions.

Silk Screen Effect, SSE

The Silk Screen Effect, often referred to as simply SSE, applies only to rear projection televisions such as DLP, LCD and LCoS. Some times, when viewing white or other very bright colored objects, you see what appears to be the texture of the screen itself in front of the image. This gives the appearance that you’re watching the content through a silk screen. Some also describe it as an unnatural shimmering or sparkling on those bright areas. It can be greatly reduced with proper calibration. Typically reducing brightness and contrast, and to some extend adjusting picture control, can nearly eliminate the issue.

 

 

Screen Door Effect, SDE

The next acronym on the list is SDE or Screen Door Effect. This applies to all digital, or fixed pixel, televisions including rear-projection, plasma and flat panel LCD. If you own one, feel free to investigate this for yourself. When you get close enough to the screen you can actually see gaps between the pixels, producing what appears to be a grid on the screen. From that vantage point, it appears as though you’re watching TV though a window screen or screen door. All digital televisions have this issue, but the larger the pixels the more pronounced the effect. For example the old EDTV (480p) plasmas were infamous for screen door effect, whereas you can only see it on newer 1080p units when you’re incredibly (uncomfortably) close to the screen. The only way to eliminate SDE is to move further away from the screen.

 

 

Rainbow Effect

Rainbows are a DLP only phenomenon, specifically single-chip DLP. They have mostly been eradicated in the newer models, especially the LED based units. Traditional, bulb-based DLP televisions use a rapidly spinning color wheel to put color on the screen. The traditional color wheel has red, blue and green segments, and the bulb illuminates the screen in color by shining enough light through each segment that it blends together to form the color you want to see on screen. As a result only one color is actually on the screen at any given time. It is possible for some people to see this formation occurring and perceive it as a rainbow of the three distinct colors. It usually happens when a bright image appears on a very dark background, and for some only happens when they pan their eyes across the screen. There is no way to reduce the effect in an existing television set. Manufacturers have eliminated it by using faster color wheels with more color segments. LED based DLP televisions refresh fast enough that the effect is all but eliminated.

 

 

Refresh Rate

A television’s refresh rate describes how often a new image can be displayed on screen. Unlike prior analog technologies (CRT) where the entire screen was redrawn periodically, the new digital TVs only need to update the pixels that have changed since the last time an image was displayed. So the refresh rate essentially describes how often the display will check to see if any pixels need to be updated. All HDTV technologies have a refresh rate that should match or exceed the maximum number of video frames that can be shown per second. As the name implies, it is a rate, witch mathematically is the inverse of time, so the larger number the better. A refresh rate of 120Hz is better than a refresh rate of 60Hz.

 

 

Frame Rate or Frames per Second, FPS

It is important to note the distinction between frame rate and refresh rate. Frame rate typically describes the video content a television will display. Again, the higher number the better because the more video frames you get per second, the smoother the motion appears on the display. So 60 fps is usually considered better than 30 fps, although film is typically shot in 24 fps, so preserving that original rate is often desirable. A screen must have a refresh rate that equals or exceeds the minimum fps you want to watch. Obviously if you’re trying to view 60 frames per second, but only refreshing the screen 30 times per second, you’ll only see every other frame. Similarly, if the refresh rate of the screen is not a even multiple of the frame rate, the display will need to do some complex math to determine how to show what frames and for how long. Otherwise some frames will appear for multiple refreshes and others will appear for only one. This causes really choppy motion on screen.

 

 

Response Time

Often confused with refresh rate, response time measures how quickly a display can update an individual pixel. As a measure of time in this case, the smaller number the better. We’d like for the response time to be instantaneous, or nearly 0. Technically, response time is how long it takes for an individual pixel to go from black to white and back to black again. LCD is the only technology that has ever really suffered from slow response times; Plasma has almost instant response and DLP is very fast as well. With slow response times it’s possible for images, or “shadows” of images to appear on screen longer than they should. This is often referred to as ghosting or smearing. In the early days of LCD TV, a 16 ms response time was deemed adequate for home video, but 12 was necessary for gaming. Most modern LCD TVs have a response time of 8ms or less, making it almost impossible for most people to see any ghosting.

 

 

In-Plane Switching, IPS

Along with slow response times, another known on early LCD televisions was their very narrow viewing angle. Off angle viewing was, let’s just say, less than ideal. The advent of in-plane switching solved that problem. The technology itself gets a little too involved to discuss on the show, but it’s important to know the LCD TVs with IPS have a practical viewing angle that rivals plasma. Early versions of IPS caused significant slowdown in response times, as high as 50ms. A newer version of IPS, called Super In-Plane Switching (S-IPS) offers all the benefit of IPS at the faster response times required by modern HDTV viewers.