For example, There's a setting for "nickname". I don't recall entering a nickname. These things I'm sure I can find out from the previously mentioned websites. Do you know if the microsoft card is based on the orinoco or.
I do a "ifup eth-pcmcia-0" it fails, saying no valid interface. The prism2 module does get loaded at boot, and does pick up the pcmcia. I have had good results with the NetGear MA, although I did need to download the latest Orinoco driver to get a reliable connection. I recently set up a wireless router with my internet connection, and bought a Microsoft mn wireless pcmcia adapter. Being that is "is made by for microsoft", I wouldn't be the least bit surprised to find a routine in the card's firmware that checks [via an "undocumented" call] what OS it is running under and either refuse to operate, or operate in a "degraded" manner, if the OS isn't windows [or worse, winxp, and pre-programmed to expect 'the next' version of windows when it is scheduled to come out Add to favorites Remove from favorites.
Mailing Lists. Sign In Sign Up. List overview All Threads Download. Freaking system clock. MPlayer questions. Michael Sacco. Ralph Sanford. The default value After having done this for both wireless LAN clients and having checked that the radio connection between the computers works, both machines can ping each other.
The procedure is the same if you use access points except for the mode, which must be changed in the wireless settings. YaST writes the network configuration along with the wireless configuration in the corresponding ifcfg file.
In our example, the content of this file is:. Regarding the network configuration, there are more variables than those that can be configured with YaST. If your wireless LAN does not run smoothly, you might find the cause among the following ones. As compared to an "ordinary" network, a wireless LAN also includes an additional level: the radio level. This means, there are again three areas where you can search for the problem.
Note: It would be impossible to cover all problems that may arise in connection to the hardware. Therefore, we will focus on wireless LAN-specific problems. In addition, the network device is called wlan0 instead of eth0. First find out the card ID with the command cardctl ident A sample output:. For this purpose, search for the other entries related to the orinoco modules and append the new entry to them.
In our example:. The right module will be loaded and the card can be setup with YaST. There are many interference sources for the reception in a wireless LAN like, for example, microwaves and TV sets.
If anything does not work, always check the noise level and the link quality before looking into your hardware or network settings. The WEP encryption might be another possible error source. All the problems that may appear in a wired network can also arise in a wireless LAN. Since wireless LANs are per se insecure networks, we provide you with some tips to make your wireless LAN more secure.
Security problems depend on the protocol, encryption method, and the structure. The first step when connecting a network device to an unsecure network is to make sure that everything that comes into the system through this device is filtered.
A packet filter such as SuSEfirewall2 can be used for this purpose. This does not protect against the packets transmitted through the wireless LAN, but against potential attackers already on the wireless LAN e.
This is an encryption method especially developed for wireless LANs that uses keys bit or 64bit long actually only bit or 40bit to encrypt the whole radio traffic. However, this method is no longer secure. Nevertheless, it should be the first measure to be implemented in order to isolate the people from your wireless LAN who cannot compile airsnort ;- But this is not enough to secure your wireless LAN.
This is one of the most widely used cards. There's a driver for it in the kernel but you need some proprietary firmware as well for it to work. This is very easy to get, just install the package ipw-firmware from the non-oss repository. This chipset has an opensource driver included and an additional firmware as well for it to work.
Ralink have been very cooperative with the free and open source software community. The driver for these cards needs a non-oss hal that is considered in violation of the kernel license. Therefore this driver is not provided with the openSUSE madwifi package. You should be able to find packages for openSUSE elsewhere. Since version 2.
This driver is reverse engineered, Broadcom have done nothing to help get support for the cards on Linux. Besides the driver you also need non-oss firmware, unlike Intel Broadcom won't allow distribution of this firmware by Linux distributors like Novell. So you need to manually extract the firmware from a Windows or Mac driver. Install the package bcm43xx-fwcutter. This package includes a script that will automatically get a driver from the internet and extract the firmware to the correct place.
The default openSUSE 2. Furthermore, you need to use driver b43, not bcm43xx, which means that you will also need new V4 firmware.
0コメント