Ошибка 101 linux - TopOshibok.ru - решение и исправление самых разных ошибок

Looking forward to resolve apt-get connect (101 network is unreachable)? We can help you in fixing it.

The error usually occurs while accessing the network for updating or installing.

At Bobcares, we often get requests from our customers to fix the error network is unreachable as part of our Server Management Services.

Today, let’s get into the details on how our Support Engineers fix this problem.

What causes apt-get connect (101 network is unreachable)?

The error mainly occurs due to problems in network connections.

This error indicates that either the IPv6 connection is unstable, or the servers are dead, or the file is not found.

For instance, the error appears as follows.

Let’s see how our Support Engineers help the customer to fix this.

Easy way to fix the error

At Bobcares, where we have more than a decade of expertise in managing servers, we see many customers face error apt-get connect (101 network is unreachable).

Now, let’s see the major reasons and how our Support Engineers fix this error.

Disabling ipv6

Recently one of the customers was getting Update information outdated alert then he applied sudo apt-get update command. Unfortunately, the user got stuck with this error.

On further analysis, we could trace from the logs that the user’s machine was using IPv6 to connect to the internet.

Hence, the reason behind the error was user’s internet service provider does not support IPv6. So we tried disabling IPv6.

To do this system-wide, we edited the file /etc/default/grub by running the below command

sudo nano /etc/default/grub

And added the following.

ipv6.disable=1

To the value of GRUB_CMDLINE_LINUX_DEFAULT.

In a default Ubuntu installation, that line reads

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

so we changed it to

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ipv6.disable=1"

Then, we ran the following command.

sudo update-grub

Finally, we rebooted the server.

Finally, the connection problem was then resolved.

Enabling secure port

In addition, in certain cases this error results due to closed port 443.

We then open the secure port and the error get disappeared.

[Having trouble with this error? We’ll fix it for you.]

Conclusion

In short, apt-get connect (101 network is unreachable) occurs due to problems in network connection. Today, we saw how our Support Engineers helped the customer in fixing the error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Источник

Ubuntu 8

In this article, we will explore how to fix the “Error 101: Network is Unreachable” issue when updating Ubuntu using the Advanced Package Tool (APT). This error is typically indicative of a network connection issue or a problem with the network configuration.

To fix the «Error 101: Network is Unreachable» when updating Ubuntu with APT, you can try changing the repository mirror to the ‘Main server’ or disabling IPv6 system-wide. These solutions should help resolve the issue and allow you to update your system successfully.

Understanding the Error
Solution 1: Changing the Repository Mirror
Solution 2: Disabling IPv6
Conclusion

Understanding the Error

The “Error 101: Network is Unreachable” is a common error that users encounter when trying to update Ubuntu using the apt-get update command. This error is usually a sign that your system is unable to establish a connection with the network, which could be due to a variety of reasons, such as an issue with your local repository mirror or a problem with your Internet Service Provider (ISP).

Solution 1: Changing the Repository Mirror

One of the simplest solutions to this problem is to change the repository to the ‘Main server’. Sometimes, local repository mirrors can experience downtime, causing the “Network is unreachable” error.

To change the repository mirror, follow these steps:

Open ‘Software & Updates’ on your Ubuntu system.
In the ‘Ubuntu Software’ tab, locate the ‘Download from’ dropdown menu.
Change the selected option to ‘Main server’.
Close the window and try running sudo apt-get update again.

This change should force your system to use the main Ubuntu repository, which is generally more reliable.

Solution 2: Disabling IPv6

Another potential cause of this error is that your machine is using IPv6 to connect to the internet, but your ISP does not support IPv6. In this case, you can disable IPv6 system-wide.

To disable IPv6, you need to edit the /etc/default/grub file and add ipv6.disable=1 to the value of GRUB_CMDLINE_LINUX_DEFAULT. Here’s how you do it:

Open the terminal and type sudo nano /etc/default/grub. This command opens the grub file in the nano editor.
Locate the line that reads GRUB_CMDLINE_LINUX_DEFAULT and add ipv6.disable=1 to it. It should look something like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ipv6.disable=1"
Save and exit the file by pressing Ctrl+X, then Y, and finally Enter.
Run sudo update-grub. This command updates the grub and applies the changes you made.
Reboot your system.

Disabling IPv6 might seem like an extreme solution, but if you’re also experiencing issues browsing the web, it might be necessary.

Conclusion

The “Error 101: Network is Unreachable” when updating Ubuntu with APT can be a nuisance, but it’s generally easy to fix. By changing the repository mirror or disabling IPv6, you should be able to resolve the issue and update your system successfully. If you’re still experiencing problems, it might be worth reaching out to your ISP to see if there are any known issues or contacting Ubuntu support for further assistance.

APT stands for Advanced Package Tool. It is a package management system used in Ubuntu and other Debian-based Linux distributions to handle the installation, removal, and updating of software packages.

To update the grub after making changes to the /etc/default/grub file, you can run the command sudo update-grub in the terminal. This command updates the grub configuration and applies the changes you made.

Disabling IPv6 might be necessary if you’re experiencing network connectivity issues or if your ISP does not support IPv6. It can help troubleshoot network-related problems and ensure compatibility with IPv4-only networks.

To get further assistance from Ubuntu support, you can visit their official website at https://ubuntu.com/support. They provide various support options, including community forums, documentation, and professional support services.

Источник

My ubuntu browsing this normally can not access any site, more apt-get update and even upgrade this giving error as shown below, what could it be?

sudo apt-get update
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94,5 kB]
Hit:2 http://ppa.launchpad.net/webupd8team/sublime-text-3/ubuntu xenial InRelease
Err:3 http://br.archive.ubuntu.com/ubuntu xenial InRelease                     
  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
Err:4 http://br.archive.ubuntu.com/ubuntu xenial-updates InRelease
  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
Err:5 http://br.archive.ubuntu.com/ubuntu xenial-backports InRelease
  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
Downloading 94,5 kB in 2min 0s (786 B/s)
Reading package lists ... Done
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/xenial/InRelease  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/xenial-backports/InRelease  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

Ubuntu:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"

karel

109k100 gold badges266 silver badges296 bronze badges

asked Nov 2, 2016 at 4:09

Have you tried changing the repository to the ‘Main server’?

You can change it by opening ‘Software & Updates’ and selecting a different mirror.

From time to time the local repository mirrors go down so its always a good idea to check other ones

I have also noticed that it is trying to connect via IPv6 which your router or ISP may not support. Have you tried this?

answered Nov 2, 2016 at 5:18

AedazanAedazan

2921 silver badge13 bronze badges

From the logs it seems that your machine is using IPv6 to connect to the internet. It could be that your internet service provider does not support IPv6. You can try disabling IPv6.

To do this system-wide, edit the file /etc/default/grub (for instance using sudo nano /etc/default/grub), and adding ipv6.disable=1 to the value of GRUB_CMDLINE_LINUX_DEFAULT.

In a default Ubuntu installation that line reads

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

so you change it to

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ipv6.disable"

Afterwards, first run sudo update-grub, then reboot.

answered Nov 2, 2016 at 5:28

zwetszwets

11.7k2 gold badges32 silver badges44 bronze badges

Looking forward to resolve apt-get connect (101 network is unreachable)? We can help you in fixing it.

The error usually occurs while accessing the network for updating or installing.

At Bobcares, we often get requests from our customers to fix the error network is unreachable as part of our Server Management Services.

Today, let’s get into the details on how our Support Engineers fix this problem.

What causes apt-get connect (101 network is unreachable)?

The error mainly occurs due to problems in network connections.

This error indicates that either the IPv6 connection is unstable, or the servers are dead, or the file is not found.

For instance, the error appears as follows.

Let’s see how our Support Engineers help the customer to fix this.

Easy way to fix the error

At Bobcares, where we have more than a decade of expertise in managing servers, we see many customers face error apt-get connect (101 network is unreachable).

Now, let’s see the major reasons and how our Support Engineers fix this error.

Disabling ipv6

Recently one of the customers was getting Update information outdated alert then he applied sudo apt-get update command. Unfortunately, the user got stuck with this error.

On further analysis, we could trace from the logs that the user’s machine was using IPv6 to connect to the internet.

Hence, the reason behind the error was user’s internet service provider does not support IPv6. So we tried disabling IPv6.

To do this system-wide, we edited the file /etc/default/grub by running the below command

sudo nano /etc/default/grub

And added the following.

ipv6.disable=1

To the value of GRUB_CMDLINE_LINUX_DEFAULT.

In a default Ubuntu installation, that line reads

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

so we changed it to

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ipv6.disable=1"

Then, we ran the following command.

sudo update-grub

Finally, we rebooted the server.

Finally, the connection problem was then resolved.

Enabling secure port

In addition, in certain cases this error results due to closed port 443.

We then open the secure port and the error get disappeared.

[Having trouble with this error? We’ll fix it for you.]

Conclusion

In short, apt-get connect (101 network is unreachable) occurs due to problems in network connection. Today, we saw how our Support Engineers helped the customer in fixing the error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Этот вопрос уже имеет ответ здесь: Почему я получаю ошибку 101? Как работает мой DNS? 3 ответа

Мой ubuntu просматривает это, как правило, не может получить доступ к любому сайту, больше apt-get update и даже upgrade это дает ошибку, как показано ниже, что это может быть?

sudo apt-get update
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94,5 kB]
Hit:2 http://ppa.launchpad.net/webupd8team/sublime-text-3/ubuntu xenial InRelease
Err:3 http://br.archive.ubuntu.com/ubuntu xenial InRelease                     
  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
Err:4 http://br.archive.ubuntu.com/ubuntu xenial-updates InRelease
  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
Err:5 http://br.archive.ubuntu.com/ubuntu xenial-backports InRelease
  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
Downloading 94,5 kB in 2min 0s (786 B/s)
Reading package lists ... Done
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/xenial/InRelease  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/xenial-backports/InRelease  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

[d7 ] Ubuntu:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"

задан
2 November 2016 в 09:29

1 ответ

Из журналов кажется, что ваша машина использует IPv6 для подключения к Интернету. Возможно, ваш провайдер интернет-услуг не поддерживает IPv6. Вы можете попробовать отключить IPv6.

Чтобы сделать это в общесистемной, отредактируйте файл /etc/default/grub (например, используя sudo nano /etc/default/grub) и добавив ipv6.disable=1 к значению GRUB_CMDLINE_LINUX_DEFAULT.

В установке Ubuntu по умолчанию эта строка читает

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

, поэтому вы меняете ее на

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ipv6.disable"

. Затем сначала запустите sudo update-grub, затем перезагрузитесь. [ ! d4]

ответ дан zwets
23 May 2018 в 04:36

Другие вопросы по тегам:

Solution 1

Have you tried changing the repository to the ‘Main server’?

You can change it by opening ‘Software & Updates’ and selecting a different mirror.

From time to time the local repository mirrors go down so its always a good idea to check other ones

I have also noticed that it is trying to connect via IPv6 which your router or ISP may not support. Have you tried this?

Solution 2

From the logs it seems that your machine is using IPv6 to connect to the internet. It could be that your internet service provider does not support IPv6. You can try disabling IPv6.

To do this system-wide, edit the file /etc/default/grub (for instance using sudo nano /etc/default/grub), and adding ipv6.disable=1 to the value of GRUB_CMDLINE_LINUX_DEFAULT.

In a default Ubuntu installation that line reads

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

so you change it to

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ipv6.disable"

Afterwards, first run sudo update-grub, then reboot.

Comments

My ubuntu browsing this normally can not access any site, more apt-get update and even upgrade this giving error as shown below, what could it be?

sudo apt-get update
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94,5 kB]
Hit:2 http://ppa.launchpad.net/webupd8team/sublime-text-3/ubuntu xenial InRelease
Err:3 http://br.archive.ubuntu.com/ubuntu xenial InRelease                     
  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
Err:4 http://br.archive.ubuntu.com/ubuntu xenial-updates InRelease
  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
Err:5 http://br.archive.ubuntu.com/ubuntu xenial-backports InRelease
  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
Downloading 94,5 kB in 2min 0s (786 B/s)
Reading package lists ... Done
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/xenial/InRelease  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/xenial-backports/InRelease  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

Ubuntu:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"

Just in case someone has similar problem — in my case, there was a problem with my network. I did have internet access, but the adapter was not configured properly. Once I switched to wifi adapter, the apt update ran smoothly.

Disabling IPv6 because of a single networking issue seems a little overkill.
@DavidFoerster agree, but since poster wasn’t able to browse the web either, I reckoned that only forcing APT on IPv4 wouldn’t cut it.
Good point I originally understood the part about browsing to mean the opposite since it’s stated so weirdly.

Recents

Я получал Update information is outdated предупреждение. Я попытался sudo apt-get update и получил эти ошибки:

W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/Release.gpg  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://repository.spotify.com/dists/stable/Release.gpg  Something wicked happened resolving 'repository.spotify.com:http' (-11 - System error)
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/main/i18n/Translation-en_IN  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/main/i18n/Translation-en  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/multiverse/i18n/Translation-en_IN  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/multiverse/i18n/Translation-en  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/restricted/i18n/Translation-en_IN  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/restricted/i18n/Translation-en  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/universe/i18n/Translation-en_IN  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/universe/i18n/Translation-en  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/universe/source/Sources  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/main/source/Sources  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/multiverse/source/Sources  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/restricted/source/Sources  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/main/binary-i386/Packages  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/restricted/binary-i386/Packages  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/universe/binary-i386/Packages  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/raring-security/multiverse/binary-i386/Packages  Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::13). - connect (101: Network is unreachable) [IP: 2001:67c:1562::13 80]

E: Some index files failed to download. They have been ignored, or old ones used instead.

Я следовал за верхний ответ этого потока, и это устранило проблему.

Но кто-то, пожалуйста, объясните, в чем была проблема и как она была устранена?

Ссылка

3 ответа

Если вы получаете такие ошибки, это означает, что либо ваше IPv6-соединение было нестабильным, либо серверы были мертвы, либо файл не был найден. Прямо сейчас прорабатывается:

http://[2001:67c:1562::13]/ubuntu/dists/raring-security/multiverse/binary-i386/

ответ дан Dima
10.10.2019, 13:29

Ссылка

Измените настройки сетевого прокси-сервера синхронно с тем, который вы используете для доступа к этой веб-странице (короче говоря, прокси вашего браузера)

Ссылка

То, что вы видите в выходных данных, — это то, что ваша машина пытается подключиться с использованием адресов IPV6 (например, 2001: 67c: 1562 :: 13), которые отличаются от адресов IPv4 (например, 192.168.0.1). Вы могли бы иметь два подхода здесь. Один — отключите IPv6, выполнив эти шаги:

Откройте /etc/sysctl.conf в любом текстовом редакторе (для этого вам понадобится sudo). Лично я бы сделал что-то вроде sudo nano /etc/sysctl.conf (nano проще всего) или sudo vi /etc/sysctl.conf.

добавить эти строки

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

Выполнить sudo sysctl --load, чтобы применить изменения

Вторым способом будет использовать IPv6 DNS. Например, нажмите на индикатор сети на верхней панели, выберите Edit Connections, и для вашего конкретного соединения Wi-Fi или Ethernet используйте 2620:0:ccc::2 DNS, который OpenDNS IPv6-сервер . Убедитесь, что вы выбрали опцию «Только адрес»

Ссылка

Тема: Не открываются страницы по http (Прочитано 3027 раз)

0 Пользователей и 1 Гость просматривают эту тему.

garmayev

Установил новую систему Ubuntu 20.04 Focal

При попытке выполнить получаю:

$ sudo apt update


Ошб:1 http://archive.ubuntu.com/ubuntu focal InRelease                                              
  Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::24). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::23). - connect (101: Сеть недоступна) Не удалось соединиться с archive.ubuntu.com:80 (91.189.88.152): время ожидания для соединения истекло Не удалось соединиться с archive.ubuntu.com:80 (91.189.88.142): время ожидания для соединения истекло
Ошб:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease                                      
  Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::24). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::23). - connect (101: Сеть недоступна)
Ошб:3 http://archive.ubuntu.com/ubuntu focal-security InRelease                                     
  Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::24). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::23). - connect (101: Сеть недоступна)
Ошб:4 http://archive.ubuntu.com/ubuntu focal-backports InRelease                                    
  Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::24). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::23). - connect (101: Сеть недоступна)
Ошб:5 http://archive.canonical.com/ubuntu focal InRelease                                           
  Невозможно инициализировать соединение с archive.canonical.com:80 (2001:67c:1360:8c01::16). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с archive.canonical.com:80 (2001:67c:1360:8c01::1b). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с archive.canonical.com:80 (2001:67c:1562::1c). - connect (101: Сеть недоступна) Не удалось соединиться с archive.canonical.com:80 (91.189.92.150): время ожидания для соединения истекло Не удалось соединиться с archive.canonical.com:80 (91.189.91.15): время ожидания для соединения истекло Не удалось соединиться с archive.canonical.com:80 (91.189.92.191): время ожидания для соединения истекло
Ошб:6 http://dl.google.com/linux/chrome/deb stable InRelease                                        
  Невозможно инициализировать соединение с dl.google.com:80 (2a00:1450:4010:c05::be). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с dl.google.com:80 (2a00:1450:4010:c05::5b). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с dl.google.com:80 (2a00:1450:4010:c05::88). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с dl.google.com:80 (2a00:1450:4010:c05::5d). - connect (101: Сеть недоступна) Не удалось соединиться с dl.google.com:80 (64.233.162.136): время ожидания для соединения истекло Не удалось соединиться с dl.google.com:80 (64.233.162.93): время ожидания для соединения истекло Не удалось соединиться с dl.google.com:80 (64.233.162.91): время ожидания для соединения истекло Не удалось соединиться с dl.google.com:80 (64.233.162.190): время ожидания для соединения истекло
Чтение списков пакетов… Готово                                     
Построение дерева зависимостей       
Чтение информации о состоянии… Готово
Все пакеты имеют последние версии.
W: Не удалось получить http://archive.ubuntu.com/ubuntu/dists/focal/InRelease  Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::24). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::23). - connect (101: Сеть недоступна) Не удалось соединиться с archive.ubuntu.com:80 (91.189.88.152): время ожидания для соединения истекло Не удалось соединиться с archive.ubuntu.com:80 (91.189.88.142): время ожидания для соединения истекло
W: Не удалось получить http://archive.ubuntu.com/ubuntu/dists/focal-updates/InRelease  Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::24). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::23). - connect (101: Сеть недоступна)
W: Не удалось получить http://archive.ubuntu.com/ubuntu/dists/focal-security/InRelease  Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::24). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::23). - connect (101: Сеть недоступна)
W: Не удалось получить http://archive.ubuntu.com/ubuntu/dists/focal-backports/InRelease  Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::24). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с archive.ubuntu.com:80 (2001:67c:1360:8001::23). - connect (101: Сеть недоступна)
W: Не удалось получить http://archive.canonical.com/ubuntu/dists/focal/InRelease  Невозможно инициализировать соединение с archive.canonical.com:80 (2001:67c:1360:8c01::16). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с archive.canonical.com:80 (2001:67c:1360:8c01::1b). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с archive.canonical.com:80 (2001:67c:1562::1c). - connect (101: Сеть недоступна) Не удалось соединиться с archive.canonical.com:80 (91.189.92.150): время ожидания для соединения истекло Не удалось соединиться с archive.canonical.com:80 (91.189.91.15): время ожидания для соединения истекло Не удалось соединиться с archive.canonical.com:80 (91.189.92.191): время ожидания для соединения истекло
W: Не удалось получить http://dl.google.com/linux/chrome/deb/dists/stable/InRelease  Невозможно инициализировать соединение с dl.google.com:80 (2a00:1450:4010:c05::be). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с dl.google.com:80 (2a00:1450:4010:c05::5b). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с dl.google.com:80 (2a00:1450:4010:c05::88). - connect (101: Сеть недоступна) Невозможно инициализировать соединение с dl.google.com:80 (2a00:1450:4010:c05::5d). - connect (101: Сеть недоступна) Не удалось соединиться с dl.google.com:80 (64.233.162.136): время ожидания для соединения истекло Не удалось соединиться с dl.google.com:80 (64.233.162.93): время ожидания для соединения истекло Не удалось соединиться с dl.google.com:80 (64.233.162.91): время ожидания для соединения истекло Не удалось соединиться с dl.google.com:80 (64.233.162.190): время ожидания для соединения истекло
W: Некоторые индексные файлы скачать не удалось. Они были проигнорированы, или вместо них были использованы старые версии.

$ wget http://yandex.ru --2021-04-11 20:27:32-- http://yandex.ru/ Распознаётся yandex.ru (yandex.ru)… 77.88.55.50, 5.255.255.5, 5.255.255.50, ... Подключение к yandex.ru (yandex.ru)|77.88.55.50|:80... ошибка: Время ожидания соединения истекло. Подключение к yandex.ru (yandex.ru)|5.255.255.5|:80...

$ wget https://yandex.ru --2021-04-11 20:31:17-- https://yandex.ru/ Распознаётся yandex.ru (yandex.ru)… 77.88.55.55, 5.255.255.50, 5.255.255.5, ... Подключение к yandex.ru (yandex.ru)|77.88.55.55|:443... соединение установлено. HTTP-запрос отправлен. Ожидание ответа… 200 Ok Длина: нет данных [text/html] Сохранение в: «index.html.2»


index.html.2                  [  <=>                              ] 196,99K   697KB/s    за 0,3s    



  


                       
  




2021-04-11 20:31:18 (697 KB/s) - «index.html.2» сохранён [201717]

Т.е. запросы по http не проходят.
Сеть получаю по wifi

$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether c0:3e:ba:04:0b:ab brd ff:ff:ff:ff:ff:ff 3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 8c:c8:4b:21:65:33 brd ff:ff:ff:ff:ff:ff inet 192.168.0.4/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp2s0 valid_lft 12781sec preferred_lft 12781sec inet6 fe80::77ee:dff7:5054:6e2f/64 scope link noprefixroute valid_lft forever preferred_lft forever

$ iwconfig lo no wireless extensions.


enp1s0    no wireless extensions.
wlp2s0    IEEE 802.11  ESSID:"RT-5GPON-50B4"  
          Mode:Managed  Frequency:5.26 GHz  Access Point: 74:9D:79:6F:50:B4   
          Bit Rate=6 Mb/s   Tx-Power=30 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=70/70  Signal level=-30 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:137   Missed beacon:0

Подскажите в чем может быть проблема?

Ничего не происходит просто так…

c47

А как себя ведёт браузер: HTTPS сайты открываются, а HTTP нет? А с 2,4 гигигерцовой сети проблема наблюдается?
Тот же http://archive.ubuntu.com к примеру. И как ведут себя устройства, подключенные к этой же ТД (если не ошибаюсь — онушка от ростелекома?)

garmayev

А как себя ведёт браузер: HTTPS сайты открываются, а HTTP нет?

Именно так, сайты http — сервер не отвечает, https — нормально работают

И как ведут себя устройства, подключенные к этой же ТД (если не ошибаюсь — онушка от ростелекома?)

Да, Ростелеком.

Другие устртойства в сетиведут себя адекватно — т.е. штатно открывают и http, и https, поэтому я предполагаю, что это что-то у меня в бубунте

Ничего не происходит просто так…

c47

Ну тогда я даже не знаю, что предложить. Кроме одного: попробуйте подключить инет системк другим путём: хоть с телефона 3/4g раздать по usb или по wifi, чтобы уже точно исключить ТД из списка подозреваемых. Если и так не получится — «ну в этой ситуации мы просто наше это самое мы уже здесь наши полномочия всё, окончены»

garmayev

Мдяаа, вот совсем забыл, что сеть еще можно с помощью проводов проевти…

Через провод соединение идет нормально, что по https, что по http.

Делаю вывод, что виновник этой пор**графии — все-таки вафля.

Как по-вашему, в чем беда, я уже половину мозга высушил, вторая боится такой же участи, а третья половина думать вообще не хочет…

Ничего не происходит просто так…

c47

мне онушки с подозрениями на разные баги приносят регулярно (я о операторе одном работаю, мы gpon/gepon в т.ч. предоставляем).
Баги у них в основном хардовые: битые порты, окисленные платы, вздутые кондёры, искарёженные адаптеры или слетела прошивка. но подобных проблем даже не припомню.

Через провод соединение идет нормально, что по https, что по http.

надо сначала максимально сузить число подозреваемых — напишите как всё-таки инет получили?
с другого устройства
или к этой же онушке по eth подключили?

если по eth от ONU проблема есть — то виноват либо оператор, либо сама онушка, попросите рт сбросить её в дефолт, а то мало ли, я не знаю как у них где сети работают, может нет в вашем регионе acs-сервера, и придётся её настраивать самому потом

если по eth проблемы нет, то из списка подозреваемых уходит рт, но подтягивается wifi ноута либо 5ггц wifi онушки (файервол я практически исключаю, в свежеустановленной системе по дефолту всё открыто, но всё же гляньте правила, чем черт не шутит)

и попробуйте всё-таки подключиться к 2,4ггц диапазону этой же онушки и если проблемы в 2.4 не повторится, то попробовать другую 5ггц точку доступа найти и с неё проверить

garmayev

Подозреваемые:
1. Точка Доступа (aka Роутер)
2. Адаптер Wifi (На уровне железа)
3. Настройки Wifi (На программном уровне)
4. Файрволл
5. Драйвер Wifi

Расследование:
1.1. Роутер раздает 2 сети вайвай: 2.4G и 5G
1.2. Подключаю мобильник к ЛЮБОЙ сети — все сайты открываются
1.3. Подключил ноутбук к сети через провод к роутеру — все работает (и http, и https)

Отсюда: Подозреваемый «Роутер» из списка исключен

2. На уровне железа как может рубиться соединение ТОЛЬКО на 80 порт? Тут, как говориться, «Меня терзают смутные сомнения»

4. Файрвол

$ sudo ufw status verbose [sudo] пароль для garmayev: [s]Никто не знает мой пароль[/s] Состояние: неактивен
Отсюда: Подозреваемый «Файрвол» из списка исключен

5. Драйвер я переустановил (качнул с github по этой инструкции https://askubuntu.com/questions/994555/qualcomm-atheros-device-168c0042-rev-31-wi-fi-driver-installation)

Отсюда: Подозреваемый «Драйвер» из списка исключен

Итого, как я понимаю, у меня что-то с конфигами сети не так, а вот что и где — ХБЗ

P.S. Для модераторов — ХБЗ = Хто Бы Знал (не мат, на всякий случай)

Ничего не происходит просто так…

c47

garmayev

Интересно девки пляшут…

Такая шутка юмора:
1. Раздал вафлю с телефона (Сам телефон раздает интернет мобильного оператора)
2. Запросы пошли нормально

$ wget http://ya.ru --2021-04-12 12:33:46-- http://ya.ru/ Распознаётся ya.ru (ya.ru)… 87.250.250.242, 2a02:6b8::2:242 Подключение к ya.ru (ya.ru)|87.250.250.242|:80... соединение установлено. HTTP-запрос отправлен. Ожидание ответа… 302 Found Адрес: https://ya.ru/ [переход] --2021-04-12 12:33:48-- https://ya.ru/ Подключение к ya.ru (ya.ru)|87.250.250.242|:443... соединение установлено. HTTP-запрос отправлен. Ожидание ответа… 200 Ok Длина: 60000 (59K) [text/html] Сохранение в: «index.html»


index.html          100%[===================>]  58,59K  2,58KB/s    за 23s     
2021-04-12 12:34:17 (2,58 KB/s) - «index.html» сохранён [60000/60000]

Т.е. я рано вычеркнул Роутер из списка подозреваемых, но адаптер можно вычеркнуть?

Что за mtr? Что это такое и с чем его едят?

Пользователь добавил сообщение 12 Апреля 2021, 07:42:36:

Всё-таки попробуйте обозвать 2.4 и 5ггцовые вафли разными ssid-ами и подключиться именно к 2.4, разные чудеса бывают на белом свете))

В том-то и весь юмор — они УЖЕ обзываются по разному (2.4G обзывается RT-GPON-50B0, а 5G — RT-GPON50B4)
На обеих не работает http

Updated: Посмотрел что за зверь такой mtr. Могу приложить traceroute и ping:

$ traceroute archive.ubuntu.com traceroute to archive.ubuntu.com (91.189.88.142), 30 hops max, 60 byte packets 1 _gateway (192.168.0.1) 1.600 ms 1.659 ms 2.057 ms 2 ulnd-bras4.sib.ip.rostelecom.ru (213.228.116.207) 7.413 ms 7.533 ms 7.508 ms 3 xe-7-1-3.ulnd-rgr6.sib.ip.rostelecom.ru (213.228.114.24) 12.702 ms 13.030 ms 13.007 ms 4 ae40.stkm-cr4.intl.ip.rostelecom.ru (217.107.67.31) 105.605 ms 113.745 ms 109.109 ms 5 10gigabitethernet1-2.core1.sto1.he.net (194.68.123.187) 109.188 ms 104.910 ms 111.122 ms 6 100ge8-2.core1.ams1.he.net (184.105.65.125) 134.337 ms 119.778 ms 124.676 ms 7 100ge16-1.core1.lon2.he.net (72.52.92.213) 140.824 ms 137.546 ms 141.237 ms 8 100ge0-36.core1.lon7.he.net (184.104.196.6) 156.049 ms 156.178 ms 156.159 ms 9 canonical-group-limited.e0-53.switch1.lon7.he.net (184.104.203.50) 134.557 ms 130.284 ms 124.547 ms 10 aerodent.canonical.com (91.189.88.142) 121.111 ms 124.509 ms 128.489 ms

$ ping archive.ubuntu.com PING archive.ubuntu.com (91.189.88.142) 56(84) bytes of data. 64 bytes from aerodent.canonical.com (91.189.88.142): icmp_seq=1 ttl=56 time=223 ms 64 bytes from aerodent.canonical.com (91.189.88.142): icmp_seq=2 ttl=56 time=143 ms 64 bytes from aerodent.canonical.com (91.189.88.142): icmp_seq=3 ttl=56 time=167 ms 64 bytes from aerodent.canonical.com (91.189.88.142): icmp_seq=4 ttl=56 time=188 ms ^C --- archive.ubuntu.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 142.714/180.192/222.684/29.308 ms

« Последнее редактирование: 12 Апреля 2021, 07:58:31 от garmayev »

Ничего не происходит просто так…

c47

Т.е. я рано вычеркнул Роутер из списка подозреваемых, но адаптер можно вычеркнуть?

нет, возможно несовместимость знаков зодиака конкретных радиомодулей роутера и ноутбука, я слышал о таком где-то, не вспомню уже…
sudo apt install mtr-tiny ### консольная, удобная штука, не путать с гуёвым аналогом — mtr, в нём функционала 0 (или я дурак)
mtr-tiny — плод любви ping и traceroute, обладает основным функционалом мамы и папы, мне по работе он особо не нужен, но иногда пригождается, поэтому о его возможностях я сужу лишь по странице man, впечатляет

garmayev

Не могу залить скрин, в файл программулина не выплевывает, попробую описать словами…

нашел 10 узлов, Процент потерь (Loss) = 0% на всех узлах,

1. _gateway
2. ulnd-bras4.sib.ip.rostelecom.ru
3. xe-7-1-3.ulnd-rgr6.sib.ip.rostelecom.ru
4. ae23.stkm-cr4.intl.ip.rostelecom.ru
5. 10gigabitethernet1-3.core1.sto1.he.net
6. 100ge8-2.core1.ams.he.net
7. 100ge16-1.core1.lon2.he.net
8. 100ge0-36.core1.lon7.he.net
9. canonical-group-limited.e0-53.switch1.lon7.he.net
10. aerodent.canonical.com

Как-то так

Пользователь добавил сообщение 12 Апреля 2021, 08:16:15:

возможно несовместимость знаков зодиака конкретных радиомодулей роутера и ноутбука

На прошлой неделе интернет на этом ноутбуке работал полностью. Правда, это было под виндой (Не виноватый я, он — ноутбук — сам такой пришел). Сейчас решил перейти на знакомую бубну — а тут такой… «Большой пушистый северный зверь по имени Песец»

« Последнее редактирование: 12 Апреля 2021, 08:16:15 от garmayev »

Ничего не происходит просто так…

c47

нашел 10 узлов, Процент потерь (Loss) = 0% на всех узлах,

ага, значит до тех же ipv4 адресов связь по icmp есть, а по 80 порту нет? да, девки пляшут всё интереснее и выкрутаснее.
Можно чисто в качестве эксперимента накатить на ноут 10ку свеженькую, (если есть пара часов свободного времени) если и на ней проблема повторится — то звёзды так сошлись хардварная несовметимость, других вариантов у меня нет, а если на винде всё будет работать — то значит линуксовые дрова на конкретный радио-модуль всё-таки неайс

Пользователь добавил сообщение 12 Апреля 2021, 08:46:32:

wlp2s0 IEEE 802.11 ESSID:»RT-5GPON-50B4″
Mode:Managed Frequency:5.26 GHz Access Point: 74:9D:79:6F:50:B4
Bit Rate=6 Mb/s Tx-Power=30 dBm

хмм, только сейчас увидел странные цифры в графе скорость. на ноуте в диспетчере драйверов нет проприетарных? а то ссылочка на дрова аж к 14й убунте относится, много воды с тех пор утекло

« Последнее редактирование: 12 Апреля 2021, 08:46:32 от c47 »

AnrDaemon

sudo iptables-save

под спойлер.

Хотите получить помощь? Потрудитесь представить запрошенную информацию в полном объёме.

Прежде чем [Отправить], нажми [Просмотр] и прочти собственное сообщение. Сам-то понял, что написал?…

garmayev

а то ссылочка на дрова аж к 14й убунте относится

А где и как их видите? Видать, у меня глаза неправильные и не знают куда глядеть…

на ноуте в диспетчере драйверов нет проприетарных

livepatch пишет, что проприетарных дров нет.

Сейчас пришлось менять сервер реп (с помощью того же livepatch) на другой (https://nl.mirror.clouvider.net), но что-то мне скорость у них не нравится

sudo iptables-save

$ sudo iptables-save # Generated by iptables-save v1.8.4 on Mon Apr 12 14:23:31 2021 *mangle :PREROUTING ACCEPT [1046171:4390694792] :INPUT ACCEPT [1044695:4390359617] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [907809:2680049716] :POSTROUTING ACCEPT [908347:2680110450] -A POSTROUTING -o anbox0 -p udp -m udp --dport 68 -m comment --comment "managed by anbox-bridge" -j CHECKSUM --checksum-fill COMMIT # Completed on Mon Apr 12 14:23:31 2021 # Generated by iptables-save v1.8.4 on Mon Apr 12 14:23:31 2021 *nat :PREROUTING ACCEPT [2032:465054] :INPUT ACCEPT [578:132966] :OUTPUT ACCEPT [4911:1196615] :POSTROUTING ACCEPT [4736:1166158] -A POSTROUTING -s 192.168.250.0/24 ! -d 192.168.250.0/24 -m comment --comment "managed by anbox-bridge" -j MASQUERADE COMMIT # Completed on Mon Apr 12 14:23:31 2021 # Generated by iptables-save v1.8.4 on Mon Apr 12 14:23:31 2021 *filter :INPUT ACCEPT [1044695:4390359617] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [907809:2680049716] -A INPUT -i anbox0 -p tcp -m tcp --dport 53 -m comment --comment "managed by anbox-bridge" -j ACCEPT -A INPUT -i anbox0 -p udp -m udp --dport 53 -m comment --comment "managed by anbox-bridge" -j ACCEPT -A INPUT -i anbox0 -p tcp -m tcp --dport 67 -m comment --comment "managed by anbox-bridge" -j ACCEPT -A INPUT -i anbox0 -p udp -m udp --dport 67 -m comment --comment "managed by anbox-bridge" -j ACCEPT -A FORWARD -o anbox0 -m comment --comment "managed by anbox-bridge" -j ACCEPT -A FORWARD -i anbox0 -m comment --comment "managed by anbox-bridge" -j ACCEPT COMMIT # Completed on Mon Apr 12 14:23:31 2021
Не знаю, что это значат эти правила, но вот выхлоп iptables-save

Ничего не происходит просто так…

c47

А где и как их видите?

В тэгах автор указал 14.04, в шапке вкладки тоже отображается, а по тексту да, нигде не фигурирует какой дистрибутив или хотя бы ядро

managed by anbox-bridge

ай-яй-яй, «установил Ubuntu, файервол отключен», а слона и не заметил который файервол включил и посуду в нём побил)

Не силён в iptables, но вроде они у тебя сломали DNS, их перехватывает anbox, попробуй поменяй в source.list имена на ip — должно заработать, лучше дождусь ответа AnrDaemon

Печать

Страницы: [1] 2 Все Вверх

Forum
The Ubuntu Forum Community
Ubuntu Official Flavours Support
General Help
[all variants] mount error(101): Network is unreachable

mount error(101): Network is unreachable

I am running Lucid 64bit. I have noticed that when booting I get the following errors when mounting cifs volumes during the boot process.

from boot.log:

mount error(101): Network is unreachable
Refer to the mount.cifs( 8 ) manual page (e.g. man mount.cifs)
mount error(101): Network is unreachable
Refer to the mount.cifs( 8 ) manual page (e.g. man mount.cifs)
mount error(101): Network is unreachable
Refer to the mount.cifs( 8 ) manual page (e.g. man mount.cifs)
mountall: mount /media/misc [932] terminated with status 32
mountall: mount /media/music [933] terminated with status 32
mountall: mount /media/fs_files [934] terminated with status 32

they do mount but this error pauses the boot process for 10 or 15 seconds.

My assumption is that an attempt is made to mount the drives before the network is available.

Here’s my fstab:
Code:
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sdc1 during installation
UUID=db3b4a6c-b264-409b-ba1a-46e540ae3697 /               ext3    errors=remount-ro 0       1
# /home was on /dev/sda3 during installation
UUID=88c8ed0c-43ee-4849-8fe3-a5603815c4d7 /home           ext3    defaults        0       2
# swap was on /dev/sdc5 during installation
UUID=32fb0558-2896-4532-86a2-480e33f08596 none            swap    sw              0       0

//192.168.5.102/misc /media/misc  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
//192.168.5.102/music /media/music  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
//192.168.5.102/files /media/fs_files  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
Any idea how to resolve this?

Thanks

Re: mount error(101): Network is unreachable

Originally Posted by bowens44
I am running Lucid 64bit. I have noticed that when booting I get the following errors when mounting cifs volumes during the boot process.
…….
My assumption is that an attempt is made to mount the drives before the network is available.

Here’s my fstab:
Code:
# /etc/fstab: static file system information.
.........
//192.168.5.102/misc /media/misc  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
//192.168.5.102/music /media/music  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
//192.168.5.102/files /media/fs_files  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
Any idea how to resolve this?

Thanks
Use the _netdev option:
Code:
//192.168.5.102/misc /media/misc  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777,_netdev 0 0
//192.168.5.102/music /media/music  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777,_netdev 0 0
//192.168.5.102/files /media/fs_files  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777,_netdev 0 0

Re: mount error(101): Network is unreachable

Originally Posted by dcstar

Use the _netdev option:

Unfortunately, this made no difference

Last edited by bowens44; May 8th, 2010 at 01:26 PM.
Re: mount error(101): Network is unreachable

Worked for me. On my system, WICD is now started, the wireless connection is made, and the shares are mounted. Thank you for the help!

Re: mount error(101): Network is unreachable

I had this same problem after upgrading to Lucid and as I didn’t find a solution, I used the /etc/rc.local script as workaround:

Code:

#!/bin/sh 
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
mount -t cifs -o iocharset=utf8,user=myuser,password=mypwd,rw,uid=myuid,_netdev //server/share /mount/point

exit 0

Hope this helps

Re: mount error(101): Network is unreachable

Hi,

I’d Like to revive this thread.

I am getting the error described here even with the _netdev option under ubuntu 10.04

As renardeau said you can add these to the rc.local file which stops the error.

My issue is that one of my mounts in my case is used for configs for vairous applications like SABNZBD + Sickbeard and using the rc.local method means that I cant use these applications as services. However the error(101) causes issuses with these applications on boot, as the mount is not available when the services are starting.

Does anyone have any more suggestions? I am thinking of trying a different version.
Re: mount error(101): Network is unreachable

Ok so i have tried this on a few different versions now, 11.10 server and desktop. Both with the same issue. Its really strange.

For me it means that I have to directly mount a native drive in order to use it as a ‘Install disk’. Shame really

does anyone have any other ideas?

Bookmarks

Posting Permissions

Hi guys
Just been experimenting with OpenVPN for a small company network. I have been trying to establish a bridge connection so that users outside of the network can connect to machines in the network.

The OpenVPN server is a Linux machine with one NIC and my test client is a Windows 7 machine. I have been able to successfully establish a single connection directly to the server.

I have been following this http://openvpn.net/index.php/open-sourc … dging.html tutorial to create a bridge so I can connect to other machines on the network.

The IP of the server on the local network is 192.168.2.252, the networks DHCP server and internet gateway is 192.168.2.254.

When I try to connect the the OpenVPN server I eventually get this message repeatedly:
Tue Sep 13 16:40:37 2011 us=216236 212.183.128.38:6711 write UDPv4 []: Network is unreachable (code=101)

These are further details:

Code: Select all

Server Config
#########
port 1194

proto udp

ca   /home/rpettefar/openvpn-2.2.1/easy-rsa/2.0/keys/ca.crt
cert /home/rpettefar/openvpn-2.2.1/easy-rsa/2.0/keys/server.crt
key  /home/rpettefar/openvpn-2.2.1/easy-rsa/2.0/keys/server.key  # This file should be kept secret

dh /home/rpettefar/openvpn-2.2.1/easy-rsa/2.0/keys/dh1024.pem

ifconfig-pool-persist ipp.txt

server-bridge 192.168.2.252 255.255.255.0 192.168.2.180 192.168.2.199

client-to-client

keepalive 10 120

comp-lzo

user nobody
group nobody

persist-key
persist-tun

status openvpn-status.log

verb 3

Code: Select all

Client Config
########
client

dev tap0

proto udp

resolv-retry infinite

nobind

persist-key
persist-tun

ca ca.crt
cert client1.crt
key client1.key

comp-lzo

verb 3

Code: Select all

Console Log
########
Tue Sep 13 17:00:51 2011 OpenVPN 2.2.1 x86_64-unknown-linux-gnu [SSL] [LZO2] [EPOLL] [eurephia] built on Sep 13 2011
Tue Sep 13 17:00:51 2011 NOTE: when bridging your LAN adapter with the TAP adapter, note that the new bridge adapter will often take on its own IP address that is different from what the LAN adapter was previously set to
Tue Sep 13 17:00:51 2011 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Tue Sep 13 17:00:51 2011 Diffie-Hellman initialized with 1024 bit key
Tue Sep 13 17:00:51 2011 TLS-Auth MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
Tue Sep 13 17:00:51 2011 Socket Buffers: R=[122880->131072] S=[122880->131072]
Tue Sep 13 17:00:51 2011 TUN/TAP device tap0 opened
Tue Sep 13 17:00:51 2011 TUN/TAP TX queue length set to 100
Tue Sep 13 17:00:51 2011 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Tue Sep 13 17:00:51 2011 GID set to nobody
Tue Sep 13 17:00:51 2011 UID set to nobody
Tue Sep 13 17:00:51 2011 UDPv4 link local (bound): [undef]:1194
Tue Sep 13 17:00:51 2011 UDPv4 link remote: [undef]
Tue Sep 13 17:00:51 2011 MULTI: multi_init called, r=256 v=256
Tue Sep 13 17:00:51 2011 IFCONFIG POOL: base=192.168.2.180 size=20
Tue Sep 13 17:00:51 2011 IFCONFIG POOL LIST
Tue Sep 13 17:00:51 2011 Initialization Sequence Completed
Tue Sep 13 17:00:57 2011 MULTI: multi_create_instance called
Tue Sep 13 17:00:57 2011 212.183.128.38:31786 Re-using SSL/TLS context
Tue Sep 13 17:00:57 2011 212.183.128.38:31786 LZO compression initialized
Tue Sep 13 17:00:57 2011 212.183.128.38:31786 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
Tue Sep 13 17:00:57 2011 212.183.128.38:31786 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Tue Sep 13 17:00:57 2011 212.183.128.38:31786 Local Options hash (VER=V4): 'f7df56b8'
Tue Sep 13 17:00:57 2011 212.183.128.38:31786 Expected Remote Options hash (VER=V4): 'd79ca330'
Tue Sep 13 17:00:57 2011 212.183.128.38:31786 TLS: Initial packet from 212.183.128.38:31786, sid=4290dab5 ad0f1198
Tue Sep 13 17:00:57 2011 212.183.128.38:31786 write UDPv4 []: Network is unreachable (code=101)
Tue Sep 13 17:00:59 2011 212.183.128.38:31786 write UDPv4 []: Network is unreachable (code=101)
Tue Sep 13 17:00:59 2011 212.183.128.38:31786 write UDPv4 []: Network is unreachable (code=101)
Tue Sep 13 17:01:03 2011 212.183.128.38:31786 write UDPv4 []: Network is unreachable (code=101)
Tue Sep 13 17:01:03 2011 212.183.128.38:31786 write UDPv4 []: Network is unreachable (code=101)

I hope I have provided enough information.
Thanks for any help you can supply.

For some reason I have an error while running this code:

with smtplib.SMTP_SSL('smtp.yandex.com.tr', 465) as server:
    server.login(email_from, password_from)
    server.sendmail(
        from_addr='mymail@yandex.ru',
        to_addrs='yourmail@yandex.ru',
        msg='Hello'
    )

The error is:

Traceback (most recent call last):
  File "report.py", line 86, in <module>
    send_report()
  File "report.py", line 82, in send_report
    notificate(*create_html_msg())
  File "report.py", line 69, in notificate
    with smtplib.SMTP_SSL('smtp.yandex.com.tr', 465, context=context) as server:
  File "/usr/lib/python3.8/smtplib.py", line 1034, in __init__
    SMTP.__init__(self, host, port, local_hostname, timeout,
  File "/usr/lib/python3.8/smtplib.py", line 253, in __init__
    (code, msg) = self.connect(host, port)
  File "/usr/lib/python3.8/smtplib.py", line 339, in connect
    self.sock = self._get_socket(host, port, self.timeout)
  File "/usr/lib/python3.8/smtplib.py", line 1040, in _get_socket
    new_socket = socket.create_connection((host, port), timeout,
  File "/usr/lib/python3.8/socket.py", line 808, in create_connection
    raise err
  File "/usr/lib/python3.8/socket.py", line 796, in create_connection
    sock.connect(sa)
OSError: [Errno 101] Network is unreachable

OS is Ubuntu 20.04. My code runs perfectly on the other machine, so the problem is obviously somewhere with the machine.

I’ve tried:

sudo ufw allow 465/tcp

Also I installed and run postfix mail server and added this to /etc/postfix/main.cf:

smtps     inet  n       -       y       -       -       smtpd
  -o syslog_name=postfix/smtps
  -o smtpd_tls_wrappermode=yes
  -o smtpd_sasl_auth_enable=yes
  -o smtpd_recipient_restrictions=permit_mynetworks,permit_sasl_authenticated,reject
  -o content_filter=smtp-amavis:[127.0.0.1]:10026

and then restarted postfix with

sudo systemctl restart postfix

But nothing solved the problem. Please help me with this error.

Источник

The error mount error(101): Network is unreachable means that you attempted the mount before the network came up.

To fix this, add the _netdev option to your /etc/fstab CIFS entry. _netdev means to delay the mount until your network is connected.

Your /etc/fstab line should look like this:

//192.168.0.100/Volume_1 /mnt/vol1 credentials=/home/user/my-sys/.user,iocharset=utf8,file_mode=0775,dir_mode=0775,_netdev 0 0

To continue using /etc/rc.local for your mount, you’ll need to set up a new job (to prevent blocking) that loops until the network is up.

From this answer in Ask Ubuntu:

(
until ping -nq -c3 W.X.Y.Z; do
   # Waiting for network
   sleep 1
done
mount -t cifs -o credentials=/home/user/my-sys/.user,iocharset=utf8,file_mode=0775,dir_mode=0775 //192.168.0.100/Volume_1 /mnt/vol1
)&

Replace W.X.Y.Z with an IP address that responds to ICMP requests, like your router gateway.

Всем привет.
Есть проблема. В сети крутится samba сервер (192.168.0.251)
На пользовательской машине установлен Alt Linux 5.0 Ковчег. В файле fstab добавлена строка:
//192.168.0.251/pomoyka /mnt/file cifs credentials=/mnt/file2,rw,noperm,iocharset=utf8,forcemand 0 0

При загрузке компа, автоматически samba не монтируется. Вручную (mount /mnt/file) монтируется «на ура».
Network Manager service стартует до попытки монтирования. Параметр _netdev не помогает.

В Alt Linux 4.1.1 такой проблемы не было.
Хелп. Заранее благодарен за помощь!

« Последнее редактирование: 15.01.2010 21:56:18 от kwinto »

Записан

может в опции стоит добавить auto ?

Записан

Поищите на форуме — Skull уже отвечал на аналогичный вопрос. Там надо добавить специальную опцию. Какую — не помню.

Записан

Искал. Не нашёл.
Чтоб скучно сообществу не было, расскажу об ещё одном баге.
При монтировании samba’ы в Alt Linux’e 4.0 вышеуказанным способом и работе с документами по сети в Openoffice’e 2.4 всё работало прекрасно.
После обновления до Alt Linux 4.1.1 в OpenOffice’e 3.0 стали наблюдаться интересные глюки. Если я на samba’вой шаре, в примонтированной папке создаю в 3-м OO документ и сохраняю его, то потом он открывается только для чтения. Но если я создаю ссылку на рабочем столе на этот документ, всё нормально редактируется. В 2.x и в 3.1.1 OO всё работает без проблем.

« Последнее редактирование: 16.01.2010 00:20:20 от kwinto »

Записан

Разобрался.
В центре управления системой, в свойствах сетевого интерфейса вместо Network manager’а выбрал Etcnet. Всё заработало.

Записан

Forum
The Ubuntu Forum Community
Ubuntu Official Flavours Support
General Help
[all variants] mount error(101): Network is unreachable

I am running Lucid 64bit. I have noticed that when booting I get the following errors when mounting cifs volumes during the boot process.

from boot.log:

mount error(101): Network is unreachable
Refer to the mount.cifs( 8 ) manual page (e.g. man mount.cifs)
mount error(101): Network is unreachable
Refer to the mount.cifs( 8 ) manual page (e.g. man mount.cifs)
mount error(101): Network is unreachable
Refer to the mount.cifs( 8 ) manual page (e.g. man mount.cifs)
mountall: mount /media/misc [932] terminated with status 32
mountall: mount /media/music [933] terminated with status 32
mountall: mount /media/fs_files [934] terminated with status 32

they do mount but this error pauses the boot process for 10 or 15 seconds.

My assumption is that an attempt is made to mount the drives before the network is available.

Here’s my fstab:
Code:
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sdc1 during installation
UUID=db3b4a6c-b264-409b-ba1a-46e540ae3697 /               ext3    errors=remount-ro 0       1
# /home was on /dev/sda3 during installation
UUID=88c8ed0c-43ee-4849-8fe3-a5603815c4d7 /home           ext3    defaults        0       2
# swap was on /dev/sdc5 during installation
UUID=32fb0558-2896-4532-86a2-480e33f08596 none            swap    sw              0       0

//192.168.5.102/misc /media/misc  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
//192.168.5.102/music /media/music  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
//192.168.5.102/files /media/fs_files  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
Any idea how to resolve this?

Thanks

Re: mount error(101): Network is unreachable

Originally Posted by bowens44
I am running Lucid 64bit. I have noticed that when booting I get the following errors when mounting cifs volumes during the boot process.
…….
My assumption is that an attempt is made to mount the drives before the network is available.

Here’s my fstab:
Code:
# /etc/fstab: static file system information.
.........
//192.168.5.102/misc /media/misc  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
//192.168.5.102/music /media/music  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
//192.168.5.102/files /media/fs_files  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
Any idea how to resolve this?

Thanks
Use the _netdev option:
Code:
//192.168.5.102/misc /media/misc  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777,_netdev 0 0
//192.168.5.102/music /media/music  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777,_netdev 0 0
//192.168.5.102/files /media/fs_files  cifs  credentials=/root/.smbcredentials,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777,_netdev 0 0

Re: mount error(101): Network is unreachable

Originally Posted by dcstar

Use the _netdev option:

Unfortunately, this made no difference

Last edited by bowens44; May 8th, 2010 at 01:26 PM.
Re: mount error(101): Network is unreachable

Worked for me. On my system, WICD is now started, the wireless connection is made, and the shares are mounted. Thank you for the help!

Re: mount error(101): Network is unreachable

I had this same problem after upgrading to Lucid and as I didn’t find a solution, I used the /etc/rc.local script as workaround:

Code:

#!/bin/sh 
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
mount -t cifs -o iocharset=utf8,user=myuser,password=mypwd,rw,uid=myuid,_netdev //server/share /mount/point

exit 0

Hope this helps

Re: mount error(101): Network is unreachable

Hi,

I’d Like to revive this thread.

I am getting the error described here even with the _netdev option under ubuntu 10.04

As renardeau said you can add these to the rc.local file which stops the error.

My issue is that one of my mounts in my case is used for configs for vairous applications like SABNZBD + Sickbeard and using the rc.local method means that I cant use these applications as services. However the error(101) causes issuses with these applications on boot, as the mount is not available when the services are starting.

Does anyone have any more suggestions? I am thinking of trying a different version.
Re: mount error(101): Network is unreachable

Ok so i have tried this on a few different versions now, 11.10 server and desktop. Both with the same issue. Its really strange.

For me it means that I have to directly mount a native drive in order to use it as a ‘Install disk’. Shame really

does anyone have any other ideas?

Bookmarks

Posting Permissions

On a newish 18.04 system, I added a few SMB mounts to my fstab and verified they do mount, interactively.

When my system boots, it complains about CIFS mount errors, then tells me I am in emergency mode and proceeds to cloud-init (eventually obtaining an IP address, I think). If I bypass the emergency mount, I find my mounts to have been mounted no problem, probably after it obtained an IP)

Would love some advice as I’d like for this machine to boot unattended.

I have attached a screenshot and various excerpt of my journalctl -b
log that seem relevant.

Sep 15 20:46:47 watcher kernel: FS-Cache: Netfs 'cifs' registered for caching
Sep 15 20:46:47 watcher kernel: Key type cifs.spnego registered
Sep 15 20:46:47 watcher kernel: Key type cifs.idmap registered
Sep 15 20:46:47 watcher kernel: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
Sep 15 20:46:47 watcher mount[645]: mount error(101): Network is unreachable
Sep 15 20:46:47 watcher mount[645]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Sep 15 20:46:47 watcher kernel: CIFS VFS: Error connecting to socket. Aborting operation.
Sep 15 20:46:47 watcher kernel: CIFS VFS: cifs_mount failed w/return code = -101
Sep 15 20:46:47 watcher systemd[1]: mnt-downloads.mount: Mount process exited, code=exited status=32
Sep 15 20:46:47 watcher systemd[1]: mnt-downloads.mount: Failed with result 'exit-code'.
Sep 15 20:46:47 watcher systemd[1]: Failed to mount /mnt/downloads.
Sep 15 20:46:47 watcher systemd[1]: Dependency failed for Local File Systems.
...
Sep 15 20:46:53 watcher cloud-init[491]: Cloud-init v. 18.3-9-g2e62cb8a-0ubuntu1~18.04.2 running 'init-local' at Sat, 15 Sep 2018 20:46:53 +0000. Up 21.61 seconds.
Sep 15 20:46:53 watcher systemd[1]: Started Initial cloud-init job (pre-networking).
Sep 15 20:46:53 watcher systemd[1]: Reached target Network (Pre).
Sep 15 20:46:53 watcher systemd[1]: Starting Raise network interfaces...
Sep 15 20:46:53 watcher systemd[1]: Starting Network Service...
Sep 15 20:46:53 watcher systemd-networkd[910]: Enumeration completed
Sep 15 20:46:53 watcher systemd[1]: Started Network Service.
Sep 15 20:46:53 watcher systemd-networkd[910]: lo: Link is not managed by us
Sep 15 20:46:53 watcher systemd-networkd[910]: eno1: IPv6 successfully enabled
Sep 15 20:46:53 watcher systemd[1]: Starting Network Name Resolution...
Sep 15 20:46:53 watcher systemd[1]: Starting Wait for Network to be Configured...
Sep 15 20:46:53 watcher kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
...
Sep 15 20:46:53 watcher systemd[1]: Started Network Name Resolution.
Sep 15 20:46:53 watcher systemd[1]: Reached target Host and Network Name Lookups.
Sep 15 20:46:53 watcher systemd[1]: Started Raise network interfaces.
Sep 15 20:46:53 watcher systemd[1]: Reached target Network.
Sep 15 20:46:57 watcher systemd-networkd[910]: eno1: Gained carrier
Sep 15 20:46:57 watcher kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Sep 15 20:46:57 watcher kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
Sep 15 20:46:57 watcher systemd-networkd[910]: eno1: DHCPv4 address 192.168.7.229/24 via 192.168.7.1
Sep 15 20:46:57 watcher systemd-timesyncd[743]: Network configuration changed, trying to establish connection.
Sep 15 20:46:58 watcher systemd-networkd[910]: eno1: Gained IPv6LL
Sep 15 20:46:58 watcher systemd-networkd[910]: eno1: Configured
Sep 15 20:46:58 watcher systemd-timesyncd[743]: Network configuration changed, trying to establish connection.
Sep 15 20:46:58 watcher systemd-networkd-wait-online[942]: managing: eno1
Sep 15 20:46:58 watcher systemd-networkd-wait-online[942]: ignoring: lo
Sep 15 20:46:58 watcher systemd[1]: Started Wait for Network to be Configured.
Sep 15 20:46:58 watcher systemd[1]: Starting Initial cloud-init job (metadata service crawler)...
Sep 15 20:46:58 watcher cloud-init[1030]: Cloud-init v. 18.3-9-g2e62cb8a-0ubuntu1~18.04.2 running 'init' at Sat, 15 Sep 2018 20:46:58 +0000. Up 26.99 seconds.
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: +++++++++++++++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++++++++++++++
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: +--------+------+------------------------------+---------------+--------+-------------------+
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: | Device |  Up  |           Address            |      Mask     | Scope  |     Hw-Address    |
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: +--------+------+------------------------------+---------------+--------+-------------------+
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: |  eno1  | True |        192.168.7.229         | 255.255.255.0 | global | xx:xx:xx:xx:xx:c7 |
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: |  eno1  | True | fe80::5265:f3ff:fe1c:6dc7/64 |       .       |  link  | xx:xx:xx:xx:xx:c7 |
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: |   lo   | True |          127.0.0.1           |   255.0.0.0   |  host  |         .         |
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: |   lo   | True |           ::1/128            |       .       |  host  |         .         |
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: +--------+------+------------------------------+---------------+--------+-------------------+
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: ++++++++++++++++++++++++++++++Route IPv4 info++++++++++++++++++++++++++++++
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: +-------+-------------+-------------+-----------------+-----------+-------+
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: | Route | Destination |   Gateway   |     Genmask     | Interface | Flags |
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: +-------+-------------+-------------+-----------------+-----------+-------+
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: |   0   |   0.0.0.0   | 192.168.7.1 |     0.0.0.0     |    eno1   |   UG  |
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: |   1   | 192.168.7.0 |   0.0.0.0   |  255.255.255.0  |    eno1   |   U   |
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: |   2   | 192.168.7.1 |   0.0.0.0   | 255.255.255.255 |    eno1   |   UH  |
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: +-------+-------------+-------------+-----------------+-----------+-------+
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: +-------+-------------+---------+-----------+-------+
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: | Route | Destination | Gateway | Interface | Flags |
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: +-------+-------------+---------+-----------+-------+
Sep 15 20:46:58 watcher cloud-init[1030]: ci-info: |   1   |  fe80::/64  |    ::   |    eno1   |   U   |
Sep 15 20:46:59 watcher cloud-init[1030]: ci-info: |   3   |    local    |    ::   |    eno1   |   U   |
Sep 15 20:46:59 watcher cloud-init[1030]: ci-info: |   4   |   ff00::/8  |    ::   |    eno1   |   U   |
Sep 15 20:46:59 watcher cloud-init[1030]: ci-info: +-------+-------------+---------+-----------+-------+
Sep 15 20:46:59 watcher systemd[1]: Started Initial cloud-init job (metadata service crawler).
Sep 15 20:46:59 watcher systemd[1]: Reached target Cloud-config availability.
Sep 15 20:46:59 watcher systemd[1]: Reached target Network is Online.
Sep 15 20:46:59 watcher systemd[1]: Starting iSCSI initiator daemon (iscsid)...
Sep 15 20:46:59 watcher iscsid[1080]: iSCSI logger with pid=1083 started!
Sep 15 20:46:59 watcher systemd[1]: Started iSCSI initiator daemon (iscsid).
Sep 15 20:46:59 watcher systemd[1]: Starting Availability of block devices...
Sep 15 20:46:59 watcher systemd[1]: Reached target Remote File Systems (Pre).
Sep 15 20:46:59 watcher systemd[1]: Mounting /mnt/video...
Sep 15 20:46:59 watcher kernel: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
Sep 15 20:46:59 watcher systemd[1]: mnt-docker.mount: Directory /mnt/docker to mount over is not empty, mounting anyway.
Sep 15 20:46:59 watcher systemd[1]: Mounting /mnt/docker...
Sep 15 20:46:59 watcher systemd[1]: Mounting /mnt/Titan...
Sep 15 20:46:59 watcher systemd[1]: Started Availability of block devices.
Sep 15 20:46:59 watcher kernel: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
Sep 15 20:46:59 watcher kernel: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
Sep 15 20:46:59 watcher systemd[1]: Mounted /mnt/video.
Sep 15 20:46:59 watcher systemd[1]: Mounted /mnt/docker.
Sep 15 20:46:59 watcher systemd[1]: Mounted /mnt/Titan.
Sep 15 20:46:59 watcher systemd[1]: Reached target Remote File Systems.

Подскажите, кто знает, такую вещь.

Есть сервер в сети с samba, есть centos 7 рабочие станции, которые монтируют с него шары. Монтирование осуществляется посредством systemd, вот таким вот юнитом:

mnt-public.mount

[Unit]
Description=cifs mount script
Requires=network-online.target
After=network-online.service
[Mount]
What=//10.67.124.1/public
Where=/mnt/public
Options=username=nobody@r05,password=1,sec=ntlm,noperm
Type=cifs
[Install]
WantedBy=multi-user.target

И всё это успешно работает, практически на всех станциях, но есть несколько «фирменных» машин HP, с которыми это не катит,
типа на момент выполнения монтирования — сети нет!

Dec  4 09:07:08 yar03 NetworkManager[886]: <info>  [1575439628.3699] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-eno1 (724c5388-edce-48ca-a1bb-a55e5b50d61f,"eno1")
Dec  4 09:07:08 yar03 dbus[877]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Dec  4 09:07:08 yar03 dbus-daemon[877]: dbus[877]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Dec  4 09:07:08 yar03 systemd[1]: Starting Hostname Service...
Dec  4 09:07:09 yar03 dbus[877]: [system] Successfully activated service 'org.freedesktop.hostname1'
Dec  4 09:07:09 yar03 dbus-daemon[877]: dbus[877]: [system] Successfully activated service 'org.freedesktop.hostname1'
Dec  4 09:07:09 yar03 systemd[1]: Started Hostname Service.
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.2345] settings: hostname: using hostnamed
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.2346] settings: hostname changed from (none) to "yar03"
Dec  4 09:07:09 yar03 nm-dispatcher[986]: req:1 'hostname': new request (5 scripts)
Dec  4 09:07:09 yar03 nm-dispatcher[986]: req:1 'hostname': start running ordered scripts...
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.5349] dhcp-init: Using DHCP client 'dhclient'
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.5350] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.5351] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.5351] manager: Networking is enabled by state file
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.5408] Loaded device plugin: NMBondDeviceFactory (internal)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.5408] Loaded device plugin: NMBridgeDeviceFactory (internal)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.5409] Loaded device plugin: NMDummyDeviceFactory (internal)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.5409] Loaded device plugin: NMEthernetDeviceFactory (internal)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.5409] Loaded device plugin: NMInfinibandDeviceFactory (internal)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.5410] Loaded device plugin: NMIPTunnelDeviceFactory (internal)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.5411] Loaded device plugin: NMMacsecDeviceFactory (internal)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.5411] Loaded device plugin: NMMacvlanDeviceFactory (internal)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.6952] Loaded device plugin: NMTunDeviceFactory (internal)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.6953] Loaded device plugin: NMVethDeviceFactory (internal)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.6953] Loaded device plugin: NMVlanDeviceFactory (internal)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.6954] Loaded device plugin: NMVxlanDeviceFactory (internal)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.8842] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wifi.so)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.8996] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/libnm-device-plugin-team.so)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.9289] device (lo): link connected
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.9299] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.9318] manager: (eno1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Dec  4 09:07:09 yar03 NetworkManager[886]: <info>  [1575439629.9334] device (eno1): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Dec  4 09:07:09 yar03 kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
Dec  4 09:07:10 yar03 kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
Dec  4 09:07:15 yar03 NetworkManager[886]: <info>  [1575439635.2754] manager: startup complete
Dec  4 09:07:15 yar03 systemd[1]: Started Network Manager Wait Online.
Dec  4 09:07:15 yar03 systemd[1]: Starting LSB: Bring up/down networking...
Dec  4 09:07:15 yar03 sssd[be[default]][954]: Backend is offline
Dec  4 09:07:15 yar03 network[1016]: Активируется интерфейс loopback:  [  OK  ]
Dec  4 09:07:15 yar03 NetworkManager[886]: <info>  [1575439635.6892] audit: op="connection-activate" uuid="724c5388-edce-48ca-a1bb-a55e5b50d61f" name="eno1" result="fail" reason="No suitable device found for this connection."
Dec  4 09:07:15 yar03 network[1016]: Активируется интерфейс eno1:  Ошибка: сбой активации соединения: No suitable device found for this connection.
Dec  4 09:07:15 yar03 network[1016]: [СБОЙ ]
Dec  4 09:07:15 yar03 systemd[1]: network.service: control process exited, code=exited status=1
Dec  4 09:07:15 yar03 systemd[1]: Failed to start LSB: Bring up/down networking.
Dec  4 09:07:15 yar03 systemd[1]: Unit network.service entered failed state.
Dec  4 09:07:15 yar03 systemd[1]: network.service failed.
Dec  4 09:07:15 yar03 systemd[1]: Reached target Network.

Типа нет устройства/сетевухи — eno1, соответственно шары не подключаются, хотя в юните же вроде прописано » After=network-online.service».

Dec  4 09:07:16 yar03 mount[1210]: mount error(101): Network is unreachable
Dec  4 09:07:16 yar03 mount[1210]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Dec  4 09:07:16 yar03 kernel: CIFS VFS: Error connecting to socket. Aborting operation.
Dec  4 09:07:16 yar03 kernel: CIFS VFS: cifs_mount failed w/return code = -101
Dec  4 09:07:16 yar03 mount[1202]: mount error(101): Network is unreachable
Dec  4 09:07:16 yar03 systemd[1]: mnt-public.mount mount process exited, code=exited status=32
Dec  4 09:07:16 yar03 systemd[1]: Failed to mount cifs mount script.
Dec  4 09:07:16 yar03 systemd[1]: Unit mnt-public.mount entered failed state.
Dec  4 09:07:16 yar03 systemd[1]: Started GNOME Display Manager.
...

Потом уже после загрузки «Гуя» нетворк-менеджер видит сетевуху и получает на неё дарес по dhcp, но юнит монтирования уже не запускается повторно..

Dec  4 09:07:30 yar03 NetworkManager[886]: <info>  [1575439650.5204] device (eno1): link connected
Dec  4 09:07:30 yar03 kernel: e1000e: eno1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
Dec  4 09:07:30 yar03 kernel: e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO
Dec  4 09:07:30 yar03 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
Dec  4 09:07:30 yar03 NetworkManager[886]: <info>  [1575439650.5210] device (eno1): state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Dec  4 09:07:30 yar03 NetworkManager[886]: <info>  [1575439650.5224] policy: auto-activating connection 'eno1'
Dec  4 09:07:30 yar03 NetworkManager[886]: <info>  [1575439650.5320] device (eno1): Activation: starting connection 'eno1' (724c5388-edce-48ca-a1bb-a55e5b50d61f)
Dec  4 09:07:30 yar03 NetworkManager[886]: <info>  [1575439650.5348] device (eno1): state change: disconnected -> prepare (reason 'none') [30 40 0]
Dec  4 09:07:30 yar03 NetworkManager[886]: <info>  [1575439650.5364] manager: NetworkManager state is now CONNECTING
Dec  4 09:07:30 yar03 NetworkManager[886]: <info>  [1575439650.5374] device (eno1): state change: prepare -> config (reason 'none') [40 50 0]
Dec  4 09:07:30 yar03 NetworkManager[886]: <info>  [1575439650.5419] device (eno1): state change: config -> ip-config (reason 'none') [50 70 0]
Dec  4 09:07:30 yar03 NetworkManager[886]: <info>  [1575439650.5428] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Dec  4 09:07:30 yar03 NetworkManager[886]: <info>  [1575439650.5903] dhcp4 (eno1): dhclient started with pid 4123
Dec  4 09:07:30 yar03 dhclient[4123]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 5 (xid=0x1f1867b8)
Dec  4 09:07:31 yar03 dhclient[4123]: DHCPREQUEST on eno1 to 255.255.255.255 port 67 (xid=0x1f1867b8)
Dec  4 09:07:31 yar03 dhclient[4123]: DHCPOFFER from 10.67.125.129
Dec  4 09:07:31 yar03 dhclient[4123]: DHCPACK from 10.67.125.129 (xid=0x1f1867b8)
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.8049] dhcp4 (eno1):   address 10.67.125.221
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.8050] dhcp4 (eno1):   plen 25 (255.255.255.128)
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.8050] dhcp4 (eno1):   gateway 10.67.125.129
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.8050] dhcp4 (eno1):   lease time 6000
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.8051] dhcp4 (eno1):   nameserver '10.67.12.134'
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.8051] dhcp4 (eno1):   nameserver '10.67.4.18'
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.8051] dhcp4 (eno1):   domain name 'r05.ru'
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.8051] dhcp4 (eno1): state changed unknown -> bound
Dec  4 09:07:31 yar03 avahi-daemon[874]: Joining mDNS multicast group on interface eno1.IPv4 with address 10.67.125.221.
Dec  4 09:07:31 yar03 avahi-daemon[874]: New relevant interface eno1.IPv4 for mDNS.
Dec  4 09:07:31 yar03 avahi-daemon[874]: Registering new address record for 10.67.125.221 on eno1.IPv4.
Dec  4 09:07:31 yar03 dhclient[4123]: bound to 10.67.125.221 -- renewal in 2770 seconds.
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.8087] device (eno1): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.8102] device (eno1): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.8119] device (eno1): state change: secondaries -> activated (reason 'none') [90 100 0]
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.8122] manager: NetworkManager state is now CONNECTED_LOCAL
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.8633] manager: NetworkManager state is now CONNECTED_SITE
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.8635] policy: set 'eno1' (eno1) as default for IPv4 routing and DNS
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.9390] device (eno1): Activation: successful, device activated.
Dec  4 09:07:31 yar03 dbus-daemon[877]: dbus[877]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Dec  4 09:07:31 yar03 dbus[877]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Dec  4 09:07:31 yar03 systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec  4 09:07:31 yar03 NetworkManager[886]: <info>  [1575439651.9482] manager: NetworkManager state is now CONNECTED_GLOBAL
Dec  4 09:07:31 yar03 dbus-daemon[877]: dbus[877]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec  4 09:07:31 yar03 dbus[877]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec  4 09:07:31 yar03 nm-dispatcher[4135]: req:1 'up' [eno1]: new request (5 scripts)
Dec  4 09:07:31 yar03 nm-dispatcher[4135]: req:1 'up' [eno1]: start running ordered scripts...
Dec  4 09:07:31 yar03 nm-dispatcher[4135]: req:2 'connectivity-change': new request (5 scripts)
Dec  4 09:07:31 yar03 systemd[1]: Started Network Manager Script Dispatcher Service.
Dec  4 09:07:31 yar03 systemd[1]: Unit iscsi.service cannot be reloaded because it is inactive.
Dec  4 09:07:32 yar03 nm-dispatcher[4135]: req:2 'connectivity-change': start running ordered scripts...

Собственно вопрос, как победить данную проблему? На не HP станциях в этой же сети с аналогичной версией ОС и настройкой — всё ОК.
И попутно вопросик, можно ли решить проблему перемонтирования шары при пропадании «сети» в рамках юнита монтирования? Т.е. комутатор выключили-включили, всё, шара отвалилась и пока не перезагрузишься, повторно она не перемонтируется при «возобновлении» физического линка.

Index
» Applications & Desktop Environments
» [SOLVED] — Cannot automount Samba share from fstab

#1 2012-09-30 12:12:38

kaipee: Member; From: Belfast, UK; Registered: 2012-07-07; Posts: 214

[SOLVED] — Cannot automount Samba share from fstab

Hi guys, I successfully got Samba working on my home serv last night but for some reason I cannot seem to automount the share at boot time (native systemd)

/etc/fstab

# kphmsrv /mnt/Files  Samba
//kphmsrv/Files /mnt/Files cifs users,username=kaipee,password={mypassword},workgroup=WORKGROUP,ip=192.168.0.10 0 0

errors.log

Sep 30 14:03:02 zoostorm-arch kernel: [    8.721292] CIFS VFS: Error connecting to socket. Aborting operation
Sep 30 14:03:02 zoostorm-arch kernel: [    8.721956] CIFS VFS: cifs_mount failed w/return code = -101

I thought systemd wouldn’t attempt mounting until network was up?

I have removed both noauto (as I did want to automount at boot) and noatime (as I read that it causes issues when mounting at boot)

Linux zoostorm-arch 3.5.4-1-ARCH #1 SMP PREEMPT Sat Sep 15 08:12:04 CEST 2012 x86_64 GNU/Linux

Last edited by kaipee (2012-10-02 18:04:25)

#2 2012-09-30 12:15:16

kaipee: Member; From: Belfast, UK; Registered: 2012-07-07; Posts: 214

Re: [SOLVED] — Cannot automount Samba share from fstab

Once logged in, however, I can successfully mount the share with

with any user

#3 2012-09-30 12:36:45

elp: Member; Registered: 2007-04-10; Posts: 27

Re: [SOLVED] — Cannot automount Samba share from fstab

My look something like this:

//192.168.0.2/big_drive /media/ArchSamba cifs auto,owner,rw,username=magnus,password=*****blabla 0 0

#4 2012-09-30 14:41:34

kaipee: Member; From: Belfast, UK; Registered: 2012-07-07; Posts: 214

Re: [SOLVED] — Cannot automount Samba share from fstab

OK so I think I have narrowed it down to the network not being connected.

My current /etc/fstab

# kphmsrv /mnt/Files  Samba
//kphmsrv/Files /mnt/Files cifs _netdev,users,username=kaipee,password={mypassword},workgroup=WORKGROUP,ip=192.168.0.10 0 0

Booting shows failed for a dependency.
Error log shows:

Sep 30 15:22:28 zoostorm-arch kernel: [ 1023.268131] CIFS VFS: default security mechanism requested.  The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.3
Sep 30 16:24:39 zoostorm-arch kernel: [   10.125967] CIFS VFS: Error connecting to socket. Aborting operation
Sep 30 16:24:39 zoostorm-arch kernel: [   10.126602] CIFS VFS: cifs_mount failed w/return code = -101

Upon login I can mount the share, however if I disable my wireless connection and try to mount I get:

[kaipee@zoostorm-arch ~]$ mount /mnt/Files
mount error(101): Network is unreachable
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

…and the same error occurs:

Sep 30 15:33:04 zoostorm-arch kernel: [  515.431106] CIFS VFS: default security mechanism requested.  The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.3
Sep 30 15:33:33 zoostorm-arch kernel: [  544.010324] CIFS VFS: Error connecting to socket. Aborting operation
Sep 30 15:33:33 zoostorm-arch kernel: [  544.010406] CIFS VFS: cifs_mount failed w/return code = -10

So it does indeed look like it won’t mount at boot because of no network connection — however I have included the _netdev option and I am using systemd which is supposed to not attempt mounting until network is available ??

Last edited by kaipee (2012-09-30 14:42:46)

#5 2012-09-30 15:23:58

kaipee: Member; From: Belfast, UK; Registered: 2012-07-07; Posts: 214

Re: [SOLVED] — Cannot automount Samba share from fstab

I just don’t get what is happening here. I have updated my /etc/fstab to read:

//192.168.0.10/Files /mnt/Files cifs x-systemd.device-timeout=60s,users,username=kaipee,password={mypassword},workgroup=WORKGROUP,ip=192.168.0.10 0 0

…forcing systemd to wait for at least 60 seconds to mount the share. My machine boots and logs in with a working connection in about 15 seconds after initial loading.

https://lh4.googleusercontent.com/-DOTi … 0409_6.jpg

Yet it still complains that the network is not available and is clearly ignoring the options about timeout and _netdev ??!

[kaipee@zoostorm-arch ~]$ systemctl status mnt-Files.mount
mnt-Files.mount - /mnt/Files
Loaded: loaded (/etc/fstab)
Active: failed (Result: exit-code) since Sun, 30 Sep 2012 17:06:44 +0100
Where: /mnt/Files
What: //192.168.0.10/Files
Process: 385 ExecMount=/bin/mount //192.168.0.10/Files /mnt/Files -t cifs -o x-systemd.device-timeout=60s,users,username=kaipee,password=P@ss,workgroup=WORKGROUP,ip=192.168.0.10 (code=exited, status=32)
CGroup: name=systemd:/system/mnt-Files.mount
Sep 30 17:06:44 zoostorm-arch mount[385]: mount error(101): Network is unreachable
Sep 30 17:06:44 zoostorm-arch mount[385]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Sep 30 17:06:44 zoostorm-arch systemd[1]: Failed to mount /mnt/Files.

Moderator edit: The image is too big. Reduced to url.

Last edited by bernarcher (2012-09-30 15:29:43)

#6 2012-09-30 16:01:49

falconindy: Developer; From: New York, USA; Registered: 2009-10-22; Posts: 4,111; Website

Re: [SOLVED] — Cannot automount Samba share from fstab

_netdev only works if you have proper activation of network.target. How are you establishing a network connection?

Alternatively, just use an automounter on the share and let it be mounted on first access — add noauto,x-systemd.automount to the options.

#7 2012-09-30 18:11:13

kaipee: Member; From: Belfast, UK; Registered: 2012-07-07; Posts: 214

Re: [SOLVED] — Cannot automount Samba share from fstab

Hi falconindy,

I’m connecting to a wireless network with WPA2 (WUSBN v2) using the NetworkManager service. How do I configure/check this network.target?

#8 2012-09-30 18:48:01

falconindy: Developer; From: New York, USA; Registered: 2009-10-22; Posts: 4,111; Website

Re: [SOLVED] — Cannot automount Samba share from fstab

NetworkManager-wait-online.service should activate network.target. You’re still better off using an automount unit.

#9 2012-09-30 22:12:56

kaipee: Member; From: Belfast, UK; Registered: 2012-07-07; Posts: 214

Re: [SOLVED] — Cannot automount Samba share from fstab

How does the automount unit work?
I have a few applications and services that use the samba share/mount so kind of want it always mounted.

#10 2012-09-30 23:20:56

falconindy: Developer; From: New York, USA; Registered: 2009-10-22; Posts: 4,111; Website

Re: [SOLVED] — Cannot automount Samba share from fstab

Automount means its… mounted automatically on first access.

#11 2012-10-01 12:26:45

kaipee: Member; From: Belfast, UK; Registered: 2012-07-07; Posts: 214

Re: [SOLVED] — Cannot automount Samba share from fstab

I was leaning more towards are there any benefits of this over mounting at boot?
Is it configured for every user automatically? Is it mounted by user or root?

Why is an automount unit better than automatically mounting during boot?

#12 2012-10-01 17:22:30

falconindy: Developer; From: New York, USA; Registered: 2009-10-22; Posts: 4,111; Website

Re: [SOLVED] — Cannot automount Samba share from fstab

kaipee wrote:

I was leaning more towards are there any benefits of this over mounting at boot?

Sure. You don’t have to worry about when the network comes up.

kaipee wrote:

Is it configured for every user automatically? Is it mounted by user or root?

It’s mounted by root according to the options in fstab. It’s exactly the same as if you were insisting it mount on boot.

kaipee wrote:

Why is an automount unit better than automatically mounting during boot?

Boot won’t explicitly hang waiting for this to mount — only for the automount to be initialized on the mountpoint.

#13 2012-10-01 19:55:43

kaipee: Member; From: Belfast, UK; Registered: 2012-07-07; Posts: 214

Re: [SOLVED] — Cannot automount Samba share from fstab

But I kind of want boot to hang — at least until the network comes up and continues to mount the share

#14 2012-10-01 19:59:40

kaipee: Member; From: Belfast, UK; Registered: 2012-07-07; Posts: 214

Re: [SOLVED] — Cannot automount Samba share from fstab

…does the automount launch a ‘daemon’ of sorts, running in the background and waiting for a working network connection before initializing the mount? Allowing the rest of the system to function normally, and mounting the share as soon as a valid connection is confirmed?

#15 2012-10-01 20:59:22

falconindy: Developer; From: New York, USA; Registered: 2009-10-22; Posts: 4,111; Website

Re: [SOLVED] — Cannot automount Samba share from fstab

Again, it mounts on first access by you (or will just fail if the endpoint is unreachable). I suggest trying this and seeing how it works before asking the same question again.

#16 2012-10-02 18:04:00

kaipee: Member; From: Belfast, UK; Registered: 2012-07-07; Posts: 214

Re: [SOLVED] — Cannot automount Samba share from fstab

Working /etc/fstab entry:

//192.168.0.10/Files /mnt/Files cifs auto,x-systemd.automount,cache=none,rsize=130048,wsize=57344,users,username=kaipee,password={mypassword},workgroup=WORKGROUP,ip=192.168.0.10 0 0

Last edited by kaipee (2012-10-02 18:04:10)

#17 2012-10-03 22:00:22

madchine: Member; From: Denmark; Registered: 2009-11-04; Posts: 62; Website

Re: [SOLVED] — Cannot automount Samba share from fstab

I gotta admit I was dead set against the automount solution when I read the suggestion but it works beautifully. Hardly any lag at all on first time access and no hanging issues (so far). Thanks, falconindy.

EDIT: Spoke too soon. This thread is marked solved, so I won’t bring up my issues here. Started a new thread instead. Apologies for the mess.

Last edited by madchine (2012-10-03 22:33:59)

#19 2018-01-07 15:19:54

ninovanhooff: Member; Registered: 2018-01-07; Posts: 1

Re: [SOLVED] — Cannot automount Samba share from fstab

Just passing by to mention that the entry that turned out to work for @kaipee contains auto, non noauto as @falconindy suggested. And indeed, this works for me too.

1 made 2 edits to my own existing lines:
remove _netdev
replace noauto by auto

Doesn’t make too much sense to me, but it works

#20 2018-01-07 15:40:17

ewaller: Administrator; From: Pasadena, CA; Registered: 2009-07-13; Posts: 19,142

Re: [SOLVED] — Cannot automount Samba share from fstab

ninovanhooff,

Welcome to the Arch Linux Forums. You opened with a fairly good post that is on topic, but do keep an eye on the age of the threads; this one is five years old.
https://wiki.archlinux.org/index.php/Co … bumping.22

Using this opportunity to close this old thread.

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

Всем доброго дня!
Прошу прощения за вопрос который неоднократно поднимался на форуме.
Много всего прочитал по этому вопросу, но для себя не нашел ответов.

Есть задача:
необходимо при загрузке сервера монтировать общедоступную виндовую папку, для ежедневного копирования в нее бекапов;

Eсть сервер: OC Linux Ubuntu-Server 10.04.4 LTS

Правлю файл /etc/fstab таким образом:

——————————————————————————————————
# /etc/fstab: static file system information.
#
# Use ‘blkid -o value -s UUID’ to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=cc7368b0-bafb-4455-858f-3cb21e050d9a / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=3d2ca314-d9ed-4882-8454-61de290f818a none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

//172.2.0.151/Mail$ /mnt/mail_bac cifs defaults,_netdev,iocharset=utf8,user=*******,
pass=*******,dom=my.domain.local 1 1
———————————————————————————————————

Сетевая папка монтируется при загрузке системы, но при этом в boot.log записывается ошибка:
———————————————————————————————————
fsck from util-linux-ng 2.17.2
/dev/sda1: clean, 53727/1253376 files, 416534/5012992 blocks

* Starting AppArmor profiles [80G mount error(101): Network is unreachable

Refer to the mount.cifs( manual page (e.g. man mount.cifs)
mountall: mount /mnt/mail_bac [632] terminated with status 32

[74G[ OK ]
Starting openfire: openfire.
——————————————————————————————————

Помогите разобраться, в чем дело??? Как исправить и в чем ошибка тут???

View previous topic :: View next topic

Author

Message

lekto
Tux’s lil’ helper

Joined: 20 Sep 2014
Posts: 134
Location: Ancient Rome

Posted: Tue Jan 02, 2018 8:18 pm Post subject: [SOLVED] Samba, error(101): Network is unreachable

Hi, I have issue with auto mounting samba shares. Shares aren’t mounted on boot, but I can mount them manually by run «mount -a». It’s possible that openrc try to mount shares before connecting to network?

/etc/fstab

Code:

//dedyk/transmission /media/lekto/transmission cifs vers=3.0,credentials=/root/.credentials 0 0

//dedyk/backup /media/lekto/backup cifs vers=3.0,credentials=/root/.credentials 0 0

/var/log/rc.log

Code:

* Mounting network filesystems …

mount error(101): Network is unreachable

Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

mount error(101): Network is unreachable

Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

* Could not mount all network filesystems

dmesg

Code:

[ 30.887392] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

[ 30.986346] CIFS VFS: Error connecting to socket. Aborting operation.

[ 30.986349] CIFS VFS: cifs_mount failed w/return code = -101

[ 30.988093] CIFS VFS: Error connecting to socket. Aborting operation.

[ 30.988095] CIFS VFS: cifs_mount failed w/return code = -101

(…)

[ 33.854946] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Last edited by lekto on Mon Jan 08, 2018 8:25 pm; edited 1 time in total

Ant P.
Watchman

Joined: 18 Apr 2009
Posts: 6920

Posted: Tue Jan 02, 2018 9:19 pm Post subject:

See the comments in /etc/conf.d/netmount and configure it appropriately.

Hu
Moderator

Joined: 06 Mar 2007
Posts: 20017

Posted: Wed Jan 03, 2018 12:15 am Post subject:

Those shares are (attempted to) mount on boot, which is your problem. You did not mark them as _netdev, so localmount attempts to mount them, which fails because localmount runs before the network is started. You should mark them as _netdev to prevent mounting them before the network starts. You may also need to follow Ant P.’s instructions to get them to mount once network is available.

lekto
Tux’s lil’ helper

Joined: 20 Sep 2014
Posts: 134
Location: Ancient Rome

Posted: Mon Jan 08, 2018 8:25 pm Post subject:

I edited netmount and added _netdev, but it sometimes worked and sometimes not. Then I haved realized I forgot to run net.eth0 and after fix it samba shares work well.

lekto
Tux’s lil’ helper

Joined: 20 Sep 2014
Posts: 134
Location: Ancient Rome

Posted: Thu Jan 21, 2021 2:47 pm Post subject:

I’m writing here because this doesn’t work anymore for me after switching network management to dhcpcd [1]. I had problem with dhcpcd that it was taking too long to get network configuration, which was delaying start of xdm. Now there is no delay during boot, but network starts working few seconds after start of xfce and samba shares are not mounted.

I got this in dmesg:

Code:

[ 22.517890] CIFS: Attempting to mount //dedyk/transmission

[ 22.517920] CIFS: VFS: Error connecting to socket. Aborting operation.

[ 22.517922] CIFS: VFS: cifs_mount failed w/return code = -101

[ 22.518849] CIFS: Attempting to mount //dedyk/backup

[ 22.518879] CIFS: VFS: Error connecting to socket. Aborting operation.

[ 22.518880] CIFS: VFS: cifs_mount failed w/return code = -101

[ 25.517359] igb 0000:05:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

/etc/conf.d/netmount:

Code:

rc_need=»dhcpcd»

/etc/fstab:

Code:

//dedyk/transmission /media/lekto/transmission cifs vers=3.0,_netdev,credentials=/root/.credentials 0 0

//dedyk/backup /media/lekto/backup cifs vers=3.0,_netdev,credentials=/root/.credentials 0 0

[1] https://wiki.gentoo.org/wiki/Network_management_using_DHCPCD

lekto
Tux’s lil’ helper

Joined: 20 Sep 2014
Posts: 134
Location: Ancient Rome

Posted: Thu Jan 28, 2021 6:07 pm Post subject:

Ok, I kludged it, in /etc/init.d/netmount I added in depend():

Code:

after xdm

and in start():

Code:

ebegin «Waiting for network connection»

for i in `seq 30`; do

echo -n «.»

sleep 1

ping -c1 192.168.0.1 &>> /dev/null

if [ «$?» == «0» ]; then

ebegin «Network seems to work»

break

done

lekto
Tux’s lil’ helper

Joined: 20 Sep 2014
Posts: 134
Location: Ancient Rome

Posted: Mon Jun 21, 2021 1:02 pm Post subject:

Well, sometime after my last post that method stopped working. Recently I came up with this:

Code:

#!/bin/sh

function loop {

local program_name=»delayed-mounter»

for i in $(awk ‘/cifs/ {print $2}’ /etc/fstab); do

echo $program_name: trying to mount $i > /dev/kmsg

while [ -z «$(mount | grep $i)» ]; do

mount $i

sleep 5

done

echo $program_name: $i is mounted, continue > /dev/kmsg

done

echo $program_name: everything was mounted, exiting > /dev/kmsg

}

loop&

To use it put it in /etc/local.d/delayed-mounter.start, give it execute permission and add local to default runlevel. This script is looking for line with cifs in /etc/fstab in second column and trying to mount it one by one until it was successfully mounted. There are some improvements that can be added:

— Ignoring lines that are comments (starts with «#»),

— It trying to mount share until it’s mounted, so it can stuck. It could be fixed by creating separate thread for every mount,

— Checking it share was mounted properly could be better.

Hu
Moderator

Joined: 06 Mar 2007
Posts: 20017

Posted: Mon Jun 21, 2021 6:55 pm Post subject:

That script will mount any line that has cifs anywhere in it:

Code:

$ printf ‘The scifs are here.n’ | awk ‘/cifs/ {print $2}’

scifs

$ printf ‘Open the door; the scifs are here.n’ | awk ‘/cifs/ {print $2}’

the

Polling like that is generally bad. Why not use a dhcpcd hook to mount the filesystems after the network is up? Add noauto to the mount options. Create a dhcpcd hook in /lib/dhcpcd/dhcpcd-hooks. The example in /usr/share/dhcpcd/hooks/29-lookup-hostname looks like a good starting point. When the interface is brought up, bring up all the cifs filesystems, which you can more cleanly list using findmnt:

Code:

findmnt —fstab -t cifs —output TARGET —noheadings

Display posts from previous:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Источник

Этот вопрос уже имеет ответ здесь: Почему я получаю ошибку 101? Как работает мой DNS? 3 ответа

sudo apt-get update
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [94,5 kB]
Hit:2 http://ppa.launchpad.net/webupd8team/sublime-text-3/ubuntu xenial InRelease
Err:3 http://br.archive.ubuntu.com/ubuntu xenial InRelease                     
  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
Err:4 http://br.archive.ubuntu.com/ubuntu xenial-updates InRelease
  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
Err:5 http://br.archive.ubuntu.com/ubuntu xenial-backports InRelease
  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
Downloading 94,5 kB in 2min 0s (786 B/s)
Reading package lists ... Done
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/xenial/InRelease  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
W: Failed to fetch http://br.archive.ubuntu.com/ubuntu/dists/xenial-backports/InRelease  Cannot initiate the connection to br.archive.ubuntu.com:80 (2801:82:80ff:8000::5). - connect (101: Network is unreachable) [IP: 2801:82:80ff:8000::5 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

[d7 ] Ubuntu:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"

задан
2 November 2016 в 09:29

1 ответ

В установке Ubuntu по умолчанию эта строка читает

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

, поэтому вы меняете ее на

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ipv6.disable"

. Затем сначала запустите sudo update-grub, затем перезагрузитесь. [ ! d4]

ответ дан zwets
23 May 2018 в 04:36

What causes apt-get connect (101 network is unreachable)?

Easy way to fix the error

Disabling ipv6

Enabling secure port

Conclusion

PREVENT YOUR SERVER FROM CRASHING!

Understanding the Error

Solution 1: Changing the Repository Mirror

Solution 2: Disabling IPv6

Conclusion

What causes apt-get connect (101 network is unreachable)?

Easy way to fix the error

Disabling ipv6

Enabling secure port

Conclusion

PREVENT YOUR SERVER FROM CRASHING!

1 ответ

Другие вопросы по тегам:

Похожие вопросы:

Solution 1

Solution 2

Related videos on Youtube

Comments

Recents

Related

3 ответа

Теги

Похожие вопросы

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> garmayev

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> c47

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> garmayev

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> c47

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> garmayev

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> c47

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> garmayev

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> c47

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> garmayev

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> c47

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> garmayev

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> c47

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> AnrDaemon

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> garmayev

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> c47

mount error(101): Network is unreachable

Re: mount error(101): Network is unreachable

Re: mount error(101): Network is unreachable

Re: mount error(101): Network is unreachable

Re: mount error(101): Network is unreachable

Re: mount error(101): Network is unreachable

Re: mount error(101): Network is unreachable

Bookmarks

Bookmarks

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://ubuntuforums.org/images/ubuntu-VB4/buttons/collapse_40b.png" /> Posting Permissions

Re: mount error(101): Network is unreachable

Re: mount error(101): Network is unreachable

Re: mount error(101): Network is unreachable

Re: mount error(101): Network is unreachable

Re: mount error(101): Network is unreachable

Re: mount error(101): Network is unreachable

Bookmarks

Bookmarks

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://ubuntuforums.org/images/ubuntu-VB4/buttons/collapse_40b.png" /> Posting Permissions

#1 2012-09-30 12:12:38

[SOLVED] — Cannot automount Samba share from fstab

#2 2012-09-30 12:15:16

Re: [SOLVED] — Cannot automount Samba share from fstab

#3 2012-09-30 12:36:45

Re: [SOLVED] — Cannot automount Samba share from fstab

#4 2012-09-30 14:41:34

Re: [SOLVED] — Cannot automount Samba share from fstab

#5 2012-09-30 15:23:58

Re: [SOLVED] — Cannot automount Samba share from fstab

#6 2012-09-30 16:01:49

Re: [SOLVED] — Cannot automount Samba share from fstab

#7 2012-09-30 18:11:13

Re: [SOLVED] — Cannot automount Samba share from fstab

#8 2012-09-30 18:48:01

Re: [SOLVED] — Cannot automount Samba share from fstab

#9 2012-09-30 22:12:56

Re: [SOLVED] — Cannot automount Samba share from fstab

garmayev

c47

garmayev

c47

garmayev

c47

garmayev

c47

garmayev

c47

garmayev

c47

AnrDaemon

garmayev

c47

Posting Permissions

Posting Permissions