Wayne <linux...@gmail.com> put forth on 1/1/2010 1:43 PM: This is a good sign:
> /var/log/wicd# ifconfig > ath0 Link encap:Ethernet HWaddr 00:26:5a:bb:e8:c5 > inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:64 errors:0 dropped:0 overruns:0 frame:0 > TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:7464 (7.2 KiB) TX bytes:2838 (2.7 KiB) This shows that your Atheros is communicating with the AP up to layer 3. Are you able to ping 192.168.1.1? If not, can you ping 192.168.1.1 from the Windows PC? I.e, does the MiFi 2200 have a firewall that discards ICMP echo packets? If the Windows PC can ping and get a response... did a CD come with the MiFi 2200? Did you install software from that CD onto the Windows machines? If so, is it possible that such software has some extra "phantom" layer of junk that allows the Windows machines to properly communicate with the AP, which you don't have available to install on Linux? If so, you need to figure out what that Windows software is providing and duplicate the function on Linux. The above output from ifconfig shows that you have IP connectivity with the MiFi 2200 AP. The effort now is to identify why the MiFi isn't apparently processing your packets. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
