Obviously replace the appropriate IP addresses. First you must load your driver if Puppy has not automatically done so alreadyĬode: Select all ifconfig ra0 192.168.0.xx broadcast 192.168.0.255 netmask 255.255.255.0 etc/network-wizard/wireless/wpa_profiles/wpa_nf - for WPA2 encryptionĪs an example, let's assume your wifi driver is the ipw2200 (so the -D parameter will be "wext") and this driver has created the network interface "eth1", and your wifi router is set for WPA2 encryption. etc/network-wizard/wireless/wpa_profiles/wpa_nf - for WPA encryption Puppy already contains 2 different configuration files Use Geany to modify the WPA configuration file to include your SSID and Personal Security Key (PSK). Wpa_supplicant needs to have a "-D" (driver) parameter specified, depending on which wifi driver is being used Ĭompatible drivers using the "hostap" parameter:Ĭompatible drivers using the "ipw" parameter:Ĭompatible drivers using the "wext" (generic) parameter:Ĭompatible drivers using the "ralink" parameter: "PART 3: WPA encryption with Ralink devices" Ralink drivers in Puppy versions older than ver 4.1 can be set up for WPA encryption with unique "iwpriv" commands. Instead, the "wpa_supplicant" utility is needed, and this is the utility which is used by Puppy's Network Wizard to configure WPA connections. But note that Puppy was described as "amazing" in the Ubuntu forum: )įor WPA encryption the "iwconfig" utility cannot be used at all. Rm /etc/dhcpc/dhcpcd-eth0.cache 2>/dev/null #ditto Rm /etc/dhcpc/dhcpcd-eth0.pid 2>/dev/null #clear stale files # clear the dhcpc folder (nothing to change here) # also change "linksys" to the essid of your wifi network # now start it - change "rausb0" to "ra0" if needed # "rausb0" is for USB wifi device use "ra0" if it is an internal device # change rt2570 below to the name of your wifi chip # The file is in /root (open /root via Menu - Files - Rox) # then save and click to get your WiFi working! # Edit this file to input your own WiFi values Run this command to see which modules are currently loaded Usually, Puppy will automatically detect your wifi device, and load the suitable driver from its "zdrv" compressed driver collection. Ndiswrapper is a workaround solution, but sometimes it's the ONLY solution. Obviously, you must supply the Windows driver files. The correct module is NOT determined by the manufacturer of the wifi adaptor, but by the CHIPSET contained within the wifi adaptor.įrom version 2.12 onwards, Puppy Linux includes EXTENSIVE wifi driver support, including many Linux drivers written by independent development projects not aligned with the official Linux kernel.įor wifi chipsets not supported by a native Linux driver, Puppy also includes ndiswrapper, which will "wrap" a Windows driver. It's an amazing accomplishment.īut it's worth knowing the commands that operate behind the Wizard, especially if you need to troubleshoot a problem, or you have an unconventional setup.įirst it's worth knowing what module (driver) is being used for your wifi device. I've tested maybe three distros with graphical network configurations that actually work for my chip. The network wizard requires several steps and clicking back and forth, but it works even with Wi-Fi Protected Access (WPA).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |