Simple thing is really hard...

Hi.

Little problem occured again.

I setup wlan using ifup method. When I configure it in yast, network settings, it finds the AP’s on the second step of configuration. I chose the AP, setup the wpa-psk2 password. Everything goes on and I don’t really know how to start the wlan device to connect to the AP i specified.

What’s the command to start the connection, which was setup in yast?
I rather use ifup than knetworkmanager.

WLAN works by knetworkmanager, but if I connect through that - the repos won’t download. I don’t know why this occurs. Same with usb 3g stick which connects to the wireless internet. That’s why i like the wvdial old traditional ifup method.

Any hints?
Thanks

you should just have to do

ifup wlan0

Replace wlan0 with the name of your wireless interface, of course.

ATM the repos are down…so not a good test. That’s for one.

If you set networking to ifup, and you have, otherwise you couldn’t have configured the card, and the card configured correctly, it should work, immediately. The card should be started and connect during boot time, i.e. long before you login.

But…what is the network card? Please open a terminal and post output of:


su -c 'lspci '
(enter rootpassword)

also post output of:


ip addr


su -c 'lspci'

 00:00.0 Host bridge: Intel Corporation 82855PM Processor to
I/O Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation 82855PM Processor to
AGP Controller (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM
(ICH4/ICH4-M) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge
(rev 83)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC
Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M)
IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-
L/ICH4-M) SMBus Controller (rev 03)
00:1f.5 Multimedia audio controller: Intel Corporation
82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller
(rev 03)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-
L/ICH4-M) AC'97 Modem Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc RV350
[Mobility Radeon 9600 M10]
02:04.0 Ethernet controller: Atheros Communications Inc.
Atheros AR5001X+ Wireless Network Adapter (rev 01)
02:06.0 CardBus bridge: O2 Micro, Inc. OZ711M3/MC3 4-in-1
MemoryCardBus Controller
02:06.1 CardBus bridge: O2 Micro, Inc. OZ711M3/MC3 4-in-1
MemoryCardBus Controller
02:06.2 System peripheral: O2 Micro, Inc. OZ711Mx 4-in-1
MemoryCardBus Accelerator
02:06.3 CardBus bridge: O2 Micro, Inc. OZ711M3/MC3 4-in-1
MemoryCardBus Controller
02:0e.0 Ethernet controller: Broadcom Corporation NetXtreme
BCM5705M_2 Gigabit Ethernet (rev 03)


ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state
UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary
lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UP qlen 1000
link/ether 00:0d:9d:8d:c1:79 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.3/24 brd 192.168.0.255 scope global eth0
inet6 fe80::20d:9dff:fe8d:c179/64 scope link
valid_lft forever preferred_lft forever
3: irda0: <NOARP> mtu 2048 qdisc pfifo_fast state DOWN qlen 8
link/irda f3:9e:51:46 brd ff:ff:ff:ff
4: wmaster0: <> mtu 0 qdisc pfifo_fast state DOWN qlen 1000
link/ieee802.11 00:0f:20:94:2a:67 brd 00:00:00:00:00:00
5: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast
state DOWN qlen 1000
link/ether 00:0f:20:94:2a:67 brd ff:ff:ff:ff:ff:ff

weird

These lines show the card is not receiving an IP address:

5: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast
state DOWN qlen 1000
link/ether 00:0f:20:94:2a:67 brd ff:ff:ff:ff:ff:ff

So check your wpa-psk settings e.g. like here: http://opensuse.swerdna.org/nicifup/nic5.png

And that it’s set to start at boot time, e.g. like here: http://opensuse.swerdna.org/nicifup/nic6.png

Also, a few questions:

  1. does the card acquire an IP address if you run ifup start:
sudo /sbin/ifup wlan0
  1. if the above answer is “no”, then what return do you get to that command?
  2. what’s the response from this command:
sudo /usr/sbin/iwconfig

PS it might help (or not) to check these NIC setup screenshots too: Configure a network card in Suse/openSUSE 11.x for Internet Access & wifi.

One thing:
(I see swerdna is on it as well:))
Check in Yast whether the card is set to start at boottime…To do so:

Yast - Network devices - Network Settings
select the card, click Edit
In the General Tab, check wether it is configured to start at boottime. If not, set it to do so.

Hint, Hint:

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UP qlen 1000
link/ether 00:0d:9d:8d:c1:79 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.3/24 brd 192.168.0.255 scope global eth0
inet6 fe80::20d:9dff:fe8d:c179/64 scope link
valid_lft forever preferred_lft forever

Looks like the “classic” again.

Did you mean this as advice for euroage. If that’s a “yes” you probably should add some words that make it meaningful.

Axel’s little puzzles; often intrigue me:

I googled on

valid_lft forever preferred_lft forever

and from the links I came up with

IPv6 Source Address Selection on Linux | davidc.net

DD-WRT Forum :: View topic - Can’t get IPv6/radvd to work on my WRT610N

… I think Axel is pointing us towards IPv6 as a demon in here …

and I suspect that would lead us to caf’s guide

Disable IPv6

are we getting warm Axel?

You pointed out the “other classic”, which is not the problem (at least yet).

It is a lot more simple, and it’s about why all testing of the “non-functional wireless” does not make any sense, even if wireless itsself would work.

I will try to make it a little clearer (but only a little, as I don’t want to spoil the fun):

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state **UP** qlen 1000
link/ether 00:0d:9d:8d:c1:79 brd ff:ff:ff:ff:ff:ff
inet **192.168.0.3/24 **brd 192.168.0.255 scope global eth0
inet6 fe80::20d:9dff:fe8d:c179/64 scope link
valid_lft forever preferred_lft forever

Let’s say your spouse’s car has a problem with the “built-in” radio (pun intended).

Would you drive to the garage with your own car, which even hasn’t got a radio, and ask the mechanics to have a look at it?

(And yes, I love this “puzzling” …)

I see you asked for help 3 days ago eurorage. I have been waiting for Akoellh to explain further. The thread seems to have stalled on a game of cryptic clues and at this time horizon that’s really unfortunate. So maybe I’ll ask you to run some diagnostic tests to see if we can get it back on track. Please open a console and enter the command su to get rootly powers then run these commands and post back:

  • iwconfig
  • ifconfig
  • lspci -nn | egrep “etwork|thernet”

and tell us: what is your wireless device/interface?

If you are still out there eurorage, we could suggest you download this excellent diagnostic script overseen by Peter

collectNWData Schnellstart/Quickstart | collectNWData.sh

if you run this and post the results back

We know it is a very good script because Peter had advice from a well-known wireless expert, who is very well regarded