TX carriers

The number received packets that experienced loss of carriers.

So carriers 1 means 1 packet experienced loss of carrier. This does not sound fatal to me.

http://www.linuxquestions.org/questi...output-260481/

"Are you using DHCP? That would override your resolv.conf every time the network is started."

http://forums.fedoraforum.org/showthread.php?t=151096

Seems resolv.conf ain't so important.

Correct me if I'm wrong, but I think the great majority of net users use dhcp.

You are correct, most people do use dhcp,but it can be very different between setups.

You are correct in saying that the carrier 1 is not too much of an issue, depending on the case. If you have transmitted less than 100kb then there are not that much information to transmit and that can keep the count low.

Running the machine a while longer means that don't just leave it on. Visit some web pages, try to surf the internet, maybe watch a short movie so we can get lots of data to have a look at and determine if that carrier issue is because of pulling out a cable somewhere or if it is something else.

The resolv.conf is on the otherhand an extremely important file.

What i would like you to try on fedora.

Open your /etc/resolv.conf

Where it says nameserver change the 192.168.1.1 to
210.80.60.1 or 8.8.8.8

That is icable in hong kong.


You must have done something really funky if you can resolve dns using 127.0.0.1

Are you trying to run bind or dnsmasq or something else that acts as a dns server and not telling us about that? If you are that would explain why you can resolve on localhost and you then mucked up your dns server settings so that it does not query other master servers on the net.

If the answer is no, then you probably have a secondary server configured with network manager amd that will make things slow since 127.0.0.1 is searched first and times out. In that case delete 127.0.0.1 and save the file and see what happens

No, I have no idea how to set up anything you mention. I can just about install Ubuntu. I am just a user. That is as far as my computing skills go. Whoever builds Ubuntu knows what they are doing, one presumes.

Go to work now. I will try alttering resolv.conf tonight, see if my laptop explodes!!

A tricky question for you: if I reset resolv.conf to 8.8.8.8 and do not restart the network, these changes will not be overwritten. How can I possibly know whether my laptop is actually contacting 8.8.8.8 to ask for info about domain names?? What tools are there to see what requests go from my computer to the net, and to whom they are addressed???

That would be very interesting to see and know.

Go to

https://www.dnsleaktest.com/

and check the dns, if it says 8.8.8.8 then that is what is used.

Follow the fedora documentation and set the dns in network manager, it will not change then.

Just started Ubuntu
dnsleak test
221.228.15.110 none China Telecom Jiangsu

Changed resolv.conf to 8.8.8.8
dnsleak test
74.125.191.83 none Google United States
74.125.191.80 none Google United States
74.125.191.84 none Google United States
74.125.191.82 none Google

Works!! But that won't fix the carrier error. I think I should buy a new laptop, it's hard to change things in a laptop.

Is your speed problem solved?

If so you can make the change permanent in network manager.

8.8.8.8 i believe is just the main server that then forward to other servers, so those ip addresses should be fine.

It is silly to buy a new laptop just because ethernet does not work if that is even the problem. That carrier can be caused if you are taking out cables etc.

Most people have internet connections that can not even be saturated with a old generation wifi connection. For connections over 70mbps, in the home scenario, you will never get that so wireless is still fine.

It starts being better with cable in my experience once you get into fiber connections or nas storage capable of 1gbps connections.

The speed has gone back to normal, that is, what it was. The change in resolv.conf made no difference. The reason I think the problem was
Linux was because, when Linux could not load a page, Windows could. The hardware was the same. Maybe Win uses a different dns, I don't know. As far as I can tell, it uses the dns in the modem. Next time I start Win, I will look at dnsleaktest.com Cool site! Thanks for that!

I have fibre optic cable internet at, they say, 8mbs. Sometimes the connection is so slow, I think they mean 8bps. I have called the technician, he comes, checks things, starts Windows, runs speedtest.com and everything is hunky dory, 8mbs or more.

So I think there is a Linux problem, or an intermittent hardware problem.

I ran nm-connection-editor and changed the dns to the ones you suggested. It uses google for some reason, not the Hongkong one you mentioned, but it works!!

If you changed the dns as suggested on the original thread by many and before as johnvv mentioned, we could have had results before,

Please try to commit changes as they are suggested.

But good that it is resolved

Hey, I'm a user, not a geek! If someone had said, "enter nm-connection-editor in a terminal then edit your home connection, change 'Automatic (dhcp)' to 'Automatic (dhcp) Addresses only' in the ipv4 tab, and set the dns in the field below." I might have known how to change my dns. Without wishing to be ungrateful, "Change your dns." is not really very informative.

The problem has not gone away, and will recur I'm sure. Things were ok yesterday, before I knew how to change my dns. But I learnt something. Anyone who wants to change their dns can ask me now!