Hi All --
I recently picked up an eMachine 6805, and got it up and running FC2, using the 64-bit version of the OS. Overall, it's not bad.
I realize that the Broadcom 802.11g chip is a LONG way from being supported, at all (any change in this?), so I went out a picked up a Netgear WG511, 802.11g. This card uses the prism54 module / driver, and works VERY well if I do not use WEP.
However, if I'm using WEP, it doesn't work at all. It cannot fetch an IP address, or anything. The hex key is being stored in /etc/sysconfig/networking/devices/keys-eth1, in the format: KEY=s:XXXXXXXXXXXXX
I've tried with several different keys (always key 1 on the router), and two different routers / access points / firewalls. Under Windows, this same card has no problems.
Is WEP working with prism54? What about on the 64-bit kernel?
What else am I missing?
--Anthony
On Thu, 2004-05-27 at 17:37, Anthony Presley wrote:
supported, at all (any change in this?), so I went out a picked up a Netgear WG511, 802.11g. This card uses the prism54 module / driver, and works VERY well if I do not use WEP.
However, if I'm using WEP, it doesn't work at all. It cannot fetch an IP address, or anything. The hex key is being stored in /etc/sysconfig/networking/devices/keys-eth1, in the format: KEY=s:XXXXXXXXXXXXX
Is WEP working with prism54? What about on the 64-bit kernel?
I'm not using that particular card but I do have a DWL-G650 card working with the prism54 drivers using WEP just fine. This is on a Dell Latitude CPx laptop with FC2.
My keys-eth0 file does not have the s: in the key. That may be the problem.
Try entering the WEP with an "0x" in the front - ie., 0xhhhhhhhhhhhhhhh
wher the 'h's are your WEP key...
Sam Stengler
Anthony Presley anthony@resolution.com said:
Hi All --
I recently picked up an eMachine 6805, and got it up and running FC2, using the 64-bit version of the OS. Overall, it's not bad.
I realize that the Broadcom 802.11g chip is a LONG way from being supported, at all (any change in this?), so I went out a picked up a Netgear WG511, 802.11g. This card uses the prism54 module / driver, and works VERY well if I do not use WEP.
However, if I'm using WEP, it doesn't work at all. It cannot fetch an IP address, or anything. The hex key is being stored in /etc/sysconfig/networking/devices/keys-eth1, in the format: KEY=s:XXXXXXXXXXXXX
I've tried with several different keys (always key 1 on the router), and two different routers / access points / firewalls. Under Windows, this same card has no problems.
Is WEP working with prism54? What about on the 64-bit kernel?
What else am I missing?
--Anthony
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
sstengler@covad.net wrote:
Try entering the WEP with an "0x" in the front - ie., 0xhhhhhhhhhhhhhhh
wher the 'h's are your WEP key...
Sam Stengler
Anthony Presley anthony@resolution.com said:
Hi All --
I recently picked up an eMachine 6805, and got it up and running FC2, using the 64-bit version of the OS. Overall, it's not bad.
I realize that the Broadcom 802.11g chip is a LONG way from being supported, at all (any change in this?), so I went out a picked up a Netgear WG511, 802.11g. This card uses the prism54 module / driver, and works VERY well if I do not use WEP.
However, if I'm using WEP, it doesn't work at all. It cannot fetch an IP address, or anything. The hex key is being stored in /etc/sysconfig/networking/devices/keys-eth1, in the format: KEY=s:XXXXXXXXXXXXX
I've tried with several different keys (always key 1 on the router), and two different routers / access points / firewalls. Under Windows, this same card has no problems.
Is WEP working with prism54? What about on the 64-bit kernel?
What else am I missing?
--Anthony
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
I believe that should be something like (no it's not my actual key):
KEY=ffb8439746e33ad722d1572efa
Bill
Bill Smithem wrote:
sstengler@covad.net wrote:
Try entering the WEP with an "0x" in the front - ie., 0xhhhhhhhhhhhhhhh
wher the 'h's are your WEP key...
Sam Stengler
Anthony Presley anthony@resolution.com said:
Hi All --
I recently picked up an eMachine 6805, and got it up and running FC2, using the 64-bit version of the OS. Overall, it's not bad.
I realize that the Broadcom 802.11g chip is a LONG way from being supported, at all (any change in this?), so I went out a picked up a Netgear WG511, 802.11g. This card uses the prism54 module / driver, and works VERY well if I do not use WEP.
However, if I'm using WEP, it doesn't work at all. It cannot fetch an IP address, or anything. The hex key is being stored in /etc/sysconfig/networking/devices/keys-eth1, in the format: KEY=s:XXXXXXXXXXXXX
I've never gotten ASCII strings to work like that, but got around it like so:
Bring down the interface run iwconfig eth1 key s:XXXXXXXXXXXXXXX Bring up the interface.
Run iwconfig again and check out the HEX value your key represents and write it down or print it out.
Then use KEY=<HEX VALUE YOU FOUND>
Only way I ever got it to work.
Regards, Ed.