A Crash Course On Myspace For Parents

It is easy to lose track of what your kids are doing online without being overly snoopy about their growing independence. Independence is a good thing when the child has demonstrated that they can make responsible decisions and good choices. Part of your responsibility as a parent is to provide the tools which will help them along this pathway. A good way to open communications with your child is to discuss the MySpace internet area with them.

MySpace is a web site where teens and preteens can journal thoughts, add pictures, chat with others about their interest, and discuss events and problems which affect their daily lives. A great deal of controversy lately has surfaced around the site, because of the potential for unwelcome elements of discussion, pedophiles who may use the site as a springboard for meeting youngsters face to face or other unhealthy aspects.

By understanding the mechanics of how MySpace works, parents are enabled to sit down with a preteen child and dialogue about the positive aspects of the web site as well as opening discussion about the dangers which can be found. Obviously, no parent is going to be able to totally block off any areas of the internet which might be perceived as unhealthy for the child. Often such actions will either be resented as overly controlling, or will create an interest where none existed previously.

Some important tips to use with your youngster is how to set privacy and profile options for security online. You can also explain to your child the importance of not lying about your age, or giving out the real name of your school or other identifying information. The important part of this exercise is that it is done jointly with the child, so they learn not only how to use guidelines in making decisions, but that there are good reasons for the guidelines.

Cisco CCNA Exam Tutorial: Five ISDN Details To Remember

CCNA exam success depends on mastering many technologies that are new to you, and few exam topics have more details than ISDN. ISDN isn't just for your CCNA exam studies, though. While ISDN is dismissed by many, the fact is that there are many small and mid-size networks out there that use ISDN as their backup to frame relay. Some of these companies have spoke networks that use ISDN to connect to their hub as well, so it's a great idea to know ISDN configuration and troubleshooting for your real-world career as well as passing the CCNA. With that in mind, let's take a look at five common ISDN errors and how to avoid them.

With dialer map statements, remember that the phone number you put in the dialer map is the phone number of the remote router, not the local one. Look at it this way - if you want to call a friend on your cell, you don't pick up your cell and dial your own number!

Speaking of dialer map statements, don't forget the all-important broadcast option at the end of the command:

R1(config-if)#dialer map ip 172.12.21.1 name R2 broadcast 5555555

The router will accept that command without the "broadcast" option, but routing protocol updates and hellos would not be able to travel across the line. (This command is also needed in frame relay map statements to allow broadcasts and multicasts to be transmitted.)

PAP is PPP's clear-text authentication scheme, and clear text is a really bad idea. But if you do have to configure it, don't forget that PAP requires additional configuration -the ppp pap sent-username command.

R1(config-if)#ppp pap sent-username R1 password CISCO

Must set encapsulation to PPP before using PPP subcommands

R1(config-if)#

The error message we got while configuring the sent-username command is another important reminder - by default, a BRI line is running HDLC, not PPP. Since HDLC doesn't allow us to use either PAP or CHAP, we'll need to set the link to PPP with the encapsulation ppp command.

R1(config-if)#encapsulation ppp

R1(config-if)#ppp authentication pap

R1(config-if)#ppp pap sent-username R1 password CISCO

But before we configure any of this information, we should configure the ISDN switch-type. Why? Because without the switch-type configuration, it doesn't matter that we avoid the other four errors - the line will not come up. Configure the switch-type with the "isdn switch-type" command, and then verify it with "show isdn status".

R1(config)#isdn switch-type basic-ni

R1#show isdn status

Global ISDN Switchtype = basic-ni (output of this command cut here for clarity)

If you forget this part of the configuration, the output of show isdn status wastes no time in reminding you!

R1#show isdn status

**** No Global ISDN Switchtype currently defined ****

ISDN is an important part of your CCNA studies, and this knowledge still comes in handy in production networks as well. Keep studying, notice the details, run those debugs, and you'll be a CCNA before you know it!

Cisco CCNA Certification Exam Tutorial: Configuring Dialer Profiles

The most common method of configuring ISDN is with dialer maps, but dial information can also be configured on a logical interface. To pass the CCNA exam, you must know how to configure and troubleshoot both dialer maps and dialer profiles.

Dialer Profiles allow different dialing information to be configured onto logical interfaces. The logical interfaces may have different dialing destinations, different remote router names, etc., but they’ll be using the same physical interface.

Dialer strings are used on dialer profiles. Note that each logical interface has a different IP address, a different remote router to dial, and a different dialer string, but they will be using the same physical interface to dial out. The commands dialer pool and dialer pool-member are used to link the logical and physical interfaces. The number following each command must match for the logical interface to correctly bind to the physical interface.


R1(config)#interface dialer0

R1(config-if)#ip address 172.16.1.1 255.255.255.0

R1(config-if)#encapsulation ppp

<. The encapsulation type is placed on both the logical and physical interfaces. >

R1(config-if)#dialer remote-name Remote0



R1(config-if)#dialer pool 1

< places logical interface into dialer pool >

R1(config-if)#dialer string 5551212

< number dialed to contact router Remote0 >

R1(config-if)#dialer-group 1

< links logical interface to dialer-list 1 >


R1(config)#interface dialer1

R1(config-if)#ip address 172.16.1.2 255.255.255.0

R1(config-if)#encapsulation ppp

R1(config-if)#dialer remote-name Remote1

R1(config-if)#dialer pool 1

R1(config-if)#dialer string 5551234

R1(config-if)#dialer-group 1


R1(config)#interface bri0

R1(config-if)#no ip address

< With dialer profiles, IP addresses are assigned to logical interfaces. >

R1(config-if)#encapsulation ppp

< The encapsulation type is place on both the logical and physical interfaces.>

R1(config-if)#dialer pool-member 1

< The number associated with this command should match the number configured with the dialer pool number on the logical dialer interfaces. >

R1(config-if)#isdn spid1 0835866101

R1(config-if)#isdn spid2 0835866301



When configuring dialer profiles, the encapsulation type should be placed on both the physical BRI interface and the logical dialer interfaces. The SPIDs are configured on the physical interface as well.

Configuring dialer profiles can be a little tricky at first, and the best way to master this skill is to get real hands-on practice in your own CCNA / CCNP home lab or a rack rental service. Either way, hands-on is the best practice. Best of luck in your CCNA studies!