Jump to content
Как правильно добавить self-test и прочую отладку в тему
Где взять тестовые сборки
  • 1

4.0.14 постоянное сообщение changed "link" layer state "pending" to "running" и ошибка в таблице марщрутизации профиля

vasek00

Asked by vasek00,

 Share

Question

vasek00 Honored Flooder

vasek00

Posted
Posted (edited)

4.0.14 настроенный wireguard клиент для выхода в интернет (в нем один cloudflare warp). В настройках прописан DNS 192.168.130.101 сам роутер AdGuardHome, весь лог забит сообщениями, "Проверка активности" стоит 240 стояло 120/30 в данном подключение думаю оно по барабану какое, "ip global 65434".  Есть созданный профиль с одним только данным подключением.

Скрытый текст

  

[I] Mar 25 10:57:15 ndm: Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "pending" to "running". 
[I] Mar 25 10:57:15 ndm: Network::Interface::Ip: "Wireguard0": interface "Wireguard0" is global, priority 65434. 
[I] Mar 25 10:57:15 ndm: Network::Interface::Ip: "Wireguard0": adding default route via Wireguard0. 
[I] Mar 25 10:57:15 ndm: Network::Interface::Ip6: "Wireguard0": interface "Wireguard0" is global, priority 65434. 
[I] Mar 25 10:57:15 ndm: Network::Interface::Ip6: "Wireguard0": adding default route via Wireguard0. 
[I] Mar 25 10:57:15 ndm: Dns::Manager: name server 192.168.130.101 added, domain (default). 
[I] Mar 25 10:57:15 ndm: Dns::InterfaceSpecific: "Wireguard0": adding a host route to name server 192.168.130.101. 
[I] Mar 25 10:57:15 ndm: Core::Syslog: last message repeated 3 times.
[I] Mar 25 11:00:18 ndm: Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "running" to "pending". 
[I] Mar 25 11:00:18 ndm: Network::Interface::Ip: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 25 11:00:18 ndm: Network::Interface::Ip6: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 25 11:00:18 ndm: Dns::Manager: name server 192.168.130.101, domain (default) deleted. 
[I] Mar 25 11:01:21 ndm: Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "pending" to "running". 
[I] Mar 25 11:01:21 ndm: Network::Interface::Ip: "Wireguard0": interface "Wireguard0" is global, priority 65434. 
[I] Mar 25 11:01:21 ndm: Network::Interface::Ip: "Wireguard0": adding default route via Wireguard0. 
[I] Mar 25 11:01:21 ndm: Network::Interface::Ip6: "Wireguard0": interface "Wireguard0" is global, priority 65434. 
[I] Mar 25 11:01:21 ndm: Network::Interface::Ip6: "Wireguard0": adding default route via Wireguard0. 
[I] Mar 25 11:01:21 ndm: Dns::Manager: name server 192.168.130.101 added, domain (default). 
[I] Mar 25 11:01:21 ndm: Dns::InterfaceSpecific: "Wireguard0": adding a host route to name server 192.168.130.101. 
[I] Mar 25 11:01:21 ndm: Core::Syslog: last message repeated 3 times.
[I] Mar 25 11:04:25 ndm: Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "running" to "pending". 
[I] Mar 25 11:04:25 ndm: Network::Interface::Ip: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 25 11:04:25 ndm: Network::Interface::Ip6: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 25 11:04:25 ndm: Dns::Manager: name server 192.168.130.101, domain (default) deleted. 
[I] Mar 25 11:05:28 ndm: Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "pending" to "running". 
[I] Mar 25 11:05:28 ndm: Network::Interface::Ip: "Wireguard0": interface "Wireguard0" is global, priority 65434. 
[I] Mar 25 11:05:28 ndm: Network::Interface::Ip: "Wireguard0": adding default route via Wireguard0. 
[I] Mar 25 11:05:28 ndm: Network::Interface::Ip6: "Wireguard0": interface "Wireguard0" is global, priority 65434. 
[I] Mar 25 11:05:28 ndm: Network::Interface::Ip6: "Wireguard0": adding default route via Wireguard0. 
...
[I] Mar 25 08:17:45 ndm: Core::Syslog: last message repeated 3 times.
[I] Mar 25 08:20:55 ndm: Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "running" to "pending". 
[I] Mar 25 08:20:55 ndm: Network::Interface::Ip: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 25 08:20:55 ndm: Network::Interface::Ip6: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 25 08:20:55 ndm: Dns::Manager: name server 192.168.130.101, domain (default) deleted. 
[I] Mar 25 08:21:52 ndm: Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "pending" to "running". 
[I] Mar 25 08:21:52 ndm: Network::Interface::Ip: "Wireguard0": interface "Wireguard0" is global, priority 65434. 
[I] Mar 25 08:21:52 ndm: Network::Interface::Ip: "Wireguard0": adding default route via Wireguard0. 
[I] Mar 25 08:21:52 ndm: Network::Interface::Ip6: "Wireguard0": interface "Wireguard0" is global, priority 65434. 
[I] Mar 25 08:21:52 ndm: Network::Interface::Ip6: "Wireguard0": adding default route via Wireguard0. 
[I] Mar 25 08:21:52 ndm: Dns::Manager: name server 192.168.130.101 added, domain (default). 
[I] Mar 25 08:21:52 ndm: Dns::InterfaceSpecific: "Wireguard0": adding a host route to name server 192.168.130.101. 
[I] Mar 25 08:21:52 ndm: Core::Syslog: last message repeated 3 times.
[I] Mar 25 08:24:21 ndm: Netfilter::Util::Conntrack: flushed 99 IPv4 connections.

 

Вопрос это просто лишняя информация в логе или что-то с созданным профилем происходит, так как в нем только один активный интерфейс Wireguard0 и для него может быть "adding default route via Wireguard0/removing default route via Wireguard0"

И для справки IP6, хотя не где не чего для него не настраивал.

 

Edited by vasek00
Link to comment
Share on other sites

7 answers to this question

Recommended Posts

  • 0
dimon27254 Advanced Member

dimon27254

Posted
Posted

@vasek00 могу предположить, что эти сообщения связаны с новым механизмом определения состояния интерфейсов:

У меня стоит 4.0 Alpha 14. Замечал их в логе, но не обращал внимание. Они появляются даже при изменении состояния Ethernet портов. Например, если отключить и заново вставить в порт Ethernet-кабель от компьютера: 

[I] Mar 25 18:09:11 ndm: Network::Interface::Switch: "GigabitEthernet0/0": switch link down at port 1. 
[I] Mar 25 18:09:11 ndm: Network::Interface::Base: "GigabitEthernet0/0": "ethernet" changed "link" layer state "running" to "pending". 
[I] Mar 25 18:09:14 ndm: Network::Interface::Switch: "GigabitEthernet0/0": switch link up at port 1 (1000FD/AN). 
[I] Mar 25 18:09:14 ndm: Network::Interface::Base: "GigabitEthernet0/0": "ethernet" changed "link" layer state "pending" to "running".
Link to comment
Share on other sites
  • 0
vasek00 Honored Flooder

vasek00

Posted
  • Author
Posted (edited)

Да но тут еще

так как в нем только один активный интерфейс Wireguard0 и для него может быть "adding default route via Wireguard0/removing default route via Wireguard0"

добавить и удалить default -> как сказал выше данный интерфейс у меня в созданном профиле. 

[I] Mar 25 11:00:18 ndm: Network::Interface::Ip: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 25 11:00:18 ndm: Network::Interface::Ip6: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 25 11:00:18 ndm: Dns::Manager: name server 192.168.130.101, domain (default) deleted. 
[I] Mar 25 11:01:21 ndm: Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "pending" to "running". 
[I] Mar 25 11:01:21 ndm: Network::Interface::Ip: "Wireguard0": interface "Wireguard0" is global, priority 65434. 
[I] Mar 25 11:01:21 ndm: Network::Interface::Ip: "Wireguard0": adding default route via Wireguard0.

и тут не 3ceк

Edited by vasek00
Link to comment
Share on other sites
  • 0
vasek00 Honored Flooder

vasek00

Posted
  • Author
Posted (edited)

Что интересно - создал еще один профиль, так же создал в нем еще один wireguard (Proton) он один канал, клиента не помещал в него. В итоге никаких лишних записей по нему нет 

"wireguard" changed "link" layer state "pending" to "running".

лог чистый по данному интерфейсу, в отличие от

Скрытый текст 
[I] Mar 26 05:37:33 ndm: Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "running" to "pending". 
[I] Mar 26 05:37:33 ndm: Network::Interface::Ip: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 26 05:37:33 ndm: Network::Interface::Ip6: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 26 05:37:33 ndm: Dns::Manager: name server 192.168.130.101, domain (default) deleted. 
[I] Mar 26 05:38:37 ndm: Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "pending" to "running". 
[I] Mar 26 05:38:37 ndm: Network::Interface::Ip: "Wireguard0": interface "Wireguard0" is global, priority 65434. 
[I] Mar 26 05:38:37 ndm: Network::Interface::Ip: "Wireguard0": adding default route via Wireguard0. 
[I] Mar 26 05:38:37 ndm: Network::Interface::Ip6: "Wireguard0": interface "Wireguard0" is global, priority 65434. 
[I] Mar 26 05:38:37 ndm: Network::Interface::Ip6: "Wireguard0": adding default route via Wireguard0. 
[I] Mar 26 05:38:37 ndm: Dns::Manager: name server 192.168.130.101 added, domain (default). 
[I] Mar 26 05:38:37 ndm: Dns::InterfaceSpecific: "Wireguard0": adding a host route to name server 192.168.130.101. 
[I] Mar 26 05:38:37 ndm: Core::Syslog: last message repeated 3 times.
...
[I] Mar 26 06:06:18 ndm: Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "running" to "pending". 
[I] Mar 26 06:06:18 ndm: Network::Interface::Ip: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 26 06:06:18 ndm: Network::Interface::Ip6: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 26 06:06:18 ndm: Dns::Manager: name server 192.168.130.101, domain (default) deleted. 
[I] Mar 26 06:07:16 ndm: Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "pending" to "running". 
[I] Mar 26 06:07:16 ndm: Network::Interface::Ip: "Wireguard0": interface "Wireguard0" is global, priority 65434. 
[I] Mar 26 06:07:16 ndm: Network::Interface::Ip: "Wireguard0": adding default route via Wireguard0. 
[I] Mar 26 06:07:16 ndm: Network::Interface::Ip6: "Wireguard0": interface "Wireguard0" is global, priority 65434. 
[I] Mar 26 06:07:16 ndm: Network::Interface::Ip6: "Wireguard0": adding default route via Wireguard0. 
[I] Mar 26 06:07:16 ndm: Dns::Manager: name server 192.168.130.101 added, domain (default). 
[I] Mar 26 06:07:16 ndm: Dns::InterfaceSpecific: "Wireguard0": adding a host route to name server 192.168.130.101. 
[I] Mar 26 06:07:16 ndm: Core::Syslog: last message repeated 3 times.
[I] Mar 26 06:10:25 ndm: Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "running" to "pending". 
[I] Mar 26 06:10:25 ndm: Network::Interface::Ip: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 26 06:10:25 ndm: Network::Interface::Ip6: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 26 06:10:25 ndm: Dns::Manager: name server 192.168.130.101, domain (default) deleted. 
...
[I] Mar 26 07:29:12 ndm: Core::Syslog: last message repeated 3 times.
[I] Mar 26 07:32:15 ndm: Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "running" to "pending". 
[I] Mar 26 07:32:15 ndm: Network::Interface::Ip: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 26 07:32:15 ndm: Network::Interface::Ip6: "Wireguard0": removing default route via Wireguard0. 
[I] Mar 26 07:32:15 ndm: Dns::Manager: name server 192.168.130.101, domain (default) deleted. 
[I] Mar 26 07:33:19 ndm: Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "pending" to "running". 
[I] Mar 26 07:33:19 ndm: Network::Interface::Ip: "Wireguard0": interface "Wireguard0" is global, priority 65434. 
[I] Mar 26 07:33:19 ndm: Network::Interface::Ip: "Wireguard0": adding default route via Wireguard0. 
[I] Mar 26 07:33:19 ndm: Network::Interface::Ip6: "Wireguard0": interface "Wireguard0" is global, priority 65434. 
[I] Mar 26 07:33:19 ndm: Network::Interface::Ip6: "Wireguard0": adding default route via Wireguard0. 
[I] Mar 26 07:33:19 ndm: Dns::Manager: name server 192.168.130.101 added, domain (default). 
[I] Mar 26 07:33:19 ndm: Dns::InterfaceSpecific: "Wireguard0": adding a host route to name server 192.168.130.101. 
[I] Mar 26 07:33:19 ndm: Core::Syslog: last message repeated 3 times.
...
ip policy Policy0
    description Cloud
    permit global Wireguard0
    no permit global Wireguard4
    no permit global PPPoE0
    no permit global GigabitEthernet0/Vlan2

ip policy Policy2
    description A
    permit global Wireguard4
    no permit global GigabitEthernet0/Vlan9
    no permit global Wireguard0
    no permit global PPPoE0

ip hotspot
    ...
    host КЛИЕНТ1:e2 permit
    host КЛИЕНТ1:e2 policy Policy0
    host КЛИЕНТ1:e2 priority 6

 

Похоже, после появления/включения клиента в данном профиле где Wireguard0 один и он default данные записи пропадают.

В итоге получаю = отличие двух профилей в которых Wirwguard0 - активен и есть клиент (тут важно включен он или нет) и Wireguard4 - активен но нет клиентов.

Edited by vasek00
Link to comment
Share on other sites
  • 0
vasek00 Honored Flooder

vasek00

Posted
  • Author
Posted (edited)

Ну вот и отловил данный - баг или не баг.

1. Убираю клиента из профиля Policy0 (Wireguard0) и помещаю его в профиль Policy2 (Wireguard3), т.е. КЛИЕНТА В ПРОФИЛЕ Policy0 нет.

2. Дожидаюсь данной описанной выше ошибки и в итоге имею такое поведение в таблице маршрутизация для данного Policy0

Скрытый текст 
Мар 26 10:02:37 ndm Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "pending" to "running".
Мар 26 10:02:37 ndm Network::Interface::Ip: "Wireguard0": interface "Wireguard0" is global, priority 65434.
Мар 26 10:02:37 ndm Network::Interface::Ip: "Wireguard0": adding default route via Wireguard0.
Мар 26 10:02:37 ndm Network::Interface::Ip6: "Wireguard0": interface "Wireguard0" is global, priority 65434.
Мар 26 10:02:37 ndm Network::Interface::Ip6: "Wireguard0": adding default route via Wireguard0.
Мар 26 10:02:37 ndm Dns::Manager: name server 192.168.130.101 added, domain (default).
Мар 26 10:02:37 ndm Dns::InterfaceSpecific: "Wireguard0": adding a host route to name server 192.168.130.101.
Мар 26 10:02:37 ndm Core::Syslog: last message repeated 3 times.

смотрим что в реале 

(Профиль Policy0)

~ # ip ro show table 42 
default dev nwg0  scope link 
...
192.168.130.101 dev nwg0  scope link 
...

~ # ip ro show table 42
10.10.10.0/24 dev eth2.9  scope link 
...
**** 192.168.130.101 dev nwg0  scope link *** ее тут нет
...

~ # date
Sun Mar 26 07:02:15 UTC 2023 *** тут нужно +3 часа
~ # ip ro show table 42
10.10.10.0/24 dev eth2.9  scope link 
...

~ # date
Sun Mar 26 07:02:25 UTC 2023
~ # ip ro show table 42
10.10.10.0/24 dev eth2.9  scope link 
...

~ # date
Sun Mar 26 07:02:33 UTC 2023
~ # ip ro show table 42
10.10.10.0/24 dev eth2.9  scope link 
...
~ # ip ro show table 42
default dev nwg0  scope link 
10.10.10.0/24 dev eth2.9  scope link 
...
192.168.130.101 dev nwg0  scope link *** появился
...

 

Edited by vasek00
Link to comment
Share on other sites
  • 0
vasek00 Honored Flooder

vasek00

Posted
  • Author
Posted

Есть связка профиля (таблица маршрутов) и маркировки пакетов. Маркировка пакетов привязана к активности клиента, т.е. его нет то нет и правил маркировки, он клиент появился и как итог появилась и маркировка для него.

Возможно что-то забыли убрать так как ранее 4.0.13 по моему этого не видел в логах.

Link to comment
Share on other sites
  • 0
vasek00 Honored Flooder

vasek00

Posted
  • Author
Posted

4.0.18 не чего не исправлено. 

Апр 17 08:42:47 ndm Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "running" to "pending".
Апр 17 08:42:47 ndm Network::Interface::Ip: "Wireguard0": removing default route via Wireguard0.
Апр 17 08:42:47 ndm Network::Interface::Ip6: "Wireguard0": removing default route via Wireguard0.
Апр 17 08:43:50 ndm Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "pending" to "running".
Апр 17 08:43:50 ndm Network::Interface::Ip: "Wireguard0": interface "Wireguard0" is global, priority 62346.
Апр 17 08:43:50 ndm Network::Interface::Ip: "Wireguard0": adding default route via Wireguard0.
Апр 17 08:43:50 ndm Network::Interface::Ip6: "Wireguard0": interface "Wireguard0" is global, priority 62346.
Апр 17 08:43:50 ndm Network::Interface::Ip6: "Wireguard0": adding default route via Wireguard0.
Апр 17 08:43:50 ndm Dns::Manager: name server 192.168.130.101 added, domain (default).
Апр 17 08:43:50 ndm Dns::InterfaceSpecific: "Wireguard0": adding a host route to name server 192.168.130.101.
Апр 17 08:43:50 ndm Dns::InterfaceSpecific: "Wireguard0": host route for name server 192.168.130.101 added.
Апр 17 08:43:50 ndm Dns::InterfaceSpecific: "Wireguard0": adding a host route to name server 192.168.130.101.
Апр 17 08:43:50 ndm Dns::InterfaceSpecific: "Wireguard0": host route for name server 192.168.130.101 added.
Апр 17 08:43:50 ndm Dns::InterfaceSpecific: "Wireguard0": adding a host route to name server 192.168.130.101.
Апр 17 08:43:50 ndm Dns::InterfaceSpecific: "Wireguard0": host route for name server 192.168.130.101 added.
Апр 17 08:43:50 ndm Dns::InterfaceSpecific: "Wireguard0": adding a host route to name server 192.168.130.101.
Апр 17 08:43:50 ndm Dns::InterfaceSpecific: "Wireguard0": host route for name server 192.168.130.101 added.
Апр 17 08:46:54 ndm Network::Interface::Base: "Wireguard0": "wireguard" changed "link" layer state "running" to "pending".
Апр 17 08:46:54 ndm Network::Interface::Ip: "Wireguard0": removing default route via Wireguard0.
Апр 17 08:46:54 ndm Network::Interface::Ip6: "Wireguard0": removing default route via Wireguard0. 

ip dhcp host хх:хх:хх:хх:хх:e2 192.168.130.2
host хх:хх:хх:хх:хх:e2 policy Policy0

ip policy Policy0
    description Cloud
    permit global Wireguard0

Повторюсь если клиент не в сети, то логи заполнены тем что выше, при подключении клиента лог.чистый. Ранее такого не было до 4.0.14 при тех же настройках.

 

  • Thanks 1
Link to comment
Share on other sites
  • 0
vasek00 Honored Flooder

vasek00

Posted
  • Author
Posted (edited)

4.0.19 все по старому. После включения клиента и если долго не работает он (страницы не просматривает) то лог так же забит сообщениями.

Есть дискомфорт при включение клиента и после его долгого тайм аута.

Edited by vasek00
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to question listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...