Apps downloading is pretty slow

[Sashank999]

Hi !

Code: [Select]

tc@box:~$ cat /etc/resolv.conf
nameserver 192.168.55.1which makes me think that it queries my router which queries DNS given by my ISP.

[Rich]

Hi Sashank999
Yup, that's what it does. Try changing the contents to this:

Code: [Select]

nameserver 8.8.4.4or:

Code: [Select]

nameserver 4.2.2.4
Then see if things run any faster.

[Sashank999]

It didn't work as the file again changed nameserver to 192.168.55.1 .

[aus9]

Sashank999

if interested, my gateway is diff to yours. for me

Code: [Select]

cat /etc/resolv.conf
search localhost
nameserver 192.168.1.1If you log into your router....hopefully you have a page for network settings (DLINK)
LAN IP address matches my above number
and I have DNS relay enabled......and I believe that takes me to ISP DNS

[Rich]

Hi Sashank999
Change the contents of the file. Don't forget to use the save command in the editor.

Do not reboot.
Do not restart your wireless adapter.

The changes should be detected immediately. Try both of those DNS servers and see if either on improves your Internet connection.

[Sashank999]

Hi Rich,

I have done as you said. Edited it and confirmed that it has the saved change in nameserver with cat /etc/resolv.conf. I did not restart my wifi adapter or reboot. The resolv.conf automatically changes.

@aus9

But I have a DASAN Router which is configured to use 192.168.55.1 as the router page.

[Rich]

Hi Sashank999
So with the changes, is your web browsing any better? Are your downloads any faster?

[GNUser]

The resolv.conf automatically changes.

Hi, Sashank999. I agree with Rich that trying a different DNS server is an important step in troubleshooting your issue. A slow DNS server can have a dramatic impact on page load speed. I've experienced this issue myself.

Some network managers try to be "helpful" and automatically change the contents of /etc/resolv.conf. Openvpn sometimes also changes /etc/resolv.conf without your permission. There are different ways to prevent unauthorized changes to /etc/resolv.conf. An easy way that will work regardless of your setup is to make the file immutable. Go ahead and edit /etc/resolv.conf to your liking, then do this:

Code: [Select]

$ tce-load -wi e2fsprogs
$ sudo chattr +i /etc/resolv.conf
Now the file will be left in peace (until you reboot or run sudo chattr -i /etc/resolv.conf) and you can see if the DNS server change helps your issue.

[Rich]

Hi Sashank999

... The resolv.conf automatically changes. ...

Did I misunderstand you?

Are you saying that the  /etc/resolv.conf  file changes back to  192.168.55.1  even though you did not reboot or restart your
wireless adapter?

[Sashank999]

@GNUser
Thank You for the suggestion. I did it. But then chattr replied with :

Code: [Select]

chattr: Inappropriate ioctl for device while reading flags on /etc/resolv.confSo, I added -f flag(help by Google). Then it replied no messages and hence I thought all was good. Then again, it changed back to its original. I think it deleted the file and made another one instead of it.
I use no network managers. I just do

Code: [Select]

sudo wifi.sh -a & in my aterm and then close aterm and open firefox.

@Rich
Yes. That is what I mean. It just changes back to its original form.

[Rich]

Hi Sashank999
Does this command produce any output:

Code: [Select]

cat /opt/wlan0.sh

[GNUser]

Sashank999, sorry chattr didn't work. Maybe your filesystem doesn't support it.

Try adding your desired DNS servers to the top of /usr/share/udhcpc/default.script like this, for example:

Code: [Select]

dns="1.1.1.1 1.0.0.1"
Then running wifi.sh

[jazzbiker]

Hi, GNUser!

Handy tip, thanks in advance! Currently I'm not suffering from DNS losses, but who knows, what's behind the corner.

[GNUser]

Hi, Shashank999. I figured out the problem with chattr: In TCL, the root file system (including /etc/resolv.conf) exists only in RAM. Apparently ext3 and ext4 filesystems (and perhaps also other filesystems on a physical harddrive) support the immutable flag, but RAM filesystem does not.

Assuming your /opt directory is persistent, this will work (if your /home is persistent but not /opt, adjust the steps accordingly):

Code: [Select]

$ cp /etc/resolv.conf /opt/resolv.conf
$ sudo rm /etc/resolv.conf
-> edit /opt/resolv.conf to taste
$ sudo chattr +i /opt/resolv.conf
$ sudo ln -s /opt/resolv.conf /etc/resolv.conf
Now your DNS settings are immutable (until you reboot or run sudo chattr -i /opt/resolv.conf).

[GNUser]

You're welcome, jazzbiker. I hope it comes in handy sometime.

The trick with /usr/share/udhcpc/default.script is specific to DNS issues being caused by DHCP. The chattr trick has more general application--you can use it whenever you want to prevent unauthorized edits to a file (it is stronger than making the file read-only using chmod).