iwl3945 problems

[bobkingof12vs]

so i have worked on this for some time and have some success

first i install
rfkill.tcz

because the card itself was blocked for whatever reason, and it blocks itself again at every reboot, so

i also need to install
wpa_gui.tcz
firmware-iwlwifi.tcz
dhcpcd.tcz

and now i have to append this to my /opt/bootlocal.sh

rfkill unblock all
rmmod iwl3945
modprobe iwl3945
ifconfig wlan0 up
wpa_supplicant -Dwext -iwlan0 -c/opt/wpa.cfg -B
dhcpcd -t 10 -d wlan0

and make /opt/wpa.cfg look like (from the how to setup wifi wiki)

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=staff
update_config=1

then back all of this up
and when i reboot my computer look! the blue light comes on

and i go into wpa_gui from applications and behold, i am able to connect to a network....
but i cannot connect to the internet via my network

i connect and get an ip address so i know i am connected, but my question is why i cannot send or receive any information.

[bobkingof12vs]

 
i restarted my computer without the ethernet plugged in and now it works

... i dont understand why it works now and it didnt before
but it does...

weird

well, sorry for taking up your time
hope this helps someone though

[maro]

If I'd be a betting man I'd put my money on the fact that you probably had initially an ethernet and then established a wifi connection in addition to that. That then lead to a routing with two interfaces, and two default route, and a "massive confusion" for the packets about which way to go. This seems to be happening to others as well.

As TC does not employ by default a bloated tool like 'NetworkManager' which oversees such activities you'll need to take care of it yourself. As long as you only activate one interface at a time you should be fine.

[hiro]

maro is right, but I did actually take care of this problem with my roam extension.
But remember to use the nodhcp boot option. If you never use ethernet anyway that's the only thing you need.