Results 1 to 10 of 14
I have just installed Slackware 13 and cannot access the Internet using my Intel wireless. I can access my router over the wlan but traffic is not going to the ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 09-16-2009 #1
Slackware 13; can't access internet using wireless
This feels like a firewall type issue as attempting to ping Google (by name or IP) results in Network Unreachable. I don't know where to look to see if wlan0 is being blocked from the Internet.
- 09-16-2009 #2
I used the command
route add default gw 192.168.0.1 wlan0
and I now have unencrypted wireless access to the Internet now to figure out wpa - phew!
Will I have to go through this every time I want to use wireless?
- 09-16-2009 #3
wpa was easy
wpa_passphrase essid passphrase
Edit /etc/rc.d/rc.inet1.conf and add the following to the appropriate interface
So when I reboot, to use wireless I have to do the following
ifconfig eth0 down route add default gw 192.168.0.1 wlan0 ifconfig eth0 up
Why is this so much fun?
- 09-17-2009 #4
You do not use DHCP?
Then you can set your gateway manually in /etc/rc.d/rc.inet1.conf
You can put all your configs there as well.
Although I must admit that I was never any good with that approach because I have different networks I need to be able to connect and I solved it by scripting.
cat /usr/local/bin/name_of_client #!/bin/bash ifconfig wlan0 up iwconfig wlan0 essid Sitecom dhcpcd wlan0
If you don't use DHCP there's a good chance you'll have to set up DNS as well. Edit your /etc/resolv.conf to taste.
Example (uses openDNS):
nameserver 188.8.131.52 nameserver 184.108.40.206
Originally Posted by elijaCan't tell an OS by it's GUI
- 09-17-2009 #5
- 09-17-2009 #6
This is bizarre.
My Wireless works but I have to take down eth0 and restart the Wireless after booting. I have been unable to find a solution. Any ideas?
- 09-17-2009 #7
Sounds like a routing problem to me.
A quick test. After boot both your interfaces are 'up' right? I don't think you need a full reboot. This should do:
After that try to ping something, but tell `ping` which interface to use:
ping -I wlan0 192.168.0.1 # the 'I' is a capital 'i'
If the first one didn't work, and the second one did then it's thinking your unconnected eth0 is up and prefers that. You want to solve this, but you don't want it happening the other way around when you're using a wired connection.
It's a setting somewhere. Funny you don't run into this when you're using DHCP
Can you post the output of `route`?Can't tell an OS by it's GUI
- 09-17-2009 #8
- 09-17-2009 #9
To boot to runlevel 3 simply press tab at the Slackware screen and type Linux 3
I have been told that the reason is as follows.
eth0 is the primary device and will therefore take priority. The solution is to use DHCP to configure a specific IP for eth0. wlan0 will then take over when eth0 isn't connected.
I'm going to set up my router as a dhcp server and give it a go tomorrow. Too drunk now
I'm sure Ubuntu did the same with static IP addresses but I may be wrong
- 09-18-2009 #10Originally Posted by elija
image = /boot/vmlinuz-huge-smp-220.127.116.11-smp root = /dev/hda1 append = "3" label = Rescue
lilo # Don't forget this!
Originally Posted by elija
I said it's a setting somewhere that you don't come across when you use DHCP. So this is one question in the category 'we must look this up'. But I'll be gone this weekend.Can't tell an OS by it's GUI