Closed ccmks closed 4 years ago
I never used Hyper-V. But you can check in State->System log why wan are losing connections.
Here is the log
Wed Mar 18 14:36:37 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:37 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI3, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI3
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI3, subsystem=tty
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI4, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI4
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI4, subsystem=tty
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI5, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI5
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI5, subsystem=tty
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI6, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI6
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI6, subsystem=tty
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI7, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI7
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI7, subsystem=tty
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI8, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI8
Wed Mar 18 14:36:38 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI8, subsystem=tty
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI9, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI9
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI9, subsystem=tty
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI10, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI10
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI10, subsystem=tty
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI11, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI11
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI11, subsystem=tty
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI12, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI12
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI12, subsystem=tty
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI13, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI13
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI13, subsystem=tty
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI14, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI14
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI14, subsystem=tty
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI15, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI15
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI15, subsystem=tty
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI16, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI16
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI16, subsystem=tty
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI17, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI17
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI17, subsystem=tty
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI18, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI18
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI18, subsystem=tty
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI19, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI19
Wed Mar 18 14:36:39 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI19, subsystem=tty
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI20, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI20
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI20, subsystem=tty
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI21, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI21
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI21, subsystem=tty
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI22, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI22
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI22, subsystem=tty
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI23, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI23
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI23, subsystem=tty
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI24, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI24
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI24, subsystem=tty
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI25, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI25
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI25, subsystem=tty
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI26, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI26
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI26, subsystem=tty
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI27, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI27
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI27, subsystem=tty
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI28, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI28
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI28, subsystem=tty
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI29, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI29
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI29, subsystem=tty
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI30, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI30
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI30, subsystem=tty
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI31, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI31
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI31, subsystem=tty
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI32, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI32
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI32, subsystem=tty
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI33, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI33
Wed Mar 18 14:36:40 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI33, subsystem=tty
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI34, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI34
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI34, subsystem=tty
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI35, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI35
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI35, subsystem=tty
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI36, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI36
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI36, subsystem=tty
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:41 2020 daemon.info glorytun: starting glorytun vpn instance vpn
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI37, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI37
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI37, subsystem=tty
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI38, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI38
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI38, subsystem=tty
Wed Mar 18 14:36:41 2020 daemon.notice netifd: Interface 'omrvpn' is enabled
Wed Mar 18 14:36:41 2020 daemon.notice netifd: Network device 'tun0' link is up
Wed Mar 18 14:36:41 2020 daemon.notice netifd: Interface 'omrvpn' has link connectivity
Wed Mar 18 14:36:41 2020 daemon.notice netifd: Interface 'omrvpn' is setting up now
Wed Mar 18 14:36:41 2020 daemon.info glorytun[11344]: INITIALIZED tun0
Wed Mar 18 14:36:41 2020 daemon.notice netifd: Interface 'omrvpn' is now up
Wed Mar 18 14:36:41 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI39, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI39
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI39, subsystem=tty
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: add network interface tun0: event processed
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: event reported: action=add, name=tun0, subsystem=net
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI40, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI40
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI40, subsystem=tty
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI41, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI41
Wed Mar 18 14:36:42 2020 user.notice firewall: Reloading firewall due to ifup of wan1 (eth1)
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI41, subsystem=tty
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI42, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI42
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI42, subsystem=tty
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI43, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI43
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI43, subsystem=tty
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:42 2020 daemon.err glorytun[11344]: 45.32.101.41.65001: connected
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI44, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI44
Wed Mar 18 14:36:42 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI44, subsystem=tty
Wed Mar 18 14:36:43 2020 daemon.info glorytun[11344]: STARTED tun0
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI45, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI45
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI45, subsystem=tty
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI46, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI46
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI46, subsystem=tty
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI47, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI47
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI47, subsystem=tty
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI48, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI48
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI48, subsystem=tty
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI49, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI49
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI49, subsystem=tty
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI50, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI50
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI50, subsystem=tty
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI51, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI51
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI51, subsystem=tty
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI52, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI52
Wed Mar 18 14:36:43 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI52, subsystem=tty
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI53, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI53
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI53, subsystem=tty
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI54, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI54
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI54, subsystem=tty
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI55, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI55
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI55, subsystem=tty
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI56, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI56
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI56, subsystem=tty
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI57, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI57
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI57, subsystem=tty
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI58, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI58
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI58, subsystem=tty
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI59, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI59
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI59, subsystem=tty
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI60, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI60
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI60, subsystem=tty
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI61, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI61
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI61, subsystem=tty
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI62, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI62
Wed Mar 18 14:36:44 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI62, subsystem=tty
Wed Mar 18 14:36:45 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:45 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI63, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI63
Wed Mar 18 14:36:45 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI63, subsystem=tty
Wed Mar 18 14:36:45 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:45 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=teql0, subsystem=net, sysfspath=/sys/devices/virtual/net/teql0
Wed Mar 18 14:36:45 2020 user.notice ModemManager: hotplug: event reported: action=add, name=teql0, subsystem=net
Wed Mar 18 14:36:45 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:45 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=tun0, subsystem=net, sysfspath=/sys/devices/virtual/net/tun0
Wed Mar 18 14:36:45 2020 user.notice ModemManager: hotplug: event reported: action=add, name=tun0, subsystem=net
Wed Mar 18 14:36:45 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:56 2020 user.notice mptcp: Reloading mptcp config due to ifup of wan1 (eth1)
Wed Mar 18 14:36:59 2020 user.notice SQM: Starting SQM script: simple.qos on tun0, in: 0 Kbps, out: 0 Kbps
Wed Mar 18 14:36:59 2020 user.notice SQM: Using generic sqm_start_default function.
Wed Mar 18 14:36:59 2020 user.notice ModemManager: hotplug: add network interface TMP_IFB_4_SQM: event processed
Wed Mar 18 14:36:59 2020 user.notice ModemManager: hotplug: event reported: action=add, name=TMP_IFB_4_SQM, subsystem=net
Wed Mar 18 14:36:59 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found
Wed Mar 18 14:36:59 2020 daemon.warn [6917]:
You are using MPTCP over VPN ? why ?
My WAN 2 connection doesn't support MPTCP so have to enable over VPN
Without this interface, it's working ?
Same issue too. The random WAN will show gateway down.
I believe this was not a new issue. It happened when I was back then v0.52 version on Sept 2019. However, didn't have a chance to bring it up here until today when I was experimenting with it again.
On the log I only tun4 interface, that is the MPTCP over VPN interface as down. Maybe some problems with the DHCP ? Each wan have own real interface and each real interface have a router directly connected ?
I have been running it for 35 minutes when I generated the log for you. Again, the random WAN disconnection happens.
I don't think it is DHCP issue, because I have setup static IP for the WAN whose GW is down and still can't ping to its gateway.
Answer to last question: It is Hyper-V so all interface is from Hyper-V virtual interface. But each interface is connected to different vSwitch, and each vSwitch is connected to each physical NIC in the Intel PRO 1000 PT Quad NIC. Each NIC in Physical port is connected to each different modem
Can you give me, when there is a disconnection, the result of ip a
and ip r
via SSH on the router ?
I could no longer be able to duplicate the issue.
Apparently, when I read the system log, I realized that I gave too low memory which was only 384 MB, after increase the memory to 512 MB, the issue is no longer there. I will go ahead and close this issue.
Thank you for your help!
Well it happened again!
Here is the output for ip a 1: lo: <LOOPBACK,UP,LOWER_UP,80000> 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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP,80000> mtu 1500 qdisc mq state UP grou p default qlen 1000 link/ether 00:15:5d:05:f7:4a brd ff:ff:ff:ff:ff:ff inet 192.168.100.1/24 brd 192.168.100.255 scope global eth0 valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1244 qdisc mq state UP group defa ult qlen 100 link/ether 00:15:5d:05:f7:4b brd ff:ff:ff:ff:ff:ff inet 192.168.80.24/24 brd 192.168.80.255 scope global eth1 valid_lft forever preferred_lft forever 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP,80000> mtu 1500 qdisc mq state UP grou p default qlen 50 link/ether 00:15:5d:05:f7:4c brd ff:ff:ff:ff:ff:ff inet 192.168.40.102/24 brd 192.168.40.255 scope global eth2 valid_lft forever preferred_lft forever 5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group defa ult qlen 100 link/ether 00:15:5d:05:f7:4d brd ff:ff:ff:ff:ff:ff inet 192.168.8.102/24 brd 192.168.8.255 scope global eth3 valid_lft forever preferred_lft forever 6: eth4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group defa ult qlen 1000 link/ether 00:15:5d:05:f7:4e brd ff:ff:ff:ff:ff:ff 7: sit0@NONE: <NOARP,80000> mtu 1480 qdisc noop state DOWN group default qlen 10 00 link/sit 0.0.0.0 brd 0.0.0.0 8: ifb0: <BROADCAST,NOARP,80000> mtu 1500 qdisc noop state DOWN group default ql en 32 link/ether 5e:7b:bf:be:e9:12 brd ff:ff:ff:ff:ff:ff 9: ifb1: <BROADCAST,NOARP,80000> mtu 1500 qdisc noop state DOWN group default ql en 32 link/ether 0e:d0:d2:1a:d1:86 brd ff:ff:ff:ff:ff:ff 10: teql0: <NOARP,80000> mtu 1500 qdisc noop state DOWN group default qlen 100 link/void 16: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP,80000> mtu 1500 qdisc fq_code l state UNKNOWN group default qlen 1000 link/none inet 10.255.255.2 peer 10.255.255.1/32 scope global tun0 valid_lft forever preferred_lft forever 19: ifb4tun0: <BROADCAST,NOARP,80000> mtu 1500 qdisc noop state DOWN group defau lt qlen 32 link/ether ce:8e:6e:64:61:68 brd ff:ff:ff:ff:ff:ff
Here is the output for ip r default via 10.255.255.1 dev tun0 default via 192.168.40.1 dev eth2 metric 4 default via 192.168.8.1 dev eth3 metric 5 10.255.255.1 dev tun0 proto kernel scope link src 10.255.255.2 45.32.101.41 via 192.168.8.1 dev eth3 metric 5 127.0.0.0/8 dev lo proto static scope link metric 1 192.168.8.0/24 dev eth3 scope link metric 5 192.168.40.0/24 dev eth2 scope link metric 4 192.168.80.0/24 dev eth1 scope link metric 3
512 is still low... eth4 have no IP, normal ? Else there is no error and gateway should be pingable.
We don't have anything on eth4. Only 3 WAN plugged in
The WAN 1 IP GW is not pingable although I already set to DHCP.
If 512 RAM is still low, what would be the minimum?
1024 is better
Already tried 1024 MB, still experiencing random WAN disconnection. I tried plug in 4 WAN, and sometimes, there are 2 WAN experience random disconnection. It happened on random WAN
What is the latency of each interfaces ? (in OpenMPTCProuter status page)
While it's not working, remove MPTCP over VPN, this doesn't help to find the issue.
I am still currently testing on various parameter. My configuration works on Banana Pi R2, however, I decided to use Hyper-V since my router is also hosted there, no need additional hardware plug in. On the top of that, the Banana Pi R2 only works with v0.53, doesn't work higher version.
I have been putting this Hyper-V on different condition, such as adjusting the core and the memory. Right now, the most stable is using 32 bit version of image and using Hyper-V with virtual memory range between 512 - 768 MB, more than that, it could trigger the Gateway Down and not stable too.
However, I still want to see if this could last for several days without having random disconnection on WAN.
Before I was only using single core on virtual processor, however, the throughput was limited, so I ended up using all core of my processor to reach the maximum speed.
I gave up on doing this, ended up migrating my router to different hardware, however, this new hardware, I only have Hyper-V core 2019. The OpenMPTCPRouter is working fine on the new hardware under Hyper-V hosting. I guess, I have to find what's wrong with the old hardware.
Expected Behavior
Stable connection running on Hyper-V and expect to work normally
Actual Behavior
After setup OpenMPTCPRouter and get everything setup, the MPTCP is working fine across 3 different WAN. However, after 5 minutes or so, random WAN (either WAN1, WAN2 or WAN3) losing connection. The status page will show "Gateway Down" on one or 2 WAN connection and it happen randomly on which WAN.
Trying to restart the interface but the router WAN which gateway is down can't ping to its respective gateway. The only way to fix it is to reboot the router again, but still having same problem within 5 minutes after rebooting.
Steps to Reproduce the Problem
Specifications