Internet Connection Issue

[Member antixjim]

Helpful

Up

0

::

On 2 August Xecure wrote:

You have 2 options:
1. Keep using connman to manage resolv.conf -> remove /etc/default/connman
sudo rm /etc/default/connman

2. Let resolvconf manage it:

sudo rm /etc/resolv.conf
sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf

Then reboot and it should work again. Option 2 is the preferred option, to make it easier to change between connman/ceni in the future (if needed). But option 1 is to keep things as they were until now.

I followed the second option, although I thought it failed because of a message I received after running the second command I rebooted anyway as you said, and it worked. Thank you.

I do have two questions:

1. The fix apparently created a file named resolv.conf (in red letters) in my “jim” sub-directory. The icon is a yellow disk with a large exclamation mark in it.
Do I need to keep this file?

2. Do you know when there will be an update to completely resolve this problem. In the meantime, will future updates cause this problem to return.

[Member Xecure]

Helpful

Up

0

::

antixjim wrote:

1. The fix apparently created a file named resolv.conf (in red letters) in my “jim” sub-directory. The icon is a yellow disk with a large exclamation mark in it.
Do I need to keep this file?

This shouldn’t have happened. Probably something was not properly written when running the command. You can remove that file.

antixjim wrote:

2. Do you know when there will be an update to completely resolve this problem. In the meantime, will future updates cause this problem to return.

The latest update is the last, and replaces the other update to work exactly as the original connman. Nothing more should break at all.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member stevesr0]

Helpful

Up

0

::

Hi Xecure,

Tonight when I booted up, ping was again lost. Without trying readlink /etc/resolv.conf, I opted for solution #1 (which I had not tried before).

This did not work, either immediately or after a reboot.

However, after doing solution #2, I regained conection to DNS services.

I will see if this stays after a reboot and edit this with that info.

stevesr0

Update after reboot – DNS still works.

Readlink is /run/connman/resolv.conf.

Is this what it is supposed to be?

stevesr0

• This reply was modified 1 year, 8 months ago by stevesr0.
• This reply was modified 1 year, 8 months ago by stevesr0.

[Member Xecure]

Helpful

Up

0

::

stevesr0 wrote:

Readlink is /run/connman/resolv.conf.

Is this what it is supposed to be?

Yes. The update went back to how the previousto-the-problematic-update connman worked.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member marcelocripe]

Helpful

Up

0

::

Hello everybody.

I would like to inform you that in the update of the day 16-08-2021 of antiX 19.2 Full 64 bits, the Connman update also occurred, as I managed to copy the information contained in the Terminal window:

connman (1.36-2.3.0antix1 => 1.36-2.3.0antix2)
connman-vpn (1.36-2.3.0antix1 => 1.36-2.3.0antix2)

In a fresh installation of ISO antiX 19.4 Full 64 bits Kernel 4.9.0-265 which occurred on 16-08-2021, after updating antiX and consequently Connman, I restarted the computer and there was no longer the problem with the connection with the internet.

I can do a positive analysis of everything that occurred, in summary, the issue that was identified and presented in this thread by @Renegade on 08-02-2021 at 11:13 am, received the corrective solution through the response brought by @Xecure on the same day at 2:29 pm, in just 3 hours and 16 minutes the solution to the problem was available on this forum. After approximately 14 days (at least for me, with access to the Brazilian repository), the definitive solution occurred through the repositories. As I cannot measure all the work that was released so that the solution was available in such a short time, it is up to me to register my sincere thanks for all the work and commitment of all the people involved in solving the problem.

Thank you very much.

marcelocripe
(Original text in Brazilian Portuguese language)

– – – – –

Olá a todos.

Eu gostaria de informar que na atualização do dia 16-08-2021 do antiX 19.2 Full 64 bits, ocorreu também a atualização do Connman, conforme consegui copiar a informação contida na janela de Terminal:

connman (1.36-2.3.0antix1 => 1.36-2.3.0antix2)
connman-vpn (1.36-2.3.0antix1 => 1.36-2.3.0antix2)

Em uma instalação nova da ISO antiX 19.4 Full 64 bits Kernel 4.9.0-265 que ocorreu no dia 16-08-2021, após a atualização do antiX e consequentemente do Connman, eu reiniciei o computador e já não havia o problema com a conexão com a internet.

Eu consigo fazer uma análise positiva de tudo que ocorreu, em resumo, o problema que foi identificado e apresentado neste tópico pelo @Renegade no dia 02-08-2021 às 11:13 am, recebeu a solução corretiva através da resposta trazida pelo @Xecure no mesmo dia às 2:29 pm, em apenas 3 horas e 16 minutos a solução ao problema estava disponível neste fórum. Após aproximadamente 14 dias (ao menos para mim, com acesso ao repositório Brasileiro), a solução definitiva ocorreu através dos repositórios. Como eu não consigo mensurar todo o trabalho que foi desprendido para que a solução estivesse disponível em tão pouco tempo, cabe a mim registrar os meus sinceros agradecimentos por todo o trabalho e comprometimento de todas as pessoas envolvidas na solução do problema.

Muito obrigado.

marcelocripe
(Texto original em idioma Português do Brasil)

[Moderator Brian Masinick]

Helpful

Up

0

::

Thanks for the analysis and the appreciation for the work and the solution.

Both anticapitalista and Xecure deserve credit for the work and the community also deserves appreciation for sharing the activity, testing, comments and thanks.

Thank you Marcelo for your clear and complete test results and comments!

Congratulations to all!

--
Brian Masinick

[Member stevesr0]

Helpful

Up

0

::

Hi all,

I remain a tad confused.

Today, I booted up my 19 full system and I again had no internet connection, due to not having a nameserver in a resolv.conf file.

I edited the /etc/resolv.conf file and all worked (I know one is not supposed to…). I have not yet tried rebooting; my connection has survived a logout and log back in.

My confusion?

I have three resolv.conf files. Two are in the /run directory (/run/connman/resolv.conf and the other /run/resolvconf/resolv.conf) and one in the /etc directory /etc/resolv.conf.

Two of these are generated by connman and the other /run/resolvconf/resolv.conf) by resolvconf.

If the fixed connman version is truly fixed, I should not have to keep on doing either solution 1 or 2 or editing the resolv.conf file, yes?

readlink connects /etc/resolv.conf and /run/connman/resolv.conf and htop search does NOT show connman to be active. wicd is active.

So, how do I test that I have the fixed setup (or does the fix not work for all systems)?

Thanks in advance.

steve

• This reply was modified 1 year, 8 months ago by stevesr0.

[Member Xecure]

Helpful

Up

0

::

The update makes connman return to the aggressive behavior (taking control of etc/resolv.conf each reboot) to keep compatibility with previous antiX installations.
If you are using wpa_supplicant or wicd or other instead of connman, disable connman.
sudo update-rc.d connman remove
You will need to give resolvconf back its powers (if not using a custom /etc/resolv.conf file as described in previous messages by blur13) with:
sudo ln -sf /run/resolvconf/resolv.conf /etc/resolv.conf

As the newest update undid the “aggressive behavior fix” to cater to other already running systems, having connman enabled will always replace the /etc/resolv.conf file (doesn’t matter if you use connman or not) as long as connman starts at boot.
Read the previous messages where I try to explain this.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member stevesr0]

Helpful

Up

0

::

thanks Xecure,

These are quite clear (and simple <g>) instructions. I have printed them and will keep them (and blur13’s instructions) next to this computer.

Today, the machine booted up and was connected. What puzzles me is that today /run/connman/resolv.conf file and (obviously) the /etc/resolv.conf (it’s symbolic link) list
nameserver ::1
nameserver 127.0.0.1

while the /run/resolvconf/resolv.conf file contains the lan address of my router which hands off messages to the internet based nameservers I am using.

I understand 127.0.01 is the address of the localhost, but can’t find a reference on the internet to ::1.

Also, I don’t understand why the nameserver address to the router was present today in the /run/resolvconf/resolv.conf file but not yesterday.

Guess I shall have to reread the whole thread several times for it all to become clear <g>.

[Member stevesr0]

Helpful

Up

0

::

Hi again,

Today, my system again did NOT connect to DNS on booting. I could ping 1.1.1.1 but not google.com. But nothing looked changed from yesterday??!

At this time,

1) /etc/default/connman doesn’t exist
2) /run/connman/resolv.conf (and its symbolic link, /etc/resolv.conf) just show nameserver ::1 and nameserver 127.0.0.1
3) /run/resolvconf/resolv.conf shows my lan gateway address

I was able to connect via DNS by manually editing the /etc/resolv.conf to list just the lan gateway address. but I was looking for a “permanent” fix.

It dawned on me that I had both connman and wicd active.

So, I changed the /etc/init.d/wicd file so it didn’t start at boot.

Then I rebooted and voila, I am connected via DNS.

However, the /etc/resolv.conf file still DOESN’T list the lan gateway address – just ::1 and the localhost (127.0.0.1).

I have looked on the internet a bit just now and apparently sometimes BUT NOT always this connects to the (wan?) gateway or to the router gateway.

So, at this moment, I guess 127.0.0.1 (for my system) is all that is necessary to allow me to connect to different sites on the internet without memorizing their ip addresses <g>.

Bottom line – apparently wicd and connman cannot RELIABLY be active at the same time.

If this is now a stable solution, I will try to remember to send a follow up confirming it.

stevesr0

[Moderator Brian Masinick]

Helpful

Up

0

::

You cannot have two or more network manager programs running at the same time so that was a problem; glad you spotted it!

--
Brian Masinick

[Member stevesr0]

Helpful

Up

0

::

Hi Brian,

Yes I had heard that. But it seemed that the two were “happy” with each other <g>. I kept posting about this simply because there might be someone else who was (knowingly or unknowingly) running both.

Parenthetically, I have learned that the ::1 is the IPv6 equivalent of 127.0.0.1, the loopback address.

So, I am able to send “stuff” to my router using only loopback addresses, which seems like it shouldn’t work, but obviously I don’t understand this well…

stevesr0

[Member crackulator]

Helpful

Up

0

::

Just wanted to point out – because I had a similar problem, for a different reason – that (apparently) you can’t just barge right in and use ceni on a fresh install. It won’t be able to DNS; it will connect to the network and DCHP, but won’t be able to find any websites, because the DNS is under the control of connman.

It’s necessary to first find Applications / antiX / Change Wifi Program and select Ceni. This changes the configuration so that DNS will work with ceni.

(Connman is undoubtedly better, except that I can’t use it on my tiny Asus EEE because the screen is too small. The dialog boxes have controls offscreen.)

[Moderator Brian Masinick]

Helpful

Up

0

::

When discussing the relative merits of software, when we say “better” that is a matter of opinion in most cases.

An advantage of Connman is that it has a relatively easy to use user interface, but it is still reasonably small, both in memory consumption and in the amount of disk space the image uses.

Ceni is a pretty old tool. It has a minimal, basic screen interface, and it is also uses resources efficiently and conservatively.

We used to use wicd. It may have used slightly more resources than Connman, but they were similar. The problem with wicd is that it is based on Python 2, deprecated in Debian 11.

Network Manager is an effective tool used by many distributions. The reason we don´t use it is because it brings many libraries with it from the GNOME desktop environment.

All of these alternatives are “effective” and useful, but not all of them are appropriate for the antiX distribution to support, either because they are not supported or they require dependencies that the development team does not include with antiX.

That is a simplistic description; hopefully it is clear enough to explain Connman and Ceni, providing examples of a couple of other network management tools and the reasons they are not chosen with antiX.

• This reply was modified 1 year, 6 months ago by Brian Masinick.

--
Brian Masinick

[Member blur13]

Helpful

Up

1

::

“Connman is undoubtedly better, except that I can’t use it on my tiny Asus EEE because the screen is too small. The dialog boxes have controls offscreen.”

I also have an Asus EEE, and initially used ceni because of the screen issue, but also because it was lighter. The main pain with ceni is that it doesnt save the wifi passwords. Maybe there is a way to enable that, but I didnt explore that issue because with connman it just works out of the box. The way to deal with dialog boxes being offscreen is to hit alt+F11 to maximize the window, this redefines the window so all content is on-screen with a scroll bar. Or you can hold down alt and “grab” the window with the mouse and drag it up so you see the controls. Or you memorize the “alt+underlined character” of the most common dialog options. Ie alt+w to view wireless services, alt+k to hit OK in a dialog box, etc. Yet another option, if using the default icewm, is to add the line:

cmst.startFullscreen: 1

to ~/.icewm/winoptions

This has the effect of always starting connman in fullscreen mode.

[Author]

Posts