Yes, more wireless talk.

[Jomkiatz]

By now, those of us interested in wireless internet have already seen the very informative and helpful link,

[Please register to see this link. ]

I downloaded and installed the new wireless tool package listed in the guide, but I'm stuck on the very next step. Every single command that I enter from this guide is not recognized by Linux...I'm just given a simple "command not found". I was under the impression the tools installed would be just that...tools. Are they only located in a specific directory? If so, what would that directory be?

Is there some other step that I need to take, perhaps, to enable these tools?

[oobuk]

I don't know if they work in YDL 6.0.

What version of YDL are you on?

[Jomkiatz]

I'm in YDL 6.0

According to the comments below the instructions, however, people did manage to get wireless working following these steps, although they had to change a few things to get the scripts running correctly on startup. There's a second set of wireless tools that I came across in the comments (and I intend to try) but I feel like my error is a user issue, not a software one.

[oobuk]

I fooled around with it a LOT in YDL 5.x.

I got WEP and "Open" to work. I briefly had WPA working, but never WPA2.

In 6.0 I only got "Open" to work in wireless and just didn't have the time to futz with it anymore.

I went back to wired. It's not like I move my PS3 around anyway.

[Jomkiatz]

Well, we'll see what ends up happening, but for now...

Remember, I'm a total Linux newbie. I have literally JUST installed the wireless tools package using the...

rpm -Uvh wireless-tools-28-1.ppc64.rpm

...command, and am now trying the "iwconfig eth0" command, but getting a "command not found" error. Am I missing a step? Do I first have to somehow open the package, or load the module? Do I have to be in a specific directory? Is there some small or tiny step that I'm missing, now matter how mundane it may be? Remember, again, total Linux newb; some step that may be taken for granted as common knowledge is probably unknown to me.

This is such a fundamental error (and no one else seems to have had it in the comments section) that I can't help but feel like it's me doing something wrong. How else could people at least get the commands to work on the exact same configuration that I have?

[Jomkiatz]

Well, I got a solution to this problem from the yellow dog forums.

In case anyone else is having this problem, try this:

Instead of just typing iwconfig eth0, or any of the other commands...preface it with /sbin/...

so, example:

/sbin/iwconfig eth0

should work fine. It did for me, at least. I have no idea why this works (total newb, remember) but it does. Anyone care to explain why it did? Remember, teach a man to fish, blah blah blah.