AirCooledFury Posted April 17, 2015 Share Posted April 17, 2015 Hello everyone. First post on here so bear with me. I am a cyber security student trying to learn to use kali and linux in general, and I have a problem with wifi. I have dual booted Kali with windows 8.1, and I cannot use the internet when I boot into kali. I get an ip address from my router's dhcp, I can ping addresses outside the network, like 8.8.8.8, but I cannot connect to any web pages. I need to connect while I work on kali for school work. Anybody know whats going on? Thanks in advance. Quote Link to comment Share on other sites More sharing options...
sud0nick Posted April 17, 2015 Share Posted April 17, 2015 If you can ping 8.8.8.8 then you are on the internet. You may just have a DNS problem if you can't open web sites. Have you configured your DNS serttings properly? Quote Link to comment Share on other sites More sharing options...
cooper Posted April 17, 2015 Share Posted April 17, 2015 You should've been given the DNS server from the DHCP response that gave you your IP. You're supposed to end up with a /etc/resolv.conf file which contains at least 1 entry for a nameserver which would point to the DNS server for the network. Check the man pages for either dhcpcd and/or resolvconf (the latter may not have been installed). Quote Link to comment Share on other sites More sharing options...
AirCooledFury Posted April 18, 2015 Author Share Posted April 18, 2015 Ok so what should the address in resolv.conf say? Because it just gives the loop back address. Quote Link to comment Share on other sites More sharing options...
AirCooledFury Posted April 18, 2015 Author Share Posted April 18, 2015 Nvmd after a reset it gives the gateway address. Quote Link to comment Share on other sites More sharing options...
Rkiver Posted April 18, 2015 Share Posted April 18, 2015 Ok so what should the address in resolv.conf say? Because it just gives the loop back address. While the issue is resolved, just to answer this question for future reference: None of us would know, that'd be based entirely on your setup at home. Quote Link to comment Share on other sites More sharing options...
AirCooledFury Posted April 18, 2015 Author Share Posted April 18, 2015 Ok so just to be more clear the issue is not resolved. I just responded ambiguously. What I meant to say was, the resolv.conf file lists my gateway address as the nameserver. I still cannot connect to any website. It is a wireless network using WPA2 - PSK security, on a belkin dual band n750 router. The network is pretty simple, a class C using 192.168.2.0 for the network with the gateway at 192.168.2.1. It uses automatic DHCP addressing. All the other machines on the network are running windows 8.1 except a few mobile devices. The kali machine I'm trying to fix has been dual booted with windows 8.1 on an HP laptop. On my kali machine, I noticed the ping is taking an unusually long time, like 67ms, and if I use the traceroute command, it gets to its destination but takes like 175ms per hop and the whole process lasts like 10 minutes. If I try to get to a website by putting it's IP address directly into the browser, I see the site name come up at the top of the browser window, but it just hangs there with a white display. Putting in a normal website name like www.google.com just causes a cannot find server error. Quote Link to comment Share on other sites More sharing options...
cooper Posted April 18, 2015 Share Posted April 18, 2015 In /etc/resolv.conf there should be a line that reads "nameserver [iP]" where [iP] is currently the IP of the gateway. This implies that the gateway is acting as DNS server for your network. It would appear that gateway is reluctant to fulfill this role which may very well also be the cause of the slow traceroute. Replace that [iP] value with 8.8.8.8 and then try accessing stuff again (restart the browser to make sure it uses the new value). If this works, your problem is the gateway not fulfilling its DNS role and you should look there for answers. Quote Link to comment Share on other sites More sharing options...
i8igmac Posted April 18, 2015 Share Posted April 18, 2015 (edited) try apt-get update... you can ping outside your network with out a problem? maybe your browser is messed up... you could try a live kali cd... As said above change your resolv conf to 8.8.8.8 Edited April 18, 2015 by i8igmac Quote Link to comment Share on other sites More sharing options...
AirCooledFury Posted April 18, 2015 Author Share Posted April 18, 2015 Ok so I tried setting resolv.conf to 8.8.8.8 and the result is the same. Another curious note is that when I use wireshark on my wlan0 interface the traffic shows the router repeatedly asking who is at my address, that is, the one assigned to kali on this machine. My machine replies and my router just asks again and again as long as I try to send packets. Is this normal? Also, could it be that my router doesn't like linux? Quote Link to comment Share on other sites More sharing options...
AirCooledFury Posted April 18, 2015 Author Share Posted April 18, 2015 Also, apt-get update returns something like: Could not resolve 'website.com' For several lines of attempted fetches. Quote Link to comment Share on other sites More sharing options...
i8igmac Posted April 18, 2015 Share Posted April 18, 2015 Dhclient wlan0 Quote Link to comment Share on other sites More sharing options...
AirCooledFury Posted April 18, 2015 Author Share Posted April 18, 2015 dhclient wlan0 returns: Reloading /etc/samba/smb.conf: smbd only RTNETLINK answers: File exists Quote Link to comment Share on other sites More sharing options...
i8igmac Posted April 18, 2015 Share Posted April 18, 2015 ping Google Quote Link to comment Share on other sites More sharing options...
AirCooledFury Posted April 18, 2015 Author Share Posted April 18, 2015 pinged 8.8.8.8 and got many replies with around 27ms each. Did you want me to ping 8.8.8.8 or their web address? Quote Link to comment Share on other sites More sharing options...
AirCooledFury Posted April 18, 2015 Author Share Posted April 18, 2015 My bad did you mean ping Google as in: root@hostname:~# ping Google ? Putting that in gives me this return : ping: unknown host Google Quote Link to comment Share on other sites More sharing options...
i8igmac Posted April 18, 2015 Share Posted April 18, 2015 Ping google.com Quote Link to comment Share on other sites More sharing options...
AirCooledFury Posted April 18, 2015 Author Share Posted April 18, 2015 ping google.com returns: ping: unknown host google.com Quote Link to comment Share on other sites More sharing options...
cooper Posted April 18, 2015 Share Posted April 18, 2015 Just to clarify, when you boot this very machine into Windows, everything works? Quote Link to comment Share on other sites More sharing options...
AirCooledFury Posted April 18, 2015 Author Share Posted April 18, 2015 Yes. It works great in windows. Quote Link to comment Share on other sites More sharing options...
AirCooledFury Posted April 18, 2015 Author Share Posted April 18, 2015 Update: I took wlan0 interface off the list in /etc/network/interfaces because I read that network manager will not manage interfaces listed there. Now when I try to ping google.com I get a reply. But when I try to go there in my browser it redirects me to charter search(charter is my ISP) and hangs with a white screen. Quote Link to comment Share on other sites More sharing options...
cooper Posted April 18, 2015 Share Posted April 18, 2015 Try a traceroute to google.com Quote Link to comment Share on other sites More sharing options...
AirCooledFury Posted April 18, 2015 Author Share Posted April 18, 2015 traceroute google.com returns: google.com: Name or service not known Cannot handle "host" cmdline arg 'google.com' on position 1 (argc 1) Quote Link to comment Share on other sites More sharing options...
AirCooledFury Posted April 18, 2015 Author Share Posted April 18, 2015 second attempt at traceroute google.com returns 15 hops and reaches google.com. Quote Link to comment Share on other sites More sharing options...
AirCooledFury Posted April 18, 2015 Author Share Posted April 18, 2015 so after several traceroute attempts it seems every other traceroute works and gives slightly different results. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.