PCI Wireless, set it up, can scan, but not connect
Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
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.
PCI Wireless, set it up, can scan, but not connect
Hi all,
I've got Atheros wireless adapter on my PC, and a NetComm NB600W router (external).
I've installed MadWiFi and it works, but the problem is following:
I can scan and see the networks around (using KInternet), but i cannot connect to any of them. It says 'Error connecting to: MYLAN You are currently not associated with this access point' or something like this 20-30 secs after 'Connect' button was pressed.
Never used mtr but quick search says it's similar to ping, so you probably have to use a command line operator to specify the network interface to use (again eth1 probably, I assume by default it uses your ethernet card). Man page says:
Quote:
-a IP.ADD.RE.SS
--address IP.ADD.RE.SS
Use this option to bind outgoing packets' socket to specific interface, so that any packet will be sent through this interface. NOTE that this option doesn't apply to DNS requests (which could be and could not be what you want).
That should be the one but it suggest ip-address as the parameter. I'd think something like
and now, when i rebooted, the firewall is down, but it doesn't work AGAIN. I mean it can see the networks around, i can connect (using random passwords), but the router does not assign me any IP address
Well, you can't send packets that you want returned if you don't have an ip addres. You mentioned that the router didn't give you one. Dhcp is how it gives the ip. The other cariant is setting the network settings manually- static ip.
It prints out some basic stuff with the -d flag and then goes to backround (ps aux | grep dhcpcd). The more important thing is did that help you establish a connection so you can use your program?
No, it does not print out anything, it just stays in the console -- does not go background. The "ps -A |grep dhcp" does not show it.
The only way to close it is Ctrl+C
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.