Jump to content
  • 0

Пропадает IPoE соединение раз в 50 минут


Igor Antarov
 Share

Question

2.10.C.1.0-0  
Работало все с последним аптаймом два месяца.  Потом почти двое суток на провайдере был ремонт. 
Сейчас интернет работает 50 минут после загрузки роутера, потом обрывается. 
Провайдер уверяет что на их строне все ОК. 

Где вообе искать концы?

Концовка лога идентична каждый раз практически по минутам:

 


[I] Dec 13 23:51:40 ndm: Ntp::Client: NTP client enabled.
[I] Dec 13 23:51:40 ndm: EasyConfig::Manager: a new check period set to 15 seconds.
[I] Dec 13 23:51:40 ndm: EasyConfig::Manager: a new maximum fail count set to 3.
[I] Dec 13 23:51:40 ndm: EasyConfig::Manager: "google.com" name added.
[I] Dec 13 23:51:40 ndm: EasyConfig::Manager: "facebook.com" name added.
[I] Dec 13 23:51:41 ndm: EasyConfig::Manager: "yahoo.com" name added.
[I] Dec 13 23:51:40 ndhcpc: GigabitEthernet1: received ACK for 128.69.162.247 from 78.107.125.141.
[I] Dec 13 23:51:41 ndm: Core::Hotplug::Manager: scanning hardware...
[I] Dec 13 23:51:41 ndm: Dhcp::Client: configuring interface ISP.
[I] Dec 13 23:51:41 ndm: Network::Interface::IP: "GigabitEthernet1": IP address is 128.69.162.247/21.
[I] Dec 13 23:51:41 ndm: Dhcp::Client: obtained IP address 128.69.162.247/21.
[I] Dec 13 23:51:41 ndm: Dhcp::Client: interface "ISP" is global, priority 700.
[I] Dec 13 23:51:41 ndm: Dhcp::Client: adding a default route via 128.69.160.1.
[I] Dec 13 23:51:41 ndm: Dhcp::Client: adding a host route to name server 85.21.192.5.
[I] Dec 13 23:51:41 ndm: Dhcp::Client: adding name server 85.21.192.5.
[I] Dec 13 23:51:41 ndm: Dns::Manager: name server 85.21.192.5 added, domain (default).
[I] Dec 13 23:51:41 ndm: Dhcp::Client: adding a host route to name server 213.234.192.7.
[I] Dec 13 23:51:41 ndm: Dhcp::Client: adding name server 213.234.192.7.
[I] Dec 13 23:51:41 ndm: Dns::Manager: name server 213.234.192.7 added, domain (default).
[I] Dec 13 23:51:41 ndm: Network::Interface::Rtx::AccessPoint: "WifiMaster0/AccessPoint1": peer isolation disabled.
[I] Dec 13 23:51:41 ndm: kernel: br1: port 1(eth2.3) entered forwarding state
[I] Dec 13 23:51:41 ndm: Network::InterfaceFlusher: flushed conntrack and route cache.
[I] Dec 13 23:51:41 ndm: Ntp::Client: unable to communicate with "1.pool.ntp.org".
[I] Dec 13 23:51:41 ndm: Ntp::Client: could not synchronize, waiting...
[I] Dec 13 23:51:41 ndm: Core::Hotplug::Manager: scanning hardware: done.
[I] Dec 13 23:51:41 ndm: Core::Authenticator: generating.
[I] Dec 13 23:51:41 ndm: Core::Init: system ready, core startup time is 22 seconds.
[I] Dec 13 23:51:41 ndm: Hotspot::Discovery::Explorer: "Bridge0": Interface Bridge0 neighbour explorer started.
[I] Dec 13 23:51:42 ndm: Hotspot::Discovery::Explorer: "Bridge1": Interface Bridge1 neighbour explorer started.
[I] Dec 13 23:51:42 ndm: kernel: Disable SMB fastpath
[I] Dec 13 23:51:42 ndm: kernel: Enable SMB fastpath for 192.168.1.1/255.255.255.0
[I] Dec 13 23:51:42 ndm: Core::System::DriverManager: loading /lib/modules/3.4.113/igmpsn.ko.
[I] Dec 13 23:51:42 ndm: kernel: igmpsn: IGMP switch snooping module (C) 2015-2017 NDM Systems Inc., v4.1.1
[I] Dec 13 23:51:42 ndm: Network::Interface::Rtx::WifiMaster: "WifiMaster0": auto channel mode set.
[I] Dec 13 23:51:42 ndm: Network::Interface::Rtx::WifiMaster: "WifiMaster1": auto channel mode set.
[I] Dec 13 23:51:42 ndm: kernel: br0: port 2(ra0) entered disabled state
[I] Dec 13 23:51:42 ndm: kernel: usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
[I] Dec 13 23:51:42 ndm: kernel: usb 2-1: New USB device found, idVendor=0bc2, idProduct=ab28
[I] Dec 13 23:51:42 ndm: kernel: usb 2-1: Product: BUP SL
[I] Dec 13 23:51:42 ndm: kernel: usb 2-1: Manufacturer: Seagate
[I] Dec 13 23:51:42 ndm: kernel: usb 2-1: SerialNumber: NA7T0FSR
[I] Dec 13 23:51:42 ndm: kernel: scsi0 : usb-storage 2-1:1.0
[I] Dec 13 23:51:43 ndm: kernel: br0: port 2(ra0) entered forwarding state
[I] Dec 13 23:51:43 ndm: kernel: br0: port 2(ra0) entered forwarding state
[I] Dec 13 23:51:43 ndm: kernel: br0: port 3(rai0) entered disabled state
[I] Dec 13 23:51:43 ndm: kernel: eth2: no IPv6 routers present
[I] Dec 13 23:51:44 ndm: kernel: br0: port 2(ra0) entered forwarding state
[I] Dec 13 23:51:44 ndm: kernel: br0: port 3(rai0) entered forwarding state
[I] Dec 13 23:51:44 ndm: kernel: br0: port 3(rai0) entered forwarding state
[I] Dec 13 23:51:44 ndm: Core::System::DriverManager: loading /lib/modules/3.4.113/hw_nat.ko.
[I] Dec 13 23:51:44 ndm: kernel: Ralink/MTK HW NAT 5.0.3.0-4 Module Enabled, FoE Size: 16384
[I] Dec 13 23:51:44 ndhcps: NDM DHCP server (version 3.2.14) started.
[I] Dec 13 23:51:44 ndm: Core::System::DriverManager: loading /lib/modules/3.4.113/fastvpn.ko.
[I] Dec 13 23:51:44 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Dec 13 23:51:44 ndm: Core::Server: client disconnected.
[I] Dec 13 23:51:44 telnetd: waiting for connections...
[I] Dec 13 23:51:44 ndm: kernel: SWNAT sizeof(bind) = 204
[I] Dec 13 23:51:44 ndm: kernel: SWNAT sizeof(hashent) = 56
[I] Dec 13 23:51:44 ndm: kernel: SWNAT is registered
[I] Dec 13 23:51:44 ndm: kernel: SWNAT enabled
[I] Dec 13 23:51:44 ndm: kernel: SWNAT caps: L2TP, PPTP, PPPoE, IPoE, MC, USB CDC/DSL
[I] Dec 13 23:51:44 ndm: kernel: Fast VPN init, v4.0-101
[I] Dec 13 23:51:44 ndm: kernel: PPPoE/IPoE LAN software acceleration is disabled
[I] Dec 13 23:51:44 ndhcps: NDM DHCP server (version 3.2.14) started.
[W] Dec 13 23:51:44 pure-ftpd: (?@?) [WARNING] Starting with an ACL support feature.
[I] Dec 13 23:51:44 ndm: kernel: SWNAT scheduled to clear binds for 10.1.30.1/255.255.255.255
[I] Dec 13 23:51:44 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Dec 13 23:51:44 upnp: HTTP listening on port 35405
[I] Dec 13 23:51:44 upnp: Listening for NAT-PMP/PCP traffic on port 5351
[I] Dec 13 23:51:44 ndm: Core::Server: started Session /var/run/ndm.core.socket.
[I] Dec 13 23:51:44 ndm: Core::Server: client disconnected.
[I] Dec 13 23:51:44 nimproxy: NDM IGMP/Multicast proxy (version 0.0.26) started.
[I] Dec 13 23:51:44 ndm: Http::Manager: new Web server configuration was applied.
[I] Dec 13 23:51:44 ndm: kernel: eth2.1: no IPv6 routers present
[I] Dec 13 23:51:45 ndm: kernel: br0: port 3(rai0) entered forwarding state
[I] Dec 13 23:51:45 ndm: kernel: scsi 0:0:0:0: Direct-Access     Seagate  BUP SL           0304 PQ: 0 ANSI: 6
[I] Dec 13 23:51:45 ndm: kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
[I] Dec 13 23:51:46 coalagent: version 0.0.6f starting.
[I] Dec 13 23:51:46 ndm: kernel: sd 0:0:0:0: [sda] Spinning up disk...
[I] Dec 13 23:51:46 ndm: kernel: eth2.3: no IPv6 routers present
[I] Dec 13 23:51:46 ndm: kernel: eth3: no IPv6 routers present
[W] Dec 13 23:51:49 ndm: kernel: ....ready
[W] Dec 13 23:51:49 ndm: kernel: sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[I] Dec 13 23:51:49 ndm: kernel: sd 0:0:0:0: [sda] 7814037167 512-byte logical blocks: (4.00 TB/3.63 TiB)
[W] Dec 13 23:51:49 ndm: kernel: sd 0:0:0:0: [sda] 2048-byte physical blocks
[I] Dec 13 23:51:49 ndm: kernel: sd 0:0:0:0: [sda] Write Protect is off
[I] Dec 13 23:51:49 ndm: kernel: br0: no IPv6 routers present
[I] Dec 13 23:51:49 ndm: kernel: sd 0:0:0:0: [sda] Mode Sense: 4f 00 00 00
[I] Dec 13 23:51:49 ndm: kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[W] Dec 13 23:51:49 ndm: kernel: sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[I] Dec 13 23:51:49 ndm: kernel:  sda: sda1 sda2
[W] Dec 13 23:51:49 ndm: kernel: sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
[I] Dec 13 23:51:49 ndm: kernel: sd 0:0:0:0: [sda] Attached SCSI disk
[W] Dec 13 23:51:49 ndm: FileSystem::Ext: "/dev/sda" has an unknown partition type, ignored.
[W] Dec 13 23:51:49 ndm: FileSystem::Ext: "/dev/sda1" has an unknown partition type, ignored.
[I] Dec 13 23:51:50 ndm: FileSystem::Ext: ntfs "E66C98E56C98B233:": filesystem initialized.
[I] Dec 13 23:51:50 ndm: kernel: tntfs info (device sda2, pid 443): ntfs_fill_super(): fail_safe is enabled.
[I] Dec 13 23:51:50 ndm: kernel: tntfs info (device sda2, pid 443): load_system_files(): NTFS volume name 'Seagate Backup Plus Drive', version 3.1 (cluster_size 4096, PAGE_SIZE 4096).
[I] Dec 13 23:51:50 ndm: kernel: ACS result: primary channel 9, 40 MHz spectrum min dirty (with CCA) = 1300
[I] Dec 13 23:51:51 wmond: WifiMaster0/AccessPoint0: (MT76x2) BSS(ra0) channel switched to 9.
[I] Dec 13 23:51:51 ndm: kernel: br1: no IPv6 routers present
[I] Dec 14 03:12:27 ndm: Core::System::Clock: system time has been changed.
[I] Dec 14 03:12:27 ndm: Ntp::Client: time synchronized with "2.pool.ntp.org".
[I] Dec 14 03:12:27 ndm: FileSystem::Repository: "E66C98E56C98B233:" registered.
[I] Dec 14 03:12:28 ndm: kernel: ACS result: primary channel 36, 80 MHz spectrum min dirty (with CCA) = 0
[I] Dec 14 03:12:28 ndm: Cifs::ServerNQ: service started.
[I] Dec 14 03:12:28 ndm: kernel: ra0: no IPv6 routers present
[I] Dec 14 03:12:29 wmond: WifiMaster1/AccessPoint0: (MT76x2) BSS(rai0) channel switched to 36.
[I] Dec 14 03:12:30 ndm: kernel: rai0: no IPv6 routers present
[I] Dec 14 03:12:42 wmond: WifiMaster1/AccessPoint0: (MT76x2) STA(10:02:b5:e4:60:d8) had associated successfully.
[I] Dec 14 03:12:43 wmond: WifiMaster1/AccessPoint0: (MT76x2) STA(10:02:b5:e4:60:d8) set key done in WPA2/WPA2PSK.
[I] Dec 14 03:12:43 ndhcps: DHCPREQUEST received (STATE_INIT) for 192.168.1.41 from 10:02:b5:e4:60:d8.
[I] Dec 14 03:12:43 ndhcps: sending ACK of 192.168.1.41 to 10:02:b5:e4:60:d8.
[I] Dec 14 03:17:16 ndhcpc: GigabitEthernet1: received ACK for 128.69.162.247 from 78.107.125.141.
[I] Dec 14 03:19:45 wmond: WifiMaster0/AccessPoint0: (MT76x2) STA(84:98:66:7d:47:f7) had associated successfully.
[I] Dec 14 03:19:46 wmond: WifiMaster0/AccessPoint0: (MT76x2) STA(84:98:66:7d:47:f7) set key done in WPA2/WPA2PSK.
[I] Dec 14 03:19:46 ndhcps: DHCPREQUEST received (STATE_INIT) for 192.168.1.72 from 84:98:66:7d:47:f7.
[I] Dec 14 03:19:46 ndhcps: sending ACK of 192.168.1.72 to 84:98:66:7d:47:f7.
[I] Dec 14 03:22:17 ndhcpc: GigabitEthernet1: received ACK for 128.69.162.247 from 78.107.125.141.
[I] Dec 14 03:27:17 ndhcpc: GigabitEthernet1: received ACK for 128.69.162.247 from 78.107.125.141.
[I] Dec 14 03:28:37 ndm: UPnP::Manager: a new nat rule appended.
[I] Dec 14 03:28:37 ndm: UPnP::Manager: redirect rule added: udp GigabitEthernet1:52599 -> 192.168.1.41:52599.
[I] Dec 14 03:28:37 ndm: UPnP::Manager: a new filter rule appended.
[I] Dec 14 03:28:37 ndm: UPnP::Manager: forward rule added: udp GigabitEthernet1 -> 192.168.1.41:52599.
[I] Dec 14 03:28:37 ndm: UPnP::Manager: a new nat rule appended.
[I] Dec 14 03:28:37 ndm: UPnP::Manager: redirect rule added: tcp GigabitEthernet1:52599 -> 192.168.1.41:52599.
[I] Dec 14 03:28:37 ndm: UPnP::Manager: a new filter rule appended.
[I] Dec 14 03:28:37 ndm: UPnP::Manager: forward rule added: tcp GigabitEthernet1 -> 192.168.1.41:52599.
[I] Dec 14 03:32:17 ndhcpc: GigabitEthernet1: received ACK for 128.69.162.247 from 78.107.125.141.
[I] Dec 14 03:57:18 ndhcpc: Core::Syslog: last message repeated 5 times.
[I] Dec 14 03:58:38 ndm: UPnP::Manager: redirect and forward rules deleted: udp 52599.
[I] Dec 14 03:58:38 ndm: UPnP::Manager: a new nat rule appended.
[I] Dec 14 03:58:38 ndm: UPnP::Manager: redirect rule added: udp GigabitEthernet1:52599 -> 192.168.1.41:52599.
[I] Dec 14 03:58:38 ndm: UPnP::Manager: a new filter rule appended.
[I] Dec 14 03:58:38 ndm: UPnP::Manager: forward rule added: udp GigabitEthernet1 -> 192.168.1.41:52599.
[I] Dec 14 03:58:38 ndm: UPnP::Manager: redirect and forward rules deleted: tcp 52599.
[I] Dec 14 03:58:38 ndm: UPnP::Manager: a new nat rule appended.
[I] Dec 14 03:58:38 ndm: UPnP::Manager: redirect rule added: tcp GigabitEthernet1:52599 -> 192.168.1.41:52599.
[I] Dec 14 03:58:38 ndm: UPnP::Manager: a new filter rule appended.
[I] Dec 14 03:58:38 ndm: UPnP::Manager: forward rule added: tcp GigabitEthernet1 -> 192.168.1.41:52599.
[I] Dec 14 04:02:16 ndm: PingCheck::Profile: interface ISP connection check failed.
[I] Dec 14 04:02:16 upnp: shutting down MiniUPnPd
[I] Dec 14 04:02:16 ndm: Core::Server: client disconnected.

 

Link to comment
Share on other sites

4 answers to this question

Recommended Posts

  • 1
3 часа назад, Igor Antarov сказал:

2.10.C.1.0-0  
Работало все с последним аптаймом два месяца.  Потом почти двое суток на провайдере был ремонт. 
Сейчас интернет работает 50 минут после загрузки роутера, потом обрывается. 
Провайдер уверяет что на их строне все ОК. 

Где вообе искать концы?

Влючайте режим отладки и прикрепляйте self-test после возникновения ошибки.

  • Thanks 1
Link to comment
Share on other sites

  • 1
Только что, Igor Antarov сказал:

 

 

Спасибо сделал, прикрепил. Сам сообщения не вижу теперь, надеюсь оно есть. :)

Интернет все-также отпадает стабильно раз в 50 минут. (

Посоветуете команду на рестарт соединения на роутере пока причина не ясна?  Чтобы каждый раз не ждать перезагрузки. 

У вас по какой-то причине перестает работать ping-check. Зачем он вам, если в вашей конфигурации есть только один WAN-интерфейс? Попробуйте его отключить.

  • Thanks 1
Link to comment
Share on other sites

  • 0
15 hours ago, sergeyk said:

Влючайте режим отладки и прикрепляйте self-test после возникновения ошибки.

 

 

Спасибо сделал, прикрепил. Сам сообщения не вижу теперь, надеюсь оно есть. :)

Интернет все-также отпадает стабильно раз в 50 минут. (

Посоветуете команду на рестарт соединения на роутере пока причина не ясна?  Чтобы каждый раз не ждать перезагрузки. 

Link to comment
Share on other sites

  • 0
2 hours ago, sergeyk said:

У вас по какой-то причине перестает работать ping-check. Зачем он вам, если в вашей конфигурации есть только один WAN-интерфейс? Попробуйте его отключить.

Точно, загадка про 50 минут решилась,  600 секунд по 5 раз = 50 минут (см. скриншот). 

Спасибо!  Вопрос на заметку разработчикам: - зачем оно роняет канал после того как несрабатывает? :)
Большое спасибо за помощь, тему можно закрывать :)  Вы - лучшие. 

PS (оффтопик): Напомнило древнюю историю про 500-мильную почту: https://rauf.livejournal.com/23552.html

 

image.png.d771f4a56a0e9e5b2298c8d130b8aeb4.png

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

  • Recently Browsing   0 members

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