[SOLVED] Successful wireless connection but no internet access
SlackwareThis Forum is for the discussion of Slackware 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.
Is that the exact error message you are getting? I ask because I know a firewall rule blocking ICMP requests will result in the following:
Code:
ping: sendmsg: Operation not permitted
rather than "permission denied".
If you really are getting "permission denied" it may not be a firewall rule, but you may want to look at something else you may be running on your system that could have a similar effect.
Since ping fails on both ethernet or wireless, that is definitely a firewall rule (another problem for another day).
When connected via ethernet, I have no problem accessing the internet. On wireless, I can't.
The only other unusual thing is that when I click on the networkmanager icon in the task bar, it shows a small (locked) padlock near the wireless symbol opposite the wireless name.
Do you know for sure if you have any firewall rules in place? I'd hate to have you chasing down non-existent problems. By default Slackware has no netfilter configuration, allowing all connections. If you are unsure, as root run the following from the command line:
Code:
iptables -L -n
If you do indeed have something in place it is possible it is set up to only allow traffic for your wired interface and not your wireless interface.
As for the lock icon show by NetworkManager, the GTK+ applet (used by XFCE, for example) shows a lock for secured connections. That is normal.
Although I don't see any clues here, this is the output from "iptables -L -n":
I forgot to have you use the "-v" option as well so we could see which interface(s) the rules applied are to. Your policies for INPUT and OUTPUT are DROP, so if your ruleset only applies to your wired interface, no traffic is going to be allowed on the wireless interface.
For the time being it may be easier to flush your rule set and set the policies of INPUT, OUTPUT, and FORWARD to ACCEPT (in other words, return netfilter to its default state of allowing all traffic). If you can then access remote hosts when using your wireless interface you know the problem lies somewhere in your firewall script.
NOW I am making some progress. When I temporarily disabled the firewall, internet access was enabled.
I originally generated the rc.firewall in Jan 2011 from Alien Bob's easy firewall generator which is available at http://connie.slackware.com/~alien/efg/. This generator has not been updated since 05/11/2005 so other users using this generator will have the same problem.
The output from iptables -L -n -v mentions "eth0" a number of times but not "wlan0".
The relevant section of rc.firewall seems to be as follows:
Code:
# Internet Interface
INET_IFACE="eth0"
Can I simply add "wlan0" at this point or is it more complicated than that?
Are you loading both rc.networkmanager and rc.wicd in /etc/rc.d/ ?
In Slackware 14.0 that is no longer an issue. rc.M has been updated so that it runs rc.wicd if that file is executable, otherwise it runs rc.networkmanager.
The help screen for the interface in Alien Bob's firewall generator states:
Quote:
If you are generating a script for a single system that sometimes uses a dail-up connection and other times uses a network connection, just specify + for the interface to match every interface.
A dated help screen for sure but it means that I only had to change the relevant section of rc.firewall as follows: (and it works)
Code:
# Internet Interface
INET_IFACE="+"
If nobody comes up within the next couple of days and says that I did something extremely stupid, I will mark this question "solved".
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,087
Rep:
Quote:
Originally Posted by psionl0
In Slackware 14.0 that is no longer an issue. rc.M has been updated so that it runs rc.wicd if that file is executable, otherwise it runs rc.networkmanager.
If rc.wicd is executable then it won't attempt to run rc.networkmanager. You can see it for yourself in /etc/rc.d/rc.M if you are running Slackware 14.0. The relevant section is as follows:
Code:
# Start wicd or networkmanager:
if [ -x /etc/rc.d/rc.wicd -a -x /usr/sbin/wicd ]; then
sh /etc/rc.d/rc.wicd start
elif [ -x /etc/rc.d/rc.networkmanager ]; then
sh /etc/rc.d/rc.networkmanager start
fi
I am guessing that you think I might have messed up the rc.M file (or that I had included the startup commands in rc.local without realizing that it is now in rc.M).
Otherwise, it appears that you asked a question that you already knew the answer to.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Successful wireless connection but no internet access
