| View previous topic :: View next topic |
| Author |
Message |
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
|
| Back to top |
|
 |
kzan
n00b
Joined: 08 Jan 2004
Posts: 50
Location: Grand Haven, MI
|
 Posted: Fri Aug 20, 2004 10:40 pm Post subject: |
 |
|
ok...i know i'm doing something completely stupid, but can anyone tell me why I am getting this...
| Code: |
root@laptop /etc/init.d # /etc/init.d/net.eth1 start
find: /etc/net.modules.d/: No such file or directory
* Loading networking scripts...
* modules: [ ok ]
* Running preup function
* Configuring wireless network for eth1
* Scanning for access points
* Found "OFFICE" at 00:0F:3D:61:FF:2A (WEP required)
* Found "wlan3" at 00:20:A6:4F:4B:35
* Found "wlan4" at 00:0D:88:3E:94:D5 (WEP required)
* Found "wlan5" at 00:20:A6:50:9F:0B
* Connecting to "OFFICE" (WEP enabled)... [ ok ]
* eth1 connected to "OFFICE" in managed mode
* on channel 3 (WEP enabled)
* configuration has not been set!
|
I have tried everything I can think of without a solution...
_________________
badger is my hero |
|
| Back to top |
|
|
kamina
Apprentice
Joined: 14 Jun 2004
Posts: 157
Location: Finland
|
| Posted: Sat Aug 21, 2004 9:20 am Post subject: Re: Wireless configuration and startup - The Gentoo way |
|
|
| UberLord wrote: |
Q. I'm seeing Wireless extensions not found for $interface - but it's a wireless device!
A. You need to enable wireless-extensions in your kernel.
To do this, enable the following config options in /usr/src/linux/.config | Code: | CONFIG_NET_RADIO=y
CONFIG_NET_WIRELESS=y |
Then recompile your kernel and modules and re-install them
If your driver is external then re-compile and re-install that.
Finally, re-emerge wireless-tools against the new kernel and driver
|
I have this excact problem. I started to edit .config file, but I don't have any line for CONFIG_NET_WIRELESS in the whole file. I found CONFIG_NET_RADIO and enabled that though... Should it work like this, do I add that line in there myself (and does it matter where?), or what should I do?
edit: I have the 2.6.7-gentoo-r11kernel. |
|
| Back to top |
|
|
kzan
n00b
Joined: 08 Jan 2004
Posts: 50
Location: Grand Haven, MI
|
| Posted: Sat Aug 21, 2004 6:48 pm Post subject: |
|
|
yep...it was as dump as I thought...i forgot to copy the net.modules.d folder to /etc/. Sorry about that...
_________________
badger is my hero |
|
| Back to top |
|
|
Onnelinen
n00b
Joined: 27 May 2003
Posts: 10
|
| Posted: Sun Aug 22, 2004 8:58 pm Post subject: late reply |
|
|
| UberLord wrote: |
Do you see anything in the output for wireless? |
Sorry for the late reply... been away for a while. What do you mean by the output for wireless? You mean the output i should get from /etc/init.d/net.wlan0 start ? There I do not get any wireless specific information... The hook in /etc/conf.d/net i am sure i have. My card works with the hostap_pci drivers. I can use iwconfig as i should.. I am actually surfing using my wireless card, so the problem is not hardware-related. What else should be present to use the script apart from the hook and net.wlan0? (my net.wlan0 is a copy of net.eth0) |
|
| Back to top |
|
|
bungernut
Apprentice
Joined: 24 Jan 2004
Posts: 173
|
| Posted: Mon Aug 23, 2004 12:01 am Post subject: Documentation Gap |
|
|
I really apprecieate the script and thanks for all the work. I have a question though. What do you do after the HOW-To to get things working? For example I believe that i have the device physically working
iwconfig
| Code: | root@lappy bung # iwconfig eth1
eth1 IEEE 802.11b/g ESSID:"RebelForce"
Mode:Managed Channel:6 Access Point: 00:C0:49:D8:EC:7C
Bit Rate:36Mb/s Tx-Power=31 dBm Sensitivity=20/200
Retry min limit:8 RTS thr:2347 B Fragment thr:2346 B
Encryption key:off
Link Quality:188/0 Signal level:-68 dBm Noise level:-53 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
|
ifconfig
| Code: | eth0 Link encap:Ethernet HWaddr 00:08:74:E4:0A:1A
inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1051 errors:0 dropped:0 overruns:0 frame:0
TX packets:609 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:914232 (892.8 Kb) TX bytes:60928 (59.5 Kb)
Interrupt:11 Base address:0xec80
eth1 Link encap:Ethernet HWaddr 00:05:5D:FA:69:BC
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:172 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20694 (20.2 Kb) TX bytes:0 (0.0 b)
Interrupt:11
...
|
Notice how IP is not set on eth1 BTW??? 
But now how do i use it now? it seems odd that no one else has had similar questions, i have to be missing something simple  . If i ping, linux uses the eth0 port, even while unplugged.
Simillarrly what is the hook doing in /etc/conf.d/net exactly? redirecting wireless to eth0 or just using the script?
Some people have net.eth1 scripts in /etc/init.d/ whereas I do not, how did this happen? Seeing how I dident acquire a net.eth1 script how would i get the wireless to automatically start up?
I am using a DWL-G650 PCMCIA card in a DELL INSPIRON 8200.
Thanks in advance for learning my confused self...
/etc/conf.d/net
| Code: | iface_eth0="192.168.0.5 broadcast 192.168.0.255 netmask 255.255.255.0"
iface_eth1="192.168.0.6 broadcast 192.168.0.255 netmask 255.255.255.0"
gateway="eth0/192.168.0.1"
source /etc/init.d/wireless.sh
preup() {
wireless_up ${1}
return $?
}
predown() {
wireless_down ${1}
return $?
} |
/etc/conf.d/wireless
| Code: |
essid_eth1="RebelForce"
mode_eth1="Managed"
channel_eth1="6"
sleep_scan_eth1="1"
sleep_associate_eth1="5"
|
EDIT
After submitting this and doing a | Code: | | ifconfig eth1 192.168.0.7 netmask 255.255.255.0 up |
i can now do a ping -I eth1 192.168.0.1 and get pings. But now how do i get the whole linux box to start using eth1 when it looses eth0?
_________________
Two idiots make a wrong |
|
| Back to top |
|
|
gmccague
n00b
Joined: 23 Aug 2004
Posts: 1
|
| Posted: Mon Aug 23, 2004 5:13 am Post subject: Bored with poor instructions? |
|
|
I'm bored with crappy instructions...
What are the proper steps to install this script? I get a "Specific key requires an operator (net-wireless/wireless-config-0.5.5)"
How about putting what we are supposed to be typing to execute each step of this tip? Some examples?
What about adding some code snippets of examples for PORTOVER what the freaking variable is?
I love this distro and hate it at the same time. I'm not sure it is worth the effort. |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Mon Aug 23, 2004 10:31 am Post subject: |
|
|
| kzan wrote: | ok...i know i'm doing something completely stupid, but can anyone tell me why I am getting this...
| Code: |
root@laptop /etc/init.d # /etc/init.d/net.eth1 start
find: /etc/net.modules.d/: No such file or directory
* Loading networking scripts...
* modules: [ ok ]
* Running preup function
* Configuring wireless network for eth1
* Scanning for access points
* Found "OFFICE" at 00:0F:3D:61:FF:2A (WEP required)
* Found "wlan3" at 00:20:A6:4F:4B:35
* Found "wlan4" at 00:0D:88:3E:94:D5 (WEP required)
* Found "wlan5" at 00:20:A6:50:9F:0B
* Connecting to "OFFICE" (WEP enabled)... [ ok ]
* eth1 connected to "OFFICE" in managed mode
* on channel 3 (WEP enabled)
* configuration has not been set!
|
I have tried everything I can think of without a solution... |
I know that you found the solution, but it's only fair to point out that the net-scripts package is still in early days and is completely un-supported by me at this stage. Unless you get me on IM that is...
_________________
Use dhcpcd for all your automated network configuration needs
Use dhcpcd-ui (GTK+/Qt) as your System Tray Network tool |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Mon Aug 23, 2004 10:32 am Post subject: Re: late reply |
|
|
| Onnelinen wrote: | | UberLord wrote: |
Do you see anything in the output for wireless? |
Sorry for the late reply... been away for a while. What do you mean by the output for wireless? You mean the output i should get from /etc/init.d/net.wlan0 start ? There I do not get any wireless specific information... The hook in /etc/conf.d/net i am sure i have. My card works with the hostap_pci drivers. I can use iwconfig as i should.. I am actually surfing using my wireless card, so the problem is not hardware-related. What else should be present to use the script apart from the hook and net.wlan0? (my net.wlan0 is a copy of net.eth0) |
That's the problem I think - net.wlan0 should be a symlink to net.eth0 instead of a direct copy.
_________________
Use dhcpcd for all your automated network configuration needs
Use dhcpcd-ui (GTK+/Qt) as your System Tray Network tool |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Mon Aug 23, 2004 10:36 am Post subject: Re: Documentation Gap |
|
|
| bungernut wrote: |
After submitting this and doing a | Code: | | ifconfig eth1 192.168.0.7 netmask 255.255.255.0 up |
i can now do a ping -I eth1 192.168.0.1 and get pings. But now how do i get the whole linux box to start using eth1 when it looses eth0? |
The actual problem is that both NICs are using the same network, and I'm not sure how apps use NICs when both "do the same". AFAIK it's the first one that comes up.
As to using eth1 when eth0 is down, I suggest looking into the ifplugd package for eth0. You may have problems using it with eth1 - if so, set eth1 to start at default and write some code in the preup to check if eth1 is being started and cause a fail (return1) if eth0 is running. I think I posted code (untested) which does this a page or two back.
_________________
Use dhcpcd for all your automated network configuration needs
Use dhcpcd-ui (GTK+/Qt) as your System Tray Network tool |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Mon Aug 23, 2004 10:46 am Post subject: Re: Bored with poor instructions? |
|
|
| gmccague wrote: | | I'm bored with crappy instructions... |
Most people can follow mine - write some better ones if you can.
| Quote: |
What are the proper steps to install this script? I get a "Specific key requires an operator (net-wireless/wireless-config-0.5.5)" |
I gave proper steps in the 1st post on this page. I think your error is because you put -0.5.5 in /etc/portage/package.keywords[/quote]
| Quote: |
How about putting what we are supposed to be typing to execute each step of this tip? Some examples? |
I thought I did ........
Yep, just double checked.
| Quote: |
What about adding some code snippets of examples for PORTOVER what the freaking variable is? |
PORTDIR_OVERLAY is a variable that specifies a portage overlay directory - so you can put ebuilds like this in which do not get affected when you do an emerge sync.
Thats a Gentoo variable - why don't you read some of their docs?
| Quote: |
I love this distro and hate it at the same time. I'm not sure it is worth the effort. |
I took the effort to write this script. I'm a developer not a documentator. I write code for a day job because I do it well. My company employs other people to write documentation because I don't document that well.
I wrote this script in my spare time, off my own back and try to support it to the best of my ability. If you don't like that then you can shove it my friend.
_________________
Use dhcpcd for all your automated network configuration needs
Use dhcpcd-ui (GTK+/Qt) as your System Tray Network tool |
|
| Back to top |
|
|
MrSandman666
Tux's lil' helper
Joined: 09 Nov 2003
Posts: 96
Location: Hamburg, Germany
|
| Posted: Tue Aug 24, 2004 9:49 pm Post subject: |
|
|
Praise the Lord! Praise the UberLord for sendung us this script!
Great work! Was actually much easier to set up and to handle than I expected!
Is there any chance we'll see this in portage any time soon?
_________________
Mr. Sandman bring me a dream... |
|
| Back to top |
|
|
GreenPea
n00b
Joined: 24 Jan 2003
Posts: 25
Location: Boise ID
|
| Posted: Tue Aug 24, 2004 10:07 pm Post subject: |
|
|
| UberLord wrote: | | GreenPea wrote: |
Now my antena stays off until I /etc/init.d/net.wlan0 start and it turns off when I /etc/init.d/net.wlan0 stop.
I understand this is not for everyone, but it works well for me since I am wired most of the time and want my wireless only when I want it.
I am not a coder so I must beg some help or at least a pointer in the right direction. Is there a script or config that will start eth0 on start up, and if that works move on with the rest of the start up skipping wlan0, but if it fails, try to start wlan0 using wireless-config? This would save a lot of hassle of having to go back and rerun ssh, ntpdate etc startup scripts after eth0 fails and I manualy start wlan0. |
This should work for you
| Code: |
###########################################
# Hook wireless into /etc/init.d/net.eth0
# Please note, these lines should appear
# at the END of the file
source /etc/init.d/wireless.sh
preup() {
local iface=${1}
if [[ wlan0 == ${iface} ]]; then
modprobe ndiswrapper
wireless_up ${iface}
return $?
else
return 0
fi
}
postdown() {
local iface=${1}
if [[ wlan0 == ${iface} ]]; then
wireless_down ${iface}
rmmod ndiswrapper
return $?
else
return 0
fi
}
# End hook
########################################### |
|
[quote="UberLord"] | GreenPea wrote: |
This is the process I was hoping for:
(durring boot)-> start eth0 IF DHCP success -> skip trying wlan0 and move on with the rest of the start up IF eth0 DHCP timout or fails -> try wlan0 (success or fail) move on with boot
|
OK - this is tricky
You will need to put both eth0 and wlan0 in default runlevel for both to start
eth0 will always be tried first (rc goes in alpha order)
So, you need to add some code to preup to case a failure if the iface is wlan0 and eth0 is started
| Code: |
local status=$( rc-status default | awk '/net.eth0/ {print $3}' | grep started )
if [[ -n ${status} ]]; then
eerror "net.eth0 has been started - aborting net.wlan0 startup"
return 1
fi
|
I really appreciate you help with this btw. I am fairly convinced that these two pieces of code need to be tied together for this to work as hoped for? I have tried putting them together with no success, hence why I state previously, I am not a coder.... May I ask your indulgence one more time?
Thanks
GP |
|
| Back to top |
|
|
Avantopia
n00b
Joined: 20 Feb 2004
Posts: 4
Location: Los Angeles
|
| Posted: Wed Aug 25, 2004 12:33 am Post subject: WIFI freezes GNOME |
|
|
When I log into Gnome now that I have my pcmcia wireless 802.11b orinoco card up and running the splash screen freezes. I can't get past the splash screen. If I log into Gnome and THEN run my wifi everything is fine. What would cause this? I can't seem to pin point the issue. It seems to have something to do with the gnome-smproxy application and my pcmcia setup.
_________________
mutually recursive |
|
| Back to top |
|
|
imesg
Guru
Joined: 12 Jul 2002
Posts: 451
|
| Posted: Wed Aug 25, 2004 1:30 am Post subject: |
|
|
Can I do this:
perffered_aps=( "my-essid" "any" )
If so, how can I get my wlan device to use dhcp if it falls back to "any"?
The IP for "my-essid" is static.
If I can not do this how can I scan for "my-essid" first and set a static IP and fall back to "any" and use dhcp if "my-essid" is not available?
Thanks,
Gene |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Wed Aug 25, 2004 8:44 am Post subject: Re: WIFI freezes GNOME |
|
|
| Avantopia wrote: | | When I log into Gnome now that I have my pcmcia wireless 802.11b orinoco card up and running the splash screen freezes. I can't get past the splash screen. If I log into Gnome and THEN run my wifi everything is fine. What would cause this? I can't seem to pin point the issue. It seems to have something to do with the gnome-smproxy application and my pcmcia setup. |
I'd say it's something "network" related rather than "wireless" related.
AFAIK the fix is to set your hostname.domainname against 127.0.0.1 in /etc/hosts
_________________
Use dhcpcd for all your automated network configuration needs
Use dhcpcd-ui (GTK+/Qt) as your System Tray Network tool |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Wed Aug 25, 2004 8:50 am Post subject: |
|
|
| imesg wrote: | Can I do this:
perffered_aps=( "my-essid" "any" ) |
No. You can do preferred_aps=( "my-essid" )
Then set a static ip for my-essid
| Code: | | ifconfig_my_essid="192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0" ) |
Here's the clever bit - you set the iface for dhcp by default
| Code: | | ifconfig_eth0=( "dhcp" ) |
You may be thinking WTF at this point, but here's how it works.
All variables in conf.d/net are loaded before the net.eth0 actually runs. So when the wireless script runs it can overwrite (in memory, not the disk) any variables already set.
So what we've done here it configure a default of DHCP, but when it connects to my-essid then it sets a static IP.
You can use the same trick with all variables found in /etc/conf.d/net 
_________________
Use dhcpcd for all your automated network configuration needs
Use dhcpcd-ui (GTK+/Qt) as your System Tray Network tool |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Wed Aug 25, 2004 10:01 am Post subject: |
|
|
| GreenPea wrote: |
I really appreciate you help with this btw. I am fairly convinced that these two pieces of code need to be tied together for this to work as hoped for? I have tried putting them together with no success, hence why I state previously, I am not a coder.... May I ask your indulgence one more time?
|
| Code: |
###########################################
# Hook wireless into /etc/init.d/net.eth0
# Please note, these lines should appear
# at the END of the file
source /etc/init.d/wireless.sh
preup() {
local iface=${1}
if [[ wlan0 == ${iface} ]]; then
local status=$( /etc/init.d/net.eth0 status | grep started )
if [[ -n ${status} ]]; then
eerror "net.eth0 has been started - aborting net.wlan0 startup"
return 1
fi
modprobe ndiswrapper
wireless_up ${iface}
return $?
fi
return 0
}
postdown() {
local iface=${1}
if [[ wlan0 == ${iface} ]]; then
wireless_down ${iface}
rmmod ndiswrapper
return $?
else
return 0
fi
}
# End hook
###########################################
|
There you go
_________________
Use dhcpcd for all your automated network configuration needs
Use dhcpcd-ui (GTK+/Qt) as your System Tray Network tool |
|
| Back to top |
|
|
imesg
Guru
Joined: 12 Jul 2002
Posts: 451
|
| Posted: Wed Aug 25, 2004 11:42 am Post subject: |
|
|
Thanks, uberlord for the help and the script.
| UberLord wrote: | | imesg wrote: | Can I do this:
perffered_aps=( "my-essid" "any" ) |
No. You can do preferred_aps=( "my-essid" )
Then set a static ip for my-essid
| Code: | | ifconfig_my_essid="192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0" ) |
|
I also had to set the default gw in /etc/conf.d/wireless, so for reference for anyone else that might want to do it this way, I had to do this also:
| Code: | | routes_my-essid=( "default gw my-gateway" ) |
Where 'routes_my-essid' is really 'routes_ESSID'.
| Quote: |
Here's the clever bit - you set the iface for dhcp by default
| Code: | | ifconfig_eth0=( "dhcp" ) |
You may be thinking WTF at this point, but here's how it works.
All variables in conf.d/net are loaded before the net.eth0 actually runs. So when the wireless script runs it can overwrite (in memory, not the disk) any variables already set.
So what we've done here it configure a default of DHCP, but when it connects to my-essid then it sets a static IP.
You can use the same trick with all variables found in /etc/conf.d/net |
|
|
| Back to top |
|
|
GreenPea
n00b
Joined: 24 Jan 2003
Posts: 25
Location: Boise ID
|
| Posted: Wed Aug 25, 2004 5:26 pm Post subject: |
|
|
BINGO!!! UberLord you are my personal hero for the week! It all works as advertised. With the PreUP additions you wrote all I do is boot. eth0 is checked and if it does not get an address, wlan0 comes up. If wlan0 does not come up, the antenna stays off saving power.
It is people like you that make running Linux more useful than running Windoze. Thank you very much. |
|
| Back to top |
|
|
ToddWest
n00b
Joined: 11 Nov 2003
Posts: 59
Location: Oregon
|
| Posted: Wed Aug 25, 2004 6:48 pm Post subject: |
|
|
Ive tried to fix this on my own but I just cant figure out whats going on. I installed ndiswrapper with my IPW2200 and I can start it perfectly on my own:
| Code: | iwconfig wlan0 mode Managed
iwconfig wlan0 key XXXXXXXXXXXXXXXXXXXXXXXXXX
iwconfig wlan0 essid myessid
dhcpcd wlan0 |
But I dont want to have to start it manually every time I reboot. So I tried using this script but Im stuck and cant figure out how to fix it. If I run /etc/init.d/net.wlan0 start it says this:
| Code: | * Running preup function
* Configuring wireless network for wlan0
* Scanning for access points
* Found XX:XX:XX:XX:XX:XX (WEP required)
* Trying to force preferred incase they are hidden
* Connecting to "myessid" (WEP enabled)... [ ok ]
* wlan0 connected to "myessid" in managed mode
* on channel 06 (WEP disabled)
* Bringing wlan0 up via DHCP...
|
My AP is running WEP 128-bit. I dont understand why its saying (WEP disabled) when Im setting the key and everything in my /etc/conf.d/wireless file. Here is my wireless config file:
| Code: | # /etc/conf.d/wireless:
# Global wireless config file for net.* rc-scripts
##############################################################################
# HINTS
##############################################################################
# Remember to change eth0 to your wireless interface which may be
# eth0, eth1, wlan0, ath0 - you get the idea. If you're not sure
# you can type "iwconfig" at the command prompt and it will tell you which
# interfaces are wireless.
# Say that your wireless interface is ath0 - the line
# #essid_eth0="any"
# becomes
# #essid_ath0="any"
#
# Remember to change ESSID to your ESSID.
# Say that your ESSID is My NET - the line
# #key_ESSID="s:passkey"
# becomes
# #key_My_NET="s:passkey"
# Notice that the space has changed to an underscore - do the same with all
# characters not in a-z A-Z (english alphabet) 0-9.
#
# Any ESSID's in quotes like essid_eth0="My NET" may need to be escaped
# This means placing the character \ before the character
# \" need to be escaped for example
# So if your ESSID is
# My "\ NET
# it becomes
# My \"\\ NET
# for example
# #essid_eth0="My\"\\NET"
#
# As a final note, most users will just need to set the following options
# key_ESSID1="s:yourkeyhere enc open"
# key_ESSID2="s:yourothrkey enc open"
# preferred_aps=( "ESSID1" "ESSID2" )
#
# Clear? Good. Now configure your wireless network below
#########################################################
##############################################################################
# SETTINGS
##############################################################################
# Hard code an ESSID to an interface - leave this unset if you wish the driver
# to scan for available Access Points
# Set to "any" to connect to any ESSID - the driver picks an Access Point
# This needs to be done when the driver doesn't support scanning
# This may work for drivers that don't support scanning but you need automatic
# AP association
# I would only set this as a last resort really - use the preferred_aps
# setting at the bottom of this file
# However, using ad-hoc (without scanning for APs) and master mode
# do require the ESSID to be set - do this here
#essid_wlan0="myessid"
# Set the mode of the interface (managed, ad-hoc or master). Managed is default
# If it's ad-hoc or master you also may need to specify the channel below
#mode_wlan0="Managed"
# If managed mode fails, drop to ad-hoc mode with the below ESSID?
#adhoc_essid_eth0="myessid"
#Channel can be set (1-14), but defaults to 3 if not set.
#
# The below is taken verbatim from the BSD wavelan documentation found at
# http://www.netbsd.org/Documentation/network/wavelan.html
# There are 14 channels possible; We are told that channels 1-11 are legal for
# North America, channels 1-13 for most of Europe, channels 10-13 for France,
# and only channel 14 for Japan. If in doubt, please refer to the documentation
# that came with your card or access point. Make sure that the channel you
# select is the same channel your access point (or the other card in an ad-hoc
# network) is on. The default for cards sold in North America and most of Europe
# is 3; the default for cards sold in France is 11, and the default for cards
# sold in Japan is 14.
channel_wlan0="6"
# Setup any other config commands. This is basically the iwconfig argument
# without the iwconfig $iface
#iwconfig_eth0=""
# Set private driver ioctls. This is basically the iwpriv argument without
# the iwpriv $iface
#iwpriv_eth0=""
# We can define various timeouts here.
#sleep_scan_eth0="1"
#sleep_associate_eth0="5"
# By default a successful association in Managed mode sets the MAC
# address of the AP connected to. However, some drivers (namely
# the ipw2100) don't set an invalid MAC address when association
# fails - so we need to check on link quality which some drivers
# don't report properly either.
# So if you have connection problems try flipping this setting
# Valid options are MAC, quality and all - defaults to MAC
#associate_test_eth0="quality"
# Some driver/card combinations need to scan in Ad-Hoc mode
# After scanning, the mode is reset to the one defined above
#scan_mode_eth0="Ad-Hoc"
# Below you can define private ioctls to run before and after scanning
# Format is the same as the iwpriv_eth0 above
# This is needed for the HostAP drivers
#iwpriv_scan_pre_eth0="host_roaming 2"
#iwpriv_scan_post_eth0="host_roaming 0"
# Define a WEP key per ESSID or MAC address (of the AP, not your card)
# You can't use "any" for an ESSID here
key_myessid="XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX"
# or you can use strings. Passphrase IS NOT supported
# Note - this example also sets the encryption method to open
# which is regarded as more secure than restricted
# The encryption type (open or restricted) must match the
# encryption type on the Access Point
#key_ESSID="s:foobar enc open"
#key_ESSID="s:foobar enc restricted"
# WEP key for the AP with MAC address 001122334455
#mac_key_001122334455="s:foobar"
# Here are some more examples of keys as some users find others work
# and some don't where they should all do the same thing
#key_ESSID="open s:foobar"
#key_myessid="open XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX"
#key_ESSID="s:foobar enc open"
#key_ESSID="1234-5678-9012 enc open"
# You may want to set muliple keys - here's an example
# It sets 4 keys on the card and instructs to use key 2 by default
#key_ESSID="[1] s:passkey1 key [2] s:passkey2 key [3] s:passkey3 key [4] s:passkey4 key [2]"
# You can also override the interface settings found in /etc/conf.d/net
# per ESSID - which is very handy if you use different networks a lot
#ifconfig_ESSID=( "dhcp" )
#dhcpcd_ESSID="-t 5"
#inet6_ESSID=()
#routes_ESSID=()
#ifconfig_fallback_ESSID=()
# iproute-2 style setup
#ipaddr_ESSID=( "dhcp" )
#iproute_ESSID=()
#ipaddr_fallback_ESSID=()
# Setting name/domain server causes /etc/resolv.conf to be overwritten
# Note that if DHCP is used, and you want this to take precedence then
# please put -R in your dhcpcd options
#nameserver_ESSID="192.168.0.1"
#domain_ESSID="some.domain"
# You can also set any of the /etc/conf.d/net variables per MAC address
# incase you use Access Points with the same ESSID but need different
# networking configs. Below is an example - of course you use the same
# method with other variables
#mac_ifconfig_001122334455=( "dhcp ")
#mac_dhcpcd_001122334455="-t 10"
# LEAP users will want to use the preassociate setting to specify
# an authentication script
#preassociate_ESSID="/run/this/script"
# Map a MAC address to an ESSID
# This is used when the Access Point is not broadcasting it's ESSID
# WARNING: This will override the ESSID being broadcast due to some
# Access Points sending an ESSID even when they have been configured
# not too!
# Change 001122334455 to the MAC address and ESSID to the ESSID
# it should map to
#essid_001122334455="ESSID"
# This lists the preferred ESSIDs to connect to in order
# ESSID's can contain any characters here as they must match the broadcast
# ESSID exactly.
# Surround each ESSID with the " character and seperate them with a space
# If the first ESSID isn't found then it moves onto the next
# If this isn't defined then it connects to the first one found
#preferred_aps=( "ESSID 1" "ESSID 2" )
# You can also define a preferred_aps list per interface
#preferred_aps_eth0=( "ESSID 3" "ESSID 4" )
preferred_aps=( "myessid" )
# You can also say whether we only connect to preferred APs or not
# Values are "yes" and "no"
# Default is "no"
#preferred_only="no"
#preferred_only_eth0="no"
# You can define blacklisted Access Points in the same way
#blacklist_aps=( "ESSID 1" "ESSID 2" )
#blacklist_aps_eth0=( "ESSID 3" ESSID 4" )
# If you have more than one wireless card, you can say if you want
# to allow each card to associate with the same Access Point or not
# Values are "yes" and "no"
# Default is "yes"
#unique_ap="yes"
#unique_ap_eth0="yes"
# IMPORTANT: preferred_aps, preferred_only, blacklisted_aps and
# unique_ap only work when essid_eth0 is not set and your card
# is capable of scanning
# NOTE: preferred_aps list ignores blacklisted_aps - so if you have
# the same ESSID in both, well, you're a bit silly :p
|
Some more info about my setup:
gentoo-dev-sources 2.6.8-r2
Pentium M 1.60Ghz w/ Centrino
IPW2200 with WEP 128-bit
0.10 ndiswrapper
Thanks. |
|
| Back to top |
|
|
Michen
n00b
Joined: 03 Aug 2004
Posts: 2
|
| Posted: Wed Aug 25, 2004 8:35 pm Post subject: wlan0 works but is interrupted by bigger transfers |
|
|
Hi,
I've got your script working easily with DLINK 650+ and AP DLINK 624+.
I can ping and the connection goes infinitely.
When I start transferring files the connection suddenly dies after about 1 second.
What could it be? |
|
| Back to top |
|
|
Avantopia
n00b
Joined: 20 Feb 2004
Posts: 4
Location: Los Angeles
|
| Posted: Thu Aug 26, 2004 12:48 am Post subject: |
|
|
| Quote: | PostPosted: Wed Aug 25, 2004 3:44 am Post subject: Re: WIFI freezes GNOME Reply with quote
Avantopia wrote:
When I log into Gnome now that I have my pcmcia wireless 802.11b orinoco card up and running the splash screen freezes. I can't get past the splash screen. If I log into Gnome and THEN run my wifi everything is fine. What would cause this? I can't seem to pin point the issue. It seems to have something to do with the gnome-smproxy application and my pcmcia setup.
I'd say it's something "network" related rather than "wireless" related.
AFAIK the fix is to set your hostname.domainname against 127.0.0.1 in /etc/hosts |
This did not fix the issue unfortunately. I think it may have to do with the fact that I have 2 iface entries in my net config file and and during the pcmcia setup at boot cardmgr complains about eth2 already being setup. I am unsure how to debug this networking issue. Any ideas where to start if /etc/hosts isn't the cause? thanks for the help.
_________________
mutually recursive |
|
| Back to top |
|
|
Cheesepie
Apprentice
Joined: 19 Jan 2004
Posts: 154
|
| Posted: Thu Aug 26, 2004 1:31 am Post subject: |
|
|
Uberlord, just wanted to say thanks for an awesome script!
I couldn't get WEP working at first, but then I removed the "s:" from the WEP key and it worked. Now I'm sitting on the curb at the corner using the gentoo forums on my laptop 
Quick question though, what does the default "s:" in the WEP key do? |
|
| Back to top |
|
|
|
Networking & Security
