Changeset 1070

Show
Ignore:
Timestamp:
01/28/07 23:06:15 (2 years ago)
Author:
tushar
Message:

Updated Hint: wireless

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • trunk/wireless.txt

    r1026 r1070  
    1 AUTHOR:Dr. Edgar Alwers <edgaralwers@gmx.de> 
    2  
    3 DATE:2006-03-26 
    4  
    5 LICENSE:GNU Free Documentation License Version 1.2 
    6  
    7 SYNOPSIS:Wireless Communication from the sources 
     1AUTHOR:                        Dr. Edgar Alwers <edgaralwers@gmx.de> 
     2 
     3DATE:                  2006-12-10 
     4 
     5LICENSE:               GNU Free Documentation License Version 1.2 
     6 
     7SYNOPSIS:              Wireless Communication from the sources 
    88 
    99PREREQUISITES: 
    10 BLFS 6.x with  kernel 2.6.15. Older kernels shoud work accordingly, with the 
    11 correspondent firmware. 
     10 
     11BLFS 6.x with  kernel 2.6.18  
     12 
    1213 
    1314DESCRIPTION: 
    14 This is a Hint explaining how to prepare a PC for wireless communication with  
    15 the Internet and how to put it into operation. I solved this problem with the  
    16 help of hints and advices given by many persons, and working through lots of  
    17 papers, many of them not beeing actual anymore at this time. 
    18 The object I had to deal with is an 'Acer' TravelMate 291LCi with Intel  
    19 Centrino Mobile Technology, equiped with an Intel PRO/Wireless 2200BG 
    20 (IEEE 802.11b/g) chip. The Laptop communicates with an 54 Mbps Wireless  
    21 Netgear ADSL Firewall Router DG834G as access point However, there are good  
    22 chances, that this hint may also be applied to other PC's with other drivers.  
    23 If you cannot obtain a native Linux driver for your wireless NIC, you may  
    24 want to try 'ndiswrapper', a package that will allow to load a Windows driver  
    25 under Linux. 
    26 The kernel compiled is version 2.6.15. This kernel includes already the driver  
    27 ipw2200-1.0.8 and the iee802 subsystem and you may ask, why to build this two  
    28 items additionally. I experienced serious difficulties not compiling them and  
    29 decided to become independent from the kernel. 
    30 This second issue of the hint deals with additional instructions, how to  
    31 operate a PC in a wireless field under a DHCP Server ( Dynamic Host Configura- 
    32 tion Protocol ) providing  IP's to the clients. This is the probably situation  
    33 which will be found in most public locations, like airports, hotels etc.  
     15 
     16This is a Hint explaining how to prepare a PC for wireless communication with 
     17the Internet and how to put it into operation. I solved this problem with the 
     18help of hints and advices given by many persons, and working through lots of 
     19papers, many of them not beeing actual anymore at this time.  
     20The object I had to deal with is an 'Acer' TravelMate 291LCi with Intel Centrino 
     21Mobile Technology, equiped with an Intel PRO/Wireless 2200BG(IEEE 802.11b/g) 
     22chip. The Laptop communicates with an 54 Mbps Wireless Netgear ADSL Firewall 
     23Router DG834G as access point However, there are good chances, that this hint 
     24may also be applied to other PC's with other drivers. If you cannot obtain a 
     25native Linux driver for your wireless NIC, you may want to try 'ndiswrapper', a 
     26package that will allow to load a Windows driver under Linux. 
     27 
     28The kernel compiled is version 2.6.18. This kernel includes already an  'old'  
     29driver ipw2200 and a iee802 subsystem, which should not be enabled, as they are 
     30beeing provided separate. 
     31 
     32Additional instructions are given, how to operate a PC in a wireless field under 
     33a DHCP Server ( Dynamic Host Configuration Protocol ) providing  IP's to the 
     34clients. This is the probably situation which will be found in most public 
     35locations, like airports, hotels etc.  
    3436 
    3537HINT: 
    36 KERNEL: 
     38 
     39KERNEL 
     40 
    3741Download: 
    38         Kernel v. 2.6.15 
     42        Kernel v. 2.6.18 
    3943        http://www.kernel.org 
     44 
    4045Configuring the kernel: 
     46 
    4147        enable Networking-> 
    42                        Networking support-> 
    43                                Networking options-> 
    44                                        Packet socket 
    45                                        TCP/IP networking 
     48                Networking support-> 
     49                        Networking options-> 
     50                                Packet socket 
     51                                TCP/IP networking 
    4652        device drivers-> 
    47                         Generic driver options-> 
    48                                 Hotplug firmware loading support 
     53                Network device support-> 
     54                        Wireless LAN (non-harmradio)-> 
     55                                Wireless LAN drivers & Wireless Extensions 
     56        cryptographic optionsI-> 
     57                ARC4 cipher algorithm (Modul) 
     58 
     59Make sure, that the following capabilities are not enabled: 
     60 
     61        networking-> 
     62                Generic IEE 802.11 Networking Stack 
    4963        device drivers-> 
    50                         Network device support-> 
    51                                 Wireless LAN (non-harmradio)-> 
    52                                         Wireless LAN drivers & Wireless  
    53                                         Extensions 
    54         cryptographic API-> 
    55                         ARC4 cipher algorithm (Modul) 
    56 compile and install the kernel according to the instructions of the book  
    57 'Linux From Scratch' 
    58  
    59 HOTPLUG-2004_09_23: 
     64                Network device support-> 
     65                        Wireless LAN ( non-hamradio ) -> 
     66                                Intel PRO/Wireless 2200BG and 
     67                                2915ABG network  
     68compile and install the kernel according to the instructions of the book 'Linux 
     69From Scratch' 
     70 
     71HOTPLUG-2004_09_23 
     72 
    6073Scripts that react upon hotplug events generated by the kernel 
    6174Download: 
    6275        hotplug-2004_09_23.tar.bz2 
    63         Http://www.kernel.org/pub/linux/utils/kernel/hotplug 
    64 Install hotplug according to the instructions given e.g. In the LFS-Book  
    65 SVN-20060125, Chapter 6.49 
    66  
    67 UDEV-071.TAR.BZ2: 
    68 Programs for dynamic creation of device nodes 
     76        http://www.kernel.org/pub/linux/utils/kernel/hotplug 
     77 
     78Install hotplug issuing a 'make install' in the untared directory. 
     79 
     80IEE80211-1.2.15 
     81 
     82Kernel subsystem dealing with communications security 
     83 
    6984Download 
    70         udev-071.tar.bz2 
    71         ftp://ftp.kernel.org/pub/linux/utils/kernel/hotplug 
    72 make DESTDIR=/ EXTRAS="extras=firmware extras/run_directory"  
    73 make DESTDIR=/ EXTRAS="extras=firmware extras/run_directory" install   
    74 install -m644 -D -v docs/writing_udev_rules/index.html /usr/share/doc/udev/ 
    75 071/index.html 
    76 /sbin/udevstart 
    77 Check that 'firmware_helper', 'udev_run_devd' and 'udev_run_hotplugd' are  
    78 installed in the /sbin directory. 
    79 Download the new udev-rules developed by Jim Gifford's cross lfs team 
    80         udev-cross-lfs.tar.bz2  
    81         http://ftp.jg555.com/udev 
    82 Untar the file, change to the 'udev-cross-lfs' directory and enter  
    83 'make install'. This  installs the new udev-rules in /etc/udev/rules.d 
    84  
    85 IEE80211-1.1.12: 
    86 Kernel subsystem dealing with communications security 
    87 Download 
    88         ieee80211-1.1.12.tgz 
     85        ieee80211-1.1.15.tgz 
    8986        http://ieee80211.sourceforge.net 
    90 Untar the file, change to the ieee80211-1.1.12 directory and enter make,  
    91 make install.  
    92 Includes headerfiles in /lib/modules/2.6.15/net 
    93  
    94 INTEL'S FIRMWARE: 
    95 Download the Firmware 
    96         ipw2200-fw-2.4 
     87Untar the file, change to the ieee80211-1.1.15 directory and enter make, make 
     88install.  
     89Includes headerfiles in /lib/modules/2.6.18/net 
     90 
     91INTEL'S PRO/WIRELESS DRIVER AND FIRMWARE 
     92 
     93Download  the file  
     94        ipw2200_linux_1_2_0.tgz 
    9795        http://ipw2200.sourceforge.net 
    98 Untar the file in the directory /lib/firmware. Seven files ipw-2.4-xxx.fw  
    99 will be found there after untaring 
    100  
    101 INTEL PRO/WIRELESS DRIVER : 
    102 Driver that works on the Intel hardware adapter PRO/Wireless 2200BG Network  
    103 Connection 
    104 Download the driver 
    105         ipw2200-1.0.10.tgz       
    106         http://ipw2200.sourceforge.net 
    107 Untar the file, change to the ipw2200-1.0.10 directory and enter make, make  
    108 install. ( as su ) 
    109 I experienced serious problems compiling the new driver versions 1.0.12 and  
    110 1.0.13, so I would advice to stick to the above one for the time beeing. 
    111 The driver requires the firmware image as well as the ieee80211 module  
    112 installed. "sysfs" should be already mounted. 
     96Unter the file. Two new tar files will be included in the new created  
     97'intel_ipw2200_120' directory: ipw2200-1.2.0.tgz, the PRO/Wireless driver, and 
     98ipw2200-fw-3.0.tgz, the firmware.  
     99 
     100Untar the firmware file in the directory /lib/firmware. Four files 
     101ipw-2200-xxx.fw will be found there after untaring 
     102 
     103Untar the PRO/Wireless driver file, change to the ipw2200-1.2.0 directory and 
     104enter make, make install. ( as su ) 
     105 
     106The driver requires the firmware image as well as the ieee80211 module 
     107installed. sysfs should be  already mounted 
     108 
    113109See also the INSTALL file for more instructions 
    114110 
    115 THE WIRELESS TOOLS: 
     111THE WIRELESS TOOLS  
     112 
    116113Set of tools that allows to manipulate Wireless Extensions 
    117114Download the wireless tools: 
    118         wireless_tools.27.tar.gz 
     115        wireless_tools.28.tar.gz 
    119116        http://pcmcia-cs.sourceforge.net/ftp/contrib/ 
    120 Untar the file, change to the wireless_tools.27 directory and enter make,  
    121 make install 
    122 Seven tools will be installed in /usr/local/sbin: iwconfig, iwlist, ifrename, 
    123 iwevent,iwgetid, iwpriv and iwspy 
     117Untar the file, change to the wireless_tools.28 directory and enter make, make 
     118install 
     119Seven tools will be installed in /usr/local/sbin: iwconfig, iwlist, 
     120ifrename,iwevent,iwgetid, iwpriv and iwspy 
    124121Make a link from KDE_Prefix/bin to /usr/local/sbin:  
    125122        ln -s /usr/local/sbin/iwconfig KDE_Prefix/bin/iwconfig 
    126123 
    127 THE DHCPCD CLIENT SOFTWARE: 
    128 Software to connect a computer to a network which uses DHCP to assign network  
    129 addresses.There are two alternatives: dhcp, which includes also the server  
    130 software, and dhcpcd, an implementation of the DHCP client specified in  
    131 RFC2131. I prefered  dhcpcd, wich seems to be more simple. 
     124THE DHCPCD CLIENT SOFTWARE 
     125 
     126Software to connect a computer to a network which uses DHCP to assign network 
     127addresses.There are two alternatives: dhcp, which includes also the server 
     128software, and dhcpcd, an implementation of the DHCP client specified in RFC2131. 
     129I prefered  dhcpcd, wich seems to be more simple. 
    132130Download  
    133         dhcpcd-2.0.1.tar.bz2 
    134         http://developer.berlios.de/projects/dhcpcd/ 
    135 Untar, change to the dhcpcd-2.0.1 directory and enter 
    136         ./configure --prefix="" --sysconfdir=/var/lib 
    137         and, as superuser, make. 
    138 The reason for the prefix "" in the configuration command is explained in the  
    139 blfs-book, version 6.1, chapter 14. Install the network service script  
    140 /etc/sysconfig/network-devices/services/dhcpcd as indicated in the same place 
     131        dhcpcd-2.0.8.tar.bz2 
     132        http://prdownload.berlios.de/dhcpcd/ 
     133Untar, change to the dhcpcd-2.0.8 directory and enter 
     134        ./configure --prefix="" --mandir=/usr/share/man 
     135        make 
     136        and, as superuser, make install, and 
     137        chmod -v 754 /etc/dhcpc/dhcpcd.exe. 
     138The reason for the prefix "" in the configuration command is explained in the 
     139blfs-book, version svn-20061028, chapter 14.  
     140Install the network service script 
     141/etc/sysconfig/network-devices/services/dhcpcd  and create 
     142/etc/sysconfig/network-devices/ifconfig.eth1/dhcpcd configuration file as 
     143indicated in the same place 
    141144         
    142 BOOTING THE PC: 
    143 If everything went right, the PC boots and loads firmware and wireless-driver.  
     145BOOTING THE PC 
     146 
     147If everything went right, the PC boots and loads firmware and wireless-driver. 
    144148The corresponding booting  messages will look like 
    145149        ........ 
    146150        ieee80211_crypt: registered algorithm 'NULL' 
    147151        ieee80211: 802.11 data/management/control stack, 1.1.6 
    148         ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux. 
    149                    intel.com> 
     152        ieee80211: Copyright (C) 2004-2005 Intel Corporation 
     153                <jketreno@linux.intel.com> 
    150154        ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.8 
    151155        ipw2200: Copyright(c) 2003-2005 Intel Corporation 
    152156        ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 10 
    153         ACPI: PCI Interrupt 0000:01:02.0[A] -> Link [LNKG] -> GSI 10  
    154                 (level, low) -> IRQ 10 
     157        ACPI: PCI Interrupt 0000:01:02.0[A] -> Link [LNKG] -> GSI 10 (level, 
     158                low) -> IRQ 10 
    155159        ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection 
     160        Detected geography ZZM (11 802.11bg channels, 0 802.11a channels) 
    156161        ......... 
    157162 
    158 MONITORING PROGRAMS: 
    159 There are many prrograms that allows the monitoring of wireless communi- 
    160 cations. I installed two of them: 'kismet' and 'KWiFiManager'. 
    161 'kismet' is a small wireless network detector, sniffer and intrusion  
    162 detection system.  
    163 Download 'kismet-2005-08-R1.tar.gz' from http://www.kismetwireless.net/ 
    164 download.shtml 
    165 untar the file, enter make and make suidinstall. Run kismet the first time  
    166 as root. Kismet runs on a  shell console. 
    167  
    168 'kwifimanager' is a KDE frontend program used to configure and monitor  
    169 wireless LAN cards. 'kwifimanager' is part of 'kdenetwork'. Download  
    170 kdenetwork_3.4.1.tar.bz2 and follow the instructions given e.g. in  
    171 BLFS - Version 6.1, chapter 29. Wireless tools should be installed before  
    172 building this packet. 
    173  
    174 CONFIGURING THE ROUTER -  SAFETY CONSIDERATIONS: 
    175 during the installation of the wireless system, the safety options of the  
    176 router are deactivated. Now, it is time to activate them. Access the settings  
    177 menu of the router through a browser, entering something like  
    178 http://192.168.0.1. I activated WEP ( Wired Equivalent Privacy ) with  64 bit  
    179 encryption. You may consider a 125 bit encryption 
    180 Enter a password in the encryption field, and the router will generate four  
    181 keys, each one consisting of 10 characters, combining numbers 1 to 9 and  
    182 letters A-F, like:EC670531BE. The first of this four keys is the one beeing  
    183 normally used. 
    184 Furthermore, the MAC-addresses ( Media Access Control ) of the laptop's and  
    185 PC's wich are allowed to access the router shoud be entered in the access  
    186 list 'trusted wireless stations'. You may get the MAC addresses  from the list  
    187 of connected devices in the settings menu of the router or with the help of  
    188 a network exploration tool like 'nmap' ( Network Mapper ), in  the last case  
    189 e.g. entering 'nmap -sP 192.168.0.1/22' 
    190 However, even a 125 bit encryption does not give a real security today.  
    191 According to a note contributed by Bryan Kadzban,  real security can only be  
    192 obtained with WPA or WPA2 encryption. You may want to consider this, if you  
    193 have confidential data to transmit. 
    194  
    195 CONFIGURING THE PC FOR WIRELESS COMMUNICATIONS: 
    196 immediately after the safety options of the router are activated, the PC will  
     163MONITORING PROGRAMS 
     164 
     165There are many prrograms that allows the monitoring of wireless communications. 
     166I installed two of them: 'Wireshark' ( former ethereal ) and 'KWiFiManager'. 
     167 
     168'wireshark' is a powerfull  network protocol analyser ( packet sniffer ).  
     169Download 'wireshark-0.99.4.tar.gz' from http://www.wireshark.org/download/src 
     170Untar the file and run ./configure, make and make install. 
     171 
     172'kwifimanager' is a KDE frontend program used to configure and monitor wireless 
     173LAN cards. 'kwifimanager' is part of 'kdenetwork'. Download 
     174kdenetwork_3.4.1.tar.bz2 and follow the instructions given e.g. In BLFS - 
     175Version 6.1, chapter 29. Wireless tools should be installed before building this 
     176packet. 
     177 
     178CONFIGURING THE ROUTER -  SAFETY CONSIDERATIONS 
     179 
     180during the installation of the wireless system, the safety options of the router 
     181are deactivated. Now, it is time to activate them. Access the settings menu of 
     182the router through a browser, entering something like http://192.168.0.1. I 
     183activated WEP ( Wired Equivalent Privacy ) with  64 bit encryption. You may 
     184consider a 125 bit encryption 
     185 
     186Enter a password in the encryption field, and the router will generate four 
     187keys, each one consisting of 10 characters, combining numbers 1 to 9 and letters 
     188A-F, like:EC670531BE. The first of this four keys is the one beeing normally 
     189used. 
     190 
     191Furthermore, the MAC-addresses ( Media Access Control ) of the laptop's and PC's 
     192wich are allowed to access the router shoud be entered in the access list 
     193'trusted wireless stations'. You may get the MAC addresses  from the list of 
     194connected devices in the settings menu of the router or with the help of a 
     195network exploration tool like 'nmap' ( Network Mapper ), in  the last case e.g. 
     196entering 'nmap -sP 192.168.0.1/22' 
     197 
     198However, even a 125 bit encryption does not give a real security today. 
     199According to a note contributed by Bryan Kadzban,  real security can only be 
     200obtained with WPA or WPA2 encryption. You may want to consider this, if you have 
     201confidential data to transmit. 
     202 
     203CONFIGURING THE PC FOR WIRELESS COMMUNICATIONS 
     204 
     205immediately after the safety options of the router are activated, the PC will 
    197206not more be able to see the access point: the PC also needs to be configured.  
    198 Entering the command 'iwconfig eth1 key xxxxxxxxxx'  enables the communi- 
    199 cation, but not permanently. For a permanent configuration, write a  
    200 shell-script e.g.'connect' in /etc/rc.d/init.d: 
     207Entering the command 'iwconfig eth1 key xxxxxxxxxx'  enables the communication, 
     208but not permanently. For a permanent configuration, write a shell-script 
     209e.g.'connect' in /etc/rc.d/init.d: 
    201210        $!/bin/sh 
    202211        /usr/local/sbin/iwconfig eth1 key xxxxxxxxxx 
    203 and make this script executable: chmod ug+x connect. Make a symbolic link  
    204 in /etc/rc.d/rc3.d that points to this script:  
    205 ln -s /etc/rc.d/init.d/connect S19connect. The link should start with  
    206 something like S19, as the script should be run before the S20network script  
    207 is executed. For an unencrypted system, likely to be found on public places,  
    208 the command in the script should not contain a key: 
     212and make this script executable: chmod ug+x connect. Make a symbolic link in 
     213/etc/rc.d/rc3.d that points to this script: ln -s /etc/rc.d/init.d/connect 
     214S19connect. The link should start with something like S19, as the script should 
     215be run before the S20network script is executed. For an unencrypted system, 
     216likely to be found on public places, the command in the script should not 
     217contain a key: 
    209218        /usr/local/sbin/iwconfig eth1 
    210 Create a directory 'ifconfig.eth1' in '/etc/sysconfig/network-devices', and  
    211 cd to this directory.  
     219 
     220Create a directory 'ifconfig.eth1' in '/etc/sysconfig/network-devices', and cd 
     221to this directory.  
    212222For operation withouth DHCP create a ipv4 file: 
    213223        ONBOOT=yes 
    214224        SERVICE=ipv4-static 
    215         IP=192.168.1.3          // the address of your box 
    216         GATEWAY=192.168.1.9     // the address of your router 
     225        IP=192.168.1.3                 // the address of your box 
     226        GATEWAY=192.168.1.9            // the address of your router 
    217227        PREFIX=24 
    218228        BROADCAST=192.168.1.255 
    219229        NETMASK=255.255.255.0 
    220230and change GATEWAY_IF in /etc/sysconfig/network to eth1. 
     231 
    221232For operation with DHCP create instead ipv4 a file dhcpcd: 
    222233        ONBOOT="no" 
    …… 
    224235        DHCP_START="eth1 -t 20" 
    225236        DHCP_STOP="-k " 
     237 
    226238        # Set PRINTIP="yes" to have the script print 
    227239        # the DHCP assigned IP address 
    228240        PRINTIP="yes" 
     241 
    229242        # Set PRINTALL="yes" to print the DHCP assigned values for 
    230243        # IP, SM, DG, and 1st NS. This requires PRINTIP="yes". 
    231244        PRINTALL="no" 
    232245 
    233 USING THE WIRELESS CONNECTION : 
     246USING THE WIRELESS CONNECTION  
     247 
    234248After booting, lsmod shows 
    235         Module                  Size                    Used by 
    236         ipw2200                 176576  0 
    237         ieee80211                 42664 1               ipw2200  
    238         ieee80211_crypt         4804    1               ieee80211  
     249        Module          Size            Used by 
     250        ipw2200         170244          0 
     251        ieee80211         45356         1  ipw2200  
     252        ieee80211_crypt     4512        1  ieee80211_crypt_wep, 
     253                                                ieee80211 
    239254 
    240255The command 'iwconfig eth1' entered in a console delivers 
    241         eth1      IEEE 802.11g  ESSID:"Mannheim"   
    242         Mode:Managed  Frequency:2.462 GHz  Access Point: 00:0A:B5:CF:64:28    
    243         Bit Rate=48 Mb/s   Tx-Power=20 dBm    
    244         Retry limit:7   RTS thr:off   Fragment thr:off 
    245         Encryption key:57E4-DB3A-B1   Security mode:open 
    246         Power Management:off 
    247         Link Quality=95/100  Signal level=-29 dBm  Noise level=-86 dBm 
    248         Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0 
    249         Tx excessive retries:0  Invalid misc:0   Missed beacon:0 
    250 As the ONBOOT parameter was set to 'yes', the connection to the access point  
    251 is already activ. 
    252 The internet browser should be configured with direct access to the internet.  
     256                eth1      IEEE 802.11g  ESSID:"Mannheim"   
     257                Mode:Managed  Frequency:2.462 GHz  Access Point: 
     258                                00:0A:B5:CF:64:28    
     259                Bit Rate=48 Mb/s   Tx-Power=20 dBm   Sensitivity=8/0 
     260                Retry limit:7   RTS thr:off   Fragment thr:off 
     261                Encryption key:57E4-DB3A-B1   Security mode:open 
     262                Power Management:off 
     263                Link Quality=95/100  Signal level=-29 dBm  Noise level=-86 dBm 
     264                Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0 
     265                Tx excessive retries:0  Invalid misc:0   Missed beacon:0 
     266As the ONBOOT parameter was set to 'yes', the connection to the access point is 
     267already activ. 
     268 
     269The internet browser should be configured with direct access to the internet. 
    253270Opening the browser should establish immediately a connection. 
    254271 
    255 USING THE WIRELESS CONNECTION UNDER A DHCP SERVER: 
    256 I experienced some problems starting the dhcpcd daemon during the boot  
    257 process. So I decided to set the ONBOOT parameter in the file  
    258 /etc/sysconfig/network-devices/ifconfig.eth1/dhcpcd to 'no', as indicated  
    259 above, and to start as 'su' a little script 'eth1_connect' : 
     272USING THE WIRELESS CONNECTION UNDER A DHCP SERVER 
     273 
     274I experienced some problems starting the dhcpcd daemon during the boot process. 
     275So I decided to set the ONBOOT parameter in the file 
     276/etc/sysconfig/network-devices/ifconfig.eth1/dhcpcd to 'no', as indicated above, 
     277and to start as 'su' a little script 'eth1_connect' : 
    260278        #!/bin/bash 
    261279        /sbin/dhcpcd eth1 
    262280        # end 
    263 After starting the daemon dhcpcd, the connection to the access point is  
    264 activ. 
    265  
    266 AKNOWLEDGEMENTS: 
    267 I have tryed to compile articles, informations, hints and answers to questions  
    268 I put in the BLFS-mailing list to this hint. Many thanks to all those who  
    269 contributed: Gabe Yoder, Andrew Benton, Alexander E. Patrakov, Jim Gifford,  
     281After starting the daemon dhcpcd, the connection to the access point is activ. 
     282 
     283AKNOWLEDGEMENTS:           
     284 
     285I have tryed to compile articles, informations, hints and answers to questions I 
     286put in the BLFS-mailing list to this hint. Many thanks to all those who 
     287contributed: Gabe Yoder, Andrew Benton, Alexander E. Patrakov, Jim Gifford, 
    270288David Fix, Rainer Peter Feller, Chris Staub, Randy McMurchy, 
    271289Jeremy Monnet, Stefan Krah, Bryan Kadzban. 
    272290 
     291 
    273292LINKS AND LITERATURE: 
     293 
    274294Intel PRO/Wireless driver 
    275295http://ipw2200.sourceforge.net                                           
    …… 
    281301http://www.hpl.hp.com/personal/jean_Tourrilhes/Linux/Tools.html 
    282302 
    283 Kismet 
    284 http://www.kismetwireless.net/documentation.shtml 
     303Wiresharkt 
     304http://www.wireshark.org/ 
    285305 
    286306The devices, the drivers... Jean Tourrilhes 
    287 http://www.hpl.hp.com/personal/jean_Tourrilhes/Linux/Linux.Wireless.drivers. 
    288 802.1.11ag.html#CentrinoAG 
     307http://www.hpl.hp.com/personal/jean_Tourrilhes/Linux/Linux.Wireless.drivers.802. 
     3081.11ag.html#CentrinoAG 
    289309 
    290310Sane network interface management with Hotplug. Jean Tourrilhes 
    …… 
    294314http://ndiswrapper.sourceforge.net/mediawiki/index.php/Installation 
    295315 
    296  
    297316CHANGELOG: 
    298 [2006-01-26] 
    299         initial hint 
     317 
    300318[2006-03-26] 
    301         Remarks concerning safety considerations 
    302         Additional notes concerning DHCP-Server operation 
    303         Chapter "The DHCPCD Client Software"  
    304         Configuring the PC for operation under DHCP  
    305         Subsystem IEE80211-1.1.6 changed to IEE80211-1.1.12 
    306         Intel PRO/WIRELESS driver ipw2200-1.0.8 changed to ipw2200-1.0.10 
    307         Using the wireless connection under a DHCP server 
    308          
     319 
     320 Remarks concerning safety considerations 
     321 Additional notes concerning DHCP-Server operation 
     322 Chapter "The DHCPCD Client Software"  
     323 Configuring the PC for operation under DHCP  
     324 Subsystem IEE80211-1.1.6 changed to IEE80211-1.1.12 
     325 Intel PRO/WIRELESS driver ipw2200-1.0.8 changed to ipw2200-1.0.10 
     326 Using the wireless connection under a DHCP server 
     327 
     328[2006-12-10] 
     329 
     330 Kernel version 2.6.18 
     331 Kernel configuration changed 
     332 Hotplug instructions changed 
     333 UDEV is now part of the system 
     334 ieee80211 version changed to 1.2.15 
     335 New versions of Intel's PRO/Wireless driver and firmware 
     336 Wireless tools version 28 
     337 dhcpcd  version 2.0.8  
     338 new message booting the PC 
     339 'Kismet' skipped,  'wireshark' introduced 
     340 Links and literature changed