Revision 3 as of 2007-06-23 22:31:44

Clear message

Ubuntu Notes

Location of the WebMail plugins (extensions) for Thunderbird<br> <a href="http://webmail.mozdev.org/"> http://webmail.mozdev.org/</a> <hr> Installing Raid 1 on Existing Ubuntu Server<br> <a href="http://ascendwiki.cheme.cmu.edu/Installing_Raid_1_on_Existing_Ubuntu_Server"> http://ascendwiki.cheme.cmu.edu/Installing_Raid_1_on_Existing_Ubuntu_Server</a> <hr> How to Prepare Intel RAID Disk for Multi-boot<br> <a href="http://computerbits.wordpress.com/2007/01/04/how-to-prepare-intel-raid-disk-for-multi-boot/"> http://computerbits.wordpress.com/2007/01/04/how-to-prepare-intel-raid-disk-for-multi-boot/</a> <hr> How to find UUID of swap and whether any swap is being used: <pre> fdisk -l vol_id /dev/xxxx #(xxxx from above) free -m #shows swap total in MB </pre> <hr> How to find UUID of boot root partition: <pre> dumpe2fs -h /dev/xxxx|grep UUID # Shows current even if newly changed ls -l /dev/disk/by-uuid # CAUTION will not reflect changes until after reboot (see below) </pre> <hr> How to <b>CHANGE</b> UUID of boot root partition: <pre> tune2fs -U random /dev/xxxx </pre> <hr> <pre> How to get redhat version of vnc going on Ubuntu:

uninstall vnccommon, vncviewer, etc

sudo dpkg -i vnc_4.1.2-2_i386.deb

as root:

cd /usr/lib cp -ip /media/SANDISKFAT/libstdc++-3-libc6.2-2-2.10.0.so . #This was copied from a Red Hat AS3 machine ln -s libstdc++-3-libc6.2-2-2.10.0.so libstdc++-libc6.2-2.so.3 </pre> <hr> <a href="http://ubuntuforums.org/showthread.php?p=1773624"> Dual Monitor Support With Xinerama HowTo</a> <p> <a href="http://www.paralipsis.org/2006/01/enabling-xinerama-in-ubuntu/"> Enabling Xinerama in Ubuntu plus how to stop gdm while testing</a> <p> <a href="https://help.ubuntu.com/community/WifiDocs/NetworkManager"> Network Manager info: https://help.ubuntu.com/community/WifiDocs/NetworkManager</a> <p> To stop using ndiswrapper and start using native Broadcom Wireless driver:<br> <a href="https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Dapper"> https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Dapper </a> <p> Disable net interfaces from network-admin if you want to manage them from network-manager-gnome.<br> "...you need to disable the connection from network-admin to make it work with NetworkManager"<br> <a href="http://ubuntuforums.org/showthread.php?p=2153671"> http://ubuntuforums.org/showthread.php?p=2153671</a> <p> Managing Gnome keyring: http://ubuntuforums.org/showthread.php?t=157808 <hr> Ubuntu Bluetooth Setup: <a href="https://help.ubuntu.com/community/BluetoothSetup"> https://help.ubuntu.com/community/BluetoothSetup</a> <p> Bluetooth Skype and VoIP: https://help.ubuntu.com/community/BluetoothSkype <pre> $ sudo hcitool inq Inquiring ...

  • 00:03:89:DC:80:6F clock offset: 0x5c4f class: 0x200404

$ sudo hidd --search Inquiring ...

  • 00:03:89:DC:80:6F clock offset: 0x5c4a class: 0x200404

$ hcitool dev Devices:

  • hci0 00:16:38:C0:90:F7 #This is the Kensington dongle

$ sudo hidd --connect 00:03:89:DC:80:6F Can't get device information: Success

$ sudo hcitool name 00:03:89:DC:80:6F 645Plantronics

$ sudo hcitool info 00:03:89:DC:80:6F Requesting information ...

  • BD Address: 00:03:89:DC:80:6F Device Name: 645Plantronics LMP Version: 2.0 (0x3) LMP Subversion: 0xa5b Manufacturer: Cambridge Silicon Radio (10) Features: 0xbc 0xe8 0x01 0x00 0x18 0x18 0x00 0x00

</pre> <hr> WPA How-To: <a href="https://help.ubuntu.com/community/WifiDocs/WPAHowTo"> https://help.ubuntu.com/community/WifiDocs/WPAHowTo</a> <p> Linksys WMP54GS with Broadcom BCM4306 chipset under Linux 2.6 kernel: <br><a href="http://dossy.org/archives/000110.html"> http://dossy.org/archives/000110.html</a> <p> <a href="http://ubuntuforums.org/showthread.php?t=200408"> HOWTO: Send and Receive Hotmail through Evolution [or Thunderbird]</a> <br>Packages needed for the above: hotsmtp, hotway, inetutils-inetd

<p> <a href="http://www.neilturner.me.uk/2006/Apr/11/using_windows_live_mail_i.html"> Using Windows Live Mail in Thunderbird</a> <p> <a href="https://wiki.ubuntu.com/HardwareSupportMachinesLaptopsOthers"> Comments on success of eMachines M2350 with Dapper</a>

<ul> <li>All works except for sound by default. <li>For sound, in a mixer, disable all jack sense and external amplifier switches. NOTE: A gotcha

  • for me was that you first have to right-click on the speaker icon, select "Open Volume Control, select "Edit", select "Preferences", and in the "Select tracks to be visible" dialog, checkmark the various jack sense and external amplifier switches, then click on the mixer's "Switches" tab and UNcheck the various jack sense and external amplifier switches.

</ul> <hr> http://ubuntuforums.org/showthread.php?t=55564 <pre>Re: wrt54g host name not showing up

Try editing your /etc/dhcp3/dhclient.conf file and unremming/editing the line:

send host-name "yourhostnamehere";

Then do:

sudo /etc/init.d/networking restart sudo ifup eth0 Last edited by Joeak : December 5th, 2005 at 11:28 PM. </pre> <hr> <a href="http://users.piuha.net/martti/comp/ubuntu/raid.html">RAID-1 on Dapper</a> <p> <a href="https://help.ubuntu.com/community/FakeRaidHowto">RAID Howto</a> <p> <a href="http://ubuntuforums.org/archive/index.php/t-2557.html">HOWTO - Discovering and using existing sata raid (eg sil3112)</a> <pre> NFS howto

After modifying /etc/exports: sudo exportfs -ra

Restart Services If /etc/default/portmap was changed, portmap will need to be restarted: sudo /etc/init.d/portmap restart

The NFS kernel server will also require a restart: sudo /etc/init.d/nfs-kernel-server restart </pre> <hr> Updating to 6.06 "Dapper Drake" Release Candidate: <pre>gksudo "update-manager -d"</pre> <hr> <a href="http://gkismet.sourceforge.net/"> gkismet, a Gnome/Gtk perl based Kismet client </a> <hr> Python / GTK / GNOME applet for wireless configuration, similar to Windows XP "Zeroconf" wireless. Shows network status, available access points, and allows the user to connect to a specific AP. Stores WEP keys and handles DHCP: <a href="http://sourceforge.net/projects/gtkwifi">gtkwifi</a> <hr> <a href="https://wiki.ubuntu.com/WiFiHowto">WiFi Howto</a> <br> See also: Debian Packages: "netapplet" and "wifi-radar" <hr> <pre> bash: export HISTCONTROL=ignoredups </pre> <hr> These are the names of some utilities which can be used to access hotmail as POP from Thunderbird: <ul> <li>mrpostman (java, platform independent) <li>hotway <li>httpmail </ul> <hr> <a href="http://mparise.wordpress.com/2006/03/01/using-xdmcp-with-ubuntu-or-any-other-gdm-running-distro/"> Using XDMCP with Ubuntu (or any other GDM running distro) <hr> <a href="https://wiki.ubuntu.com/SettingUpNFSHowTo?action=show&redirect=NFSServerHowTo"> NFS Server and Client HowTo <hr> <a href="http://ubuntuforums.org/archive/index.php/t-7127.html"> .deb package installation</a> <HR> Installing Ubuntu  'dual boot' with Windows, for Absolute Beginners: <BR><A href="http://users.bigpond.net.au/hermanzone/">http://users.bigpond.net.au/hermanzone/</A><BR></DIV> <HR> Remote GUI Login: <br><A href="http://ubuntuforums.org/showthread.php?t=73199">http://ubuntuforums.org/showthread.php?t=73199</A> <DIV> </DIV> <DIV>Re: remote GUI login </DIV> <DIV> </DIV> <DIV>Offhand, I'm assuming that you don't want to use VNC for some reason.</DIV> <DIV> </DIV> <DIV>In that case, GDM configuration is where you want to go. You'll probably need to configure both machines though.</DIV> <DIV> </DIV> <DIV>System -> Administration -> Login Screen Setup...</DIV> <DIV> </DIV> <DIV>Under Security you probably want to add "Show Actions Menu" and "Allow Running XDMCP Chooser from the login screen". You will also need to switch to "Greeter: Local -> Standard Greeter" on the General tab. If you don't you won't get the Actions Menu. This is only needed on the machine that you want to use as a client (i.e. sit in front of)</DIV> <DIV> </DIV> <DIV>Under XDMCP select "Enable XDMCP" and make sure that you are allowing sessions. This is only needed on the machine that you want to connect to.</DIV> <DIV> </DIV> <DIV>Then you should be able to log out on the "client" and select Actions on the login screen and there should be a chooser option. That will allow you to choose which machine to connect to. Select the appropriate machine and log in...</DIV> <DIV> </DIV> <DIV> <HR> </DIV> <DIV> <DIV> </DIV> <DIV><FONT size=2><A href="http://ubuntuforums.org/showthread.php?t=139783">http://ubuntuforums.org/showthread.php?t=139783</A></FONT></DIV> <DIV> </DIV><FONT size=2></FONT></DIV> <DIV><FONT size=2><STRONG>General - HOWTO: Change auto fsck after "X" reboots</STRONG> <HR style="COLOR: #d9d2c3" SIZE=1> <!-- / icon and title --><!-- message --> <DIV id=post_message_793242>The default fsck (File system check) of your Ubuntu root partition is 30 reboots (or six months after the last reboot, whichever comes first). These settings are part of the ext2 filesystem that Ubuntu defaults to and can be easily changed, but to do so <B>you must be very careful with the command used as it could potentially do a lot of damage is used incorrectly!</B><BR><BR>If you want to change the count of when the auto fsck is done (to 20 instead of the default 30, for example), do (and replace the "your-filesystem-partition" with the appropriate hda or sda designation of your partition):<BR> <DIV style="MARGIN: 5px 20px 20px"> <DIV class=smallfont style="MARGIN-BOTTOM: 2px">Code:</DIV><PRE class=alt2 style="BORDER-RIGHT: 1px inset; PADDING-RIGHT: 6px; BORDER-TOP: 1px inset; PADDING-LEFT: 6px; PADDING-BOTTOM: 6px; MARGIN: 0px; OVERFLOW: auto; BORDER-LEFT: 1px inset; WIDTH: 640px; PADDING-TOP: 6px; BORDER-BOTTOM: 1px inset; HEIGHT: 34px"><DIV dir=ltr style="TEXT-ALIGN: left"><FONT size=3>sudo tune2fs -c20 /dev/your-filesystem-partition</FONT></DIV></PRE></DIV>To also set a fsck check after a certain period of time since the previous reboot (this example will set it to 1 week, "-i1d" would set the interval to 1 day, "-i1m" one month etc.), do:<BR> <DIV style="MARGIN: 5px 20px 20px"> <DIV class=smallfont style="MARGIN-BOTTOM: 2px">Code:</DIV><PRE class=alt2 style="BORDER-RIGHT: 1px inset; PADDING-RIGHT: 6px; BORDER-TOP: 1px inset; PADDING-LEFT: 6px; PADDING-BOTTOM: 6px; MARGIN: 0px; OVERFLOW: auto; BORDER-LEFT: 1px inset; WIDTH: 640px; PADDING-TOP: 6px; BORDER-BOTTOM: 1px inset; HEIGHT: 34px"><DIV dir=ltr style="TEXT-ALIGN: left"><FONT size=3>sudo tune2fs -i1w /dev/your-filesystem-partition</FONT></DIV></PRE></DIV>You can individually alter all of your ext2/ext3 filesystems in this way, and the tune2fs man page has many more options (like setting a partition label) which may be of use.<BR><BR>To see the settings for a particular ext2/ext3 filesystem:<BR> <DIV style="MARGIN: 5px 20px 20px"> <DIV class=smallfont style="MARGIN-BOTTOM: 2px">Code:</DIV><PRE class=alt2 style="BORDER-RIGHT: 1px inset; PADDING-RIGHT: 6px; BORDER-TOP: 1px inset; PADDING-LEFT: 6px; PADDING-BOTTOM: 6px; MARGIN: 0px; OVERFLOW: auto; BORDER-LEFT: 1px inset; WIDTH: 640px; PADDING-TOP: 6px; BORDER-BOTTOM: 1px inset; HEIGHT: 34px"><DIV dir=ltr style="TEXT-ALIGN: left"><FONT size=3>sudo dumpe2fs -h /dev/your-filesystem-partition</FONT></DIV></PRE></DIV></DIV><!-- / message --><!-- sig --> <DIV>Regards, David.<BR></DIV></FONT></DIV> <DIV><FONT size=2> </DIV> <DIV> <HR> </DIV></FONT> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Ndiswrapper HowTo:</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><A href=""><FONT size=2>https://wiki.ubuntu.com/WifiDocs/Driver/Ndiswrapper?highlight=%28ndiswrapper%29</FONT></A></DIV> <DIV> </DIV> <DIV> <H2 id=head-4b7c00c6654b2d109b9330c28d9210db329ba573>1. Introduction</H2> <UL>

  • <LI style="LIST-STYLE-TYPE: none"> <P>If your wireless network card does not have a native linux driver for it you can use the windows drivers with <STRONG class=highlight>ndiswrapper</STRONG>. <STRONG class=highlight>Ndiswrapper</STRONG> is a module in linux that allows linux to use the windows driver for wireless cards (in most cases). </P> <P>If you do not know what chipset your wifi card uses, issue the <TT>lspci</TT> command in a terminal. It should be listed there. In order to see if your chipset is known to work with the <STRONG class=highlight>ndiswrapper</STRONG> module, find your card in the list <A class=external href=""> here</A>. That link might even provide you with useful tips to get your specific card to work, as well as providing a link to the working Windows drivers. </P></LI></UL>

<P> Before going any further, are you using a Live CD? If you are, give up now. This won't work. </P> <P> If you are running ubuntu AMD64 bit, go to links section for instructions. </P> <H2 id=head-5b66eea3b1c2ff43e0afaae9814164fe8c7c3a17>2. Install Repository Version</H2> <H3 id=head-5ca809b3ca692f63119fb309fbf52a02a585fbeb>2.1. Install necessary packages</H3> <UL>

  • <LI style="LIST-STYLE-TYPE: none"> <P>Ubuntu comes with the necessary <STRONG class=highlight>ndiswrapper</STRONG> module pre-installed but it needs the <STRONG class=highlight>ndiswrapper</STRONG>-utils package to get it working. There is also a graphical interface to using <STRONG class=highlight>ndiswrapper</STRONG> which you can use. </P></LI></UL>

<H4 id=head-32af89fbc90498bd5ce957d6b475b913b42b9f7a>2.1.1. With internet access on ubuntu pc</H4> <UL>

  • <LI style="LIST-STYLE-TYPE: none"> <P>If you have internet access via some other method while logged into ubuntu, you can install the apps from the repositories. If you don't know how to install apps then you can read <A class=external href=""> how to here</A> </P></LI></UL>

<P> <EM>You may have to add the multiverse and universe repositories which is explained in the link.</EM> </P> <H4 id=head-c245d4db9d54182442aa9e4059ee00fd016b0849>2.1.2. With internet access from another pc</H4> <UL>

  • <LI style="LIST-STYLE-TYPE: none"> <P>If you do not have internet access you can go to a pc that has internet access and download these two packages. </P></LI></UL>

<OL type=1>

<P></P> <UL>

  • <LI style="LIST-STYLE-TYPE: none"> <P>Copy the appropriate files over to a directory on your ubuntu machine <EM>(a good location is /home/(user_name)/drivers)</EM> and install them <STRONG><U>in this order</U></STRONG>: </P><PRE> <FONT size=3>sudo dpkg -i <STRONG class=highlight>ndiswrapper</STRONG>-utils_1.1-4ubuntu2_i386.deb</FONT> </PRE><PRE> <FONT size=3>sudo dpkg -i ndisgtk_0.5-1ubuntu1_all.deb</FONT> </PRE></LI></UL>

<P> <EM>The commands listed above are a general example on how to install a .deb package from the command line. You need to be in the directory where the files were copied to and you need to replace the end with the actual package name you are installing. If you are new to the terminal, I suggest reading the <A class=badinterwiki title=BasicCommands href="">BasicCommands</A> page here on the wiki.</EM> </P> <H4 id=head-ca33fd114571c6d6326d1e7dc9e97d1c0a64ffe1>2.1.3. With no internet access</H4> <UL>

  • <LI style="LIST-STYLE-TYPE: none"> <P>With out any access you can still install <STRONG class=highlight>ndiswrapper</STRONG>-utils from the install cd but ndisgtk is not on the disk. Put the disk back in the drive, open up synaptic from System>Admin and search for ndis. If you do not know how to install apps, click on the lifepreserver on the top panel and read Ubuntu X.XX starter guide. </P></LI></UL><A id=install></A>

<P></P> <H3 id=head-ccd66d4fcaaab3a6e7a5c47162c1b7c6f52d41e5>2.2. Set up and install drivers</H3> <P> </P> <UL>

  • <LI style="LIST-STYLE-TYPE: none"> <P><STRONG>Important: Do NOT use drivers on your CD. They may work and you can try them, but you may experience kernel crashes etc., if the driver on your CD has not been tested. Instead, you need to download appropriate Windows XP driver for your card from the Wiki entry List. To identify the driver that you need, first identify the card you have with 'lspci' and note the first column such as 0000:00:0c.0 and then find out the PCI ID of the card that with 'lspci -n' corresponding to the first column of 'lspci' output. The PCI ID is third column or fourth in some distributions and of the form '104c:8400'. Now you need to get the Windows driver for this chipset. In the <A class=external href=""> list</A>, find out an entry for the same PCI ID and download the driver corresponding to it <EM>(don't worry if the link is not under your exact card as many cards you the same chipsets)</EM>. Unpack the Windows driver with unzip/cabextract/unshield tools and find the INF file (.INF or

  • inf extension) and the SYS file (.SYS or .sys extension). <EM>(this is important as some drivers have a connection with the .sys file which makes the driver work properly) If there are multiple INF/SYS files, you may look in the <A class=external href=""> List</A> if there are any hints about which of them should be used. Make sure the INF file, SYS file and any BIN files for example, TI drivers use BIN firmware files are all in one directory on your harddrive.</STRONG> </EM></P></LI></UL>

<P> The above statement is pulled from the <STRONG class=highlight>ndiswrapper</STRONG> wiki site. Your drivers from your cd may work and you can try them, it's not hard to remove and try a different driver. It might save you some time searching to find someone who has verified a driver and provide a download site. </P> <H4 id=head-c733381c7852759d2469bce16a33097d378d0605>2.2.1. ndisgtk instructions</H4> <UL>

  • <LI style="LIST-STYLE-TYPE: none"> <P>If you chose the ndisgtk route, after install, click on </EM>System > Admin > Windows wireless drivers<EM> and follow through the prompts. </EM></P></LI></UL>

<P> </EM>Some screen shots of ndisgtk can be found <A class=external href=""> here</A>.<EM> </EM></P> <H4 id=head-558430826c18c7a080e3eb11984fc8138cc2a4f2>2.2.2. Command line instructions</H4> <H5 id=head-d64243c23190a2de53a0bd32e070bc639e5006d2> Install the windows driver</H5> <UL>

  • <LI style="LIST-STYLE-TYPE: none"><PRE> <FONT size=3>sudo <STRONG class=highlight>ndiswrapper</STRONG> -i ~/drivers/{driver}.inf</FONT> </PRE> <P>(assuming the driver is in a directory in your home folder called <STRONG>drivers</STRONG>) </P></LI></UL>

<P> If file has spaces in name or it is named .INF, you will need to rename the file so there are no spaces and the file is in lower case letters. </P> <P><STRONG class=highlight>ndiswrapper</STRONG> copies the <TT><FONT size=3>.inf</FONT></TT> and <TT><FONT size=3>sys</FONT></TT> files into <TT><FONT size=3>/etc/<STRONG class=highlight>ndiswrapper</STRONG>/...</FONT></TT>. </P> <H5 id=head-30e7e1f16ec6d268e8600a99b739c4923b5a3ff9> checking to make sure it installed correctly.</H5> <UL>

  • <LI style="LIST-STYLE-TYPE: none"> <P>Run this command: </P><PRE> <FONT size=3><STRONG class=highlight>ndiswrapper</STRONG> -l</FONT> </PRE> <P>If this is installed correctly you should see: </P></LI></UL>

<P>   Installed ndis drivers:<BR>  {name of driver}  driver present, hardware present<BR>  </P> <UL>

  • <LI style="LIST-STYLE-TYPE: none"> <P>If you do NOT see this message. </P> <OL type=a>

    • <LI> <P>Try a different driver such as the drivers for win2k or another driver matching the pciid on the <A class=external href=""> <STRONG class=highlight>ndiswrapper</STRONG> list</A> </P> <LI> <P>There is a <A href="">troubleshooting</A> section, you can see if there is an answer there. </P> <LI> <P>Look for additional help at <A class=external href=""> the Ubuntu Forums</A>. </P></LI></OL></LI></UL>

<H5 id=head-c4fb6afc393e6473c8ae67938da0fe752bacb4fc> loading the new module.</H5> <UL>

  • <LI style="LIST-STYLE-TYPE: none"> <P>First run this command: </P><PRE> <FONT size=3>sudo depmod -a</FONT> </PRE> <P>then: </P><PRE><FONT size=3> sudo modprobe <STRONG class=highlight>ndiswrapper</STRONG>

</FONT> </PRE>

  • <P>Check for error messages: </P><PRE><FONT size=3> tail /var/log/messages</FONT> </PRE> <P>With no errors given you can go to the networking tool </EM>System > Administration > Networking<EM> and configure your device, or try the commands <TT><FONT size=3>ifconfig</FONT></TT> and <TT><FONT size=3>iwconfig</FONT></TT>. Your wireless card should now appear with an interface name of wlan0. If it doesn't appear here then the driver is not working properly. </EM></P> <P>During startup, the system will activate the settings kept in <TT><FONT size=3>/etc/network/interfaces</FONT></TT>. </EM>System > Administration > Networking<EM> saves settings there. Edit the file by hand if you discover settings with <TT><FONT size=3>iwconfig</FONT></TT> beyond those on offer in the Networking user interface. Also, the </EM>order<EM> of the wireless settings can be very important. If you discover that issuing <TT><FONT size=3>iwconfig</FONT></TT> commands </EM>in a certain order<EM> on the command line is necessary, make sure the file asserts the settings in the same order. </EM></P> <P>Test <TT><FONT size=3>/etc/network/interfaces</FONT></TT> by activating and deactivating the wireless network interface from the command line, which shows some diagnostic messages: </P><PRE> <FONT size=3>sudo ifdown wlan0</FONT> <FONT size=3>sudo ifup wlan0</FONT> </PRE></LI></UL>

<H4 id=head-c918018f2241f7b72b9d8c5296ae2c01bb370d8a>2.2.3. automatically load at boot-time</H4> <UL>

  • <LI style="LIST-STYLE-TYPE: none"> <P>If everything works, you need to tell your system to load the module on boot. Two ways you can do this are: </P><PRE> <FONT size=3>sudo <STRONG class=highlight>ndiswrapper</STRONG> -m</FONT> </PRE> <P>which will add the proper line to the /etc/modules file or you can add it manually by opening the file with this command: </P><PRE> <FONT size=3>sudo gedit /etc/modules

</FONT> </PRE>

  • <P>and add the word <TT><STRONG class=highlight><FONT size=3>ndiswrapper</FONT></STRONG></TT> to the end of this file and save. </P></LI></UL><A id=trouble></A>

<P></P> <H2 id=head-46777dc8e45dd15e9504db4c6f7e613b97036809>3. Troubleshooting</H2> <UL>

  • <LI> <P>If you can not get a working driver, you may want to consider compiling and using the latest <STRONG class=highlight>ndiswrapper</STRONG> release. Breezy comes with v1.1 As of Jan 2006 v1.8 is the stable release. </P> <LI> <P>Can not modprobe <STRONG class=highlight>ndiswrapper</STRONG>, fatal error given. </P> <UL>

    • <LI> <P>This error is usually given when <STRONG class=highlight>ndiswrapper</STRONG> is compiled and installed. You have a bad installation or you didn't remove the module that came with ubuntu. Need to uninstall <STRONG class=highlight>ndiswrapper</STRONG> and make sure you remove the <STRONG class=highlight>ndiswrapper</STRONG> module that came with ubuntu. Uninstall instructions can be found <A class=external href=""> here</A> </P></LI></UL></LI></UL>

<H3 id=head-c1d02586fd139d6e32f018b19392d255aa190a26>3.1. Some common errors</H3> <UL>

  • <LI> <P>Tried to install driver from cd-rom </P> <UL>

    • <LI> <P>The files need to be on your hard drive, they can not be loaded from the cd-rom </P></LI></UL>

    <LI> <P>Not all files are copied over to the hard drive </P> <UL>

    • <LI> <P>Not all files from the drive are needed. You basically need a inf and a

    • sys file. Some drivers also use a .bin file but there shouldn't be any

      other file type needed. </P></LI></UL>

    <LI> <P>Two many driver files copied to folder </P> <UL>

    • <LI> <P>You should only have 1 .inf and 1 .sys file in the directory on your hard drive. </P></LI></UL>

    <LI> <P>Can't get driver.inf file to install - </EM>file not found<EM> </EM></P> <UL>

    • <LI> <P>You have to be in the directory where the .inf file is or specify the full path to the file. </P></LI></UL>

    <LI> <P>Another driver loads and binds to the device </P> <UL>

    • <LI> <P>Sometimes <STRONG class=highlight>ndiswrapper</STRONG> is used prematuerly. There may be a native driver that comes with Ubuntu that's taking the primary driver position and conflicting with <STRONG class=highlight>ndiswrapper</STRONG>. For more about this go to the <A class=badinterwiki title=WirelessTroubleshootingGuide href="">WirelessTroubleshootingGuide</A> and the step on device drivers. </P></LI></UL></LI></UL>

<H2 id=head-2c7bea8535ee4a5b38d5be23825128a0ca1a932e>4. Compile latest version of <STRONG class=highlight>ndiswrapper</STRONG></H2> <UL>

  • <LI> <P>This HOWTO is based on <STRONG class=highlight>ndiswrapper</STRONG> <A class=external href=""> Wiki Page</A> </P> <LI> <P>This was copied from the forums, page found <A class=external href=""> here</A>. You can discuss any problems or errors there. </P> <LI> <P>It is recommended to remove any sign of <STRONG class=highlight>ndiswrapper</STRONG> from your pc. There is a module that installs by default with ubuntu. To do this, from a terminal run these commands: </P></LI></UL><BR>

<P></P> <UL>

  • <LI style="LIST-STYLE-TYPE: none"><PRE><FONT size=3> sudo modprobe -r <STRONG class=highlight>ndiswrapper</STRONG> sudo apt-get --purge remove <STRONG class=highlight>ndiswrapper</STRONG>-utils sudo rm -r /etc/<STRONG class=highlight>ndiswrapper</STRONG>/ sudo rm -r /etc/modprobe.d/<STRONG class=highlight>ndiswrapper</STRONG> sudo rm /lib/modules/uname -r/kernel/drivers/net/<STRONG class=highlight>ndiswrapper</STRONG>/<STRONG class=highlight>ndiswrapper</STRONG>.ko

</FONT> </PRE></LI></UL> <H3 id=head-c9be6f8b63abaf13f5116e844bc36fc9877f9f68>4.1. Install kernel headers:</H3> <UL>

  • <LI style="LIST-STYLE-TYPE: none"><PRE><FONT size=3> sudo apt-get install linux-headers-$(uname -r)

</FONT> </PRE>

  • <P>and dependencies: </P><PRE><FONT size=3> sudo apt-get install dh-make fakeroot gcc-3.4 build-essential

</FONT> </PRE></LI></UL> <H3 id=head-6345f001578cecd8a87c6a08c54f3cff434326f8>4.2. Download the current version</H3> <UL>

  • <LI style="LIST-STYLE-TYPE: none"> <P>You will find the current version of <STRONG class=highlight>ndiswrapper</STRONG> <A class=external href=""> here</A>. </P></LI></UL>

<H3 id=head-a9f35431d8bea593e38f368bc0151eb58df2d657>4.3. Untar</H3> <UL>

  • <LI style="LIST-STYLE-TYPE: none"> <P>Move to the file where you downloaded the file and run these commands. On the second command replace <TT><FONT size=3>[current version]</FONT></TT> with the actual version of the file you downloaded. </P><PRE><FONT size=3> tar xvfz <STRONG class=highlight>ndiswrapper</STRONG>-[current version].tar.gz cd <STRONG class=highlight>ndiswrapper</STRONG>-[current version]

</FONT> </PRE></LI></UL> <H3 id=head-bbdb07be021c1d80127fd52e14c732a350eb520b>4.4. Build deb packages:</H3> <UL>

  • <LI style="LIST-STYLE-TYPE: none"><PRE><FONT size=3> fakeroot debian/rules binary-modules fakeroot debian/rules binary-utils cd ..

</FONT> </PRE></LI></UL> <H3 id=head-32211f68d6a2ffd6d23e8fcbfc8056769adc2ec0>4.5. Install</H3> <UL>

  • <LI style="LIST-STYLE-TYPE: none"><PRE><FONT size=3> sudo dpkg -i <STRONG class=highlight>ndiswrapper</STRONG>-modules-[your kernel]_[current version]-1_i386.deb <STRONG class=highlight>ndiswrapper</STRONG>-utils_[current version]-1_i386.deb

</FONT> </PRE>

  • <P>Now go back to the <A href="">install</A> section to set up and use your newly installed <STRONG class=highlight>ndiswrapper</STRONG> package.

</P></LI></UL> <H2 id=head-eae8e4bdce437c9af9713924bbfad815f0843c42>5. WPA setup</H2> <P>This information has been moved to: <A href=""> https://wiki.ubuntu.com/WPAHowto</A> to reduce duplication </P> <H2 id=head-dbef3861e9af22273b9c4699abcda3f4787bc7b6>6. links</H2> <P><A class=external href=""> <STRONG class=highlight>ndiswrapper</STRONG> wiki</A> </P> <P><A class=external href=""> <STRONG class=highlight>Ndiswrapper</STRONG> on amd64 box</A> </P> <P><A class=badinterwiki title=WifiDocs href="">WifiDocs</A> </P> <H2 id=head-1862acdb364b93783b50d7cfec6f64ca00d3c3c3>7. FAQ</H2> <P> </P> <UL>

  • <LI style="LIST-STYLE-TYPE: none"> <P>There is a FAQ page being built for <STRONG class=highlight>ndiswrapper</STRONG>. You can read or add your question at this link: <A href="">WifiDocs/Driver/<STRONG class=highlight>Ndiswrapper</STRONG>/FAQ</A></P></LI></UL></DIV>

<DIV> </DIV> <DIV> <HR> </DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2></FONT><FONT size=2> <DIV><FONT size=2>Nvidia drivers howto:</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2><A href="">https://wiki.ubuntu.com/BinaryDriverHowto/Nvidia</A></FONT></DIV> <DIV> </DIV> <DIV> <DIV lang=en id=content dir=ltr><A id=top></A> <P>This page should be rewritten using <A href="">BinaryDriverHowto/ATI</A> as a model, with an emphasis on the differences in procedure and packages between the current driver and the legacy driver. These differences are in the package containing the kernel modules in addition to the package containing the Xorg modules. </P> <H2 id=head-b8ef705b4120cdfb5eea7006d3e75cbaec166a7a>Installation Procedure</H2> <P>The NVIDIA drivers are in the "restricted" section of the Ubuntu Package repository, so before you will be able to install the drivers, you must enable this section on your system. If you have already done this, skip to step 7. </P> <OL type=1>

  • <LI> <P>Select the <STRONG>System</STRONG> menu at the top of the screen. </P> <LI> <P>Select <STRONG>Administration</STRONG> then <STRONG>Synaptic Package Manager</STRONG>. </P> <LI> <P>In the package manager, select the <STRONG>Settings</STRONG> menu, then <STRONG>Repositories</STRONG>. </P> <LI> <P>In the <STRONG>Software Sources</STRONG> dialog that comes up, click the <STRONG>Add</STRONG> button. </P> <LI> <P>In the <STRONG>Edit Repository</STRONG> dialog, ensure that the <STRONG>Restricted copyright</STRONG> box is checked, then press <STRONG>OK</STRONG>. </P> <LI> <P>Press <STRONG>OK</STRONG> to close the <STRONG>Software Sources</STRONG> dialog, when Synaptic asks you to reload the package database, say yes. </P> <LI> <P>You now have access to the many additional packages in the <STRONG>restricted</STRONG> section, including the nvidia driver packages.


  • <LI> <P>Click the <STRONG>Search</STRONG> button and search for "nvidia". </P> <LI> <P>Once the search is complete, click the white box next to the following packages and select <STRONG>Mark for Installation</STRONG> in the menu that pops up: </P> <UL>

    • <LI> <P>Everybody should install: </P> <UL>

      • <LI> <P>nvidia-settings </P></LI></UL>

      <LI> <P>If you have an older TNT, TNT2, TNT Ultra, <A class=nonexistent href="">GeForce1</A> or <A class=nonexistent href="">GeForce2</A> card: </P> <UL>

      • <LI> <P>nvidia-glx-legacy </P></LI></UL>

      <LI> <P>Otherwise if you have a newer card: </P> <UL>

      • <LI> <P>nvidia-glx </P></LI></UL></LI></UL>

    <LI> <P>Press the <STRONG>Search</STRONG> button again and this time search for "linux-restricted-modules". </P> <LI> <P>Once the search is complete find <STRONG>linux-restricted-modules-386</STRONG> (or <STRONG>linux-restricted-modules-686</STRONG> if you are running the 686 kernel) in the list and mark it for installation the same way as before. </P> <LI> <P>Click the <STRONG>Apply</STRONG> button to install the new packages. </P> <LI> <P>Once Synaptic has finished applying your changes, exit the application.


  • <LI> <P>Select the <STRONG>Applications</STRONG> menu at the top of the screen, then <STRONG>Accessories</STRONG> and then <STRONG>Terminal</STRONG>. </P> <LI> <P>In the terminal window, type the following command to enable the driver: </P> <UL>

    • <LI style="LIST-STYLE-TYPE: none"> <P><FONT size=3><TT>sudo nvidia-glx-config enable</TT> </FONT></P></LI></UL>

    <LI class=gap> <P>Close all your applications, then press <STRONG>Ctrl-Alt-Backspace</STRONG> to restart the X server. If you see an nVidia splashscreen after hitting <STRONG>Ctrl-Alt-Backspace</STRONG>, your drivers are properly installed. </P></LI></OL>

<H2 id=head-25d26bb166158beeff13520345659f002827c94b>Remove the nVidia logotype</H2> <P>If you want to get rid of the nVidia logotype that shows up before your login screen you need to perform some manual edits in the Xorg configuration file. </P> <OL type=1>

  • <LI> <P>Select the <STRONG>Applications</STRONG> menu at the top of the screen, then <STRONG>Accessories</STRONG> and then <STRONG>Terminal</STRONG>. </P> <LI> <P>Type the following: </P></LI></OL>

<P><TT><FONT size=3>sudo gedit /etc/X11/xorg.conf</FONT></TT> </P> <OL type=3>

  • <LI> <P>Find the line Driver "nvidia" in the Device section </P> <LI> <P>Just after this line, add </P></LI></OL><PRE><FONT size=3>Option "NoLogo"</FONT></PRE>

<OL type=5>

  • <LI> <P>Save the file and exit </P> <LI> <P>Close all your applications, then press <STRONG>Ctrl-Alt-Backspace</STRONG> to restart the X server. If the logotype is gone and everything seems to work you are done. </P></LI></OL>

<H2 id=head-0ee4ad32c13f1b972290afc3d6b31926f946d0c5>Notes</H2> <P>If you are going to compile 3d applications, you will want to install the <STRONG>nvidia-glx-dev</STRONG> package </P> <P><STRONG>Note</STRONG>: If you wish to use these drivers and run the XMMS music player, you should be aware of <A class=external href=""> this bug (fixed at least in Breezy</A>. You can get around this bug by installing libmik. </P> <P><STRONG>Note</STRONG>: Be sure to have the right version of linux-restricted-modules installed. It must match the version of the running kernel. </P> <P><STRONG>Note</STRONG>: Render<STRONG></STRONG>Accel has a bug. Memory leak and crashes. Disable it in /etc/X11/xorg.conf in the section "Device". </P><PRE><FONT size=3>Option "RenderAccel" "false"</FONT></PRE> <P><STRONG>Getting suspend to work with the binary driver:</STRONG> See <A href="">NvidiaLaptopBinaryDriverSuspend</A> </P> <P>For other drivers, refer to the <A href="">BinaryDriverHowto</A> Part of <A href="">UserDocumentation</A> </P> <P><A href="">CategoryDocumentation</A> <A href="">CategoryCleanup</A> </P><A id=bottom></A></DIV> <P class=info lang=en id=pageinfo dir=ltr>last edited 2006-03-01 01:02:23 by <SPAN title=dhcp0534.hrn.resnet.group.upenn.edu>JasonRibeiro</SPAN></P></DIV> <DIV><FONT size=2> </DIV> <DIV> <HR> </DIV></FONT> <DIV><FONT size=2>PPTP Client Howto for Ubuntu 5.10 Breezy:</FONT></DIV> <DIV><A href=""><FONT size=2>http://pptpclient.sourceforge.net/howto-ubuntu.phtml</FONT></A></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV> <DIV align=center><FONT face="verdana, Arial, Helvetica, sans-serif" color=#00659c hidesize="4"><B>PPTP Client</B></FONT></DIV><BR><BR><!


><FONT face="verdana, arial, helvetica, sans-serif" color=#000000><B>Ubuntu HOWTO</B> <P><!-- $Id: howto-ubuntu.phtml,v 1.1 2005/12/27 23:08:38 james Exp $ --> <DIV align=right>by James Cameron<BR>28th December 2005</DIV> <P>These are instructions for installing PPTP Client on Ubuntu Linux, last tested with the 5.10 Breezy version on i386. The Ubuntu kernel has MPPE already.

<P>Contents: <UL>

  • <LI><A href="">installing the client program</A> <LI><A href="">installing the configuration program</A> <LI><A href="">configuring a tunnel using the configuration program</A> <LI><A href="">configuring a tunnel by hand</A> </LI></UL><A name=install>

<HR noShade> </A><B>Installing the Client Program</B> <P>Install PPTP Client from the Ubuntu Project: <P> <CENTER> <TABLE cellPadding=6 width="90%" bgColor=#d8f8d8 border=0>

  • <TBODY> <TR>

    • <TD><TT>apt-get install pptp-linux </TT></TD></TR></TBODY></TABLE></CENTER>

<P><A name=install_gui> <HR noShade> </A><B>Installing the Configuration Program</B> <P>Note: you may wish to skip the configuration program and <A href="">configure the client by hand</A>. <OL>

  • <LI>add the following lines to the sources list file, <TT>/etc/apt/sources.list</TT> : <P> <CENTER> <TABLE cellPadding=6 width="90%" bgColor=#d8f8d8 border=0>

    </TT></TD></TR></TBODY></TABLE></CENTER> <P>Note: can use a text editor, or simply <I>cat</I> the lines on to the end of the file using <I>>></I>, but if you make a mistake in formatting you will likely be told by the <I>apt-get update</I> step. <P></P> <LI>update the list of packages: <P> <CENTER> <TABLE cellPadding=6 width="90%" bgColor=#d8f8d8 border=0>

    • <TBODY> <TR>

      • <TD><TT>apt-get update </TT></TD></TR></TBODY></TABLE></CENTER>

    <P></P> <LI>install the PPTP Client GUI: <P> <CENTER> <TABLE cellPadding=6 width="90%" bgColor=#d8f8d8 border=0>

    • <TBODY> <TR>

      • <TD><TT>apt-get install pptpconfig </TT></TD></TR></TBODY></TABLE></CENTER>

    <P>Note: you may be told that the packages could not be authenticated. For the moment, tell your system to install them anyway. We'll take patches to our release process if anyone can explain simply how to provide authentication. <P></P></LI></OL><A name=configure_gui>

<HR noShade> </A><B>Configuration</B> <P><!-- future, table, images on right hand side --> <OL>

  • <LI>obtain from your PPTP Server administrator: <P> <UL>

    • <LI>the IP address or host name of the server, <LI>the authentication domain name, (e.g. WORKGROUP), <LI>the username you are to use, <LI>the password you are to use, <LI>whether encryption is required. </LI></UL>

    <P></P> <LI>run <I>pptpconfig</I> <A href="">as root</A>, and a window should appear, <P> <P></P> <LI>enter the server, domain, username and password into the <I>Server</I> tab, <P></P> <LI>if you decided in Installation step 1 above that you would need MPPE, and if your administrator says encryption is required, then on the <I>Encryption</I> tab, click on <I>Require Microsoft Point-to-Point Encryption (MPPE)</I>, <P> <P></P> <LI>click on <I>Add</I>, and the tunnel will appear in the list, <P></P> <LI>click on the tunnel to select it, click on <I>Start</I>, and a window will appear with the tunnel connection log and status, <P></P> <LI>if the connection fails, you will need to gather more information, so on the <I>Miscellaneous</I> tab, click on <I>Enable connection debugging facilities</I>, click <I>Update</I>, try <I>Start</I> again, then look at the <A href="">Diagnosis HOWTO</A> for whatever error is displayed. <P> <P></P> <LI>if the connection succeeded, you can try the <I>Ping</I> test button. If the ping fails, you should try to find out why before proceeding. If the ping works, then the tunnel is active and you may now work on routing. <P></P> <LI>decide whether all your network traffic should go via the tunnel or not. If so, <I>Stop</I> the tunnel, select it again, then on the <I>Routing</I> tab, click on <I>All to Tunnel</I>, then click <I>Update</I> and try <I>Start</I> again. Now try to access the network behind the server. <P></P> <LI>on the other hand, if only some of your network traffic should go via the tunnel, you will need to obtain from the server administrator or folk lore a series of network routes to enter. <I>Stop</I> the tunnel, select it again, then click on either <I>Client to LAN</I> or <I>LAN to LAN</I> on the <I>Routing</I> tab, use the <I>Edit Network Routes</I> button to enter the routes one by one, and then try <I>Start</I> again. Now try to access the network behind the server. <P> <P>For further help with Routing, read our <A href="">Routing HOWTO</A>. <P></P></LI></OL>

<HR noShade> <B>Diagnosing Problems</B> <P>If you have problems with the tunnel and need to ask for help, start <TT>pppd</TT> with complete logging: <P> <CENTER> <TABLE cellPadding=6 width="90%" bgColor=#d8f8d8 border=0>

  • <TBODY> <TR>

    • <TD><TT># script pptp.log<BR>Script started, file is pptp.log<BR># pppd

      • call <I>tunnelname</I> dump debug logfd 2 nodetach<BR># exit<BR>Script done, file is pptp.log </TT></TD></TR></TBODY></TABLE></CENTER>

<P>where <I>tunnelname</I> is the name of the tunnel you created in the configuration program. For more detail, see <A href="">enabling debug logging</A>. <P>This will give you a file <TT>pptp.log</TT> that you can use to search for known solutions in the <A href="">Diagnosis HOWTO</A> or attach to an e-mail to the <A href="">mailing list</A>. <P><A name=configure_by_hand> <HR noShade> </A><B>Configuration, by hand</B> <P> <OL>

  • <LI>obtain from your PPTP Server administrator: <P> <UL>

    • <LI>the IP address or host name of the server ($SERVER), <LI>the name you wish to use to refer to the tunnel ($TUNNEL), <LI>the authentication domain name ($DOMAIN), <LI>the username you are to use ($USERNAME), <LI>the password you are to use ($PASSWORD), <LI>whether encryption is required. </LI></UL>

    <P>In the steps below, substitute these values manually. For example, where we write $PASSWORD we expect you to replace this with your password. <P></P> <LI>create the <TT>/etc/ppp/options.pptp</TT> file, which sets options common to all tunnels: <P> <CENTER> <TABLE cellPadding=6 width="90%" bgColor=#d8f8d8 border=0>

    • <TBODY> <TR>

      • <TD><TT>lock noauth nobsdcomp

    nodeflate<BR></TT></TD></TR></TBODY></TABLE></CENTER> <P></P> <LI>create or add lines to the <TT>/etc/ppp/chap-secrets</TT> file, which holds usernames and passwords: <P> <CENTER> <TABLE cellPadding=6 width="90%" bgColor=#d8f8d8 border=0>

    • <TBODY> <TR>


  • <BR></TT></TD></TR></TBODY></TABLE></CENTER> <P>Note: if you are using a PPTP Server that does not require a domain name, omit the slashes as well as the domain name. <P>Note: if the passwords contain any special characters, quote them. See <TT>man pppd</TT> for more details. <P></P> <LI>create a <TT>/etc/ppp/peers/$TUNNEL</TT> file: <P> <CENTER> <TABLE cellPadding=6 width="90%" bgColor=#d8f8d8 border=0>

    • <TBODY> <TR>

      • <TD><TT>pty "pptp $SERVER --nolaunchpppd"<BR>name

        • $DOMAIN\\$USERNAME<BR>remotename PPTP<BR>require-mppe-128<BR>file /etc/ppp/options.pptp<BR>ipparam

    $TUNNEL<BR></TT></TD></TR></TBODY></TABLE></CENTER> <P>Note: if you do not need MPPE support, then remove the <I>require-mppe-128</I> option. <P></P> <LI>start the tunnel using the <I>pon</I> command: <P> <CENTER> <TABLE cellPadding=6 width="90%" bgColor=#d8f8d8 border=0>

    • <TBODY> <TR>

      • <TD><TT>pon $TUNNEL </TT></TD></TR></TBODY></TABLE></CENTER>

    <P>to further diagnose a failure, add options to the command: <P> <CENTER> <TABLE cellPadding=6 width="90%" bgColor=#d8f8d8 border=0>

    • <TBODY> <TR>

      • <TD><TT>pon $TUNNEL debug dump logfd 2 nodetach

    </TT></TD></TR></TBODY></TABLE></CENTER> <P>Note: we have further information on <A href="">enabling debug mode</A>, and on <A href="">diagnosing problems</A>. <P></P> <LI>stop the tunnel using the <I>poff</I> command: <P> <CENTER> <TABLE cellPadding=6 width="90%" bgColor=#d8f8d8 border=0>

    • <TBODY> <TR>

      • <TD><TT>poff $TUNNEL </TT></TD></TR></TBODY></TABLE></CENTER>

    <P></P> <LI>to script the tunnel connection so that something is done as soon as the tunnel is up, use either <TT>ip-up.d</TT> scripts or the <I>updetach</I> keyword. <P> <OL type=a>

    • <LI>see the <A href="">Routing HOWTO</A> for examples of <TT>ip-up.d</TT> scripting that adds routes or iptables rules. <P></P> <LI>using <I>updetach</I> will cause <TT>pppd</TT> to fork, detach, and exit with success once the network link is up. This example connects a provider link, then the tunnel, then runs <TT>fetchmail</TT> to get new e-mail: <P> <CENTER> <TABLE cellPadding=6 width="90%" bgColor=#d8f8d8 border=0>

      • <TBODY> <TR>

        • <TD><TT>pon provider updetach && pon $TUNNEL updetach

          • && fetchmail </TT></TD></TR></TBODY></TABLE></CENTER>

      <P>Note: the double ampersand && means that the commands following it will only be executed if the command to the left of it was successful. If the tunnel fails to connect, the fetchmail will not happen. <P></P></LI></OL>

    <LI>to have the tunnel automatically restarted if it fails, add the option <I>persist</I> to either the command line or the <TT>/etc/ppp/peers/$TUNNEL</TT> file. <P></P> <LI>to have the tunnel started on system boot: <P> <UL type=a>

    • <LI>for Debian Sarge, edit the <TT>/etc/network/interfaces</TT> file, and add this section: <P> <CENTER> <TABLE cellPadding=6 width="90%" bgColor=#d8f8d8 border=0>

      • <TBODY> <TR>

        • <TD><TT>auto tunnel<BR>iface tunnel inet

          • ppp<BR>        provider $TUNNEL </TT></TD></TR></TBODY></TABLE></CENTER>

      <P> <P></P> <LI>for Debian Woody, edit the <TT>/etc/ppp/no_ppp_on_boot</TT> file, remove the first line comment, and change the word <I>provider</I> to the name of your tunnel, so that it looks like this: <P> <CENTER> <TABLE cellPadding=6 width="90%" bgColor=#d8f8d8 border=0>

      • <TBODY> <TR>

        • <TD><TT>#!/bin/sh<BR>...<BR>$PPPD call $TUNNEL

      </TT></TD></TR></TBODY></TABLE></CENTER> <P>(The line ... means the other lines in the file, it doesn't mean a line with three dots.) <P>Then rename the no_ppp_on_boot file and make it executable: <P> <CENTER> <TABLE cellPadding=6 width="90%" bgColor=#d8f8d8 border=0>

      • <TBODY> <TR>

        • <TD><TT># mv /etc/ppp/no_ppp_on_boot /etc/ppp/ppp_on_boot<BR># chmod

          • +x /etc/ppp/ppp_on_boot </TT></TD></TR></TBODY></TABLE></CENTER>


    <UL></UL>Every time your computer starts, the tunnel will be started automatically. <P></P> <LI>to set up routing, read our <A href="">Routing HOWTO</A>. <P></P></LI></OL>

<HR noShade>

<H3><A name=comments>Comments</A></H3>If you have <I>comments</I> on this document, please send them to the author at james.cameron at hp.com. But if you <I>need help</I>, use the <A href="">mailing list</A> so that we can share the load. <HR noShade>

<H3><A name=ChangeLog>ChangeLog</A></H3> <TABLE>

  • <TBODY> <TR vAlign=top>

    • <TH align=left>Date</TH> <TH align=left>Change</TH></TR><!-- policy; link to change, undo change bar highlight one month after -->

    <TR vAlign=top>

    • <TD>2005-12-28</TD> <TD>Written using Debian HOWTO as basis, after feedback from Jeff Nelson.</TD></TR></TBODY></TABLE></FONT></DIV></FONT></DIV>