iB::Topic::orinoco mystery

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » Networking » orinoco mystery

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

Pages: (3) </ 1 2 [3] >/

[ Track this topic :: Email this topic :: Print this topic ]

Topic: orinoco mystery

< Next Oldest | Next Newest >

wes33
Unregistered

Posted: Nov. 25 2004,03:15

sorry no luck with the key restricted trick

it seems obvious to me (i.e. it's probably wrong) that
I should see the send/receive light flicker with every
ping signal (this is what happens when the card is
working).

by the way, I booted up dsl on the acer extensa's
big brother (acer travelmate 734, p3-600). I manually
set the wireless parameters with iwconfig and manually
set the network parameters with ifconfig.

everythings works perfectly -- right down to seeing the
flicker with each ping packet and of course all networking
works fine.

there must just be something screwy with the acer extensa's
pcmcia (though, as I say, the wireless card works fine in
windows -- probably lucent did something special in the
windows drivers for the card in windows 95 ...)

oh well ... thanks everybody

akuma6099

Group: Members
Posts: 3
Joined: Jan. 2004

Posted: Dec. 22 2004,02:46

I too have ran into this problem on my vaio. A simple yet effective method would be to make a little shell script that sets up your wep key before the "pump -i wvlan0 or eth0" is executed by cardmgr. instead, I just do a "ifconfig eth0 down", setup the key, and a "pump -i eth0". yes I'm lazy but I'm also still a newbie since I've played with linux off and on

the lazy way out:

#!/bin/bash
case $1 in
start)
echo "Bringing down orinoco...."
ifconfig eth0 down
echo "Setting Key...."
iwconfig eth0 key ababababab
echo "Bringing it up now....."
pump -i eth0
;;
*)
echo "Nothing to be Done here"
;;
esac

Throw this little script in /bin or wherever and make a symbolic link in your /etc/rc5.d/ folder.

root@box:/etc/rc5.d# ln -s /bin/fixme S30fixme

now it'll do it for you while you boot up. stupid yet simple..... I'm learning still

asz
Unregistered

Posted: Jan. 19 2005,20:29

Having exactly the same problem.
I have a Compaq armada 1750 and the Orinoco silver (8461-02). I run DSl 9.2.
The silliest thing is, I had it working!!! Then one day, zip! No more! Right in front of me!
Cardctl ident gives me "Atheros Communications, Inc" "AR5001-0000-0000", so the ath_hal.o and ath_pci seams right.
When doing a "ifup ath0" the card blinks and you can use iwlist to see ap, signal strength and so on. After 30 sec. the prompt gives me "Operation failed" (from pump?) and the card stops blinking.
I Put my DHCPD in debug mode, and the server gets the DHCP-request, and send an offer... which never arrives! #¤"%¤#"¤%
This drives me half mad... please help!

asz
Unregistered

Posted: Jan. 19 2005,20:36

Posting followup....

Tried the same card in my "worktop", HP NX7010, SuSE 9.2 and it did the same thing... Is the card broken?

Also, when saying DHCPD and SERVER in the above post, I mean my estate server, another machine, on the other side of an NETGEAR 814 wireless router.

asz
Unregistered

Posted: Jan. 20 2005,11:05

Okey, I got it working again... I must say it is definitly _not_ a scientific solution, but it worked, now liten to this:

A little about my environment helps understanding. I have a server for infrastructure (firewall, dhcpd, web, automation and other). It is a debian woody, solid as a rock!
At my attic i have a wireless router/switch wich I use only as a wireless accesspoint (switch <=> wifi). WAN port is not connected.

First time the orinoco card stopped working, I had a power outage. So the wifi router (NETGEAR MR814 v2), restarted.
The only card affected was the orinoco a/b silver (8461-02) and in linux only (ath_* drivers?). The same card and computer, running XP, worked.
P*ssed med off really. So I gave it three days fiddeling. I upgraded my router software from 5.03 to 5.3, reset it and... nothing! I saw that my server got the DHCP request, that made me think firewalls. Made a guess that the router was interacting even if the traffic not was going though the wan port. Tried disabling the SPI firewall, and whooops, the orinoco got online. Strange is that re-enbling the firewall did not shut the orinoco out again.... Don't laugh, this is what happened. Or?

If anyone have another explanation, i will be more than happy to accept. But it is another last grasp to check for. Also disconnecting the router from the rest of the net and running the routers dhcp server, did not solve anything.

14 replies since Nov. 23 2004,22:36

< Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

Pages: (3) </ 1 2 [3] >/

Damn Small Linux Board » Damn Small Linux » Networking » orinoco mystery