Hi Ellen,
It isn't you. It is the Linksys. I spent a week on tech support with
Linksys trying to get a Cabletron card (also Lucent chip set) working on
Linksys AP router. First I had trouble with Windoze 2000 laptop, and tried
every imaginable configuration. When I got tired of rebooting, I tried my
IPAQ also. I could ping the router, but couldn't ping through the thing to
anything else (tried WAN, another wireless machine, a wired machine). I
tried gateway mode and router mode, manual static routes, DHCP, static IPs,
RIP1, RIP2, etc.
Last weekend, I finally gave up and bought a Linksys 802.11 card and it
works just fine with the exact same settings. As far as I can tell, Linksys
appears to be doing something stupid like filtering on their MAC address
prefix (more likely some more obscure 802.11b compliance issue).
I'd love to hear if someone else has a solution.
Brian
--------------------------------------------
Brian Schott, Project Leader
USC Information Sciences Institute
4350 N. Fairfax Dr., #770, Arlington VA 22203
ph: 703-812-3722 fx: 703-812-3712
mailto:bschott@east.isi.edu
--------------------------------------------
> -----Original Message-----
> From: familiar-admin@handhelds.org
> [mailto:familiar-admin@handhelds.org]On Behalf Of Ellen Dash
> Sent: Friday, June 01, 2001 3:44 PM
> To: familiar@handhelds.org
> Subject: [Familiar] wireless config?
>
>
> Hi gang,
>
> I'm still banging my head on this problem ... trying to get my iPAQ
> (Familiar .3 w/Lucent Orinooco Silver) card to talk to my Linksys
> wireless
> AP/Router. The AP/Router is in turn connected to a cable modem (yes,
> RoadRunner). I know that I'm close... iwconfig shows that it is
> able to get
> the MAC address of the AP, but when I try to ping the AP, I get nothing
> back. The lights on the card flash and seem to sync up with
> lights on the
> AP, but still no reply from the AP. (Pinging AP does work from a wired
> laptop; wireless from laptop also works via Windows.)
>
> I've tried various configurations -- I'd be happy to get this working in
> Infrastructure mode (or ad-hoc). I've seemed to have gotten
> closer with a
> static IP address, rather than using DHCP. Below are file snippets and
> output from the iPAQ in case anyone is able to provide some clues!
>
> Thanks so much for any help you can send my way!
>
> I do get the following error, but I thought I had read in the
> archives that
> it is not a problem. Is this still true?
>
> cardmgr[685]: + ./network: /sbin/ifuser: not found
>
> Ellen Dash
> edash_dgi@hotmail.com
>
> ------------ output from iPAQ --------
>
> # /etc/init.d/pcmcia start
> Starting PCMCIA services: modulesLinux PCMCIA Card Services 3.1.22
> options: [pm]
> SA-1100 PCMCIA (CS release 3.1.22)
> bitsy_pcmcia_configure_socket: socket=0 vcc=50 reset=0
> bitsy_pcmcia_configure_socket: finished
> bitsy_pcmcia_configure_socket: socket=0 vcc=50 reset=1
> bitsy_pcmcia_configure_socket: finished
> bitsy_pcmcia_configure_socket: socket=0 vcc=50 reset=0
> bitsy_pcmcia_configure_socket: finished
> cardmgr.
> # cardmgr[685]: starting, version is 3.1.20
> cardmgr[685]: watching 2 sockets
> cardmgr[685]: Card Services release does not match
> cardmgr[685]: initializing socket 0
> cardmgr[685]: socket 0: Lucent Technologies WaveLAN/IEEE Adapter
> cardmgr[685]: executing: 'modprobe wvlan_cs port_type=1
> network_name=linksys channel=6 station_na'wvlan_cs: WaveLAN/IEEE PCMCIA
> driver v1.0.4
> wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de>
> bitsy_pcmcia_configure_socket: socket=0 vcc=50 reset=0
> bitsy_pcmcia_configure_socket: finished
> bitsy_pcmcia_configure_socket: socket=0 vcc=50 reset=0
> bitsy_pcmcia_configure_socket: finished
> wvlan_cs: index 0x01: Vcc 5.0, irq 42, io 0xf6000000-0xf600003f
> wvlan_cs: Registered netdevice wvlan0
> wvlan_cs: MAC address on wvlan0 is 00 02 2d 2b 91 f4
> cardmgr[685]: executing: './network start wvlan0'
> modprobe: modprobe: Can't locate module net-pf-4
> modprobe: modprobe: Can't locate module net-pf-5
> modprobe: modprobe: Can't locate module net-pf-4
> modprobe: modprobe: Can't locate module net-pf-5
> modprobe: modprobe: Can't locate module net-pf-4
> modprobe: modprobe: Can't locate module net-pf-5
> modprobe: modprobe: Can't locate module net-pf-4
> modprobe: modprobe: Can't locate module net-pf-5
> modprobe: modprobe: Can't locate module net-pf-4
> modprobe: modprobe: Can't locate module net-pf-5
> cardmgr[685]: + ./network: /sbin/ifuser: not found
>
> # ping -n 192.168.1.1 ==> [THIS IS THE IP ADDRESS OF MY AP/ROUTER]
> PING 192.168.1.1 (192.168.1.1): 56 data bytes
>
> --- 192.168.1.1 ping statistics ---
> 37 packets transmitted, 0 packets received, 100% packet loss
> #
> # ifconfig
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:3904 Metric:1
> RX packets:343 errors:0 dropped:0 overruns:0 frame:0
> TX packets:343 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:38388 (37.4 Kb) TX bytes:38388 (37.4 Kb)
>
> wvlan0 Link encap:Ethernet HWaddr 00:02:2D:2B:91:F4
> inet addr:192.168.1.50 Bcast:192.168.1.255
> Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:39 errors:0 dropped:0 overruns:0 frame:0
> TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:2652 (2.5 Kb) TX bytes:2652 (2.5 Kb)
> Interrupt:42
>
> # iwconfig
> modprobe: modprobe: Can't locate module net-pf-4
> modprobe: modprobe: Can't locate module net-pf-5
> lo no wireless extensions.
>
> wvlan0 IEEE 802.11-DS ESSID:"linksys" Nickname:"familiar"
> Frequency:2.437GHz Sensitivity:1/3 Mode:Managed
> Access Point: 00:04:5A:26:5B:5F
> Bit Rate=11Mb/s RTS thr:off Fragment thr=2347 B
> Encryption key:off
> Power Management:off
> Link quality:55/92 Signal level:-34 dBm Noise level:-90 dBm
> Rx invalid nwid:0 invalid crypt:0 invalid misc:0
> # netstat -rn
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt
> Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 40 0 0
> wvlan0
> 192.168.1.0 0.0.0.0 255.255.255.0 U 40 0 0
> wvlan0
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 40 0 0
> wvlan0
>
> # route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
> wvlan0
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
> wvlan0
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 1 0 0
> wvlan0
>
> ---------------iPAQ config file contents -----------
>
> Just listing the important parts ...
>
> network.opts (only showing the parts that I've modified.)
>
> # Use BOOTP (via /sbin/bootpc, or /sbin/pump)? [y/n]
> BOOTP="n"
> # Use DHCP (via /sbin/dhcpcd, /sbin/dhclient, or /sbin/pump)? [y/n]
> DHCP="n"
> PUMP='n'
> # If you need to explicitly specify a hostname for DHCP requests
> DHCP_HOSTNAME=""
> # Host's IP address, netmask, network address, broadcast address
> IPADDR="192.168.1.50"
> NETMASK="255.255.255.0"
> NETWORK="192.168.1.0"
> BROADCAST="192.168.1.255"
> # Gateway address for static routing
> GATEWAY="192.168.1.1"
> # Things to add to /etc/resolv.conf for this interface
> DOMAIN=""
> SEARCH=""
> DNS_1="192.168.1.1"
> DNS_2=""
> DNS_3=""
>
> config.opts
> # Options for WaveLAN/IEEE driver (AccessPoint mode)...
> module "wvlan_cs" opts "port_type=1 network_name=linksys channel=6
> station_name=dash2"
>
> (is there any reason to exclude other irq ports?)
>
>
> wireless.opts
>
> case "$ADDRESS" in
>
> # Lucent Wavelan IEEE
> # Note : wvlan_cs driver only, and version 1.0.4+ for encryption support
>
> *,*,*,00:02:2D:*)
> INFO="iPAQ"
> ESSID="linksys"
> MODE="Managed"
> RATE="11M"
> # KEY="s:secu1"
> # To set all four keys, use :
> # KEY="s:secu1 [1] key s:secu2 [2] key s:secu3 [3] key s:secu4 [4] key
> [1]"
> ;;
>
> esac
>
>
> Contents of /etc/resolv.conf
>
> # wvlan0 begin
> nameserver 192.168.1.1
> # wvlan0 end
>
>
>
>
>
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
> _______________________________________________
> Familiar mailing list
> Familiar@handhelds.org
> http://handhelds.org/mailman/listinfo/familiar
>
Received on Fri Jun 1 14:29:51 2001
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:38:25 EDT