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.
Hi all, just installed my new tp-link WN350GD wireless card, tp-link WR340GD router & network manager with KDE plasmoid included . After reboot the card gets detected and scan the near wifi spots. Router is set to security "none".
Network manager detects my router, connects and gets IP. Shows status connected. Switch to firefox and nothing. ifconf and iwconf shows the card is detected and connected with IP assigned trough dhcpcd. Tried alienBob's wiki to the letter and same result.
Any help is welcome.
You should use the ISP DNS if possible. If '192.168.1.1' is a valid DNS then it could be a problem there. I suspect '192.168.1.1' is your router/modem that is the Gateway. 'nameserver 10.0.0.2' not valid with the kernel routing you show.
You could try from the cli to 'ping 67.215.65.132' and if that is valid then 'ping opendns'. If the latter fails then your DNS is not setup properly.
You could select a few from the above for your '/etc/resolv.conf' file but it would be best to at least use one of your ISP provided DNS. Unless of course you wish to setup a DNS server for your LAN.
You should use the ISP DNS if possible. If '192.168.1.1' is a valid DNS then it could be a problem there. I suspect '192.168.1.1' is your router/modem that is the Gateway. 'nameserver 10.0.0.2' not valid with the kernel routing you show.
You could try from the cli to 'ping 67.215.65.132' and if that is valid then 'ping opendns'. If the latter fails then your DNS is not setup properly.
You could select a few from the above for your '/etc/resolv.conf' file but it would be best to at least use one of your ISP provided DNS. Unless of course you wish to setup a DNS server for your LAN.
10.0.0.2 is my ISP adsl modem
192.168.1.1 is my wireless router
Code:
root@cesarion:/home/cesar# ping 67.215.65.132
PING 67.215.65.132 (67.215.65.132) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
How is the LAN configured? How do you have the router configured to comm with the modem? Which port on the router to the port on the modem?
It would be easier to stay with a range rather than having two different levels. Why have the modem on a different range of the class?
A lot easier to setup with the modem local IP in the same range. Set the modem to '192.168.1.1' with the router to say '192.168.1.2'. Set either the modem as the dhcp server or the router. No need to worry about the modems Internet IP, just set the local IP.
You can use the wired device on your computer (Internet) plugged into the router/modem to enter the web admin page. Be sure to restart 'inet' as root at command line(cli) with '/etc/rc.d/rc.inet1 restart' to get a new IP from the router/modem device. Then open a browser and in the address bar enter the IP that is currently set for the device. For the router you would use '192.168.1.1' then enter the assigned username & password. Most router will have a basic configuration page. You would then change the IP and save the settings.
Same with the modem, you would use '10.0.0.2' for the address entry(after cycling inet with a restart). Enter the username & password. You can get that information from the manual. Depending on the manufacture the username may be 'admin' and password could be 'password'. Look at both modem & router manuals for setup information. Sometimes you will find setup examples & procedures for the router/modem in their manuals.
For the modem you will need to connect & get a new IP from the dhcp for that range by using the '/etc/rc.d/rc.inet1 restart'.
You can use the links that I provided earlier to get some helpful background information. I like to provide a scope of my address assignments in written form for future reference(s).
For a 'SOHO' LAN your dhcp pool will not be that big nor will static IP assignments.
The problem was that I had the rc.firewall pointing at eth0. just chmod -x /etc/rc.d/rc.firewall do the job. Commented out /etc/rc.d/rc.inet1.conf and config all through Networ Manager, WPA2 included. Can't be more happy and tiered I checked the links you suggested and clarified some dark spots for me. thanx for the help
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.