Davide Bianchi wrote:
> It would be interesting to see which ip address you gave to the Wireless.
> ifconfig wlan0 should show something usefull. My reading of this is that
> your wireless is quite confused and doesn't know which ip to get.
So far as my knowledge allows: I'm quite sure the ip is ok. DHCP is
working much faster with wlan as it does with lan.
The router ip: 192.168.178.1
moskito:/home/modr # ifconfig wlan0
wlan0 Protokoll:Ethernet Hardware Adresse 00:90:4B:67:61:B8
inet Adresse:192.168.178.25 Bcast:192.168.178.255
Maske:255.255.255.0
inet6 Adresse: fe80::290:4bff:fe67:61b8/64
Gültigkeitsbereich:Verbindung
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:77 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:5988 (5.8 Kb) TX bytes:2064 (2.0 Kb)
Interrupt:11 Speicher:faffc000-faffdfff
and iwconfig says:
moskito:/home/modr # iwconfig wlan0
wlan0 IEEE 802.11g ESSID:"Webtechnics" Nickname:"moskito"
Mode:Managed Frequency:2.462GHz Access Point: 00:01:E3:41:6B:E3
Bit Rate=54Mb/s Tx-Power:25 dBm
RTS thr=2347 B Fragment thr=2346 B
Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx Security
mode:restricted
Power Management

ff
Link Quality:100/100 Signal level:-61 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:1 Invalid misc:190 Missed beacon:0
--------------------------------------------------------------------
I've no idea where to look any further. Sometimes i think it has
somthing to do with SuSE and/or me. I usually get probs often reportet
but can't be solved in the described manner.
But I still have hope an never give up!
TIA
Julian