Vern W Heesch wrote:
> snip
>
[snip]
>>
>
> Thanks David. That got me closer. It now loads the driver and the cards green
> light is active. I still have something wrong though because I can't ping any
> other machines here. I am using WEP on the Access Point, perhaps that makes a
> difference somewhere. Here is my log messages now:
>
> Dec 2 21:32:11 sttl cardmgr[3006]: socket 0: Intersil PRISM2 11 Mbps
> Wireless Adapter
> Dec 2 21:32:11 sttl cardmgr[3006]: executing: 'modprobe hermes'
> Dec 2 21:32:11 sttl kernel: hermes.c: 12 Dec 2000 David Gibson
> <[EMAIL PROTECTED]>
> Dec 2 21:32:11 sttl cardmgr[3006]: executing: 'modprobe orinoco_cs'
> Dec 2 21:32:11 sttl kernel: dldwd: David's Less Dodgy WaveLAN/IEEE Driver
> Dec 2 21:32:11 sttl kernel: eth1: Firmware ID 1F vendor 0x0 (UNKNOWN)
> version 0.08
> Dec 2 21:32:11 sttl kernel: eth1: MAC address 00:03:2F:02:47:8B
> Dec 2 21:32:11 sttl kernel: eth1: Station name "Prism I"
> Dec 2 21:32:11 sttl kernel: eth1: ready
> Dec 2 21:32:11 sttl kernel: eth1: index 0x01: Vcc 5.0, irq 3, io
> 0x0100-0x013f
> Dec 2 21:32:11 sttl cardmgr[3006]: executing: './network start eth1'
> Dec 2 21:32:11 sttl dhclient: Internet Software Consortium DHCP Client
> V3.0b2pl9
> Dec 2 21:32:11 sttl dhclient: Copyright 1995-2000 Internet Software
> Consortium.
> Dec 2 21:32:11 sttl dhclient: All rights reserved.
> Dec 2 21:32:11 sttl dhclient: For info, please visit
> http://www.isc.org/products/DHCP
> Dec 2 21:32:11 sttl dhclient:
> Dec 2 21:32:12 sttl dhclient: Listening on LPF/eth1/00:03:2f:02:47:8b
> Dec 2 21:32:12 sttl dhclient: Sending on LPF/eth1/00:03:2f:02:47:8b
> Dec 2 21:32:12 sttl dhclient: Sending on Socket/fallback
> Dec 2 21:32:14 sttl dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port
> 67 interval 3
> Dec 2 21:32:17 sttl dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port
> 67 interval 4
> Dec 2 21:32:21 sttl dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port
> 67 interval 8
> Dec 2 21:32:29 sttl dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port
> 67 interval 17
> Dec 2 21:32:46 sttl dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port
> 67 interval 20
> Dec 2 21:33:06 sttl dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port
> 67 interval 9
> Dec 2 21:33:15 sttl dhclient: No DHCPOFFERS received.
> Dec 2 21:33:15 sttl dhclient: No working leases in persistent database -
> sleeping.
> Dec 2 21:33:15 sttl cardmgr[3006]: exiting
>
> I have no idea where it is picking up Station Name "Prism 1" from or why it
> is looking at 255.255.255.255 either. I've looked at network.opts and
> wireless.opts but can't figure out where I went wrong. Can you point to
> things to check?
>
> Thanks much,
> Vern
OK, couple of things:
1. you need to edit /etc/pcmcia/wireless.opts. Read the file, but at
the very least you'll need to be sure you have something for:
ESSID (that's your network name)
KEY (the crypto key to enter the network -- shame on them if they don't
use one)
check your setup using iwconfig eth1
The PRISM1 is coming from the card type. Mine usually picks up my
hostname (although in older kernels/wireless utils it picked up the same
basic thing as what you're seeing).
2. Make sure your provider is using DHCP. If not, you'll need to
configure the /etc/pcmcia/network.opts file.
You can do the above right now without modifying anything yet by using
the ifconfig eth1 and route commands to set up basic networking
(assuming you have a static IP) and using the iwconfig eth1 command to
set up ESSID, KEY, and whatever else is required.
Once you get the card running, ping your upstream (the access point) and
then run:
iwspy eth1 <IP_of_AP>
the next time you look at iwconfig you should see how good your
connection is.
Ciao,
David A. Bandel
--
Focus on the dream, not the competition.
-- Nemesis Racing Team motto
_______________________________________________
Linux-users mailing list
Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
