Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in 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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have CAT5 cable running to first and second story rooms in the house. As laptops, PDA's and maybe VOIP have come into more use, I want to improve the coverage.
Here's what I have:
1. an old WRT54GS v.1 that cannot handle DHCP routing and gateway services properly, but does still work as a WAP. I have SVEASOFT Talisman installed. Host name - SVEASOFT, IP 192.168.1.2
2. a new Linksys WRT54GS v.7 that broadcasts a strong signal but has limited functionality because of the OS. Host name WRT54GS, IP 192.168.1.1
3. cable modem and hubs.
1. Use WRT54GS as the gateway, DHCP, firewall and router so that it can cover the downstairs and support desktops and server.
2. Connect SVEASOFT to WRT54GS as a repeater/AP/client-bridge (what ever is available in the software)
3. I would like to use the same ESSID for both and the same WPA shared key for both and have them on the same 192.168.1.x network. This would allow roaming with devices.
There is little mention of how to do this with cable, although I think it would be preferable to using WDS. I may not be able to do it because of roaming is not supported.
What I've tried while using the same ESSID and WPA shared key:
1. If I set up SVEASOFT as a Repeater and disable internet access and connect it to WRT54GS for gateway, the network throughput degrades.
2. If I set up SVEASOFT as an ACCESS POINT and use WRT54GS as the gateway, the network throughput degrades.
After two days of Googling, I'm asking for suggestions.
Apart from trying a different ESSID on the SVEASOFT in my experience the only way to sort this sort of stuff out is by using a packet sniffer - wireshark for example. Because the issue could be at either end if you've got a linux box attached to the new WRT54GS, running wireshark on that as well as the client PC would be good.
In my setup I actually have my main linux server as a multihomed box with wired and wireless on separate NICs. That way I can use its firewall to completely control access to/from internet and also isolate wireless from wired. Also means that I only have to run wireshark on server to see all traffic.