Cannot access an ISP blocked site via mx linux v21 (32bits) [Solved]

[CharlesV]

There are two points to accessing a site:

1) dns - can you ping using the site's name and does the name resolve to an ip?
and
2) actual access.

TO my knowledge, unless you have specifically added some type of watch / blocker to your linux load, there should be nothing blocking you. You MAY not have changed dns servers in the system, or it may still be using the original cached DNS servers.

Try rebooting after the DNS changes.

[richb]

Seems to me you should be asking your ISP.

[SideTips]

To "CharlesV", I have just booted a live session of mx21 in the same computer. Changed the dns servers (disconnected and the re-connected WiFi) and get the exact same result. So my linux "load" is fine. And I also decided to try the access on Windows10 changing DNS and voila! It works!

To richb (thank you). Yeap I think I should ask my ISP, Hehehehe.

[SideTips]

So I can access the blocked site from Win7 and Win10 but not with mx linux 21. I'm going to check what happens with a live session from mx 19.3 and I will let you know...

[DukeComposed]

My point here (to both of you) is: I can access that blocked site from Win7 (changing DNS servers) and I can not do the same thing in Linux. Why?

Julia Evans was on a podcast in 2018 that explains this in detail. She wrote about it on her blog and provided a link to the episode that includes a complete transcript. I think she does a pretty decent job breaking down the steps involved in answering your question.

[SideTips]

To "DukeComposed", thank you for your suggestion, I will have a look at that link for sure.

[SideTips]

Well I want to thank all of you for your help as it was very useful for me.

I also want to say thanks in particular to "Charlie Brown". Mainly for the idea of the live session and as said before. I tried a live session of mx21 and it does not work.

Now guess what. I also gave it try with a live session of mx19.3 and voila! It works! And I followed the exact same steps with both mx21 and mx19.3 (live sessions) as I had explained all the way down this post. Why this happens, I will leave it to your consideration...

My adventure (for this matter) ends here.

Thank you!

P.S. I will give the SOLVED to "Charlie Brown"

[Charlie Brown]

Glad to hear it works on any MX :)

Just loudly thinking:

If it was just MX-23, the difference is that ufw is enabled by default. (Was not up to 23)

But the common point of 21 and 23 is that resolvconf (package) is not installed ootb (on MX-19 and before, that package manages those things ootb).


In fact that was the 1st thing that came to my mind but didn't write as you already verified the dns , also the contents of resolv.conf file ... there must still be something about that ...

[SideTips]

Thank very much for your time "Charlie Brown".

Let me make one thing clear (that I think you got wrong).

I'm NOT able to access the blocked site using MX Linux v21. But I am ABLE to access the blocked site using MX linux v19.3 without problems. Please note that I followed the same steps in both versions regarding the configuration of DNS and so on.

So, something is wrong with MX21. My question is why does this happen? I think MX21 just ignores the GUI that is used to configure WiFi settings and does something else instead.

I have no need to access the blocked site. I just use it as a test. And I can skip the block created by my ISP using: windows 7, windows 10 and also MX19.3 but not MX21 (I have not tested the live session from v23. I do not know if I ever will.)

Do you have any ideias why this happens in MX21?

I wrote this post to satisfy my curiosity and to confirm that MX21 may have some kind of bug regarding the configurations of DNS servers by the user to override the ones established by the ISP.

Take care "CB"

P.S. I do not use ufw in linux

[FullScale4Me]

This sounds more like the browser headers returned to the webserver are being evaluated against a local block list.

With a few 10s of years of website building experience, this does NOT sound like any ISP interference. Banking sites do this all the time. They are usually more polite about it and ask you to use a different browser and/or OS. Not an MX 21 issue IMHO.

A possible good test would be to install the same version of web browser as used on MX 19 on MX 21.