Intel Pro Wireless 3945

[treak007]

Hello, I have been trying to get my Intel Pro Wireless 3945 card to work on my dell latiude. I downloaded the intel linux drivers, and correctly installed ieee80211 that came with the drivers, however when I attempt to get make the actual card drivers, I get the error message attached. Any help would be greatly appreciated.

[asio_bob]

Simple way,

go to freshrpms.net

1. Download the driver rpm and install it
dkms-ipw3945

(the above dkms means it builds the module for you, its not precompiled, but you don't have to worry about compiling it either). Just install the above rpm, it will build the module for you to match your kernel (yum / rpm will check you meet the dependancy for this rpm (devel package for your kernel)

2. Download and install daemon rpm
ipw3945d

3. Download and install the ucode rpm
ipw3945-firmware

Add the following lines to /etc/modprobe.conf
install ipw3945 /sbin/modprobe --ignore-install ipw3945 ; sleep 0.5 ; /sbin/ipw3945d --quiet
remove ipw3945 /sbin/ipw3945d --kill ; sbin/modprobe -r --ignore-remove ipw3945

A ipw3945d service has already been installed as part of the driver package in step one.

Reboot (or modprobe ipw3945 and start the ipw3945d service) and you can move onto configuring a wifi connection which I've done by starting the NetworkManager service and letting it handle everything, it found my wifi network (I use gnome) and allowed me to enter my wifi WPA key etc.. and here I am.

Remember the following.
1. you need to re-install the dkms-ipw3945 rpm after a kernel upgrade.
2. You said you installed the ieee80211 subsystem, you'll may need to probably install a version of that for your new kernel if you upgrade (I think in this case you don't need to even install it if you get it from freshrpms) as long as you have a fairly up to date kernel (because that subsystem is compatible -- I think). The reason I'm not sure is because like you I installed it before finding freshrpms packages

[Mallgur]

Hi;

I tried these steps to get my 3945ABG to work. I did manage to get ipw3945d started and all, but when I start the Network Manager, it does not recognise my wireless network. I am using FC6 and when I go to System -> Administration -> Network, the wireless card is not there in the Hardware tab.

What else do I need to do?

Thanks.

[Mallgur]

Hi;

I tried these steps to get my 3945ABG to work. I did manage to get ipw3945d started and all, but when I start the Network Manager, it does not recognise my wireless network. I am using FC6 and when I go to System -> Administration -> Network, the wireless card is not there in the Hardware tab.

What else do I need to do?

Thanks.

[Eclipse19]

Check http://www.fedoraforum.org/forum/showthread.php?p=661455#post661455 and see if it has some helpful info. Particularly for NM not seeing your wireless card. If you use NetworkManager, I would suggest not using system-config-network.

May or may not be helpful.

[SouthPaw]

Not sure if this helps:
I usually struggle with wireless and Fedora releases. Especially since I have gotten a laptop with the iwp3945 driver. With FC6 it was a breeze. A lot easier then building packages. It is the easiest experience I have ever had in Linux.

First add the following lines to the /etc/yum.conf file

[atrpms]
name=Fedora Core $releasever - $basearch - ATrpms
enabled=1
baseurl=http://dl.atrpms.net/fc$releasever-$basearch/atrpms/stable
gpgkey=http://ATrpms.net/RPM-GPG-KEY.atrpms
gpgcheck=1

As su run the command
yum install ipw3945

edit the /etc/rc.d/rc.local file and add the line

/sbin/ipw3945d

REBOOT

Finally still as su run the command

system-config-network

Under hardware you should see your wireless adapter. Under devices choose new from the tool bar. Select wireless connections then forward, from the list select your wireless card then forward on the last screen enter your networks info such as SSID and WEP key.

The only problems that I have is that this setup does not roam well. Im also not sure how to configure WPA2 on this way either.

Good Luck



__________________________________________________ _____________________________________
Fedora Releases are like StarTrek movies, Only the even numbered ones are any good.

[trung_bmt]

If you want to compile the wireless driver, you will have to edit the source code a little bit. In the ipw3945.c, remove the #include <linux/config.c>, because this file was deprecated in fedora 5 and you no longer need it

you must install the kernel-devel package first

ieee80211 version: 1.2.15: compile:
#make (yes all the warning)
#make install

ipw3945 1.1.0 (after edited the source as mentioned above)
(as normal user): make

copy the daemon to /sbin (as in the instruction of ipw3945)
copy microcode (as in the instruction of ipw3945)

to start the wireless: go to the place you untar the ipw3945, run: #./load
you can now get the device up: iwconfig eth1 essid "MyNet" up
get IP: dhclient eth1

Hope it help. Feel free to ask if you have any difficulty.

[Mallgur]

Ok...

Thanks South_paw.
I maged to get the card to appear on the Network configuration.
The only problem is that I can't connect to any wireless network. When I try to activate the card, I get a failure to obtain IP address...
In campus we have one that is open and so, in XP, all you need to do is access the network and put in your username and password.
In FC6, the card appears as eth1 (shouldn't it be wth1?) and when I try to activate it, it fails. I have tried several combinations on the Wire less tab of the Network configuation window, but none works.
I don't have much information on the AP setup and it's hard to get info becaus I study at night, after work.

Maybe this is no longer related to Hardware and I should change the topic elsewhere? Thanks for any help.

[Eclipse19]

Just FYI, make sure you don't have it setup in system-config-network. If so, NM doesn't have full control over your wireless card. Also, you could "#service NetworkManager stop" and connect manually to test your wireless connection. I'm not sure but I think since the connection is open, you would do "#iwconfig essid=my-access-point". You might hafta play with the syntax as I haven't messed with it in a while. Afterwards, you might wanna make sure you set it back to "any" or "off" cuz I don't know if that is static or if it forgets it.

Sorry, apparantly I don't know much but maybe I can give you a push in the right direction.

[ever-free]

With my FujitsuSiemens V3505 I must first inactivate the other NIC. If the network connection with the cable is active, I always get error messages. Inactivate it first and try again. It seems, that only one NIC may be active.

[tbjudge]

Hi:

Im in the same boat , maybe a little further down the river but not complete yet.

I suspect your problem may be the ieee update. I found one in rpm format and that installed easy
My fedora is kernel 2.6.20.....

IN my case I can load the driver using the load utility that came with the package.
If I then restart my network manager svc I can see all the available nets
but cannot connect to ANY of them

sorry I cant be more help.

Tom Judge

[h*klown]

Simple way,

go to freshrpms.net

1. Download the driver rpm and install it
dkms-ipw3945

(the above dkms means it builds the module for you, its not precompiled, but you don't have to worry about compiling it either). Just install the above rpm, it will build the module for you to match your kernel (yum / rpm will check you meet the dependancy for this rpm (devel package for your kernel)

2. Download and install daemon rpm
ipw3945d

3. Download and install the ucode rpm
ipw3945-firmware

Add the following lines to /etc/modprobe.conf
install ipw3945 /sbin/modprobe --ignore-install ipw3945 ; sleep 0.5 ; /sbin/ipw3945d --quiet
remove ipw3945 /sbin/ipw3945d --kill ; sbin/modprobe -r --ignore-remove ipw3945

A ipw3945d service has already been installed as part of the driver package in step one.

Reboot (or modprobe ipw3945 and start the ipw3945d service) and you can move onto configuring a wifi connection which I've done by starting the NetworkManager service and letting it handle everything, it found my wifi network (I use gnome) and allowed me to enter my wifi WPA key etc.. and here I am.

Remember the following.
1. you need to re-install the dkms-ipw3945 rpm after a kernel upgrade.
2. You said you installed the ieee80211 subsystem, you'll may need to probably install a version of that for your new kernel if you upgrade (I think in this case you don't need to even install it if you get it from freshrpms) as long as you have a fairly up to date kernel (because that subsystem is compatible -- I think). The reason I'm not sure is because like you I installed it before finding freshrpms packages

Ok i downloaded dkms-ipw3945-1.2.0-1.src.rpm... do i install with yum like #yum install /home/hklown/Desktop/dkms-ipw3945-1.2.0-1.src.rpm ?

edit**
[[root@localhost hklown]# yum install /home/hklown/Desktop/dkms-ipw3945-1.2.0-1.src.rpm
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Parsing package install arguments
Examining /home/hklown/Desktop/dkms-ipw3945-1.2.0-1.src.rpm: dkms-ipw3945 - 1.2.0-1.noarch
Marking /home/hklown/Desktop/dkms-ipw3945-1.2.0-1.src.rpm to be installed
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package dkms-ipw3945.noarch 0:1.2.0-1 set to be updated
--> Running transaction check

Dependencies Resolved

================================================== ===========================
Package Arch Version Repository Size
================================================== ===========================
Installing:
dkms-ipw3945 noarch 1.2.0-1 /home/hklown/Desktop/dkms-ipw3945-1.2.0-1.src.rpm 198 k

Transaction Summary
================================================== ===========================
Install 1 Package(s)
Update 0 Package(s)
Remove 0 Package(s)

Total download size: 198 k
Is this ok [y/N]: y
Downloading Packages:
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
warning: user machbuild does not exist - using root
warning: group machbuild does not exist - using root
Installing: dkms-ipw3945 [1/1]warning: user machbuild does not exist - using root
warning: group machbuild does not exist - using root
Installing: dkms-ipw3945 ######################### [1/1]

Installed: dkms-ipw3945.noarch 0:1.2.0-1
Complete!
[root@localhost hklown]#

[tbjudge]

Actually I was referring to finding the ieee8011 as an rpm I did not realize that the ipw3945 was avail as an rpm

y not try that. Its already broken :-)

Let me know if it works?

TBK

[adking80]

asio_bob, thanks! Your guide did the trick perfectly. Gotta bookmark this.

[h*klown]

Simple way,

go to freshrpms.net

1. Download the driver rpm and install it
dkms-ipw3945

(the above dkms means it builds the module for you, its not precompiled, but you don't have to worry about compiling it either). Just install the above rpm, it will build the module for you to match your kernel (yum / rpm will check you meet the dependancy for this rpm (devel package for your kernel)

2. Download and install daemon rpm
ipw3945d

3. Download and install the ucode rpm
ipw3945-firmware

Add the following lines to /etc/modprobe.conf
install ipw3945 /sbin/modprobe --ignore-install ipw3945 ; sleep 0.5 ; /sbin/ipw3945d --quiet
remove ipw3945 /sbin/ipw3945d --kill ; sbin/modprobe -r --ignore-remove ipw3945

A ipw3945d service has already been installed as part of the driver package in step one.

Reboot (or modprobe ipw3945 and start the ipw3945d service) and you can move onto configuring a wifi connection which I've done by starting the NetworkManager service and letting it handle everything, it found my wifi network (I use gnome) and allowed me to enter my wifi WPA key etc.. and here I am.

Remember the following.
1. you need to re-install the dkms-ipw3945 rpm after a kernel upgrade.
2. You said you installed the ieee80211 subsystem, you'll may need to probably install a version of that for your new kernel if you upgrade (I think in this case you don't need to even install it if you get it from freshrpms) as long as you have a fairly up to date kernel (because that subsystem is compatible -- I think). The reason I'm not sure is because like you I installed it before finding freshrpms packages

So download the dkms which im assuming is this dkms-ipw3945-1.2.0-1.noarch.rpm - from freshrpms http://zod.freshrpms.net/rpm.html?id=903 .Can anyone walk me through the steps. Ive tried(if you look down like three post) ANY HELP MY NUBE ASS

[h*klown]

im still working on this....

i downloaded the noarch.rpm versionBTW

**BUMP**

[h*klown]

how can i build this dkms-ipw3945-1.2.0-1.src.rpm so that i can install in via rpm or yum?

[wpurcell]

Hello! I've gotten all the steps completed except for:
Add the following lines to /etc/modprobe.conf
install ipw3945 /sbin/modprobe --ignore-install ipw3945 ; sleep 0.5 ; /sbin/ipw3945d --quiet
remove ipw3945 /sbin/ipw3945d --kill ; sbin/modprobe -r --ignore-remove ipw3945
Perhaps you can tell I'm new to this? Any advice would be appreciated! Thanks in advance.

[rexus]

Hi guys, I'm a noob who just made it to activate the wireless feature in my HP nx6320 which use the Intel Corporation PRO/Wireless 3945ABG chipset.

my previous kernel version is kernel-2.6.18-1.2798.fc6
I update it to kernel-2.6.20-1.2933.fc6

the new kernel requested mkinitrd and nash to be updated as well
so this is what I did : rpm -Uvh nash-5.1.19.0.2-1.i386.rpm mkinitrd-5.1.19.0.2-1.i386.rpm
that will update nash and mkinitrd at the same time.

update:
before you do the following steps, please reboot to the new kernel first the you can install all of the following packages altogether. I just experienced it where I installed the following rpms in my old kernel and as a result, I wasn't able to see my WLAN card, but after I remove all the rpms and re installed it in the right kernel, everything is running ok and this update is actually written using the WLAN connectivity. :)

move on to the wireless card, these are the steps:
1. install the ipw3945-kmdl-2.6.20-1.2933.fc6-1.2.0-18.2.fc6.at.i686.rpm
2. install the ieee80211-kmdl-2.6.20-1.2933.fc6-1.2.16-17.fc6.at.i686.rpm
3. install the ipw3945-ucode-1.13-2.at.noarch.rpm
4. install the dkms-0.31.04-0.2.fc6.rf.i386.rpm
5. install the dkms-ipw3945-1.2.0-1.noarch.rpm
6. restart the laptop and everything runs perfectly well

may be some of you are wondering, where do I get those packages.
Well, package in step #4 and #5 is from freshrpm.net and the rest are from rpm.pbone.net

[h*klown]

for installing
1. install the ipw3945-kmdl-2.6.20-1.2933.fc6-1.2.0-18.2.fc6.at.i686.rpm
2. install the ieee80211-kmdl-2.6.20-1.2933.fc6-1.2.16-17.fc6.at.i686.rpm
3. install the ipw3945-ucode-1.13-2.at.noarch.rpm
4. install the dkms-0.31.04-0.2.fc6.rf.i386.rpm
5. install the dkms-ipw3945-1.2.0-1.noarch.rpm
6. restart the laptop and everything runs perfectly well

are you doing
root:::rpm -ivh ipw3945-kmdl-2.6.20-1.2933.fc6-1.2.0-18.2.fc6.at.i686.rpm
root:::rpm -ivh ipw3945-ucode-1.13-2.at.noarch.rpm

and so on?

Or are they local rpms?
if so the command for local is ROOT#install local file/name*? right?

[JN4OldSchool]

hey dog, just search "intel 3945" I got all kinds of hits. Try this for starters.

[h*klown]

its not that i dont know how to find it as that all the instructions i find are not step by step there like really generic...

[root@localhost hklown]# rpm -Uvh nash-5.1.19.0.2-1.i386.rpm mkinitrd-5.1.19.0.2-1.i386.rpm
error: open of nash-5.1.19.0.2-1.i386.rpm failed: No such file or directory
error: open of mkinitrd-5.1.19.0.2-1.i386.rpm failed: No such file or directory
[root@localhost hklown]#

[JN4OldSchool]

its not that i dont know how to find it as that all the instructions i find are not step by step there like really generic...

[root@localhost hklown]# rpm -Uvh nash-5.1.19.0.2-1.i386.rpm mkinitrd-5.1.19.0.2-1.i386.rpm
error: open of nash-5.1.19.0.2-1.i386.rpm failed: No such file or directory
error: open of mkinitrd-5.1.19.0.2-1.i386.rpm failed: No such file or directory
[root@localhost hklown]#

lol, I am sorry H. I was posting towards my friend Dograzor who has the same problems. You might want to check the other Intel 3945 thread going on n ow. Duli has made a great little howto on this wireless card.

edit: Here ya go:

http://www.fedoraforum.org/forum/showthread.php?t=148278

[rexus]

for installing
1. install the ipw3945-kmdl-2.6.20-1.2933.fc6-1.2.0-18.2.fc6.at.i686.rpm
2. install the ieee80211-kmdl-2.6.20-1.2933.fc6-1.2.16-17.fc6.at.i686.rpm
3. install the ipw3945-ucode-1.13-2.at.noarch.rpm
4. install the dkms-0.31.04-0.2.fc6.rf.i386.rpm
5. install the dkms-ipw3945-1.2.0-1.noarch.rpm
6. restart the laptop and everything runs perfectly well

are you doing
root:::rpm -ivh ipw3945-kmdl-2.6.20-1.2933.fc6-1.2.0-18.2.fc6.at.i686.rpm
root:::rpm -ivh ipw3945-ucode-1.13-2.at.noarch.rpm

and so on?

Or are they local rpms?
if so the command for local is ROOT#install local file/name*? right?

they are local rpms, I download it first on rpm.pbone.net.
as for the problems you were facing there, rpm -Uvh nash-5.1.19.0.2-1.i386.rpm mkinitrd-5.1.19.0.2-1.i386.rpm, well I don't experience it at all here.
may be you might want to do this:

# rpm -qa | grep nash
# rpm -qa | grep mkinitrd

paste the result here

as for the other, when I typed install, what I meant was rpm -ivh <package name>

btw, you might also want to tell us about your linux version and distro.
please give us the result of

# uname -a


regards,
rexus

[glennzo]

For what it's worth, on my Toshiba Satellite my wireless is working and has been for the last 2 days. I've been fighting with it for the three weeks I've had the computer and have tried many of the suggestions in the forums. This time around I spent some time re-reading related posts to glean what info I could. Then I decided that since the wireless is detected by Fedora 7 but just not working that I would just install/enable NetworkManager and disable the wired lan. I rebooted and fiddled with NetworkManager and was easily able to get a wireless connection. I don't know how long it will continue to work. All is well at this writing. I'm thinking that disabling the wired lan played a huge role in getting the wireless to work.

[rexus]

Hi glennzo, would you be so kind to copy paste the error that you were facing back then?
mine also not working even after I installed those rpms I mentioned above, any how, I think I read an article of installing that wireless driver, it was written in the article that you need to restart the computer after installing all of the rpms. It worked on me after I restart the computer.

regards,
rexus

[glennzo]

I'd be happy to post them if I could but any error messages are long gone. I didn't write them down. Sorry. I didn't install any drivers this time. (I've installed Fedora 7 3 times on this laptop) When I rebooted after the last install the ipw3945 stuff was just there. The card was recognized, therefore I enabled/installed NetworkManager and rebooted. I gave the required info such as SSID and passkey, using WPA-Personal (new wireless router) and it connected. It does drop out once in a while. Seems to happen especially if I leave the computer for a while and screen saver comes on. It will also quit unexpectedly, like while I'm posting a message to a forum or surfing for naked Linux installs.

[Malachai]

Not sure if this helps:
I usually struggle with wireless and Fedora releases. Especially since I have gotten a laptop with the iwp3945 driver. With FC6 it was a breeze. A lot easier then building packages. It is the easiest experience I have ever had in Linux.

First add the following lines to the /etc/yum.conf file

[atrpms]
name=Fedora Core $releasever - $basearch - ATrpms
enabled=1
baseurl=http://dl.atrpms.net/fc$releasever-$basearch/atrpms/stable
gpgkey=http://ATrpms.net/RPM-GPG-KEY.atrpms
gpgcheck=1

As su run the command
yum install ipw3945

edit the /etc/rc.d/rc.local file and add the line

/sbin/ipw3945d

REBOOT

Finally still as su run the command

system-config-network

Under hardware you should see your wireless adapter. Under devices choose new from the tool bar. Select wireless connections then forward, from the list select your wireless card then forward on the last screen enter your networks info such as SSID and WEP key.

The only problems that I have is that this setup does not roam well. Im also not sure how to configure WPA2 on this way either.

Good Luck



__________________________________________________ _____________________________________
Fedora Releases are like StarTrek movies, Only the even numbered ones are any good.




You know what after adding this entry above I was able to turn on my wifi on with FN+F2 ... Most dell you're able to do that by default...

I restarted the ipw3945 service, Networkmanager and the NetworkmanagerDispatcher...

after I restarted the service above , I went into my system-config-network
and added the wifi card. it showed up on the list ... after configuring it not to boot up, I saved it and closed out the window.

after that I hit the key

FN+F2 and bammmm my wifi light was turn on.

I was able to see some access points ... One thing I'm having trouble understand...
I downloaded knetworkmanger... when I click on a unprotected access point it got to 28% and stayed there for a while. Below is the log i seen in the message... Can anyone tell me why I was not able to connect ...



Jun 9 14:31:15 localhost avahi-daemon[2783]: Registering new address record for fe80::21b:77ff:fe38:2441 on eth1.
Jun 9 14:31:42 localhost NetworkManager: <information> User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / linksys
Jun 9 14:31:42 localhost NetworkManager: <information> Deactivating device eth1.
Jun 9 14:31:42 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason
Jun 9 14:31:42 localhost NetworkManager: <information> Device eth1 activation scheduled...
Jun 9 14:31:42 localhost NetworkManager: <information> Activation (eth1) started...
Jun 9 14:31:42 localhost NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jun 9 14:31:42 localhost NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jun 9 14:31:42 localhost NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jun 9 14:31:42 localhost NetworkManager: <information> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jun 9 14:31:42 localhost NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jun 9 14:31:42 localhost NetworkManager: <information> Activation (eth1/wireless): access point 'linksys' is unencrypted, no key needed.
Jun 9 14:31:42 localhost avahi-daemon[2783]: Withdrawing address record for fe80::21b:77ff:fe38:2441 on eth1.
Jun 9 14:31:42 localhost avahi-daemon[2783]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::21b:77ff:fe38:2441.
Jun 9 14:31:42 localhost avahi-daemon[2783]: iface.c: interface_mdns_mcast_join() called but no local address available.
Jun 9 14:31:42 localhost avahi-daemon[2783]: Interface eth1.IPv6 no longer relevant for mDNS.
Jun 9 14:31:43 localhost NetworkManager: <information> SUP: sending command 'INTERFACE_ADD eth1 wext /var/run/wpa_supplicant '
Jun 9 14:31:43 localhost NetworkManager: <information> SUP: response was 'OK'
Jun 9 14:31:43 localhost NetworkManager: <information> SUP: sending command 'AP_SCAN 1'
Jun 9 14:31:43 localhost NetworkManager: <information> SUP: response was 'OK'
Jun 9 14:31:43 localhost NetworkManager: <information> SUP: sending command 'ADD_NETWORK'
Jun 9 14:31:43 localhost NetworkManager: <information> SUP: response was '0'
Jun 9 14:31:43 localhost NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 ssid 6c696e6b737973'
Jun 9 14:31:43 localhost NetworkManager: <information> SUP: response was 'OK'
Jun 9 14:31:43 localhost NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Jun 9 14:31:43 localhost NetworkManager: <information> SUP: response was 'OK'
Jun 9 14:31:43 localhost NetworkManager: <information> SUP: sending command 'ENABLE_NETWORK 0'
Jun 9 14:31:43 localhost NetworkManager: <information> SUP: response was 'OK'
Jun 9 14:31:43 localhost NetworkManager: <information> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jun 9 14:32:23 localhost NetworkManager: <information> Activation (eth1/wireless): association took too long (>40s), failing activation.
Jun 9 14:32:23 localhost NetworkManager: <information> Activation (eth1) failure scheduled...
Jun 9 14:32:23 localhost NetworkManager: <information> Activation (eth1) failed for access point (linksys)
Jun 9 14:32:23 localhost NetworkManager: <information> Activation (eth1) failed.
Jun 9 14:32:23 localhost NetworkManager: <information> Deactivating device eth1


If anyone could tell me if I missed configured something wrong.

Thanks

[manin]

Hallo, my laptop works fine with my wireless card, Intel Pro 3945ABG. I have also the wifi-radar to connect to my router. I think that router must give me an ip and a gw. But it doesn' t. I must configure it myself. Nevertheless I can't connect to the web.

Also with if config

[root@localhost ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:19:B9:6C:55:39
inet addr:192.168.1.210 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::219:b9ff:fe6c:5539/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:189030 errors:0 dropped:0 overruns:0 frame:0
TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15616296 (14.8 MiB) TX bytes:15483 (15.1 KiB)
Interrupt:17

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1966 errors:0 dropped:0 overruns:0 frame:0
TX packets:1966 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5164729 (4.9 MiB) TX bytes:5164729 (4.9 MiB)

virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:8098 (7.9 KiB)

What is [/B]virb0[B]? I see it with iwconfig also.
Thanks

[tbjudge]

Looks like you need to configure your DHCP. especially for the wireless router. Not sure what the radar thing is.

Funny IP address assignment. Looks like a virtual wireless connection not really sure.