IPW2200 refuses to catch signal... am I missing something?

Message

DrWoland · Post by **DrWoland** » Fri Oct 14, 2005 5:53 am

voyager ~ # iwconfig eth1
Warning: Driver for device eth1 has been compiled with version 18
of Wireless Extension, while this program supports up to version 17.
Some things may be broken...

eth1 IEEE 802.11g ESSID:"ilnyarienafaire"
Mode:Managed Frequency:2.437 GHz Access Point: 00:13:10:1A:B7:7B
Bit Rate=54 Mb/s Tx-Power=20 dBm
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:******************************** Security mode:open
Power Management:off
Link Quality=97/100 Signal level=-27 dBm Noise level=-86 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:11 Missed beacon: 0

voyager ~ # ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:12:F0:D3:7D:26
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:421 errors:0 dropped:11 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:5256 (5.1 Kb)
Interrupt:11 Base address:0x2000 Memory:a8401000-a8401fff

Looks like everything is fine, but when I try to ping 192.168.1.1 which is the router, it says Network Not Accessible. Que pasa?!!

Cpt_McLane · Post by **Cpt_McLane** » Fri Oct 14, 2005 6:33 am

ifconfig says eth1 has no ip address.
try

ifconfig eth1 192.168.1.x

x= free ip in your network.

or use dhcp

blamefrost · Post by **blamefrost** » Fri Oct 14, 2005 9:37 am

I also get this output when running iwconfig:

Warning: Driver for device eth1 has been compiled with version 18
of Wireless Extension, while this program supports up to version 17.
Some things may be broken...

and as you say, it's possible to set an ip-address manually,
but sometimes you have to use dhcp, and the problem is,
dhcp is not working with this.
it tries to get an ip, but then it says nothing, until it timeouts and doesn't recieve an ip-address...

I've also experienced problems involving the ipw2200 dropping connection for about 40seconds every two minutes,
which is quite annoying.

any ideas on this one?

Cpt_McLane · Post by **Cpt_McLane** » Fri Oct 14, 2005 10:17 am

http://forums.gentoo.org/viewtopic-t-383604.html... don't worry about the Warning.
For DrWoland, maybe he just forgot to run dhcpd or to set the ip-address.
For blamefrost: strange thing, dhcp sometimes works and sometimes not. does that happen with the same dhcp-server?

DrWoland · Post by **DrWoland** » Fri Oct 14, 2005 2:17 pm

DHCP doesn't work, I've tried. I'll try setting the IP manually later today...

IPW2200 refuses to catch signal... am I missing something?

IPW2200 refuses to catch signal... am I missing something?

same problem