262
262
#: network/C/network.xml:379(para)
263
msgid "Wireless networking has gotten better with Kubuntu 7.10, however there are still problems for users who do not have a card supported natively. These issues are at times easy to overcome using utilities such as the <application>bcm43xx-fwcutter</application> for <emphasis role=\"bold\">some</emphasis> Broadcom devices, or <application>NdisWrapper</application> for other non-native wireless adapters. The following help sections will follow a generic route for getting wireless to work with either <application>NdisWrapper</application> or <application>bcm43xx-fwcutter</application>. If neither of the following sections help with your issue, then it is recommended that you use another connection source to the Internet and read through the many topics for wireless connections. The following are just a couple locations to review. <placeholder-1/>"
263
msgid "Wireless networking has gotten better with Kubuntu 7.10, however there are still problems for users who do not have a card supported natively. If you have not purchased a wireless card yet, please take a look at the supported hardware at <ulink url=\"https://help.ubuntu.com/community/WifiDocs/WirelessCardsSupported\"/>."
266
#: network/C/network.xml:408(title)
266
#: network/C/network.xml:389(title)
267
267
msgid "How do I..."
270
#: network/C/network.xml:413(term)
270
#: network/C/network.xml:394(term)
271
msgid "...figure out if my wireless card works?"
274
#: network/C/network.xml:396(para)
275
msgid "If your wireless card has been detected, <application>KNetworkManager</application> will have a menu entry listing your wireless device. You can attempt to connect to your wireless network by clicking on the System Tray icon and selecting your wireless network. If you are able to browse the network with the a web browser, you have successfully connected to the internet."
278
#: network/C/network.xml:408(term)
279
msgid "...configure encryptions such as <acronym>WEP</acronym> or <acronym>WPA</acronym>"
282
#: network/C/network.xml:411(para)
283
msgid "With <application>KNetworkManager</application> you simple click the application icon in the system tray and select the wireless network you want to connect to. When you click on a network that has encryption enabled, you will get a pop-up dialog to enter this information. Once entered, this information is stored within the <application>KWallet</application> utility. This allows you to connect to that network in the future just by entering your <application>KWallet</application> password."
286
#: network/C/network.xml:424(term)
287
msgid "...check if I have a Internet connection?"
290
#: network/C/network.xml:426(para)
291
msgid "Open up <application>Konqueror</application>, and try to browse to <ulink url=\"http://www.ubuntu.com\"/>. If this worked, you have a fully working internet connection."
294
#: network/C/network.xml:431(para)
295
msgid "If the above did not work, open up <application>Konsole</application> (<menuchoice><guimenu>KMenu</guimenu><guisubmenu>System</guisubmenu><guimenuitem>Konsole - Terminal Program</guimenuitem></menuchoice>) and type <userinput>ping gateway_ip_address</userinput> (substitude gateway_ip_address by the ip address of your gateway. This address is usually 192.168.1.1, but may vary depending on the nature of your network). If you are able to ping your gateway, then the DNS on your computer is not being correctly. If you are not able to ping the gateway, then you donot have a proper internet connection."
298
#: network/C/network.xml:444(term)
271
299
msgid "...figure out which wireless card my system uses?"
274
#: network/C/network.xml:415(para)
302
#: network/C/network.xml:446(para)
275
303
msgid "<application>KInfoCenter</application>: (<menuchoice><guimenu>KMenu</guimenu><guisubmenu>System</guisubmenu><guimenuitem>KInfoCenter - Info Center</guimenuitem></menuchoice>) A KDE utility that provides information about your computer system. Once <application>KInfoCenter</application> is opened, select <guilabel>PCI</guilabel> from the left hand window. This will display all of the <acronym>PCI</acronym> information about your system. Scroll down until you see <guilabel>Network controller:</guilabel>. This will provide information about your wireless adapter."
278
#: network/C/network.xml:425(para)
279
msgid "<emphasis role=\"bold\">Command line</emphasis>: (<menuchoice><guimenu>KMenu</guimenu><guisubmenu>System</guisubmenu><guimenuitem>Konsole = Terminal Program</guimenuitem></menuchoice>) This will open up <application>Konsole</application> providing you with a terminal or the command line. Once you are sitting at the command prompt simply type <userinput>lspci</userinput> and press the <keycap>Enter</keycap> key. Locate the <guilabel>Network controller:</guilabel> line as this will provide information about your wireless adapter."
282
#: network/C/network.xml:437(term)
306
#: network/C/network.xml:456(para)
307
msgid "<emphasis role=\"bold\">Command line</emphasis>: (<menuchoice><guimenu>KMenu</guimenu><guisubmenu>System</guisubmenu><guimenuitem>Konsole - Terminal Program</guimenuitem></menuchoice>) This will open up <application>Konsole</application> providing you with a terminal or the command line. Once you are sitting at the command prompt simply type <userinput>lspci</userinput> and press the <keycap>Enter</keycap> key. Locate the <guilabel>Network controller:</guilabel> line as this will provide information about your wireless adapter."
310
#: network/C/network.xml:468(term)
311
msgid "...get help with my wireless connection?"
314
#: network/C/network.xml:470(para)
315
msgid "It is recommended that you use another connection source to the Internet and read through the many topics for wireless connections. The following are just a couple locations to review."
318
#: network/C/network.xml:491(term)
283
319
msgid "...get my Broadcom wireless adapter to work?"
286
#: network/C/network.xml:439(para)
287
msgid "Since kernel version 2.6.17, support for Broadcom wireless devices were included. This means that there are some Broadcom devices that work out of the box, however there are still many that don't. If your Broadcom wireless device isn't working then you have one of two choices; <application>bcm43xx-fwcutter</application> or <application>NdisWrapper</application>. With the <application>bcm43xx-fwcutter</application> utility there are only a select few devices that actually work. To see the devices that are currently supported please review <ulink url=\"http://bcm43xx.berlios.de/?go=devices\"/>. If your device is not supported then it is advised that you use the <application>NdisWrapper</application> utility. For information on configuring your device with the <application>bcm43xx-fwcutter</application> utility please see <xref linkend=\"network-connect-wifi-bcm43xx\"/> and for configuring your device with <application>NdisWrapper</application> utility please see <xref linkend=\"network-connect-wifi-ndiswrapper\"/>."
290
#: network/C/network.xml:460(term)
291
msgid "...configure encryptions such as <acronym>WEP</acronym> or <acronym>WPA</acronym>"
294
#: network/C/network.xml:463(para)
295
msgid "With <application>KNetworkManager</application> you simple click the application icon in the system tray and select the wireless network you want to connect to. When you click on a network that has encryption enabled, you will get a pop-up dialog to enter this information. Once entered, this information is stored within the <application>KWallet</application> utility. This allows you to connect to that network in the future just by entering your <application>KWallet</application> password."
298
#: network/C/network.xml:479(title)
322
#: network/C/network.xml:493(para)
323
msgid "Since kernel version 2.6.17, support for Broadcom wireless devices were included. This means that there are some Broadcom devices that work out of the box, however there are still many that don't. If your Broadcom wireless device isn't working then you have two choices; <application>bcm43xx-fwcutter</application> or <application>NdisWrapper</application>."
326
#: network/C/network.xml:501(para)
327
msgid "With the <application>bcm43xx-fwcutter</application> utility there are only a select few devices that actually work. To see the devices that are currently supported please review <ulink url=\"http://bcm43xx.berlios.de/?go=devices\"/>. If your device is not supported then it is advised that you use the <application>NdisWrapper</application> utility. For information on configuring your device with the <application>bcm43xx-fwcutter</application> utility please see <xref linkend=\"network-connect-wifi-bcm43xx\"/> and for configuring your device with <application>NdisWrapper</application> utility please see <xref linkend=\"network-connect-wifi-ndiswrapper\"/>."
330
#: network/C/network.xml:519(title)
299
331
msgid "NdisWrapper"
302
#: network/C/network.xml:482(title)
334
#: network/C/network.xml:522(title)
303
335
msgid "Command Line Intensive"
306
#: network/C/network.xml:483(para)
338
#: network/C/network.xml:523(para)
307
339
msgid "Configuration of <application>NdisWrapper</application> is command line intensive. There are currently no graphical clients to aide in this configuration. Even though it is command line oriented, the instructions are easy to follow."
310
#: network/C/network.xml:491(para)
311
msgid "<application>NdisWrapper</application> is considered the wireless fix-all for Linux. A great percentage of wireless adapters that are not supported natively or with other utilities are supported with <application>NdisWrapper</application>. Installation is the same as it is for any other application in Kubuntu. If you are uncomfortable with installation practices then it is advised that you review the <ulink url=\"help:/kubuntu/add-applications/\">Adding Applications</ulink> document."
314
#: network/C/network.xml:501(para)
315
msgid "Once you have installed <application>NdisWrapper</application> your next step would be to locate the Windows drivers either on a <acronym>CD</acronym> or the Internet. Drivers for Windows XP are preferred, however Windows 2000 drivers will usually work just as well. Once you have located the CD or the drivers on the Internet, you will want to copy them to a local folder on your system. In some instances, you may have your drivers in a <filename>driver.zip</filename> or a <filename>driver.exe</filename> file. If it the file is in a <filename>.zip</filename> format, you can unzip the file by either <mousebutton>right</mousebutton> clicking on the file and selecting <guilabel>Extract</guilabel> from the pop-up menu. If the file is in a <filename>.exe</filename> format, then you will have to install the <application>cabextract</application> utility and open up <application>Konsole</application> to navigate the correct directory. Once you have navigated to the directory storing the <filename>.exe</filename> file, you would type <userinput>cabextract filename.exe</userinput>. This will extract or unzip the file to the directory you are in. The driver will be in the <filename>.inf</filename> format, so what you will want to do is type <userinput>sudo ndiswrapper -i filename.inf</userinput> and press <keycap>Enter</keycap>. If successful you shouldn't receive any errors. This command has gone ahead and loaded or installed the drivers in the <application>NdisWrapper</application> module. To see if these drivers worked, simply type <userinput>sudo modprobe ndiswrapper</userinput> and press <keycap>Enter</keycap>. Test to see if you have a network and/or Internet connection."
318
#: network/C/network.xml:528(para)
342
#: network/C/network.xml:532(title)
343
msgid "Hardware Platforms"
346
#: network/C/network.xml:533(para)
347
msgid "This method is only supported for users of the Intel and AMD platforms. Users of older iBooks and Powerbooks cannot use this method. However, users of MacBooks (Intel based) should be able to use this method."
350
#: network/C/network.xml:540(para)
351
msgid "<application>NdisWrapper</application> is considered the wireless fix-all for Linux. A great percentage of wireless adapters that are not supported natively or with other utilities are supported with <application>NdisWrapper</application>. Install <application>ndiswrapper</application> by using <application>Adept</application>. If you are uncomfortable with installation practices then it is advised that you review the <ulink url=\"help:/kubuntu/add-applications/\">Adding Applications</ulink> document."
354
#: network/C/network.xml:551(para)
355
msgid "Once you have installed <application>NdisWrapper</application>, locate the Windows drivers either on a <acronym>CD</acronym> or the Internet. Drivers for Windows XP are preferred, however Windows 2000 drivers will usually work just as well. Once you have located the CD or the drivers on the Internet, copy them to a local folder on your system. In some instances, you may have your drivers in a <filename>driver.zip</filename> or a <filename>driver.exe</filename> file. If it the file is in a <filename>.zip</filename> format, unzip the file by either <mousebutton>right</mousebutton> clicking on the file and selecting <guilabel>Extract</guilabel> from the pop-up menu. If the file is in a <filename>.exe</filename> format, then install the <application>cabextract</application> utility and open up <application>Konsole</application> to navigate the correct directory. Once you have navigated to the directory storing the <filename>.exe</filename> file, type <userinput>cabextract filename.exe</userinput>. This will extract or unzip the file to the directory you are in. The driver will be in the <filename>.inf</filename> format, so what you will want to do is type <userinput>sudo ndiswrapper -i filename.inf</userinput> and press <keycap>Enter</keycap>. If successful you shouldn't receive any errors. This command has gone ahead and loaded or installed the drivers in the <application>NdisWrapper</application> module. To see if these drivers worked, simply type <userinput>sudo modprobe ndiswrapper</userinput> and press <keycap>Enter</keycap>. Test to see if you have a network and/or Internet connection."
358
#: network/C/network.xml:578(para)
319
359
msgid "If everything went well then the final step would be to load the <application>NdisWrapper</application> module by default. To do this simple type <userinput>sudo sh -c \"echo ndiswrapper >> /etc/modules\"</userinput> and press <keycap>Enter</keycap>. This will automatically start <application>NdisWrapper</application> at boot time."
322
#: network/C/network.xml:536(para)
362
#: network/C/network.xml:586(para)
323
363
msgid "If everything didn't go so well, the issue may not be with <application>NdisWrapper</application> but possibly with <application>KNetworkManager</application>. To see if in fact that <application>KNetworkManager</application> was at fault, simply click the system tray icon and select <guilabel>Quit</guilabel>. Once <application>KNetworkManager</application> has closed, go back to the command line and type <userinput>sudo modprobe -r ndiswrapper && sudo modprobe\nndiswrapper</userinput> and press <keycap>Enter</keycap>. This will unload <application>NdisWrapper</application> and then reload it. After you have reloaded it, test your network and/or Internet connection again."
326
#: network/C/network.xml:552(title)
366
#: network/C/network.xml:602(title)
330
#: network/C/network.xml:554(para)
370
#: network/C/network.xml:604(para)
331
371
msgid "Since the 6.10 (Edgy Eft) release, the kernel has included driver support for some Broadcom cards utilizing the <application>bcm43xx-fwcutter</application> utility. Currently there are not that many supported cards, however development continues. To see if your card is supported please review the list at <ulink url=\"http://bcm43xx.berlios.de/?go=devices\"/>. If your card is not included in the list, then refer to <xref linkend=\"network-connect-wifi-ndiswrapper\"/>."
334
#: network/C/network.xml:563(para)
374
#: network/C/network.xml:613(para)
335
375
msgid "To get started, the first thing you will need to do is install the <application>bcm43xx-fwcutter</application> utility. For more information on installing extra applications, please refer to the <ulink url=\"help:/kubuntu/add-applications/\">Adding Applications</ulink> section."
338
#: network/C/network.xml:570(para)
339
msgid "Once you have <application>bcm43xx-fwcutter</application> installed you can read through a list of links to various drivers for your Broadcom device. To do this open up <application>Konsole</application> (<menuchoice><guimenu>KMenu</guimenu><guisubmenu>System</guisubmenu><guimenuitem>Konsole = Terminal Program</guimenuitem></menuchoice>) and type at the prompt <userinput>zless /usr/share/doc/bcm43xx-fwcutter/README.gz</userinput> and press <keycap>Enter</keycap>. You have the choice of picking a driver from that list, driver CD, or manufacturer's website. The file you are interested in using is the <filename>bcwl5.sys</filename> file. If you have the drivers in a <filename>.zip</filename> format, unzip the files to a local directory. If the drivers are in a <filename>.exe</filename> format, you will need to install <application>Cabextract</application>. With <application>Cabextract</application>, at the command line locate the directory where you downloaded or copied the file to. Once there type at the prompt <userinput>cabextract filename.exe</userinput> and press <keycap>Enter</keycap>. This will extract the file into the directory you are in."
378
#: network/C/network.xml:620(para)
379
msgid "Once you have <application>bcm43xx-fwcutter</application> installed you can read through a list of links to various drivers for your Broadcom device. To do this open up <application>Konsole</application> (<menuchoice><guimenu>KMenu</guimenu><guisubmenu>System</guisubmenu><guimenuitem>Konsole - Terminal Program</guimenuitem></menuchoice>) and type at the prompt <userinput>zless /usr/share/doc/bcm43xx-fwcutter/README.gz</userinput> and press <keycap>Enter</keycap>. You have the choice of picking a driver from that list, driver CD, or manufacturer's website. The file you are interested in using is the <filename>bcwl5.sys</filename> file. If you have the drivers in a <filename>.zip</filename> format, unzip the files to a local directory. If the drivers are in a <filename>.exe</filename> format, you will need to install <application>Cabextract</application>. With <application>Cabextract</application>, at the command line locate the directory where you downloaded or copied the file to. Once there type at the prompt <userinput>cabextract filename.exe</userinput> and press <keycap>Enter</keycap>. This will extract the file into the directory you are in."
342
#: network/C/network.xml:588(para)
382
#: network/C/network.xml:638(para)
343
383
msgid "Now that you have the driver files extracted, navigate with <application>Konsole</application> to the directory with the driver files. Next you will use the <application>bcm43xx-fwcutter</application> utility to install the drivers. To do so, at the prompt type <userinput>sudo bcm43xx-fwcutter -w\n/lib/firmware/$(uname -r) bcwl5.sys</userinput>. You may receive a couple of warnings which are nothing to worry about. If it didn't work, it will provide an error that states either driver isn't supported or the driver is to old. If this is the case, you would repeat this step using one of the drivers from the list in the <filename>README.gz</filename> file shown above. If you continue to have issues, connect to the Internet with another source and review the following sites: <placeholder-1/> If you continue to have issues with loading the drivers, then you may need to use the <application>NdisWrapper</application> utility."
346
#: network/C/network.xml:609(para)
386
#: network/C/network.xml:659(para)
347
387
msgid "Now if you went through the driver installation without any major errors or issues, the next step would be to load the new module you created in the previous step. At the command line type <userinput>sudo modprobe\nbcm43xx</userinput> and press <keycap>Enter</keycap>. To see if the module loaded and is working, at the prompt type <userinput>iwconfig</userinput> and press <keycap>Enter</keycap>. If it works it should return the name of the interface as <acronym>ethX</acronym> where X is the number of the device. In most cases it may be <acronym>eth1</acronym> if you have a <acronym>CAT-5</acronym> Ethernet device already installed and configured. Also to test and see if your device can scan, at the command prompt type <userinput>sudo iwlist ethX scan</userinput> and press <keycap>Enter</keycap>. Don't worry if it reports <emphasis>no networks found</emphasis> as your connection may still be working. Test and see if you can connect to your network and the Internet. If everything has worked then you will want to add the module so it will load at boot. To do so, at the command prompt type <userinput>sudo sh -c \"echo bcm43xx >> /etc/modules\"</userinput> and press <keycap>Enter</keycap>."
350
#: network/C/network.xml:635(title)
390
#: network/C/network.xml:685(title)
354
#: network/C/network.xml:638(title)
394
#: network/C/network.xml:688(title)
358
#: network/C/network.xml:641(para)
398
#: network/C/network.xml:691(para)
359
399
msgid "Please refer to <ulink url=\"https://help.ubuntu.com/community/ADSLPPPoE\"/> for further information if you run into issues with the following procedures."
362
#: network/C/network.xml:648(title)
402
#: network/C/network.xml:698(title)
363
403
msgid "PPPoE ADSL Modem Installation"
366
#: network/C/network.xml:652(para) network/C/network.xml:910(para)
367
msgid "Open <application>Konsole</application> by going to <menuchoice><guimenu>KMenu</guimenu><guisubmenu>System</guisubmenu><guimenuitem>Konsole = Terminal Program</guimenuitem></menuchoice>."
406
#: network/C/network.xml:702(para) network/C/network.xml:960(para)
407
msgid "Open <application>Konsole</application> by going to <menuchoice><guimenu>KMenu</guimenu><guisubmenu>System</guisubmenu><guimenuitem>Konsole - Terminal Program</guimenuitem></menuchoice>."
370
#: network/C/network.xml:658(para)
410
#: network/C/network.xml:708(para)
371
411
msgid "At the command prompt type <userinput>sudo pppoeconf</userinput> and press <keycap>Enter</keycap>."
374
#: network/C/network.xml:665(para)
414
#: network/C/network.xml:715(para)
375
415
msgid "A text-based menu program will guide you through the next steps, which are:"
378
#: network/C/network.xml:670(para)
418
#: network/C/network.xml:720(para)
379
419
msgid "Confirm that your Ethernet card is detected."
382
#: network/C/network.xml:675(para)
422
#: network/C/network.xml:725(para)
383
423
msgid "Enter your username provided by your <acronym>ISP</acronym>."
386
#: network/C/network.xml:680(para)
426
#: network/C/network.xml:730(para)
387
427
msgid "Enter your password provided by your <acronym>ISP</acronym>."
390
#: network/C/network.xml:685(para)
430
#: network/C/network.xml:735(para)
391
431
msgid "If you already have a <acronym>PPPoE</acronym> connection configured, you will be asked if it may be modified."
394
#: network/C/network.xml:691(para)
434
#: network/C/network.xml:741(para)
395
435
msgid "When asked if you want the <option>noauth</option> and the <option>defaultroute</option> options and want to remove the <option>nodetach</option> option, choose <emphasis role=\"bold\">Yes</emphasis>."
398
#: network/C/network.xml:698(para)
438
#: network/C/network.xml:748(para)
399
439
msgid "When asked if you want to use <option>peer DNS</option>, choose <emphasis role=\"bold\">Yes</emphasis>."
402
#: network/C/network.xml:704(para)
442
#: network/C/network.xml:754(para)
403
443
msgid "When asked if you want the <option>Limited MSS</option>, choose <emphasis role=\"bold\">Yes</emphasis>."
406
#: network/C/network.xml:710(para)
446
#: network/C/network.xml:760(para)
407
447
msgid "When asked if you want to connect at start up, select <emphasis role=\"bold\">Yes</emphasis> to enable a start up connection, or <emphasis role=\"bold\">No</emphasis> to manually connect."
410
#: network/C/network.xml:717(para)
450
#: network/C/network.xml:767(para)
411
451
msgid "When asked if you want to connect immediately, select the appropriate response."
414
#: network/C/network.xml:725(para)
454
#: network/C/network.xml:775(para)
415
455
msgid "To start your <acronym>ADSL</acronym> connection on demand type <userinput>pon\ndsl-provider</userinput> and press <keycap>Enter</keycap>."
418
#: network/C/network.xml:732(para)
458
#: network/C/network.xml:782(para)
419
459
msgid "To stop your <acronym>ADSL</acronym> connection type <userinput>poff\ndsl-provider</userinput> and press <keycap>Enter</keycap>."
422
#: network/C/network.xml:742(title)
462
#: network/C/network.xml:792(title)
423
463
msgid "USB ADSL Modem Installation"
426
#: network/C/network.xml:744(para)
466
#: network/C/network.xml:794(para)
427
467
msgid "Due to similar issues of that with a Winmodem, installation and configuration of a <acronym>USB</acronym><acronym>ADSL</acronym> modem may require lengthy procedures depending on the type of modem. For further installation information, pleas refer to <ulink url=\"https://help.ubuntu.com/community/UsbAdslModem\"/>. You will of course need another means of connection in order to review this documentation."
430
#: network/C/network.xml:757(title)
470
#: network/C/network.xml:807(title)
434
#: network/C/network.xml:763(term)
474
#: network/C/network.xml:813(term)
435
475
msgid "Software Modems"
438
#: network/C/network.xml:765(para)
478
#: network/C/network.xml:815(para)
439
479
msgid "Software modems, also known as Winmodems, are the type that are usually built into the system itself whether it is a desktop or a laptop. These modems are usually connected to a <acronym>PCI</acronym> port inside of the computer or a <acronym>USB</acronym> port outside of the computer. There are still quite a few of these types of modems that are not supported by Linux due to the type of binary driver or firmware they use. Winmodems supported in Linux are also known as Linmodems."
442
#: network/C/network.xml:777(term)
482
#: network/C/network.xml:827(term)
443
483
msgid "Hardware Modems"
446
#: network/C/network.xml:779(para)
486
#: network/C/network.xml:829(para)
447
487
msgid "Hardware modems, or true modems, are usually connected to the serial port outside of the computer and process the raw modem commands unlike a Winmodem. These types of modems have become rare of late however they still stand as the most supported type of modem for Linux as they typically do not need a special driver."
450
#: network/C/network.xml:759(para)
490
#: network/C/network.xml:809(para)
451
491
msgid "Many people still access the Internet via a dial-up modem today. There are two basic types of dial-up modems in use. <placeholder-1/>"
454
#: network/C/network.xml:791(para)
494
#: network/C/network.xml:841(para)
455
495
msgid "The following sections will provide information on installation and configuration of your modem. The last section will provide configuration information on configuring a dial-up connection (see <xref linkend=\"dialup-config\"/>)."
458
#: network/C/network.xml:799(title)
498
#: network/C/network.xml:849(title)
459
499
msgid "Winmodem Installation"
462
#: network/C/network.xml:801(para)
502
#: network/C/network.xml:851(para)
463
503
msgid "Unfortunately due to the many different types of chipsets and the work involved in getting a Winmodem installed and functioning would be difficult to document in this one location. However, there are already documents out there to help you in your success at getting your Winmodem to work with Kubuntu. Not every Winmodem is guaranteed to work, but there are utilities out there to aide you in getting a supported Winmodem to work. The following links will hopefully provide the information needed to get your Winmodem working."
466
#: network/C/network.xml:813(para)
506
#: network/C/network.xml:863(para)
467
507
msgid "<ulink url=\"http://www.linmodems.org/\"/> - This site is the main informational point for getting Winmodems, or Linmodems as they are also known as, installed and working in Linux."
470
#: network/C/network.xml:821(para)
510
#: network/C/network.xml:871(para)
471
511
msgid "<ulink url=\"http://132.68.73.235/linmodems/index.html#scanmodem\"/> - This site provides useful information on the <application>scanModem</application> utility. This is the utility that will not only detect your Winmodem, but it will also provide information on the type of support for your device."
474
#: network/C/network.xml:830(para)
514
#: network/C/network.xml:880(para)
475
515
msgid "<ulink url=\"https://help.ubuntu.com/community/DialupModemHowto/ScanModem\"/> - Ubuntu community documentation on utilizing the <application>scanModem</application> utility within Ubuntu and Kubuntu."
478
#: network/C/network.xml:838(para)
518
#: network/C/network.xml:888(para)
479
519
msgid "<ulink url=\"https://help.ubuntu.com/community/DialupModemHowto\"/> - Ubuntu community documentation on general dial-up modem information. A good starting point for Ubuntu and Kubuntu systems alike."
482
#: network/C/network.xml:846(para)
522
#: network/C/network.xml:896(para)
483
523
msgid "<ulink url=\"http://start.at/modem\"/> - Winmodems are not modems website that contains a very broad database of Winmodem support. Use this to further verify support for your modem, or research the list first before trying to install a device that may not be supported."
486
#: network/C/network.xml:858(title)
526
#: network/C/network.xml:908(title)
487
527
msgid "Hardware Modem Installation"
490
#: network/C/network.xml:860(para)
530
#: network/C/network.xml:910(para)
491
531
msgid "Unlike software modems, or Winmodems, hardware modems do not need special software drivers. If your modem connects to your <acronym>PC</acronym> via the serial port, then you are in fact using a hardware modem. In order to configure your modem, you need to know which <acronym>COM</acronym> port, or serial port, you are using. The typical structure for <acronym>COM</acronym> devices is <filename>/dev/ttySx</filename>, where x is one less than the <acronym>COM</acronym> port number. For instance, if you plug your modem into <acronym>COM</acronym> port 1, then you would use the <filename>/dev/ttyS0</filename> device. Port 2 would be <filename>/dev/ttyS1</filename> and so on."
494
#: network/C/network.xml:876(title)
534
#: network/C/network.xml:926(title)
495
535
msgid "Dial-up Internet configuration"
498
#: network/C/network.xml:878(para)
538
#: network/C/network.xml:928(para)
499
539
msgid "There are a few ways in order for you to get your dial-up connection working with the Internet."
502
#: network/C/network.xml:884(title)
542
#: network/C/network.xml:934(title)
503
543
msgid "Using KPPP"
506
#: network/C/network.xml:886(para)
546
#: network/C/network.xml:936(para)
507
547
msgid "<application>KPPP</application> - The dialer and front end for <application>pppd</application> which allows for interactive script generation and network setup. This is the preferred application in Kubuntu for dial-up modems. For more information on setting up <application>KPPP</application>, please refer to <ulink type=\"help\" url=\"help:/kppp\">The KPPP Handbook</ulink>."
510
#: network/C/network.xml:898(title)
550
#: network/C/network.xml:948(title)
511
551
msgid "Using WvDial"
514
#: network/C/network.xml:900(para)
554
#: network/C/network.xml:950(para)
515
555
msgid "<application>WvDial</application> - The command line Linux application for dial-up modems. This utility has been around almost since the invention of Linux itself. The following is a quick step-by-step procedure for using <application>WvDial</application>. Note that <application>WvDial</application> use is command line intensive."
518
#: network/C/network.xml:916(para)
558
#: network/C/network.xml:966(para)
519
559
msgid "At the command prompt, type <userinput>sudo wvdialconf\n/etc/wvdial.conf</userinput> and then press <keycap>Enter</keycap>."
522
#: network/C/network.xml:920(title)
562
#: network/C/network.xml:970(title)
526
#: network/C/network.xml:921(para)
566
#: network/C/network.xml:971(para)
527
567
msgid "If you see the following error, then your modem is not supported, in use, or not properly configured."
530
#: network/C/network.xml:926(screen)
570
#: network/C/network.xml:976(screen)
532
572
msgid "\nEditing `/etc/wvdial.conf'.\n\nScanning your serial ports for a modem.\n\nModem Port Scan<*1>: S0 S1 S2 S3\n\n\nSorry, no modem was detected! Is it in use by another program?\nDid you configure it properly with setserial?\n\nPlease read the FAQ at http://open.nit.ca/wiki/?WvDial\n\nIf you still have problems, send mail to <wvdial-list@lists.nit.ca>.\n"
535
#: network/C/network.xml:944(para)
575
#: network/C/network.xml:994(para)
536
576
msgid "If you did not receive the previous error message then you can move on and finish the setup by manually editing the <filename>/etc/wvdial.conf</filename> configuration file. To do so press <keycombo><keycap>Alt</keycap><keycap>F2</keycap></keycombo>, type <userinput>kdesu kwrite /etc/wvdial.conf</userinput> and press the <keycap>OK</keycap> button."
539
#: network/C/network.xml:955(para)
579
#: network/C/network.xml:1005(para)
540
580
msgid "After opening the <filename>wvdial.conf</filename>, insert your <acronym>ISP</acronym> information where needed. Other options may be needed in order to get your Winmodem to work correctly. This information is either available on the <ulink url=\"http://www.linmodems.org/\">Linmodems</ulink> website, or if you sent an email to their mailing-list, the information they provided to aide you in your setup. You can also type <userinput>man\nwvdial.conf</userinput> at the command prompt for further information."
543
#: network/C/network.xml:967(para)
583
#: network/C/network.xml:1017(para)
544
584
msgid "Save and close out of the <filename>/etc/wvdial.conf</filename> configuration file."
547
#: network/C/network.xml:974(para)
587
#: network/C/network.xml:1024(para)
548
588
msgid "At the command line, try to dial out by typing <userinput>sudo\nwvdial</userinput> and pressing <keycap>Enter</keycap>."
551
#: network/C/network.xml:985(title)
591
#: network/C/network.xml:1035(title)
552
592
msgid "Using pppconfig with pon & poff"
555
#: network/C/network.xml:987(para)
595
#: network/C/network.xml:1037(para)
556
596
msgid "<application>pppconfig</application> is another command line option used to manage dial-up connections. This setup is not the easiest to configure, however it is a very flexible application. The <application>pon</application> and <application>poff</application> dial and hang-up when using the <application>pppconfig</application> utility."
559
#: network/C/network.xml:995(para)
599
#: network/C/network.xml:1045(para)
560
600
msgid "If you are interested in using this utility, please refer to the <ulink url=\"https://help.ubuntu.com/community/DialupModemHowto/SetUpDialer#head- 0769b0061bf81bfba710118540bd86223e815761\">wiki topic for pppconfig</ulink>."
563
#: network/C/network.xml:1008(title)
603
#: network/C/network.xml:1058(title)
564
604
msgid "Network sharing"
567
#: network/C/network.xml:1015(application) network/C/network.xml:1053(title)
607
#: network/C/network.xml:1065(application) network/C/network.xml:1103(title)
571
#: network/C/network.xml:1017(para)
611
#: network/C/network.xml:1067(para)
572
612
msgid "Provides file and print services to all <acronym>SMB</acronym>/<acronym>CIFS</acronym> clients, including Microsoft Windows. <acronym>Samba</acronym> is the recommended way to connecting to your Microsoft shares and the easiest to setup and configure."
575
#: network/C/network.xml:1027(application) network/C/network.xml:1088(acronym)
615
#: network/C/network.xml:1077(application) network/C/network.xml:1138(acronym)
579
#: network/C/network.xml:1029(para)
619
#: network/C/network.xml:1079(para)
580
620
msgid "Network File System supports sharing of files, printers and resources over a network. <application>NFS</application> is more difficult to setup and configure however it contains extra features and added benefits to an all Linux network."
583
#: network/C/network.xml:1039(application)
623
#: network/C/network.xml:1089(application)
587
#: network/C/network.xml:1041(para)
627
#: network/C/network.xml:1091(para)
588
628
msgid "Zero Configuration Networking is a system that automatically creates an <acronym>IP</acronym> network without configuration or servers. This type of setup allows users without the knowledge of networking to easily configure a simple network."
591
#: network/C/network.xml:1010(para)
631
#: network/C/network.xml:1060(para)
592
632
msgid "Network sharing in Kubuntu, or Linux in general is easy and only requires very little configuration. Three quick choices are <placeholder-1/>"
595
#: network/C/network.xml:1055(para)
635
#: network/C/network.xml:1105(para)
596
636
msgid "If you are using a Windows network, then <application>Samba</application> may be your choice and configuration does not require use of the command line. To start simply press <keycombo><keycap>Alt</keycap><keycap>F2</keycap></keycombo> and type <userinput>kdesu kwrite /etc/samba/smb.conf</userinput> and press the <guibutton>Run</guibutton> button. This will open the <application>KWrite</application> text editor. Navigate down just below the <guilabel>Global Settings</guilabel> section to where it says <guilabel>workgroup = MSHOME</guilabel> and change out the <guilabel>MSHOME</guilabel> to match your Windows workgroup. Save the file and close <application>KWrite</application>. The next step is to install <application>Samba</application>. For more information on installation please review the section <ulink url=\"help:/kubuntu/add-applications\">Adding Applications</ulink>."
599
#: network/C/network.xml:1071(para)
639
#: network/C/network.xml:1121(para)
600
640
msgid "Using the icons located in the <application>Kicker</application>, the terminal looking icon (<application>System Menu</application>) to the immediate right of the <application>KMenu</application> icon will allow you to navigate to <guilabel>Remote Places</guilabel>. Once you have navigated to there, you will be able to access <guilabel>Samba Shares</guilabel>."
603
#: network/C/network.xml:1079(para)
643
#: network/C/network.xml:1129(para)
604
644
msgid "For more information, further instructions, or advanced features of <application>Samba</application> please review <ulink url=\"https://help.ubuntu.com/community/SettingUpSamba\"/>."
607
#: network/C/network.xml:1090(para)
647
#: network/C/network.xml:1140(para)
608
648
msgid "<acronym>NFS</acronym>, or Network File System, is a file system supporting the sharing of files, printers and resources permanently over a network. <acronym>NFS</acronym> is much more advanced and difficult than <application>Samba</application>. Considering <acronym>NFS</acronym> is a very extensive protocol for file sharing, this portion of the Kubuntu System Documentation will ask you to review the following sites for further information: <placeholder-1/>"
611
#: network/C/network.xml:1120(title)
651
#: network/C/network.xml:1170(title)
612
652
msgid "ZeroConf Networking"
615
#: network/C/network.xml:1122(para)
655
#: network/C/network.xml:1172(para)
616
656
msgid "<acronym>ZeroConf</acronym>, or Zero Configuration Networking, is a system that automatically creates an <acronym>IP</acronym> network without special configurations or servers. This type of networking and sharing is by far the most simple and is targeted to users with little or no networking knowledge. <acronym>ZeroConf</acronym> allows a user to to connect to computers, networked printers, and other shareable resources on the network without configuring network settings by hand."
619
#: network/C/network.xml:1133(title)
659
#: network/C/network.xml:1183(title)
620
660
msgid "ZeroConf Configuration"
623
#: network/C/network.xml:1135(para)
663
#: network/C/network.xml:1185(para)
624
664
msgid "Open <application>System Settings</application> by going to <menuchoice><guimenu>KMenu</guimenu><guimenuitem>System Settings</guimenuitem></menuchoice>."
627
#: network/C/network.xml:1141(para)
667
#: network/C/network.xml:1191(para)
628
668
msgid "Select <guilabel>Network Settings</guilabel>."
631
#: network/C/network.xml:1147(para)
671
#: network/C/network.xml:1197(para)
632
672
msgid "In the left hand side of the <application>Network Settings</application> dialog, select the <guilabel>Zeroconf Service Discovery</guilabel> option."
635
#: network/C/network.xml:1154(para)
675
#: network/C/network.xml:1204(para)
636
676
msgid "If the <guilabel>Enable Zeroconf network browsing</guilabel> or the <guilabel>Browse local network</guilabel> options are not selected, please select them now and press the <guibutton>Apply</guibutton> button."
639
#: network/C/network.xml:1163(title)
679
#: network/C/network.xml:1213(title)
640
680
msgid "Accessing network shares"
643
#: network/C/network.xml:1165(para)
683
#: network/C/network.xml:1215(para)
644
684
msgid "Select <guimenuitem>Remote Places</guimenuitem> from the <guibutton>System Menu</guibutton> icon located to the immediate right of the <application>KMenu</application>."
647
#: network/C/network.xml:1173(para)
687
#: network/C/network.xml:1223(para)
648
688
msgid "To view other <acronym>ZeroConf</acronym> systems, select <guilabel>Network Services</guilabel> from the main window."
651
#: network/C/network.xml:1180(para)
691
#: network/C/network.xml:1230(para)
652
692
msgid "To view all available systems on your network, select <guilabel>Samba Shares</guilabel> from the main window."
655
#: network/C/network.xml:1192(title)
695
#: network/C/network.xml:1242(title)
656
696
msgid "Networking Applications"
659
#: network/C/network.xml:1194(para)
699
#: network/C/network.xml:1244(para)
660
700
msgid "Kubuntu has a a great deal of applications designed around networking. Whether it is network monitoring, network security, or many others, Kubuntu has a solution for you. For more information on some of the available networking applications for Kubuntu, please see: <placeholder-1/>"
663
#: network/C/network.xml:1208(title)
703
#: network/C/network.xml:1258(title)
664
704
msgid "KNetworkManager"
667
#: network/C/network.xml:1220(para)
707
#: network/C/network.xml:1270(para)
668
708
msgid "Wired Ethernet (<acronym>IEEE</acronym> 802.3)"
671
#: network/C/network.xml:1226(para)
711
#: network/C/network.xml:1276(para)
672
712
msgid "Wireless Ethernet (<acronym>IEEE</acronym> 802.11): Unencrypted, WEP, WPA (Personal and Enterprise)"
675
#: network/C/network.xml:1233(para)
715
#: network/C/network.xml:1283(para)
676
716
msgid "Virtual Private Network (<acronym>VPN</acronym>): <application>OpenVPN</application>, <application>VPNC</application>"
679
#: network/C/network.xml:1240(para)
719
#: network/C/network.xml:1290(para)
680
720
msgid "Dial-Up (<acronym>PPP</acronym>)"
683
#: network/C/network.xml:1210(para)
723
#: network/C/network.xml:1260(para)
684
724
msgid "<application>KNetworkManager</application> is the KDE front end for <application>NetworkManager</application>. Providing a sophisticated yet intuitive user interface, <application>KNetworkManager</application> allows users to easily switch their network environment. <application>KNetworkManager</application> is installed with every Kubuntu system. The following is a brief list of the devices that <application>KNetworkManager</application> supports: <placeholder-1/>"
687
#: network/C/network.xml:1248(para)
727
#: network/C/network.xml:1298(para)
688
728
msgid "More information can be found on the <application>KNetworkManager</application> website located at <ulink url=\"http://en.opensuse.org/Projects/KNetworkManager\"/>."
691
#: network/C/network.xml:1257(title)
731
#: network/C/network.xml:1307(title)
692
732
msgid "Wireshark"
695
#: network/C/network.xml:1259(para)
735
#: network/C/network.xml:1309(para)
696
736
msgid "<application>Wireshark</application> is a network traffic analyzer, or \"sniffer\", used to capture packets off the wire while decoding numerous protocols. More information can be found on the <application>Wireshark</application> website located at <ulink url=\"http://www.wireshark.org/\"/>."
699
#: network/C/network.xml:1267(para)
739
#: network/C/network.xml:1317(para)
700
740
msgid "<application>Wireshark</application> isn't installed initially with Kubuntu. Installation is easy using <application>Adept</application>. For more information on installing extra applications with Kubuntu, please see the <ulink url=\"help:/kubuntu/add-applications/\">Adding Applications</ulink> document."
703
#: network/C/network.xml:1276(title)
743
#: network/C/network.xml:1326(title)
707
#: network/C/network.xml:1278(para)
747
#: network/C/network.xml:1328(para)
708
748
msgid "<application>EtherApe</application> graphically displays network activities. Active hosts are shown as circles of varying size, and the traffic among them is shown as lines of varying width. <application>EtherApe</application> is a <application>GNOME</application> application and requires the <application>GNOME</application> libraries. These libraries will automatically be installed and configured for you if you decide to use <application>EtherApe</application>. More information can be found on the <application>EtherApe</application> website located at <ulink url=\"http://etherape.sourceforge.net\"/>."
711
#: network/C/network.xml:1290(para)
751
#: network/C/network.xml:1340(para)
712
752
msgid "<application>EtherApe</application> isn't installed initially with Kubuntu. Installation is easy using <application>Adept</application>. For more information on installing extra applications with Kubuntu, please see the <ulink url=\"help:/kubuntu/add-applications/\">Adding Applications</ulink> document."
715
#: network/C/network.xml:1300(title)
755
#: network/C/network.xml:1350(title)
719
#: network/C/network.xml:1307(para)
759
#: network/C/network.xml:1357(para)
720
760
msgid "Novice to intermediate users who are not experts in <acronym>TCP/IP</acronym> networking and security"
723
#: network/C/network.xml:1314(para)
763
#: network/C/network.xml:1364(para)
724
764
msgid "Those users who don't want the hassle of dealing with cryptic shell scripts and ipchains or iptables parameters."
727
#: network/C/network.xml:1302(para)
767
#: network/C/network.xml:1352(para)
728
768
msgid "<application>Guarddog</application> is a firewall configuration utility for KDE. It is aimed at two groups of users: <placeholder-1/> More information can be found on the <application>Guarddog</application> website located at <ulink url=\"http://www.simonzone.com/software/guarddog/\"/>."
731
#: network/C/network.xml:1324(para)
771
#: network/C/network.xml:1374(para)
732
772
msgid "<application>Guarddog</application> isn't installed initially with Kubuntu. Installation is easy using <application>Adept</application>. For more information on installing extra applications with Kubuntu, please see the <ulink url=\"help:/kubuntu/add-applications/\">Adding Applications</ulink> document."