absolutely no clue about how your distribution works. I'm just
collecting random information here without beeing able to verify it.
+ -----
+
+WIRELESS DRIVERS
+----------------
+ Most Linux wireless drivers support Wireless Extensions, and
+therefore may be configure via Wireless Tools and the methods
+described in this file.
+
+ However, a few drivers have no support or limited support for
+Wireless Extensions (like read only). In those cases, these are your
+options :
+ o read the driver documentation.
+ o use the driver specific interface or tools to
+configure the card, and try to integrate that in your distribution.
+ o implement Wireless Extension support in the driver.
+ In some cases, there are easier workaround. Different version
+of the driver may add Wireless Extension (often alongside the
+proprietary method). In some other case, there may be another driver
+supporting the same card and with support for Wireless Extensions.
+
+ Some Linux wireless drivers don't export all wireless settings
+via Wireless Extensions, not even through iwpriv. Those setting may be
+available through the driver specific interface. Refer to previous
+section for workarounds.
+
---------------------------------------------------------------------
PCMCIA METHOD
/etc/network/interfaces that are specific for wireless interfaces. They
are of the form:
- wireless_<function> <value>
+ wireless-<function> <value>
Before the interface is brought up, such a statement will result in the
execution of the following command:
network 192.168.1.0
netmask 255.255.255.0
broadcast 192.168.1.255
- wireless_essid Home
- wireless_mode ad_hoc
+ wireless-essid Home
+ wireless-mode ad-hoc
The current Debian script support all arguments present in
wireless.opts apart from Nickname. You can check this in the script
auto wlan0
mapping wlan0
- script /usr/local/bin/ifscheme
+ script /usr/local/bin/ifscheme-mapping
iface wlan0-home inet static
address 192.168.1.5
gateway 192.168.1.1
netmask 255.255.255.0
- wireless_mode ad_hoc
- wireless_essid wortroot
- wireless_nick dragon
- wireless_channel 1
+ wireless-mode ad-hoc
+ wireless-essid wortroot
+ wireless-nick dragon
+ wireless-channel 1
iface wlan0-away inet dhcp
- wireless_mode managed
+ wireless-mode managed
Now I can type 'ifscheme -s away' when I leave home, rather like
cardctl scheme.
combination of MAC address and scheme info to return a stanza name to
ifupdown.
+ -----
+
+ (Contributed by Jean Tourrilhes <jt@hpl.hp.com>)
+ The 'ifscheme' scripts mentionned above are now available in
+Debian Sarge, in the 'ifscheme' package.
+ The MAC address based mapping mentioned above is deprecated,
+you should use 'ifrename' to assign a consistent interface name to
+each of your network interface. This is documented in
+HOTPLUG-UDEV.txt. This enable the combination of MAC address
+identification of interfaces with scheme multi-configuration.
+
+ -----
+
+ If you need automatic wireless configuration, you can look at
+the following packages :
+ o ifupdown-roaming :
+ http://panopticon.csustan.edu/thood/ifupdown-roaming.html
+ o waproamd
+ http://0pointer.de/lennart/projects/waproamd/
+
+---------------------------------------------------------------------
+
+SuSE 8.0 and later
+--------
+ (Contributed by Christian Zoz <zoz@suse.de>)
+ All network configuration is done in the directory
+/etc/sysconfig/network. It does not matter if it's a build in NIC or
+PCMCIA, USB, etc. The files network.opts and wireless.opts in
+/etc/pcmcia are not used any longer. There is /sbin/ifup to set up all
+kind of network interface.
+ There is a file /etc/sysconfig/network/wireless where you may
+set most of the options of iwconfig in seperate variables (they are
+named like the options). Additionally you may use
+WIRELESS_IWCONFIG_OPTIONS e.g. for setting key 2, 3 or 4 or
+unsupported iwconfig commands. This file is documented and its
+settings are used for any wlan NIC.
+ Configuration of wireless variable looks like :
+ WIRELESS_ESSID="<essid>"
+ Every variable from file wireless may be used in the interface
+configuration files /etc/sysconfig/network/ifcfg-* as well. As
+expectable this overwrites the global setting in wireless. For
+sophisticated use of the ifcfg-* files read 'man ifup'.
+
+ Hint for PCMCIA and USB users:
+ You need not to use the iterface name for the configuration as
+this may vary from one plugin to another. You may use a description of
+your hardware instead (ifcfg-<MACADDRESS> or ifcfg-pcmcia-1 for card
+in Slot 1)
+
+ Some of the variables can be set with YaST2 as well.
+
+ If you miss the 'schemes' functionality from the pcmcia-cs
+packages use the tool SCPM (System Configuration Profile Management)
+instead. This extends the pcmcia schemes to the whole system
+configuration. Read 'info scpm'. Since SuSE 8.1 there also is a YaST2
+modul for SCPM.
+
---------------------------------------------------------------------
RED-HAT 7.2
---------------------------------------------------------------------
+RED-HAT 9.0 and later
+-----------
+ (Cut'n'pasted from Dax Kelson web page)
+ http://www.gurulabs.com/RedHatLinux9-review.html
+
+ A little known fact is that newer versions of RHL support
+multiple network profiles. This is useful for machines that commonly
+plug into different networks (think laptops). The easy way to create
+network profiles is to use the redhat-config-network command. The
+question then becomes, what happens when you type "ifup eth0"? The
+behavior wasn't defined in previous versions, however, now in RHL 9
+the following behavior is defined;
+
+ search path for:
+# ifup $DEV
+ is:
+/etc/sysconfig/networking/profiles/$CURRENT_PROFILE/ifcfg-$DEV
+/etc/sysconfig/networking/profiles/default/ifcfg-$DEV
+/etc/sysconfig/network-scripts/ifcfg-$DEV
+
+ A cool trick is to boot your RHL box directly into a profile
+from the GRUB boot screen. To do this, create a separate
+/etc/boot/grub.conf entry for each network profile, and in each entry
+add the kernel argument netprofile=profilename.
+
+ -----
+
+ I'm pretty certain the profile scheme above also apply to
+wireless settings, which is good news...
+
+---------------------------------------------------------------------
+
MANDRAKE 8.2 and later
------------
(Grabbed from various source - Google is your friend)
all of them. The script doing the configuration and where you can
check the details is :
/etc/network/network-scripts/ifup-wireless
- You will of course need the Wireless Extension package :
+ You will of course need the Wireless Tools package :
rpm -Uvh wireless-tools-XX-Xmdk.XXX.rpm
Mandrake can also have wireless setting added to its
Auto-Install procedure :
http://members.shaw.ca/mandrake/drakx/8.2/HTML/section4-13.html
----------------------------------------------------------------------
-
-SuSE 8.0 and later
---------
- (Cut'n'pasted from Unofficial SuSE FAQ, by Keith Winston)
- http://www.smaug42.com/susefaq/ethernetproblems.html#AEN768
- The old PCMCIA network scripts used to read
-/etc/pcmcia/wireless.opts to get the wireless options like mode,
-ESSID, encryption key, etc. Well, the wireless.opts file is still
-there but it is NOT used. It would have been nice if there was some
-documentation about it. Instead, the new scripts read this info from
-another brand new file called /etc/sysconfig/network/wireless. You can
-edit this file to store your wireless options. If you don't use key 1,
-you may have to put the other key in the WIRELESS_IWCONFIG_OPTIONS
-variable.
-
-----
- <Need confirmation :>
- Configuration of wireless settings looks like :
- WIRELESS_ESSID="<essid>"
- It also seem that the same directives can be added to the file :
- /etc/sysconfig/network/ifcfg-ethX
- Note that there seems to be other problems with SuSE, such as
-the Pcmcia scripts binding the linux-wlan-ng driver to Orinoco cards
-(which of course won't work - see link in FAQ above).
+ (in e-mail from Thierry Vignaud <tvignaud@mandrakesoft.com>)
+ You may use the following tool :
+ o drakconnect
+ You may read the following documentation :
+ o ifcfg
---------------------------------------------------------------------
OSDN Git Service
