SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
You'll have to setup the card by editing the configuration file
with something like this (as a replacement for the -assumed- empty values for the "eth1"):
# Config information for ra0:
Things like WEP key could be added, too but you did not give any info on that. Just play with the values, make them match your Access Point. I also assumed you are using DHCP - if not, supply IP address, netmask and possibly a GATEWAY value.
If the install was successfull (the "installpkg" command), and the driver loaded OK (the "modprobe rt2500" command), then "ifconfig ra0" should show that the ra0 interface is present.
If you entered the configuration correctly, the interface can be configured and brought "up" using the command
wow, that's satisfying, seeing someone sort out their problem with the right help!
OK, I have a WEP setting, how do I work out the syntax for it and so insert it into rc.inet1.conf? I lookedin rc.inet1, and didn't get much of a clue. I guess WLAN_WEP="1234etc". Still on this file's syntax, how come
settings don't use double quotes?
Also, what's with this "Slackware 10.2" package? Put in that way, it implies it won't do for "Slackware 10.1"? Suppose I'll try it out to find out.
On another line of investigation, I compiled the rt2500 from CVS source, got it up, but then when I apply my wep and dhcpcd, it pauses a minute or two and switches off! Weirdly, dhcpcd does not come up as a running process in "ps". Ah well, I must be mispelling something. I remember ages back I had similar problems though I was using "dhcpd" instead of "dhcpcd"... took me a while to sort that one out.