|
Old vs new hardware
ipw2200 not stable in Debian6! Is old hardware not stable? is old hardware not safer than new?
/Repet |
Hi Repet and Welcome to LQ!
As a rule, old hardware is quite stable. I'm using a ZyXel wifi dongle that is probably older than your ipw2200 and it works fine. Can you explain what exactly the problem is and what driver you're using for the ipw2200? ciao, jdk |
Old versus new is not a selection for stable would be my opinion.
Stability is a wide topic that covers hardware, firmware, software, configuration, power settings, maybe even things like emi/rfi, static, and thermal considerations. Another issue is that a product that is produced each day may have slight changes to components. Even if the revision level doesn't change, some parts may cause slight changes in timings or power or whatnot that can cause the one device to act differently than a seemingly similar product. A revision level may also affect it's target use. |
root@debian:/home/bo# dmesg | grep ipw2200
[ 3.824044] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq [ 3.824047] ipw2200: Copyright(c) 2003-2006 Intel Corporation [ 4.225656] ipw2200 0000:02:06.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 4.226494] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection [ 4.226536] ipw2200 0000:02:06.0: firmware: requesting ipw2200-bss.fw [ 4.705238] ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels) root@debian:/home/bo# ifconfig eth0 Link encap:Ethernet HWaddr 00:c0:9f:5c:d7:7e UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 Base address:0x3000 eth1 Link encap:Ethernet HWaddr 00:0e:35:73:4f:06 inet addr:192.168.1.75 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20e:35ff:fe73:4f06/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:19746 errors:4 dropped:4 overruns:0 frame:0 TX packets:15282 errors:0 dropped:15 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:22894166 (21.8 MiB) TX bytes:1978682 (1.8 MiB) Interrupt:18 Base address:0xe000 Memory:e0206000-e0206fff 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:92 errors:0 dropped:0 overruns:0 frame:0 TX packets:92 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:7584 (7.4 KiB) TX bytes:7584 (7.4 KiB) root@debian:/home/bo# ping 192.168.1.75 PING 192.168.1.75 (192.168.1.75) 56(84) bytes of data. 64 bytes from 192.168.1.75: icmp_req=1 ttl=64 time=0.057 ms 64 bytes from 192.168.1.75: icmp_req=2 ttl=64 time=0.054 ms 64 bytes from 192.168.1.75: icmp_req=3 ttl=64 time=0.057 ms 64 bytes from 192.168.1.75: icmp_req=4 ttl=64 time=0.055 ms 64 bytes from 192.168.1.75: icmp_req=5 ttl=64 time=0.056 ms 64 bytes from 192.168.1.75: icmp_req=6 ttl=64 time=0.056 ms ^C --- 192.168.1.75 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 4998ms rtt min/avg/max/mdev = 0.054/0.055/0.057/0.009 ms root@debian:/home/bo# ^C root@debian:/home/bo# ifconfig eth0 Link encap:Ethernet HWaddr 00:c0:9f:5c:d7:7e inet addr:192.168.1.80 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::2c0:9fff:fe5c:d77e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:108 errors:0 dropped:0 overruns:0 frame:0 TX packets:121 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:47372 (46.2 KiB) TX bytes:14715 (14.3 KiB) Interrupt:16 Base address:0x3000 eth1 Link encap:Ethernet HWaddr 00:0e:35:73:4f:06 inet addr:192.168.1.75 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20e:35ff:fe73:4f06/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:19897 errors:4 dropped:4 overruns:0 frame:0 TX packets:15501 errors:0 dropped:15 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:22914446 (21.8 MiB) TX bytes:2000104 (1.9 MiB) Interrupt:18 Base address:0xe000 Memory:e0206000-e0206fff 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:151 errors:0 dropped:0 overruns:0 frame:0 TX packets:151 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12827 (12.5 KiB) TX bytes:12827 (12.5 KiB) root@debian:/home/bo# ping 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. 64 bytes from 192.168.1.254: icmp_req=1 ttl=64 time=5.81 ms 64 bytes from 192.168.1.254: icmp_req=2 ttl=64 time=4.42 ms 64 bytes from 192.168.1.254: icmp_req=3 ttl=64 time=2.84 ms 64 bytes from 192.168.1.254: icmp_req=4 ttl=64 time=0.882 ms 64 bytes from 192.168.1.254: icmp_req=5 ttl=64 time=10.0 ms 64 bytes from 192.168.1.254: icmp_req=6 ttl=64 time=8.86 ms ^C --- 192.168.1.254 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5006ms rtt min/avg/max/mdev = 0.882/5.472/10.006/3.196 ms I do not remember any issues with Debian5 The problem is that I loos wifi connection. It is a strange problem. I am in the progress of testing what acctualy is hapening. Right now I tried a new approach. Usualy I am behind a VPN, vpntunnel.se. Berhaps I thought it is the culprit. Before I was the only one affected but a windows computer also lost its wifi connection. Before with VPN I was the only one effected. On those occations the firmware failed according to dmesg. Why would the router go dow only on the wifi side. As you can see I connected a hard cabel to the router before I rebooted it an that had internet. Also it looked as if the wifi was doing something, lamps blinking as they do under normal circumstances. Strange? /bo |
I've already tried old and very new hardware with debian and i've never got problem even if the hardware isn't supported it's a matter of time to get it working about one or two month. But old hardware is very stable yes.
spring logout |
I don't understand. Your output of ifconfig doesn't show any wireless network like wlan0 or ath0 or something like that. I see two wired connections: eth0 and eth1. What is the output of this command?
Code:
lsmod |grep ipw |
I appreciate your help your post have helped me in the passed. I am glad that I joined.
Here is that output. root@debian:/home/bo# lsmod | grep ipw ipw2200 108264 0 libipw 18403 1 ipw2200 lib80211 2834 2 ipw2200,libipw My wlan is on eth1. The firs dmesg is for showing the driver used. Sometimes when a fault occurs the firmware is reported to be the culprit. The second ifconfig is for showing what is configured by dhcp. eth1 is configured and working internally but ca not connect with router. I there connect a wire cable to the ports of the router and though that line I get connected. What can make the router loose the wifi totally? The win-box also lost connection? /bo |
Ok, it looks like the correct driver is installed. For my ZyXEL wifi dongle I had to install the zd1211rw firmware package for it to work at all. I don't think you have a firmware issue.
I don't understand why you are getting an inet address for eth0? You get in ip of 192.168.1.80 for eth0 and 192.168.1.168 for eth1. Do you have some cable plugged in while you're trying to use your wifi. You seem to be getting network traffic off both eth0 and eth1. I don't really understand your setup at all. Sorry. My ifconfig output looks like this: Code:
eth0 Link encap:Ethernet HWaddr aa:00:04:00:0a:04 |
OK
This is how you see what you see. wifi is configured on eth1. Cable tp/rj45 is on eth0. First I loos connection on eth1 but it looks as if I am online still! However I can not connect to either my router or the internet! But i can ping my own eth1 IP. I then, this time around, without doing any thing else connect a physical cable to my eth0 built in network interface. It talks to the router and receives an IP address. I get online. The main question here is why does my routers wifi interface get smashed by my wifi so it goes down? If that is the case. What ever problem I have on my laptop somehow destroys the router wifi so that a windows box also looses connection. So I will next time the problem occurs only reboot the router. This said I want to point out that more people than I have experienced similar problems with their intel pro ipw2200 driver firmware combinations. Strangely I have had this problem for a period of time only. I wounder if the problem perhaps is coming from the internet, is that a possibility? /bo |
Have you tried running your router with only the wifi connection and no wired connection. If you always have both eth0 and eth1 connected maybe that confuses your router. Maybe unplugging the cable or giving the command
Code:
sudo ifconfig eth0 downciao, jdk |
You are wright it might be confusing to a router. I connect eth0/rj45 only after I lost wifi to see what the router would do. Under normal circumstances I only have wifi out of convenience.
So when the problem occurs I am only using wifi. When I lose wifi connection simultaneously on both winbox and my debian6 i walk up to the router with my laptop and connects it through rj45 and I get online thorough the rj45/eth0. Previously when I have been behind a VPN only MY laptop have been affected. I find this strange! I disconnected my laptop from the VPN to minimize the number of possible culprits. When I did the router seams to have acquired a problem. It was by chance that a winbox was online at that time. So what can cause this? /bo |
Ok Repet. Your setup is clearly well beyond my experience. I have no knowledge of Windows and what it may or may not do. I installed vpn out of curiosity but haven't got around to configuring it yet. Maybe someone more experienced in these things can help. I hope so.
ciao, jdk |
Thank you for your time.
|
| All times are GMT -5. The time now is 08:55 PM. |