if you are using WEP encryption, you have the option of using 4 different keys they will probably be listed as " key 1, key 2, key 3, key 4" and, so make sure the router is using Key 1 to accept the encryption, as linux will only allow(as far as I know) to use the first key.

I'm actually baffled as to why you can't connect.

Actually. I recently had problems using "ifup" and noticed that at some point someone had changed the method for calling "ifup-wireless" in the "ifup" script. After an install of Mandriva 2006 line #133 of "ifup" has the following:

exec ${OTHERSCRIPT} ${CONFIG} ${boot}

From the shell help:

exec: exec [-cl] [-a name] file [redirection ...]
Exec FILE, replacing this shell with the specified program.
If FILE is not specified, the redirections take effect in this
shell. If the first argument is `-l', then place a dash in the
zeroth arg passed to FILE, as login does. If the `-c' option
is supplied, FILE is executed with a null environment. The `-a'
option means to make set argv[0] of the executed process to NAME.
If the file cannot be executed and the shell is not interactive,
then the shell exits, unless the shell option `execfail' is set.

So basically anything set in the file that is exec'd doesn't stay set when the exec comes back unless it's exported (I think).

I changed line #133 to:

. ${OTHERSCRIPT} ${CONFIG} ${boot}

Again reading the shell help:

.: . filename [arguments]
Read and execute commands from FILENAME and return. The pathnames
in $PATH are used to find the directory containing FILENAME. If any
ARGUMENTS are supplied, they become the positional parameters when
FILENAME is executed.

This is the same as using the "source" shell command which is used in other places in the "ifup" script. Also this method is similar to what it used to be in Mandrake 2005LE.

For me everything started working again.

Hope this helps with running "ifup" from the commandline.

Also as a note. I usually pays to set the encryption key prior to setting the ESSID as some APs don't allow you to see them without the key installed.

Cheers
Julz

Hi, guys,

I have got a similar problem with a wireless card under Mandriva 2006. It says: Determining IP information for wlan0 ... failed.

well, post your network setup.

When configuring, avoid eth0, wlan0 or sit0 in your case, because they may conflict with the driver setting up.

If you can remove the any network cards, that makes it easier for config...

I've seen others too, ifup interface-name, (not, eth0 wlan0 or sit0)

if you are newbie at wireless have a good read of
http://www.linuxhomenetworking.com/w...ess_Networking

look at wikis as well

Welcome to the board
Well this is going nowhere: no information from you
You need to give as much info as possible, equipment, commands you used etc,
look in other posts for example

my 2cents if you are new to linux you need to read rute or newbie admin guide
(see LQ bookmarks)

Hi, and thanks for the suggestions. I have been tying this morning and here's what I get.

I was wondering if the card was installed at all (I used NdisWrapper).
So, here is what I get when I type

****************************

iwlist scan

wlan0 Scan completed :
Cell 01 - Address: 00:12:44:B8:9B:90
ESSID:"uio"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.472 GHz (Channel 13)
Quality:0/100 Signal level:-77 dBm Noise level:-256 dBm
Encryption keyn
Bit Rate:1 Mb/s
Bit Rate:2 Mb/s
Bit Rate:5.5 Mb/s
Bit Rate:6 Mb/s
Bit Rate:9 Mb/s
Bit Rate:11 Mb/s
Bit Rate:12 Mb/s
Bit Rate:18 Mb/s
Extra:bcn_int=100
Extra:atim=0
(Unknown Wireless Token 0x8C05)***********************************

Here is the output of iwconfig:

*****************************

wlan0 IEEE 802.11b ESSIDff/any Nickname:"at_home"
Mode:Auto Frequency:2.412 GHz Access Point: 00:00:00:00:00:00
Bit Rate=11 Mb/s Tx-Power:20 dBm Sensitivity=0/3
RTS thr=2432 B Fragment thr=2432 B
Encryption keyff
Power Managementff
Link Quality:100/100 Signal level:-95 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0



****************************

I don't know why it does not take into account the settings which I introduced from the graphical tool (Mandriva Control Center) which correspond to the network ones.

In /etc/sysconfig/network-scripts/wireless.d/

I have got two files whose content I list below.

[root@at_home wireless.d]# ls
00:12:44:b8:9b:90* uio*

[root@at_home wireless.d]# more 00\:12\:44\:b8\:9b\:90
BOOTPROTO=dhcp
WIRELESS_MODE=Managed
WIRELESS_ESSID=uio
WIRELESS_WPA_DRIVER=ndiswrapper

[root@at_home wireless.d]# more uio
DEVICE=wlan0
BOOTPROTO=dhcp
IPADDR="No IP"
NETMASK="No Mask"
BROADCAST=255
ONBOOT=yes
HWADDR=00:50:fc:f1:de:7c
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=no
WIRELESS_MODE=Managed
WIRELESS_ESSID=uio
IPV6INIT=no
IPV6TO4INIT=no
PEERDNS=yes
NETMASK="No Mask"
IPADDR="No IP"
DHCP_CLIENT=dhclient
NEEDHOSTNAME=yes
PEERDNS=yes
PEERYP=no
PEERNTPD=no

*************************************

When trying to t smth like
iwconfig wlan0 essid uio

non pop up messages, but no result either

thanks

nikolai

Glenn, do you mean removing the cards (eth0, sit0) or just setting 'no' option on boot?
Thanks

nikolai

Start a terminal as root and look for clues
tail -f /var/log/syslog

then in another terminal modprobe ndiswrapper and
for example as root
service network restart

Have you googled for this?

I can help only a bit (time restriction) so you need a good
dose of research, self-help and homework, or somebody else help.
You are definetely in the right direction

Emmanuel_uk, thanks. Here is what I get in a syslog. Weird - I have configured wlan0, yet it seems to be looking for eth0. I have a ifcfg-eth0 file (I am not using my ethernet card), so shall I simply remove it and configure the wireless card as eth0. Actually this is what Glen suggested above, in the posting...


[root@at_home niki]# tail -f /var/log/syslog
Oct 18 11:10:04 at_home dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Oct 18 11:10:28 at_home last message repeated 2 times
Oct 18 11:10:28 at_home drakroam[5415]: ### Program is exiting ###
Oct 18 11:10:40 at_home dhclient: No DHCPOFFERS received.
Oct 18 11:10:40 at_home ifplugd(eth0)[5468]: client: Determining IP information for eth0... failed.
Oct 18 11:10:40 at_home ifplugd(eth0)[5468]: Program execution failed, return value is 1.
Oct 18 11:10:40 at_home ifplugd(eth0)[5468]: Exiting.
Oct 18 11:10:50 at_home net_applet[4239]: running: /sbin/iwgetid -r wlan0
Oct 18 11:10:50 at_home net_applet[4239]: running: /sbin/iwgetid -r -a wlan0
Oct 18 11:10:50 at_home net_applet[4239]: running: /sbin/iwlist wlan0 scanning
Oct 18 11:11:50 at_home net_applet[4239]: running: /sbin/iwgetid -r wlan0
Oct 18 11:11:50 at_home net_applet[4239]: running: /sbin/iwgetid -r -a wlan0
Oct 18 11:11:50 at_home net_applet[4239]: running: /sbin/iwlist wlan0 scanning
Oct 18 11:12:50 at_home net_applet[4239]: running: /sbin/iwgetid -r wlan0
Oct 18 11:12:50 at_home net_applet[4239]: running: /sbin/iwgetid -r -a wlan0
Oct 18 11:12:50 at_home net_applet[4239]: running: /sbin/iwlist wlan0 scanning

service network restart gives the following

Shutting down interface eth0 : ok
Shutting down interface wlan0 : ok
Setting network parameters : ok
bringing up interface sit0 : ok
bringing up interface wlan0 : ok

everything seems fine? Actually during startup, eth0 is disabled. I wonder why it is shutting it down here. Any clue??

disable eth0 whichever way you can
the eth0 errors have nothing to do with wlan0

I would expect a WEP key just below that (at some point later when you get it working)

This looked good apart from the lack of IP address

maybe try iwconfig wlan0 192.168.0.1
to give a fixed IP to your card
It sounds like somehow you do not get the dhcp offer from the wireless router

Sometimes, it is best to restart from scratch, log all the details
and see what step went wrong

am no expert at wireless

I'll do so. I'll even try to configure the card with a different driver - the one suggested by sourceforge. Yet, dsmeg says ndiswrapper is working properly, so is wlan0. Well, I proceed to the "from scratch approach".

Thanks, Emmanuel_uk

nikolai

Yes, If it's onboard the disabling should be ok, Firewire too if you don't need it to boot...

Don't config the wireless as eth0. eth is for 10/100 local area network adaptors.

If you turn the start daemon(service) off for eth0 then it should keep out of the way.

Glen, I cannot disable the Firewire, or probably, after disablibg eth0, the built-in network card appears as eth1? Is there a way to disable all of them on boot. I have a Mandriva and there is not such a thing like interfaces file. There are ifcfg-eth* ifcfg-wlan* etc. What shall I do?