What is the name of the package to report network bug UBUNTU 18.10

As long as you do not provide any details about the issue, we can only guess.

For diagnostic purposes, what is he output of the commands

uname -a
lsb_release -crid
apt-cache policy netplan.io network-manager-gnome libnma0 libnm0

Following is my problem:
https://answers.launchpad.net/ubuntu/+question/679631
---------

----------
Linux joe-N53SV 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Distributor ID: Ubuntu

Description: Ubuntu 18.10

Release: 18.10

Codename: cosmic

netplan.io:

Installed: 0.40.2

Candidate: 0.40.2

Version table:
 *** 0.40.2 100
        100 /var/lib/dpkg/status

network-manager-gnome:
  Installed: 1.8.18-2ubuntu2

Candidate: 1.8.18-2ubuntu2

Version table:
 *** 1.8.18-2ubuntu2 100
        100 /var/lib/dpkg/status

libnma0:
  Installed: 1.8.18-2ubuntu2

Candidate: 1.8.18-2ubuntu2

Version table:
 *** 1.8.18-2ubuntu2 100
        100 /var/lib/dpkg/status

libnm0:
  Installed: 1.12.4-1ubuntu1

Candidate: 1.12.4-1ubuntu1

Version table:
 *** 1.12.4-1ubuntu1 100
        100 /var/lib/dpkg/status

Sorry, I occasionally did not mention the problem in the question.

1. I do not think that this is a bug, but more probably caused by configuration errors on your system.

2. Ubuntu-bug is not accepting your package names, because you have not the newest versions installed. You seem to be missing all package updates from the cosmic-updates and cosmic-security repositories

What output do you receive for the commands

sudo apt update
apt list --upgradeable

Well, I looked at 'UBUNTU-BUG' as the last chance to inform developers, that something was wrong with Ubuntu 18.

You can find all information here:
https://askubuntu.com/questions/1125228/ubuntu-18-10-wifi-login-problem?noredirect=1#comment1862194_1125228.

If You have a little time to figure out what it is, will you, please, do so.

And the workaround is:
 sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

But it still does not seem right to me. Unless /etc/resolve.conf link is done the way it is by mistake.

The strangest thing for me was having connection work by adding ANY NAMESERVER to original /etc/resolv.conf. Or replacing 127.0.053 with any other value, except 127.0.../0.0.0.0.

My DNS is 192.168.11.1. I had access even if I put 192.168.0.1 and any figure, what one may imagine.

I am on cargo vessel, and unfortunately, I am not able to do any updates due to limited internet access.
But I am able to do anything else.

I think, I will be able to get on the net in a couple weeks, when we are in port.

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

I do not have any reply. What shell I do?

What exactly is the current problem?
My interpretation of your comments in question 679631 was, that you found a workaround.

My intention is to inform developer team. This problem is not supposed to happen on fresh installed system. The same thing happens when using live CD. Please correct it in future builds. This is my point.

This question was expired because it remained in the 'Open' state without activity for the last 15 days.