I am having an issue connecting to webpages, when I am not plugged into a wired connection. I can connect to the internet through the ethernet just fine. I can also, regardless of wether I am plugged in, connect to my wireless network. When I am only connecting wirelessly, It tells me (in Firefox) that it cannot connect to the server.

I used Linux Mint 12 before this, and it worked fine (I don't recall having to do anything to get the wireless to work). I am a super newb, so suggestions and requests that are as step-by-step as possible are greatly appreciated.

Since the script you are attempting to invoke has been converted to anUpstart job, you may also use the reload(8) utility, e.g. reload smbdRTNETLINK answers: File exists-------------------------* VI. querying nslookup google.com...Server: 192.168.1.1Address: 192.168.1.1#53

The last sections of your results show that you do have a working wireless connection, which appears to be successfully connecting at least as far as the router, and appears to be resolving DNS. I do see that your connection is defaulting to use your local gateway for DNS, though.

For diagnostic purposes, try the following:

- In Terminal, type host lizkalish.com and see if it returns the IP address 23.25.11.180. Then try host lizkalish.com 8.8.8.8 and see if that returns the same thing. (This is a low-traffic domain I have control over.)

- In Firefox, put 23.25.11.180 in the URL bar and see if it takes you to a website.

- If you get the website using the IP, but not by using the URL; or if the two host commands in the first step return different results, then it might be a DNS issue. Let us know what the results are and we'll take it from there.

Sixth, no ethernet (connected to wifi) did take me to the site with just the numerical address

Seventh, to make sure this was not just a fluke due to cookies/browser data - I deleted all cookies and history and then repeated - this time wifi did not take me to the site using the numerical addressI get the message: "Firefox can't establish a connection to the server at 23.25.11.180."

I'm not sure what to tell you. You're connected, but your connection isn't letting you do anything. If you go your Network Connections and edit the current wireless connection, what options are selected in the IPv4 tab?

Require IPv4 addressing for this connection to complete: [box not checked]

available to all users: [box checked]

when I click on the "Routes..." button: [nothing is included in the 'address/netmask/gateway/metric' box - and - neither of the boxes (the 'ignore automatically obtained routes' and the 'use this connection only for resources on its network' boxes) are checked

Yeah, all of the other machines in the house (acer laptop (running ubuntu), mac desktop, ipad 1, ipad 2, android and iphones, and roku boxes) connect just fine, so did my machine until I installed Mint 13 (the same issue occurs when I run the new ubuntu release).

Postby LMDEFan1 on Mon Jul 23, 2012 7:10 pmdnsmasq usage is causing network connection definitions to be ignored for DNS Servers and Search Domains. This issue is in all the Mint 13 releases from what I have seen. I suspect it's an upstream issue from Ubuntu.

The script at this link will create a solution that works between system restarts.

If dnsmasq was intentionally implemented there are tons of irritated network and vpn users. Especially those of us who like this distro at work where we have to configure DNS Servers and Search Domains. It also impacts being able to actually make a connection to an Oracle 11g database with the 11g r2 client (and probably any other database and client combination you are trying to reach on your network). Really frustrating. This is one reason I’m hoping Linux Mint becomes Debian based instead of Debian/Ubuntu. Although I realize there is a ton of work done by Ubuntu to polish Debian just as there is a ton of work done by the Linux Mint team to polish Ubuntu to the point we all prefer it over Ubuntu."

The link in the post brings you to this post by "linc"

"Mint 13 Fix for Broken DNS.By linc Linux Mint Add comments

I really love Mint, just let me get that out of that way first. That being said, there are usually a couple things I catch, per release, that filter down from Ubuntu, that I wish were taken care of before Mint hits my desktop.

This time it is DNS.

I installed Mint 13 and was cruising around my home network and noticed that my dns searches weren’t appending my local domain. I had to use the FQDN to get to *anything* on my home network. Well, this frustrated me a bit because I worked hard to set up my own home network, I have resources on it including DNS, and I would like to actually use it. So, I went on the hunt for WHY I had to use a fully qualified domain name on my network…

For some strange reason, someone, somewhere thought it would be a great idea to mess with the way we handle DNS. In fact, the way Linux/Unix/unix has traditionally handled DNS for ever. That being if you put stuff ™ in the friggin /etc/resolv.conf file, your DNS just magically works. Well, not any more.

I have done 3 Mint 13 / Cinnamon installs now (assuming that Mate is the same here) and, in fact, THERE IS NO RESOLV.CONF file! What has happened is this, as far as I can tell. Someone in the Ubuntu camp (I assume) decided that it would be a great idea to start using dnsmasq through the NetworkManager to take care of DNS because they wanted to skirt some VPN issues with single homing. In layman’s terms, when you use a VPN, you are *ONLY* supposed to be able to connect to that network to be secure. Using dnsmasq, you could conceivably be on your VPN and route local traffic around too (multi homing). IPSEC guys frost themselves over stuff like this, BTW.

So, I set about to correct this injustice. Here is a simple script you can run which will turn off the dnsmasq garbage, put your resolv.conf files back in place where they belong and start those services back up so stuff works like we have been doing it for 20+ years.

Can anyone here tell if this script looks right?When I get to "fi" it closes terminal on me... and I'm not sure what I'm supposed to expect anyway (after most of the input it just takes me to the next line)

Because I need wireless internet, I have installed Ubuntu 11.10. I'm not experiencing any problems.

I experienced the problem mentioned above when I booted either LM 13, LMDE, or Ubuntu 12.04 LTS . The problem occured both when installed and when run from flashkeys. The debian looks like it's the common factor here, and might explain why I have no problems with the release I'm using now.

If someone is interested in helping me trouble shoot the problem, I am happy to do so through flash boot or even to install a dual partition (if necessary).

All Ubuntu is based on Debian, including the release you're successfully using now. So I don't think Debian itself is the issue. Rather, the version list you posted makes me think there's a driver or kernel support issue that is causing a problem with your particular hardware. Ubuntu 11.10 is the oldest of the four distros you listed. I'm thinking whatever it is probably changed upstream in Debian between the release of Ubuntu 11.10 and 12.04, and it is now in the current rolling-release LMDE, Ubuntu 12.04, and Mint 13 (which is based on Ubuntu 12.04).

If you can use Ubuntu 11.10, you can probably also use Mint 11 or 12. Which one you go with is up to you. I'd take Mint 11.

As an experiment, you might try uninstalling network-manager in Mint 13 and configuring your network connection manually. If you want to do that I'll do my best to point you in the right direction. But it's a shot in the dark.

They didn't work for me personally. If they don't work for you then either replace the wireless card with another model or replace Network Manager with WICD. I changed to WICD first but as WICD does not support USB tethering I ended up changing the card to an Atheros one.

Postby LMDEFan1 on Mon Jul 23, 2012 7:10 pmdnsmasq usage is causing network connection definitions to be ignored for DNS Servers and Search Domains. This issue is in all the Mint 13 releases from what I have seen. I suspect it's an upstream issue from Ubuntu.

The script at this link will create a solution that works between system restarts.

If dnsmasq was intentionally implemented there are tons of irritated network and vpn users. Especially those of us who like this distro at work where we have to configure DNS Servers and Search Domains. It also impacts being able to actually make a connection to an Oracle 11g database with the 11g r2 client (and probably any other database and client combination you are trying to reach on your network). Really frustrating. This is one reason I’m hoping Linux Mint becomes Debian based instead of Debian/Ubuntu. Although I realize there is a ton of work done by Ubuntu to polish Debian just as there is a ton of work done by the Linux Mint team to polish Ubuntu to the point we all prefer it over Ubuntu."

The link in the post brings you to this post by "linc"

"Mint 13 Fix for Broken DNS.By linc Linux Mint Add comments

I really love Mint, just let me get that out of that way first. That being said, there are usually a couple things I catch, per release, that filter down from Ubuntu, that I wish were taken care of before Mint hits my desktop.

This time it is DNS.

I installed Mint 13 and was cruising around my home network and noticed that my dns searches weren’t appending my local domain. I had to use the FQDN to get to *anything* on my home network. Well, this frustrated me a bit because I worked hard to set up my own home network, I have resources on it including DNS, and I would like to actually use it. So, I went on the hunt for WHY I had to use a fully qualified domain name on my network…

For some strange reason, someone, somewhere thought it would be a great idea to mess with the way we handle DNS. In fact, the way Linux/Unix/unix has traditionally handled DNS for ever. That being if you put stuff ™ in the friggin /etc/resolv.conf file, your DNS just magically works. Well, not any more.

I have done 3 Mint 13 / Cinnamon installs now (assuming that Mate is the same here) and, in fact, THERE IS NO RESOLV.CONF file! What has happened is this, as far as I can tell. Someone in the Ubuntu camp (I assume) decided that it would be a great idea to start using dnsmasq through the NetworkManager to take care of DNS because they wanted to skirt some VPN issues with single homing. In layman’s terms, when you use a VPN, you are *ONLY* supposed to be able to connect to that network to be secure. Using dnsmasq, you could conceivably be on your VPN and route local traffic around too (multi homing). IPSEC guys frost themselves over stuff like this, BTW.

So, I set about to correct this injustice. Here is a simple script you can run which will turn off the dnsmasq garbage, put your resolv.conf files back in place where they belong and start those services back up so stuff works like we have been doing it for 20+ years.

Can anyone here tell if this script looks right?When I get to "fi" it closes terminal on me... and I'm not sure what I'm supposed to expect anyway (after most of the input it just takes me to the next line)

bbthomp,1) Copy that script into a text file and save it, with name of fixmint13.sh, to your home folder. You want to start copying with line: #!/bin/bash and then end with line: reboot

2) Open a console window / terminal. It should open in your home folder. If you type ls and hit enter you should see the fixmint13.sh file in the list of files displayed.

3) Now, in your terminal window, type: sudo ./fixmint13.sh

It will ask your for your password. Once you enter your password it will run the script and reboot your computer so make sure you've saved and closed any other applications you may have open before you run this script.

Once your computer reboots, and you've logged in, you should be able to access the internet.

If you want to see what the changes are to your system open the following files in your text editor:/etc/NetworkManager/NetworkManager.conf Notice that the following line has been commented out: dns=dnsmasq It's now #dns=dnsmasq

/etc/resolv.conf This file contains the definition for your name servers (DNS servers) as well as any domain and search domains that you have defined in your network connection.

I was able to connect to my VPN server at work using openVPN. However, once I was connected, the internet stopped working and it couldn't resolve any page names on the internets. Running your script fixed everything so I am now VPNing and surfing simultaneously. Thanks again.

1) Copy that script into a text file and save it, with name of fixmint13.sh, to your home folder. You want to start copying with line: #!/bin/bash and then end with line: reboot

2) Open a console window / terminal. It should open in your home folder. If you type ls and hit enter you should see the fixmint13.sh file in the list of files displayed.

3) Now, in your terminal window, type: sudo ./fixmint13.sh

It will ask your for your password. Once you enter your password it will run the script and reboot your computer so make sure you've saved and closed any other applications you may have open before you run this script.

Once your computer reboots, and you've logged in, you should be able to access the internet.

If you want to see what the changes are to your system open the following files in your text editor:/etc/NetworkManager/NetworkManager.conf Notice that the following line has been commented out: dns=dnsmasq It's now #dns=dnsmasq

/etc/resolv.conf This file contains the definition for your name servers (DNS servers) as well as any domain and search domains that you have defined in your network connection.

Hope this helps.

Does this work for Mint 14?

I enter all the above but after "sudo ./fixmint13.sh" it says command not found?

1) Copy that script into a text file and save it, with name of fixmint13.sh, to your home folder. You want to start copying with line: #!/bin/bash and then end with line: reboot

2) Open a console window / terminal. It should open in your home folder. If you type ls and hit enter you should see the fixmint13.sh file in the list of files displayed.

3) Now, in your terminal window, type: sudo ./fixmint13.sh

It will ask your for your password. Once you enter your password it will run the script and reboot your computer so make sure you've saved and closed any other applications you may have open before you run this script.

Once your computer reboots, and you've logged in, you should be able to access the internet.

If you want to see what the changes are to your system open the following files in your text editor:/etc/NetworkManager/NetworkManager.conf Notice that the following line has been commented out: dns=dnsmasq It's now #dns=dnsmasq

/etc/resolv.conf This file contains the definition for your name servers (DNS servers) as well as any domain and search domains that you have defined in your network connection.

Hope this helps.

Does this work for Mint 14?

I enter all the above but after "sudo ./fixmint13.sh" it says command not found?

Thanks

There is a step missing. Before you can run that script file you need to set it executable. In between step 2 and 3, type chmod +x fixmint13.sh and then continue to step 3.

Brilliant fix (god I love the Mint forums). Just to add my details, perhaps to make it easier for others to find what they're searching for:

I recently upgraded from Mint 10 to Mint 13 (Maya). With the older Mint release, I was successfully able to connect to internet and browse webpages over wireless at home, at work, and at the library, no problem. With Mint 13, on the other hand, I was able to connect and browse at home, but not at work or at the library.

At work, the SSID is not broadcast, and my first thought was that the hidden SSID had something to do with the problem, but I didn't have a chance to look into it; then I was at the library a couple of days later and saw that I was getting a proper internet connection, it was just that I was unable to load webpages ...

So when I got home, I searched for a few minutes on the forum, and voila', I found this thread. After running the fixmint13.sh script, I could still connect and browse the web just fine at home, and sure enough, when I tested it out at work this morning everything was working fine there too.

This could definitely have been a painful bug, but bugs are going to happen ... to me the real takeaway is that five minutes of browsing the forum got me a perfect solution, and that I get to keep using a fantastic release that in every other respect has been flawless for me. Thanks all.

xox101 wrote:If they don't work for you then either replace the wireless card with another model or replace Network Manager with WICD. I changed to WICD first but as WICD does not support USB tethering I ended up changing the card to an Atheros one.