OSPF

How OSPF for IPv6 Works

OSPF is a routing protocol for IP. It is a link-state protocol, as opposed to a distance-vector protocol. Think of a link as being an interface on a networking device. A link-state protocol makes its routing decisions based on the states of the links that connect source and destination machines. The state of a link is a description of that interface and its relationship to its neighboring networking devices. The interface information includes the IPv6 prefix of the interface, the network mask, the type of network it is connected to, the routers connected to that network, and so on. This information is propagated in various type of link-state advertisements (LSAs).

A router's collection of LSA data is stored in a link-state database. The contents of the database, when subjected to the Dijkstra algorithm, result in the creation of the OSPF routing table. The difference between the database and the routing table is that the database contains a complete collection of raw data; the routing table contains a list of shortest paths to known destinations via specific router interface ports.

OSPF version 3, which is described in RFC 2740, supports IPv6.

Comparison of OSPF for IPv6 and OSPF Version 2

Much of the OSPF for IPv6 feature is the same as in OSPF version 2. OSPF version 3 for IPv6, which is described in RFC 2740, expands on OSPF version 2 to provide support for IPv6 routing prefixes and the larger size of IPv6 addresses.

In OSPF for IPv6, a routing process does not need to be explicitly created. Enabling OSPF for IPv6 on an interface will cause a routing process, and its associated configuration, to be created.

In OSPF for IPv6, each interface must be enabled using commands in interface configuration mode. This feature is different from OSPF version 2, in which interfaces are indirectly enabled using the router configuration mode.

When using an nonbroadcast multiaccess (NBMA) interface in OSPF for IPv6, users must manually configure the router with the list of neighbors. Neighboring routers are identified by their router ID.

In IPv6, users can configure many address prefixes on an interface. In OSPF for IPv6, all address prefixes on an interface are included by default. Users cannot select some address prefixes to be imported into OSPF for IPv6; either all address prefixes on an interface are imported, or no address prefixes on an interface are imported.

Unlike OSPF version 2, multiple instances of OSPF for IPv6 can be run on a link.

LSA Types for IPv6

The following list describes LSA types, each of which has a different purpose:

• Router LSAs (Type 1)—Describes the link state and costs of a router's links to the area. These LSAs are flooded within an area only. The LSA indicates if the router is an Area Border Router (ABR) or Autonomous System Boundary Router (ASBR), and if it is one end of a virtual link. Type 1 LSAs are also used to advertise stub networks. In OSPF for IPv6, these LSAs have no address information and are network-protocol-independent. In OSPF for IPv6, router interface information may be spread across multiple router LSAs. Receivers must concatenate all router LSAs originated by a given router when running the SPF calculation.


• Network LSAs (Type 2)—Describes the link-state and cost information for all routers attached to the network. This LSA is an aggregation of all the link-state and cost information in the network. Only a designated router tracks this information and can generate a network LSA. In OSPF for IPv6, network LSAs have no address information and are network-protocol-independent.


• Interarea-prefix LSAs for ABRs (Type 3)—Advertises internal networks to routers in other areas (interarea routes). Type 3 LSAs may represent a single network or a set of networks summarized into one advertisement. Only ABRs generate summary LSAs. In OSPF for IPv6, addresses for these LSAs are expressed as prefix, prefix length instead of address, mask. The default route is expressed as a prefix with length 0.


• Interarea-router LSAs for ASBRs (Type 4)—Advertise the location of an ASBR. Routers that are trying to reach an external network use these advertisements to determine the best path to the next hop. ASBRs generate Type 4 LSAs.


• Autonomous system external LSAs (Type 5)—Redistributes routes from another AS, usually from a different routing protocol into OSPF. In OSPF for IPv6, addresses for these LSAs are expressed as prefix, prefix length instead of address, mask. The default route is expressed as a prefix with length 0.


• Link LSAs (Type 8)—Have local-link flooding scope and are never flooded beyond the link with which they are associated. Link LSAs provide the link-local address of the router to all other routers attached to the link, inform other routers attached to the link of a list of IPv6 prefixes to associate with the link, and allow the router to assert a collection of Options bits to associate with the network LSA that will be originated for the link.


• Intra-Area-Prefix LSAs (Type 9)—A router can originate multiple intra-area-prefix LSAs for each router or transit network, each with a unique link-state ID. The link-state ID for each intra-area-prefix LSA describes its association to either the router LSA or the network LSA and contains prefixes for stub and transit networks.

An address prefix occurs in almost all newly defined LSAs. The prefix is represented by three fields: PrefixLength, PrefixOptions, and Address Prefix. In OSPF for IPv6, addresses for these LSAs are expressed as prefix, prefix length instead of address, mask. The default route is expressed as a prefix with length 0. Type 3 and Type 9 LSAs carry all IPv6 prefix information that, in IPv4, is included in router LSAs and network LSAs. The Options field in certain LSAs (router LSAs, network LSAs, interarea-router LSAs, and link LSAs) has been expanded to 24 bits to provide support for OSPF in IPv6.

In OSPF for IPv6, the sole function of link-state ID in interarea-prefix LSAs, interarea-router LSAs, and autonomous-system external LSAs is to identify individual pieces of the link-state database. All addresses or router IDs that are expressed by the link-state ID in OSPF version 2 are carried in the body of the LSA in OSPF for IPv6.

The link-state ID in network LSAs and link LSAs is always the interface ID of the originating router on the link being described. For this reason, network LSAs and link LSAs are now the only LSAs whose size cannot be limited. A network LSA must list all routers connected to the link, and a link LSA must list all of the address prefixes of a router on the link.

NBMA in OSPF for IPv6

On NBMA networks, the designated router (DR) or backup DR (BDR) performs the LSA flooding. On point-to-point networks, flooding simply goes out an interface directly to a neighbor.

Routers that share a common segment (Layer 2 link between two interfaces) become neighbors on that segment. OSPF uses the Hello protocol, periodically sending hello packets out each interface. Routers become neighbors when they see themselves listed in the neighbor's hello packet. After two routers become neighbors, they may proceed to exchange and synchronize their databases, which creates an adjacency. Not all neighboring routers have an adjacency.

On point-to-point and point-to-multipoint networks, the software floods routing updates to immediate neighbors. There is no DR or BDR; all routing information is flooded to each networking device.

On broadcast or NBMA segments only, OSPF minimizes the amount of information being exchanged on a segment by choosing one router to be a DR and one router to be a BDR. Thus, the routers on the segment have a central point of contact for information exchange. Instead of each router exchanging routing updates with every other router on the segment, each router exchanges information with the DR and BDR. The DR and BDR relay the information to the other routers.

The software looks at the priority of the routers on the segment to determine which routers will be the DR and BDR. The router with the highest priority is elected the DR. If there is a tie, then the router with the higher router ID takes precedence. After the DR is elected, the BDR is elected the same way. A router with a router priority set to zero is ineligible to become the DR or BDR.

When using NBMA in OSPF for IPv6, you cannot automatically detect neighbors. On an NBMA interface, you must configure your neighbors manually using interface configuration mode.

Force SPF in OSPF for IPv6

When the process keyword is used with the clear ipv6 ospf command, the OSPF database is cleared and repopulated, and then the shortest path first (SPF) algorithm is performed. When the force-spf keyword is used with the clear ipv6 ospf command, the OSPF database is not cleared before the SPF algorithm is performed.

Load Balancing in OSPF for IPv6

When a router learns multiple routes to a specific network via multiple routing processes (or routing protocols), it installs the route with the lowest administrative distance in the routing table. Sometimes the router must select a route from among many learned via the same routing process with the same administrative distance. In this case, the router chooses the path with the lowest cost (or metric) to the destination. Each routing process calculates its cost differently and the costs may need to be manipulated in order to achieve load balancing.

OSPF performs load balancing automatically in the following way. If OSPF finds that it can reach a destination through more than one interface and each path has the same cost, it installs each path in the routing table. The only restriction on the number of paths to the same destination is controlled by the maximum-paths command. The default maximum paths is 16, and the range is from 1 to 64.

Importing Addresses into OSPF for IPv6

When importing the set of addresses specified on an interface on which OSPF for IPv6 is running into OSPF for IPv6, users cannot select specific addresses to be imported. Either all addresses are imported, or no addresses are imported.

OSPF for IPv6 Customization

You can customize OSPF for IPv6 for your network, but you likely will not need to do so. The defaults for OSPF in IPv6 are set to meet the requirements of most customers and features. If you must change the defaults, refer to the IPv4 configuration guide and the IPv6 command reference to find the appropriate syntax.

---

Caution Be careful when changing the defaults. Changing defaults will affect your OSPF for IPv6 network, possibly adversely.

---

How to Implement OSPF for IPv6

This section contains the following procedures:

• Enabling OSPF for IPv6 on an Interface (required)


• Configuring NBMA Interfaces (optional)


• Forcing an SPF Calculation (optional)


• Verifying OSPF for IPv6 Configuration and Operation (optional)

Enabling OSPF for IPv6 on an Interface

This task explains how to enable OSPF for IPv6 routing and configure OSPF for IPv6 on each interface. By default, OSPF for IPv6 routing is disabled and OSPF for IPv6 is not configured on an interface.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. ipv6 ospf process-id area area-id [instance instance-id]

5. exit

DETAILED STEPS

Command or Action Purpose Step 1 enable Example: Router> enable Enables privileged EXEC mode. Enter your password if prompted. Step 2 configure terminal Example: Router# configure terminal Enters global configuration mode. Step 3 interface type number Example: Router(config)# interface ethernet 0/0 Specifies an interface type and number, and places the router in interface configuration mode. Step 4 ipv6 ospf process-id area area-id [instance instance-id] Example: Router(config-if)# ipv6 ospf 1 area 0 Enables OSPF for IPv6 on an interface. Step 5 exit Example: Router(config-if)# exit Exits interface configuration mode, and returns the router to global configuration mode.

Configuring NBMA Interfaces

You can customize OSPF for IPv6 in your network to use NBMA interfaces. OSPF for IPv6 cannot automatically detect neighbors over NBMA interfaces. On an NBMA interface, you must configure your neighbors manually using interface configuration mode.

Prerequisites

Before you configure NBMA interfaces, you must perform the following tasks:

• Configure your network to be an NBMA network


• Identify each neighbor

Restrictions

You cannot automatically detect neighbors when using NBMA interfaces. You must manually configure your router to detect neighbors when using an NBMA interface.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. frame-relay map ipv6 ipv6-address dlci [broadcast] [cisco] [ietf] [payload-compression {packet-by-packet frf9 stac [hardware-options] data-stream stac [hardware-options]}]

5. ipv6 ospf neighbor ipv6-address [priority number] [poll-interval seconds] [cost number] [database-filter all out]

6. exit

DETAILED STEPS

Command or Action Purpose Step 1 enable Example: Router> enable Enables privileged EXEC mode. Enter your password if prompted. Step 2 configure terminal Example: Router# configure terminal Enters global configuration mode. Step 3 interface type number Example: Router(config)# interface serial 0 Specifies an interface type and number, and places the router in interface configuration mode. Step 4 frame-relay map ipv6 ipv6-address dlci [broadcast] [cisco] [ietf] [payload-compression {packet-by-packet frf9 stac [hardware-options] data-stream stac [hardware-options]}] Example: Router(config-if)# frame-relay map ipv6 FE80::A8BB:CCFF:FE00:C01 120 Defines the mapping between a destination IPv6 address and the data-link connection identifier (DLCI) used to connect to the destination address. In this example, the NBMA link is frame relay. For other kinds of NBMA links, different mapping commands are used. Step 5 ipv6 ospf neighbor ipv6-address [priority number] [poll-interval seconds] [cost number] [database-filter all out] Example: Router(config-if) ipv6 ospf neighbor FE80::A8BB:CCFF:FE00:C01 Configures an OSPF for IPv6 neighboring router. Step 6 exit Example: Router(config-if)# exit Exits interface configuration mode, and returns the router to global configuration mode.

Forcing an SPF Calculation

This task explains how to start the SPF algorithm without first clearing the OSPF database.

SUMMARY STEPS

1. enable

2. clear ipv6 ospf [process-id] {process force-spf redistribution counters [neighbor [neighbor-interface]]}

Command or Action Purpose Step 1 enable Example: Router> enable Enables privileged EXEC mode. Enter your password if prompted. Step 2 clear ipv6 ospf [process-id] {process force-spf redistribution counters [neighbor [neighbor-interface]]} Example: Router# clear ipv6 ospf force-spf Clears the OSPF state based on the OSPF routing process ID.

Verifying OSPF for IPv6 Configuration and Operation

This task explains how to display information to verify the configuration and operation of OSPF for IPv6.

SUMMARY STEPS

1. enable

2. show ipv6 ospf [process-id] [area-id] interface [interface-type interface-number]

3. show ipv6 ospf [process-id] [area-id]

DETAILED STEPS

Command or Action Purpose Step 1 enable Example: Router> enable Enables privileged EXEC mode. Enter your password if prompted. Step 2 show ipv6 ospf [process-id] [area-id] interface [interface-type interface-number] Example: Router# show ipv6 ospf interface Displays OSPF-related interface information. Step 3 show ipv6 ospf [process-id] [area-id] Example: Router# show ipv6 ospf Displays general information about OSPF routing processes.

What to Do Next

For output examples of the commands used to verify OSPF for IPv6 configuration and operation, refer to the IPv6 for Cisco IOS Command Reference.

Configuration Examples for Implementing OSPF for IPv6

This section provides the following configuration examples:

• Enabling OSPF for IPv6 on an Interface Configuration Example


• Configuring NBMA Interfaces Configuration Example


• Forcing SPF Configuration Example

Enabling OSPF for IPv6 on an Interface Configuration Example

The following example configures an OSPF routing process 109 to run on the interface and puts it in area 1:

ipv6 ospf 109 area 1

Configuring NBMA Interfaces Configuration Example

The following example configures an OSPF neighboring router with the IPv6 address of FE80::A8BB:CCFF:FE00:C01.

interface serial 0

ipv6 enable

ipv6 ospf 1 area 0

encapsulation frame-relay

frame-relay map ipv6 FE80::A8BB:CCFF:FE00:C01 120

ipv6 ospf neighbor FE80::A8BB:CCFF:FE00:C01

Forcing SPF Configuration Example

The following example triggers SPF to redo the SPF and repopulate the routing tables:

clear ipv6 ospf force-spf

Search for Ebook server with Google

As you know Google.com is the most popular search engine in the world.





Here are some tips to helps you find eBooks with Google:





Find Apache's (default) Index page





Try this query:






+("index of") +("/ebooks""/book") +(chmpdfziprar) +apache









Find a particular eBook file





Try this query:






allinurl: +(rarchmzippdftgz) TheTitle

Top Ten Cisco IOS Tip

When O'Reilly asked me to write a collection of hints and tips about Cisco routers, I knew that it would be difficult to come up with a list that would do justice to all the various features of a Cisco IOS device.
In hopes of making the list smaller and more useful, I decided to list ten tips that discuss situations I have encountered either through my own experience or that were sparked by other people's questions. Some of these hints are simple while others a little more advanced. Whether you are a novice or an expert, I hope you will find them useful.
1. Commands take effect right away.
If you are an experienced Cisco router user, you probably just groaned. However, I find that this concept escapes new users.
As you type commands into the configuration mode, they immediately take effect. For example, if we change the router's name, we see that the very next line contains the new router name:

Router1#config terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router1(config)#hostname MyRouter
MyRouter(config)#^Z
MyRouter#
As you can see, we changed the router's name to MyRouter, which was immediately processed. This concept applies to everything in the router's configuration mode.
2. Use all the descriptions you can.
In the router's configuration, there are certain commands that let you document various portions of a configuration. For example, the interface description command, an access-list remark command, or a banner message. All of these commands stay within the router configuration, which helps greatly when you are trying to configure or troubleshoot a router.
Here's an example of a description on an interface:

! Here is an interface description.
! Document as much about the interface as possible
interface Serial0
description Connection To Irvine: Wan ID [23499]
The available banner messages are the message of the day, or MOTD, login, incoming, and exec. Consult the documentation or Cisco IOS in a Nutshell for a description of each. Here is an example of the MOTD banner, which is the first message a person sees when connecting to the device:

MyRouter(config)#banner motd #
Enter TEXT message. End with the character '#'.
Welcome to MyRouter.
Some legalese should go here about unauthorized access.
#
The remark statement in an access-list is a relatively new feature. It first appeared in version 12.0(2)T of the IOS. This handy command allows you to make an entry in your access-list that describes what you are trying to accomplish. The comment can be up to 100 characters in length. <>statements work for both numbered and named access-lists.

access-list 1 remark Permit our private network through the list
access-list 1 permit 10.1.1.0 0.0.0.255
access-list 1 remark Just deny everything else
access-list 1 deny any
You might be wondering about commenting a configuration with the "!" symbol.
Yes, you can comment a configuration with a "!" as I have done in the above examples. However, these comments do not stay in the router configuration. They are great when you are working on a configuration offline in a text editor. (Where you plan to upload the configuration to a router.)
However, these "!" comments will get lost when you send the configuration to the router because the router ignores them.
3. The reload command can get you out of a jam.
Related Reading
Cisco IOS in a NutshellBy James BoneyDecember 2001Table of ContentsIndexSample ExcerptFull Description
4. No matter how well you plan an upgrade, you are eventually going to need to change a router configuration remotely. If you make a mistake and can no longer get to the router because of the change you made, you have to make the embarrassing call to someone to go "hit the power." The power cycle takes the router back to the original starting configuration because your change was never saved. In other words, since you lost connection, you couldn't type "copy run start" to save your changes.
5. One of the classic mistakes (I know because I have done it myself a number of times) is to incorrectly update an access-list on an interface when you are connected to the device remotely. And suddenly, the Telnet connection is dropped to the router because of a forgotten list entry that would permit your incoming connection.
6. There is another way. When you are doing something tricky, you can use the following feature of the reload command, which causes the router to reboot in a certain number of minutes. For example, let's tell the router to reboot in three minutes.
7.
8. MyRouter#reload in 3
9. Reload scheduled in 3 minutes
10. Proceed with reload? [confirm]y
11. Now, we have three minutes to do what we need to do. Let's say we are applying an access-list to serial0.
12.
13. MyRouter#config terminal
14. Enter configuration commands, one per line. End with CNTL/Z.
15. MyRouter(config)#interface serial0
16. MyRouter(config-if)#ip access-group 110 in
17. MyRouter(config-if)#^Z
18. MyRouter#
19. We made the change and everything still works. (Well, at least our connection wasn't dropped.) Now all we have to do cancel the impending reload with the following command:
20.
21. MyRouter#reload cancel
22. Or, if our access-list update did destroy our connection to the router, all we need to do is wait three minutes (plus the router's reload time) before the router is back online. After the reload, the router uses the original saved configuration before our access-list change.
23. Don't forget to add either an enable password or an enable secret password.
If you are planning to telnet into your router remotely, you need to add an enable password or enable secret password, or the router will not allow you to go to enable mode. Of course, it goes without saying that adding an enable password is always a good thing.

! Enable service password-encryption if it isn't already.
service password-encryption
! Here is our enable password, which is ok
! but not too secure.
enable password 7 141B171F01012325
! Here is our enable secret, much better.
enable secret 5 $1$99Jc$dxVXUkwMM3Edvj7f0SUrL/
Don't forget that "enable secret" overrides the "enable" password. Just be safe and use the enable secret command. The enable secret uses a better encryption method to encode the password.
24. Stopping the router from trying to telnet.
This is often an annoying problem. Mistype a command and the router thinks you just typed a hostname. For example:

MyRouter#shwo
Translating "shwo"...domain server (10.1.1.2)
% Unknown command or computer name, or unable to find computer address
MyRouter#
Here, we just mistyped the word show. We didn't want to telnet to a device named "shwo." The way to handle this is to change the preferred transport method:

! Console port
line con 0
transport preferred none
! VTY Ports
line vty 0 5
transport preferred none
The output shows the lack of a failed connection based on our mistyped keyword:

MyRouter#shwo
^
% Invalid input detected at '^' marker.

6. Two common access-list pitfalls.
The first common access-list problem I have seen is not allowing some ICMP (Internet Control Message Protocol) traffic through a gateway firewall.
For example, you just configured an access-list on your DSL link for your home router. All of the sudden, when you send big transmissions like a large email attachment, you find your connections timing out or closing unexpectedly. Unsure, you take the access-list off and the problem goes away. When you put the access-list back on, the problem reappears. You ask yourself what happened as you review the access-list. Well, the problem is as simple as not permitting ICMP through your list.
As I say in Cisco IOS in a Nutshell, people often think of ICMP as the hacker's tool. But in reality, it plays a very important role. In the problem I just described, it sounds like an MTU (Maximum Transmission Unit) or source-quench problem, which means the ICMP information isn't getting through the access-list. Either way, add the following commands to your access-list and your problems might go away:

! allow pings into the network
access-list 110 permit icmp any any echo
! allow ping responses
access-list 110 permit icmp any any echo-reply
! allow ICMP source-quench
access-list 110 permit icmp any any source-quench
! allow path MTU discovery
access-list 110 permit icmp any any packet-too-big
! allow time-exceeded, which is useful for traceroute
access-list 110 permit icmp any any time-exceeded
! deny all other ICMP packets
access-list 110 deny icmp any any
A second common access-list pitfall is when people forget to allow DNS (Domain Name Servers) from their internal network to the provider's DNS servers. Mainly this is a problem on home or small office routers where you might not have an internal DNS server running.
The following command allows DNS access from your hosts to the outside DNS server. In this example, our outside DNS servers are 172.16.1.1 and 172.30.1.1

access-list 110 permit udp host 172.16.1.1 eq domain any gt 1023
access-list 110 permit udp host 172.30.1.1 eq domain any gt 1023
7. Useful show commands.
Configuration of a router is only half the battle. Without a good toolbox of show commands, configuring your router properly will be very difficult. Throughout the tutorial section of my book, I tried to include the appropriate show commands for each topic.
But here are some of the most useful show commands that you should have at a minimum. Of course, the bias here is towards IP.
show ip arp
Displays the entire ARP (Address Resolution Protocol)table, which is the MAC-to-IP resolution table.
show version
This command gives a good amount of information; the IOS version you are running, the available interfaces, the system uptime, the last reload reason, and the configuration register setting.
show ip protocols
Displays information about the currently running routing protocols.
show ip route
The old standby, which displays the entire IP route table.
show ip route summary
Gives a very useful summary of the IP route table.
show ip interface
Gives a summary of each interface from the IP level.
show ip interface brief
A very brief summary of each interface.
show ip traffic
An extensive summary of IP traffic statistics on the router.
show access-list
This useful command not only shows the all the currently configured access-lists, but it also shows you the number of hits each line has received. You can use this information to better troubleshoot your access-lists.
show cdp neighbors
Assuming you have CDP enabled, this command gives you a report of all Cisco devices that the current device is connected to. CDP stands for Cisco Discovery Protocol, which can be an invaluable tool.
show cdp neighbors detail
This command gives even more information about CDP neighbors.
8. Learn the command-line editing keys.
When spending time on a Cisco IOS device, it is good to know some of the hot keys. People are always surprised (so it seems) that these editing keys even exist. If you are familiar with Unix, these commands will also look familiar. (The Bash shell, for example, uses a very similar list of keys.)
The entire list is included in Cisco IOS in a Nutshell. But here are a few to get you started:

Control A Goes to the beginning of the line
Control E Goes to the end of the line
Control K Deletes everything to the right of the cursor
Control P Recalls the previous command in the history buffer
Control N Recalls the next command in the history buffer
9. A common frame-relay misunderstanding.
The encapsulation type on the physical interface must be set to frame-relay before any sub-interfaces can be created. The default encapsulation type is usually HDLC (High-level Data Link Control).
So, before starting to create our frame-relay sub-interfaces, we need to first set the encapsulation type to frame-relay on the physical interface:

interface serial0
encapsulation frame-relay
Now we can create our sub-interfaces:

interface serial0.1 point-to-point
description This is our first sub interface for serial1
10. Setting the bandwidth on serial links.
Setting the bandwidth on a serial interface has nothing to do with the actual link speed. Rather, it provides the value that some routing protocols use in calculating routing metrics. The default bandwidth is 1.544mps, which is the speed of a T1 link.
However, if you aren't using a T1, setting your bandwidth on serial links is always a good (and sometimes forgotten) idea.

interface serial0
description This is a 56k link
bandwidth 56
That's it for now. I hope these tips will help you avoid some of the common pitfalls of dealing with Cisco IOS devices.
James Boney is a consultant specializing in a wide variety of subjects, including network design, network management, Unix administration, and programming.

Getting Your Dream Job

Essentially, a letter of application should be brief and to the point. In terms of length, it should not exceed a single page. And to make it more effective in serving its purpose, the letter should meet the following three objectives:1. Express interest in the job for which you are applying.2. Brie�ly show how your background and work experience qualify you for the job. 3. Ask for an interview. As we found out in earlier chapters, when the application letter >>>>>>>>>>>>>>>>>>

Download

watch Fish robot

Watch

1



Watch

2

Skype Robot Demonstration

Have a look at this cool video, call your robot using Skype and have it perform spoken commands while you remotely watch the results. I for one am very impressed

Watch

welcome Fedora 10

As always, Fedora continues to develop (http://www.fedoraproject.org/wiki/RedHatContributions) and integrate the latest free and open source software (http://www.fedoraproject.org/wiki/Features.) The following sections provide a brief overview of major changes from the last release of Fedora. For more details about other features that are included in Fedora 10, refer to their individual wiki pages that detail feature goals and progress:
http://www.fedoraproject.org/wiki/Releases/10/FeatureList
Throughout the release cycle, there are interviews with the developers behind key features giving out the inside story:
http://www.fedoraproject.org/wiki/Interviews
The following are major features for Fedora 10:
Wireless connection sharing enables ad hoc network sharing -- http://www.fedoraproject.org/wiki/Features/ConnectionSharing
Better setup and use of printers through improved management tools -- http://www.fedoraproject.org/wiki/Features/BetterPrinting
Virtualization storage provisioning for local and remote connections now simplified -- http://www.fedoraproject.org/wiki/Features/VirtStorage
SecTool is a new security audit and intrusion detection system -- http://www.fedoraproject.org/wiki/Features/SecurityAudit
RPM 4.6 is a major update to the powerful, flexible software management libraries -- http://www.fedoraproject.org/wiki/Features/RPM4.6
Some other features in this release include:
Glitch free audio and better performance is achieved through a rewrite of the PulseAudio sound server to use timer-based audio scheduling -- http://www.fedoraproject.org/wiki/Features/GlitchFreeAudio
Improved webcam support -- http://www.fedoraproject.org/wiki/Features/BetterWebcamSupport
Better support for infrared remote controls makes them easier to connect and work with many applications -- http://www.fedoraproject.org/wiki/Features/BetterLIRCSupport
The paths /usr/local/sbin:/usr/sbin:/sbin have been added to the PATH for normal users, to simplify command-line administration tasks -- http://fedoraproject.org/wiki/Features/SbinSanity
The online account service provides applications with credentials for online accounts listed on http://online.gnome.org/ or stored in GConf -- http://www.fedoraproject.org/wiki/Features/OnlineAccountsService

Download Gnome

Download Now!

Download KDE

Download Now!