Wifi connected to router, ping to router ok, no webaccess. what is wrong?
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.
Wifi connected to router, ping to router ok, no webaccess. what is wrong?
I have spend the whole day trying to get my wifi working.
So far i have managed:
- to access the network using KWifimanager
- to obtain an ip using dhcpcd.
- access the wifi routers web interface over the wireless link using its IP
I cannot, however get access to the web.
I suppose there might something wrong with my DNS, but i am not sure how to fix it.
If i plug the LAN cable into the computer and the same wireless router
there are no problems at all, IP is recieved without me having to do something, and i can access the web.
Other computers that can access the router over wifi does not have problems
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
Try adding/editing to your /etc/resolv.conf file the DNS that comes from your ISP information from your wireless router and your wireless router's internal IP address, for example;
nameserver <ISP DNS IP address #1 from the wireless router here>
nameserver <ISP DNS IP address #2 from the wireless router here>
nameserver <your wireless routers internal IP address here>
Thanks a lot. I did manage to solve it on my own.
It seems that dhcpcd newer terminates but stays running in the console.
While it correctly fetches the IP address the nameserverinfo appearently disappears when the console is closed.
so the solution was simply to keep the program running.
If anyone knows why it is like this, and why this program is needed in the first place (I would think the abstractionlayers between the nic and the os should make all nics seem alike, wifi as ethernet?
You may struggle to find anyone who can give you a definitive answer for Fedora Core 4. It's been a long time since it was supported anywhere.
Fedora has a policy of only supporting a distribution for about 13 months from its release. As that means no security updates after that time most users move on to the next version fairly quickly.
As they released Fedora 8 a couple of months ago you can see that not many people will have current experience of 4.
A good bet might be to install a new version if you can.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.