Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There is an "ULTIMATE" signal, and scanning for networks does find my wireless network. The access point is a DWL-700AP and its MAC address is found.
The Bad News is that there is no connectivity. Also KWiFiManager complains that my AccessPoint is UNKNOWN even after finding my wireless network! There is no IP address assigned.
Encryption is 26-digit hex WEP.
Operation Mode is set to "Manager" becase the other settings seem to kill the signal.
The [Autodetect] button was used for the Interface. It came back with "eth2".
Although Kwifimanager is a nice program, it is, IMO, not so helpful for diagnosing what is going wrong. I would try to get things working in a terminal, then use it for monitoring your connection.
First, switch off encryption and MAC-address filtering on your WAP. Once wireless is working, you can switch that stuff back on if you need it. Then reset the interface: $sudo ifconfig eth2 down
$sudo ifconfig eth2 up
Try connecting to your WAP: $ sudo iwconfig eth2 essid <your essid> key off
Then type iwconfig by itself. If you are successful, it should indicate that it has attached itself to your WAP by displaying its MAC address and signal strength. Then get a DHCP lease: $ sudo dhclient eth2
If you are assigned an IP number, the connection should now be active, and you should be able to ping remote hosts: $ ping google.com
If you start Kwifimanager now, it should display the details of your connection. Note: If it displays UKNOWN in the bottom left, you have to add your WAP's MAC address to the list of recognized hosts. See the manual on how to do this. This should not affect its operation though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.