Jump to content
r13

Непрерывная попытка резолва tunnel source

Recommended Posts

@Le ecureuil

Добрый вечер,

Если отключить сетевой интерфейс указанный как  tunnel source для тунеля, то туннель будет бесконечно безуспешно пытаться отрезолвить его ip.

Надо бы добавить проверку активности целевого интерфейса.

ЗЫ Как поживает доработка использования в качестве tunnel source текущего активного интернет соединения? Есть прогнозы?

Feb 21 20:58:21ndm
Network::Interface::SecureIPTunnel: "IPIP0": updating server IP secure configuration.
Feb 21 20:58:21ndm
IpSec::Manager: IP secure connection "IPIP0" and keys was deleted.
Feb 21 20:58:21ndm
IpSec::Manager: IP secure connection "IPIP0" was added.
Feb 21 20:58:22ndm
Network::Interface::SecureIPTunnel: "IPIP0": unable to start server mode without specified local source.
Feb 21 20:58:22ndm
Network::Interface::SecureIPTunnel: "IPIP0": invalid local source address, reresolving.
Feb 21 20:58:22ndm
Network::Interface::Tunnel: "IPIP0": resolved source 0.0.0.0, any destination.
Feb 21 20:58:22ndm
IpSec::Manager: IP secure connection "IPIP0" and keys was deleted.
Feb 21 20:58:22ndm
Network::Interface::SecureIPTunnel: "IPIP0": updating server IP secure configuration.
Feb 21 20:58:22ndm
IpSec::Manager: IP secure connection "IPIP0" and keys was deleted.
Feb 21 20:58:22ndm
IpSec::Manager: IP secure connection "IPIP0" was added.
Feb 21 20:58:23ndm
Network::Interface::SecureIPTunnel: "IPIP0": unable to start server mode without specified local source.
Feb 21 20:58:23ndm
Network::Interface::SecureIPTunnel: "IPIP0": invalid local source address, reresolving.
Feb 21 20:58:23ndm
Network::Interface::Tunnel: "IPIP0": resolved source 0.0.0.0, any destination.
Feb 21 20:58:23ndm
IpSec::Manager: IP secure connection "IPIP0" and keys was deleted.
Feb 21 20:58:23ndm
Network::Interface::SecureIPTunnel: "IPIP0": updating server IP secure configuration.
Feb 21 20:58:23ndm
IpSec::Manager: IP secure connection "IPIP0" and keys was deleted.
Feb 21 20:58:23ndm
IpSec::Manager: IP secure connection "IPIP0" was added.
Feb 21 20:58:24ndm
Network::Interface::SecureIPTunnel: "IPIP0": unable to start server mode without specified local source.

 

Share this post


Link to post
Share on other sites

@r13 спасибо за репорт, поправлю.

А не напомните тему и пост, где обсуждалось активное соединение в качестве source? Ну для порядка, чтобы восстановить нить обсуждения.

Share this post


Link to post
Share on other sites
6 минут назад, Le ecureuil сказал:

@r13

А не напомните тему и пост, где обсуждалось активное соединение в качестве source? Ну для порядка, чтобы восстановить нить обсуждения.

Тут:

 

  • Thanks 1

Share this post


Link to post
Share on other sites
В 2/21/2017 в 21:25, r13 сказал:

Тут:

 

Насчет tunnel source auto сделано, насчет недоступности целевого интерфейса продолжаем работу.

  • Thanks 1

Share this post


Link to post
Share on other sites

Работает, теперь в логе при недоступности интерфейса

ndm: Network::Interface::Tunnel: "IPIP6": source interface CdcEthernet0 is down, standby.

Но в процессе включений отключений интерфейсов в логе вылезла кучка  красноты system failed

 

Mar 27 22:26:43ndm
Io::Netlink: unable to bind: address already in use.
Mar 27 22:26:43ndm
Ip6::Util::NetlinkTools: system failed [0xcffd003c].
Mar 27 22:26:43ndm
Ip6::Addressing: system failed [0xcffd0055], unable to set 2a02:2168:18db:8800:ee43:f6ff:fe04:9b24  to  br0: no error.
Mar 27 22:26:43root
Modem NAT rule applied
Mar 27 22:26:43root
Core::Syslog: last message repeated 3 times.
Mar 27 22:26:44ipsec
10[KNL] fe80::ee43:f6ff:fe04:9b25 appeared on eth2.2 
Mar 27 22:26:45ipsec
13[KNL] interface ipip2 deactivated 
Mar 27 22:26:45ndm
Network::Interface::Base: "IPIP2": interface is down.
Mar 27 22:26:45ipsec
08[KNL] interface ipip2 activated 
Mar 27 22:26:45ndm
Network::Interface::Base: "IPIP2": interface is up.
Mar 27 22:26:45ndhcpc
GigabitEthernet0/Vlan2: NDM DHCP client (version 3.2.11) started.
Mar 27 22:26:45ndhcpc
GigabitEthernet0/Vlan2: created PID file "/var/run/ndhcpc-eth2.2.pid".
Mar 27 22:26:45root
Modem NAT rule applied
Mar 27 22:26:46root
Core::Syslog: last message repeated 2 times.
Mar 27 22:26:46ndm
Ip6::Addressing: system failed [0xcffd0055], unable to remove 2a02:2168:18db:8800:ee43:f6ff:fe04:9b24  from  br0: address not available.

С доработкой не связано, но кину пока селф сюда.

Порезвлюсь если будет воспроизводимо, создам новую тему.

 

Share this post


Link to post
Share on other sites
10 часов назад, r13 сказал:

Работает, теперь в логе при недоступности интерфейса


ndm: Network::Interface::Tunnel: "IPIP6": source interface CdcEthernet0 is down, standby.

Но в процессе включений отключений интерфейсов в логе вылезла кучка  красноты system failed

 


Mar 27 22:26:43ndm
Io::Netlink: unable to bind: address already in use.
Mar 27 22:26:43ndm
Ip6::Util::NetlinkTools: system failed [0xcffd003c].
Mar 27 22:26:43ndm
Ip6::Addressing: system failed [0xcffd0055], unable to set 2a02:2168:18db:8800:ee43:f6ff:fe04:9b24  to  br0: no error.
Mar 27 22:26:43root
Modem NAT rule applied
Mar 27 22:26:43root
Core::Syslog: last message repeated 3 times.
Mar 27 22:26:44ipsec
10[KNL] fe80::ee43:f6ff:fe04:9b25 appeared on eth2.2 
Mar 27 22:26:45ipsec
13[KNL] interface ipip2 deactivated 
Mar 27 22:26:45ndm
Network::Interface::Base: "IPIP2": interface is down.
Mar 27 22:26:45ipsec
08[KNL] interface ipip2 activated 
Mar 27 22:26:45ndm
Network::Interface::Base: "IPIP2": interface is up.
Mar 27 22:26:45ndhcpc
GigabitEthernet0/Vlan2: NDM DHCP client (version 3.2.11) started.
Mar 27 22:26:45ndhcpc
GigabitEthernet0/Vlan2: created PID file "/var/run/ndhcpc-eth2.2.pid".
Mar 27 22:26:45root
Modem NAT rule applied
Mar 27 22:26:46root
Core::Syslog: last message repeated 2 times.
Mar 27 22:26:46ndm
Ip6::Addressing: system failed [0xcffd0055], unable to remove 2a02:2168:18db:8800:ee43:f6ff:fe04:9b24  from  br0: address not available.

С доработкой не связано, но кину пока селф сюда.

Порезвлюсь если будет воспроизводимо, создам новую тему.

 

Это все нестрашно, можете не волноваться - эти особенности уже были выявлены в процессе разработки.

Передадим товарищам, занимающимся ipv6, или создавайте тему и зовите @vst.

  • Thanks 2

Share this post


Link to post
Share on other sites
В 17.03.2017 в 13:37, Le ecureuil сказал:

@r13 обработка состояния tunnel source поправлена, просьба проверить на следующем релизе.

@Le ecureuil, а я верно понимаю, что обработка была исправлена именно для случая отключения интерфейса? Дело в том, что сейчас (3.1.6 Beta) при упавшем коннекте до провайдера (то есть интерфейс остается включен) каждые 2 секунды валятся эти ошибки:

Сен 27 14:53:12 ndm Network::Interface::Tunnel: "IPIP0": resolved source 0.0.0.0, any destination.
Сен 27 14:53:13 ndm Network::Interface::SecureIpTunnel: "IPIP0": unable to start server mode without specified local source.
Сен 27 14:53:13 ndm Network::Interface::SecureIpTunnel: "IPIP0": invalid local source address, reresolving.
Сен 27 14:53:13 ndm IpSec::Manager: "IPIP0": IP secure connection and keys was deleted.
Сен 27 14:53:13 ndm Network::Interface::Tunnel: "IPIP0": resolved source 0.0.0.0, any destination.
Сен 27 14:53:13 ndm Network::Interface::SecureIpTunnel: "IPIP0": updating server IP secure configuration.
Сен 27 14:53:13 ndm IpSec::Manager: "IPIP0": IP secure connection was added.

 

Share this post


Link to post
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
Reply to this topic...

×   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.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...