On Monday 22 September 2008 09:16:01 am Rodney Baker wrote:
On Mon, 22 Sep 2008 22:09:29 Verner Kjærsgaard wrote:
Umm, if this is a desktop you could run an AP in client mode and the computer will not even know it's wireless, solved my problem before it started. Mike
- elaborate, please :-)
That is actually a good suggestion if you happen to have a spare wireless router/AP. By plugging the desktop machine's ethernet port into a wireless AP, then running that AP in client mode so that it connects to the main wireless AP, the desktop machine simply thinks it is talking to a wired connection.
The RF side effectively becomes a wireless ethernet bridge to the main wireless router. No wireless NIC drivers, no messing around on the client machine with authentication etc; let the wireless AP client take care of all of that.
Wish I'd thought of it myself...:-)
Yup, sometimes the simlpest things just boggle the mind after you do it. When I first got the AP (with a usb dongle) I used it with a win machine to get it online until I got a chance to pull a cable, then it sat and I started reading the docs to see what I could actually do with it as an experiment. The Buffalo was just such a deal ($25 after rebate) that I had to buy it, after I set it up I ended up stacking 2 computers on it and doing Remote Desktop to the WinXP machine thru the switch, one cable vs 2 or 4 with a kvm. Sometimes you have everything you need to get the job done, you just don't know it. I learned that from being a Ham.. Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org