I've checked my resolv.conf file, and it matches the other working computers on the LAN. The only thing I can think of is that curl, metasploit, and a couple other things got updated the other day, and now I can't load pages by name. For instance, I getBut I can load them by IP address. Someone please tell me what the **** is going on.Quote:
Could not resolve 'http.kali.org'
This might shed some light on the issue,Quote:
$ sudo dhclient wlan0
Reloading /etc/samba/smb.conf: smbd only.
RTNETLINK answers: File exists
Does anybody know how to troubleshoot this problem?
How would I check for "new services"? I didn't activate anything new, if that's what you're asking. I cannot apt-get anything with this problem. The problem only occurred the day after I performed the updates.
The problem has resolved itself somehow after a restart. I had installed Wicd, and I think there may have been a conflict between Wicd and the preexisting network manager. Now Wicd handles everything.
Scratch that. The problem surfaces when I'm on an AT&T nameserver. Are they intentionally blocking access for Kali machines?
Ok, see http://www.dslreports.com/faq/5975. I've tried several different MTUs, but I'll test it more thoroughly later and report back. If someone is aware of a script that auto-detects the optimal MTU on a network, that would be pretty handy.
Try manually setting your DNS in your internet connection settings to the Google DNS. 8.8.8.8, and 8.8.4.4 See if that helps.
You're saying I can set these as my nameservers in the resolv.conf file? Is there a special way to prevent the resolv.conf file from getting changed each time I connect to a different network? I've noticed that until my resolv.conf file gets updated on the AT&T network, my internet works with no problem. Thanks, by the way.Quote:
Originally Posted by charonsecurity
Following the advice of the article in post #8, I've found that an MTU below 1400 works. Contrary to the article, I am in the Southwest and apparently AT&T sucks no matter where you go in the country.