I need to have my wireless up before NIS authentication. I read somewhere that wpa_supplicant can do the job. Is there a guide somewhere that is somewhat recent that details how to do it for opensuse 11.3?
Do youi use “traditional with ifup” or network manager. The first will have your network up and running during the boot sequence (as all Unix/Linux system have done for ages). The second will up the network underr end-user direction end thus only after a user logs in (as is required for traveling laptops and the like).
I’ve set ifup in Yast but it is not working with wireless. ifup with wired works fine.
If you set the networking to ifup, configuration of the networkcards, incl. wireless is available. You still have to configure the card though, incl. proper ESSID, sec. protocol and passphrase. Wired interfaces are configured to use DHCP by default, so that will work. Protected Wifi needs the configuration of the card.
You are a bit short with your info. When you say “I’ve set ifup in Yast but it is not working with wireless”, I, like Knurpht want of course to know what you all filled in in YaST (you will prefer NOT to post pass phrases here of course). We can not help when you do not tell us what you do there. We can not look over your shoulder.
Can you please output the contents of /etc/sysconfig/network/ifcfg-wlan0:
cat /etc/sysconfig/network/ifcfg-wlan0
because it is there where YaST puts the parameters you gave it. (And again: obfuscate your passphrase in there!)
Here it is. Once i’m in gnome I am connected through the wireless.
BOOTPROTO=‘dhcp’
BROADCAST=’’
ETHTOOL_OPTIONS=’’
IPADDR=’’
MTU=’’
NAME=‘Wireless WiFi Link 5100’
NETMASK=’’
NETWORK=’’
REMOTE_IPADDR=’’
STARTMODE=‘auto’
USERCONTROL=‘no’
WIRELESS_AP=’’
WIRELESS_AP_SCANMODE=‘1’
WIRELESS_AUTH_MODE=‘psk’
WIRELESS_BITRATE=‘auto’
WIRELESS_CA_CERT=’’
WIRELESS_CHANNEL=’’
WIRELESS_CLIENT_CERT=’’
WIRELESS_CLIENT_KEY=’’
WIRELESS_CLIENT_KEY_PASSWORD=’’
WIRELESS_DEFAULT_KEY=‘0’
WIRELESS_EAP_AUTH=’’
WIRELESS_EAP_MODE=’’
WIRELESS_ESSID=‘happy’
WIRELESS_FREQUENCY=’’
WIRELESS_KEY=’’
WIRELESS_KEY_0=’’
WIRELESS_KEY_1=’’
WIRELESS_KEY_2=’’
WIRELESS_KEY_3=’’
WIRELESS_KEY_LENGTH=‘128’
WIRELESS_MODE=‘Managed’
WIRELESS_NICK=’’
WIRELESS_NWID=’’
WIRELESS_PEAP_VERSION=’’
WIRELESS_POWER=‘yes’
WIRELESS_WPA_ANONID=’’
WIRELESS_WPA_IDENTITY=’’
WIRELESS_WPA_PASSWORD=’’
WIRELESS_WPA_PSK=’********’
PREFIXLEN=‘24’
Thanks.
First, please next time that you provide computer output, place CODE tags around it. In this case readbility is fine, but often the lay-out of computer text vanished when CODE is not used: Posting in Code Tags - A Guide.
Then your output. It looks as if it is configured to start on boot (USERCONTROL=‘no’) and not when the desktop (in your case Gnome is used)!
Further, it has to connnect to the router with WIRELESS_ESSID=‘happy’ in WIRELESS_MODE=‘Managed’ using WIRELESS_AUTH_MODE=‘psk’ (that is WSA-PSK). I think that you checked if WIRELESS_WPA_PSK=’********’ was correct before you changed it into the ***.
That looks all perfect to me. I manage a system which has the same parameters, not only the ones mentioned above, but the whole list, inclusing the emtpty ones.
I other words, why does this not start on boot? And maybe a bit nasty, are you sure it does not start on boot. we will try to find out.
Please boot the sytem, BUT DO NOT login in the GUI. When the loginscreen is there type Ctrl-Alt-F1 (that is: hold don the Ctrl and Alt keys and press the F1 key). That will the change the screen to the console. There will be a login prompt. Login there with your normal username andd password (when typing your password, you will see no echo, not even *s). Then type
/sbin/ifconfig -a
There will be a section about wlan0. Does it contain an IP addreess?
You can not copy/paste from here, but you can save the output generated above with
/sbin/ifconfig -a >/tmp/ifcsaved
logout by typing:
exit
and go back to the GUI login with Ctrl-Alt-F7. Now login normaly, open a terminal and do:
cat /tmp/ifcsaved
Copy and paste in a post.
Second thing you can do here is:
dmesg | less
use the SPACE bar to page through that output and look were it says something about wlan0. Leave this by typing the q.
eth0 Link encap:Ethernet HWaddr 00:17:42:90:8C:48
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:766 errors:0 dropped:0 overruns:0 frame:0
TX packets:766 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:46756 (45.6 Kb) TX bytes:46756 (45.6 Kb)
wlan0 Link encap:Ethernet HWaddr 00:21:6B:97:E6:2E
inet addr:192.168.2.36 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:77 errors:0 dropped:0 overruns:0 frame:0
TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6334 (6.1 Kb) TX bytes:7798 (7.6 Kb)
It is connected at boot. I’m thinking that the problem might be with NFS. I want to mount another home directory over my local one, so /home/**** /home/**** mount options. Maybe NFS is not mounting on boot in the same order with wlan0 as it does with eth0.
PLEASE, I repeat what I said above about CODE tags. This output is hardly interpretable!
It should function the same if cabled or wireless. But it could be that the establishment of the connection takes more time.
Well you can check if the NFS mounts are there by doing the same as you did to check if wlan0 was up. With
mount[/mount/]
you can see what is mounted.
When it is timing you could try if it helps when you mount again at the very end of the boot sequence. This can be done by creating a file /etc/init.d/after.local as root and putting there the statement mount -a. In one command this can be dan with
su -c ‘echo “mount -a” >/etc/init.d/after.local’
Mind all the quoting! Best is to copy and past. It asks for the root password.I fixed it. Set my IP to static and added a sleep timer to /etc/init.d/nfs on the following line: mount -at nfs,nfs4
to
sleep 5 && mount -at nfs,nfs4 &
Congratulations.
It is quite possible that DHCP takes some time and when a fixed IP address does not hamper you further I would allways prefer it.
Do not forget to check if the nfs script isn’t updated and thus your change is lost. Especily if you go to the next openSUSE level.