search

Ysurac / openmptcprouter

OpenMPTCProuter is an open source solution to aggregate multiple internet connections using Multipath TCP (MPTCP) on OpenWrt
https://www.openmptcprouter.com/
GNU General Public License v3.0
1.8k stars 258 forks source link

Wan1 is reported as DOWN but isn't #966

Closed bernic closed 4 years ago

bernic commented 4 years ago

Expected Behavior

Report the real state of the interface

Current Behavior

Wan1 is always reported as down after a few minutes of functioning (restart router and everything is reported as working for a few minutes) This is reported in System/OpenMtcpRouter/ State(tab) But you can tell it is not down as if you start downloading something on internet you can see a lot of traffic going through it in State/Real time traffic

Possible Solution

Steps to Reproduce the Problem

I suppose it is linked to my devices especially my sagemcom modem since there is no issue with my LTE modem:

My setting: 1 SAGEMCOM modem/router (=WAN1) 1 NETGEAR LTE modem LB2120 (=WAN2) 1 Atom nuc running OMR 1 netgear 3500WRL running advance tomato

All above network appliances are connected via ethernet to the SAGEMCOM modem

All connected devices of the house (like computers,NAS...) are connected through the Netgear 3500WRL

It would seem that SAGEMCOM modem as some reserved address : it cannot adress anything between 2 and 10 (168.192.0.10 is the first ip that can be given by its dhcp) but for instance it has a dlna service that is linked to 168.192.0.5

So I made sure that OMR is using 168.192.0.11 on Wan1 it seems that it solved a few issues (but I am not sure yet: everytime I though it was working it broke after a certain time)

Context (Environment)

Slightly annoying because I am never sure I am running on my 4G connection alone because the Wan1 is effectively down or not.

Specifications

OpenMPTCProuter version: v0.54.7 OpenMPTCProuter VPS version: 0.1015 4.19.54-mptcp OpenMPTCProuter platform: x86

Ysurac commented 4 years ago

To check state of an interface by default ICMP Ping is used. Check that ICMP is not blocked somewhere or use another method in omr-tracker for this interface. You can also check in State->System log why the interface is show as down.

bernic commented 4 years ago

Ok I will try to set another method The strange thing with my modem is that at first it respond to ping , but after a while it stops. I deactivated the firewall , and the portscan prevention, but it did not change anything. I need to recheck but it seems that it respond to ping again if I turn OMR down and back up. So it doesn't look like a banning feature of some sort.

Is there a prefered way to send you the error log. I have plenty of error indeed but I am not sure if it refers to my issue

De : Ycarus (Yannick Chabanois) notifications@github.com Envoyé : mardi 14 avril 2020 06:15 À : Ysurac/openmptcprouter openmptcprouter@noreply.github.com Cc : bernic bayarder@hotmail.com; Author author@noreply.github.com Objet : Re: [Ysurac/openmptcprouter] Wan1 is reported as DOWN but isn't (#966)

To check state of an interface by default ICMP Ping is used. Check that ICMP is not blocked somewhere or use another method in omr-tracker for this interface. You can also check in State->System log why the interface is show as down.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Ysurac/openmptcprouter/issues/966#issuecomment-613246897, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABPRKAFSLTDPAFZMDUWVT5DRMP5PJANCNFSM4MHH2JIA.

Ysurac commented 4 years ago

On pastebin or paste it here.

bernic commented 4 years ago

ok there are some strange results

[cid:a97e2da8-d2ec-4f23-bd13-6f4f66067d2b] as you can see wan 1 uses a lot of bandwidth but the log says

Tue Apr 14 17:03:15 2020 daemon.info glorytun: starting glorytun vpn instance vpn Tue Apr 14 17:03:30 2020 user.notice post-tracking-post-tracking: wan1 switched off because gateway down and ping from 192.168.0.11 error (4.2.2.1,8.8.8.8,51.25...)

here is the log in more details (most external ip are anonymized by regexp):

Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=tty21, subsystem=tty, sysfspath=/sys/devices/virtual/tty/tty21 Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: event reported: action=add, name=tty21, subsystem=tty Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=tty5, subsystem=tty, sysfspath=/sys/devices/virtual/tty/tty5 Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: event reported: action=add, name=tty5, subsystem=tty Tue Apr 14 07:42:49 2020 daemon.err usbmuxd[10775]: [07:42:49.395][3] usbmuxd v1.1.1 starting up Tue Apr 14 07:42:49 2020 user.notice post-tracking-post-tracking: omrvpn down Tue Apr 14 07:42:49 2020 daemon.err usbmuxd[10775]: [07:42:49.409][3] Initialization complete Tue Apr 14 07:42:49 2020 daemon.err usbmuxd[10775]: [07:42:49.409][3] Enabled exit on SIGUSR1 if no devices are attached. Start a new instance with "--exit" to trigger. Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:49 2020 user.notice SQM: Starting SQM script: simple.qos on tun0, in: 0 Kbps, out: 0 Kbps Tue Apr 14 07:42:49 2020 user.notice SQM: Using generic sqm_start_default function. Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: add serial interface ttyI54: event processed Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI54, subsystem=tty Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=tty11, subsystem=tty, sysfspath=/sys/devices/virtual/tty/tty11 Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: event reported: action=add, name=tty11, subsystem=tty Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=tty58, subsystem=tty, sysfspath=/sys/devices/virtual/tty/tty58 Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: event reported: action=add, name=tty58, subsystem=tty Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: add serial interface ttyI55: event processed Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI55, subsystem=tty Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=tty3, subsystem=tty, sysfspath=/sys/devices/virtual/tty/tty3 Tue Apr 14 07:42:49 2020 user.notice ModemManager: hotplug: event reported: action=add, name=tty3, subsystem=tty Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=tty48, subsystem=tty, sysfspath=/sys/devices/virtual/tty/tty48 Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: add serial interface ttyI56: event processed Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: event reported: action=add, name=tty48, subsystem=tty Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI56, subsystem=tty Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyS8, subsystem=tty, sysfspath=/sys/devices/platform/serial8250/tty/ttyS8 Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyS8, subsystem=tty Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: add serial interface ttyI57: event processed Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI57, subsystem=tty Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=tty38, subsystem=tty, sysfspath=/sys/devices/virtual/tty/tty38 Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: event reported: action=add, name=tty38, subsystem=tty Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=sit0, subsystem=net, sysfspath=/sys/devices/virtual/net/sit0 Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: event reported: action=add, name=sit0, subsystem=net Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: add serial interface ttyI58: event processed Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI58, subsystem=tty Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ifb0, subsystem=net, sysfspath=/sys/devices/virtual/net/ifb0 Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ifb0, subsystem=net Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:50 2020 user.notice post-tracking-post-tracking: Set server vps (5xx.xxx.xxx.xxx) route via 192.168.0.1 metric 3 Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: add serial interface ttyI59: event processed Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI59, subsystem=tty Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ifb1, subsystem=net, sysfspath=/sys/devices/virtual/net/ifb1 Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ifb1, subsystem=net Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:50 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:51 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI0, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI0 Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI0, subsystem=tty Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: add serial interface ttyI60: event processed Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI60, subsystem=tty Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI1, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI1 Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI1, subsystem=tty Tue Apr 14 07:42:51 2020 user.notice SQM: simple.qos was started on tun0 successfully Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: add serial interface ttyI61: event processed Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI61, subsystem=tty Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI2, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI2 Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI2, subsystem=tty Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:51 2020 user.notice firewall: Reloading firewall due to ifup of omrvpn (tun0) Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI3, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI3 Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI3, subsystem=tty Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: add serial interface ttyI62: event processed Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI62, subsystem=tty Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI4, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI4 Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI4, subsystem=tty Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: add serial interface ttyI63: event processed Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI5, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI5 Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI63, subsystem=tty Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI5, subsystem=tty Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:51 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI6, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI6 Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI6, subsystem=tty Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI7, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI7 Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI7, subsystem=tty Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: add network interface teql0: event processed Tue Apr 14 07:42:52 2020 user.err vnstat_backup: cannot restore, backup file does not exist (yet) Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: event reported: action=add, name=teql0, subsystem=net Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:52 2020 user.notice adb-enablemodem: INFO: waiting for device Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI8, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI8 Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI8, subsystem=tty Tue Apr 14 07:42:52 2020 daemon.notice procd: /etc/rc.d/S99omr-6in4: net.ipv6.conf.all.disable_ipv6 = 1 Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:52 2020 user.notice omr-6in4: Disable IPv6 Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: add network interface eth0: event processed Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI9, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI9 Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: event reported: action=add, name=eth0, subsystem=net Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI9, subsystem=tty Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI10, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI10 Tue Apr 14 07:42:52 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI10, subsystem=tty Tue Apr 14 07:42:52 2020 user.notice omr-bypass: Starting OMR-ByPass... Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: add network interface TMP_IFB_4_SQM: event processed Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: event reported: action=add, name=TMP_IFB_4_SQM, subsystem=net Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI11, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI11 Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI11, subsystem=tty Tue Apr 14 07:42:53 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Done Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:53 2020 daemon.warn [5195]: Invalid sysfs path read for net/TMP_IFB_4_SQM Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: remove network interface TMP_IFB_4_SQM: event processed Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI12, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI12 Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: event reported: action=remove, name=TMP_IFB_4_SQM, subsystem=net Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI12, subsystem=tty Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:53 2020 user.notice Shadowsocks: Rules UP Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI13, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI13 Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: add network interface TMP_IFB_4_SQM: event processed Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI13, subsystem=tty Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: event reported: action=add, name=TMP_IFB_4_SQM, subsystem=net Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:53 2020 daemon.warn [5195]: Invalid sysfs path read for net/TMP_IFB_4_SQM Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI14, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI14 Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI14, subsystem=tty Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: remove network interface TMP_IFB_4_SQM: event processed Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: event reported: action=remove, name=TMP_IFB_4_SQM, subsystem=net Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI15, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI15 Tue Apr 14 07:42:53 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI15, subsystem=tty Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: add network interface TMP_IFB_4_SQM: event processed Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: event reported: action=add, name=TMP_IFB_4_SQM, subsystem=net Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI16, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI16 Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI16, subsystem=tty Tue Apr 14 07:42:54 2020 daemon.warn [5195]: Invalid sysfs path read for net/TMP_IFB_4_SQM Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: remove network interface TMP_IFB_4_SQM: event processed Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: event reported: action=remove, name=TMP_IFB_4_SQM, subsystem=net Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI17, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI17 Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI17, subsystem=tty Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI18, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI18 Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: add network interface TMP_IFB_4_SQM: event processed Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI18, subsystem=tty Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: event reported: action=add, name=TMP_IFB_4_SQM, subsystem=net Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:54 2020 daemon.warn [5195]: Invalid sysfs path read for net/TMP_IFB_4_SQM Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI19, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI19 Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI19, subsystem=tty Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: remove network interface TMP_IFB_4_SQM: event processed Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: event reported: action=remove, name=TMP_IFB_4_SQM, subsystem=net Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI20, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI20 Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI20, subsystem=tty Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: add network interface TMP_IFB_4_SQM: event processed Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:54 2020 user.notice ModemManager: hotplug: event reported: action=add, name=TMP_IFB_4_SQM, subsystem=net Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI21, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI21 Tue Apr 14 07:42:55 2020 daemon.warn [5195]: Invalid sysfs path read for net/TMP_IFB_4_SQM Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI21, subsystem=tty Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: remove network interface TMP_IFB_4_SQM: event processed Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: event reported: action=remove, name=TMP_IFB_4_SQM, subsystem=net Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI22, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI22 Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI22, subsystem=tty Tue Apr 14 07:42:55 2020 user.notice Shadowsocks: Reload omr-bypass rules Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: add network interface wan1: event processed Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: event reported: action=add, name=wan1, subsystem=net Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI23, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI23 Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI23, subsystem=tty Tue Apr 14 07:42:55 2020 user.notice omr-bypass: Starting OMR-ByPass... Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI24, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI24 Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI24, subsystem=tty Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: add network interface wan2: event processed Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: event reported: action=add, name=wan2, subsystem=net Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI25, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI25 Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI25, subsystem=tty Tue Apr 14 07:42:55 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:56 2020 daemon.info unbound: [7752:0] info: service stopped (unbound 1.10.0). Tue Apr 14 07:42:56 2020 daemon.info unbound: [7752:0] info: server stats for thread 0: 17 queries, 0 answers from cache, 17 recursions, 0 prefetch, 0 rejected by ip ratelimiting Tue Apr 14 07:42:56 2020 daemon.info unbound: [7752:0] info: server stats for thread 0: requestlist max 8 avg 1.82353 exceeded 0 jostled 0 Tue Apr 14 07:42:56 2020 daemon.info unbound: [7752:0] info: average recursion processing time 0.072144 sec Tue Apr 14 07:42:56 2020 daemon.info unbound: [7752:0] info: histogram of recursion processing times Tue Apr 14 07:42:56 2020 daemon.info unbound: [7752:0] info: [25%]=0.02048 median[50%]=0.0382293 [75%]=0.12288 Tue Apr 14 07:42:56 2020 daemon.info unbound: [7752:0] info: lower(secs) upper(secs) recursions Tue Apr 14 07:42:56 2020 daemon.info unbound: [7752:0] info: 0.008192 0.016384 3 Tue Apr 14 07:42:56 2020 daemon.info unbound: [7752:0] info: 0.016384 0.032768 5 Tue Apr 14 07:42:56 2020 daemon.info unbound: [7752:0] info: 0.032768 0.065536 3 Tue Apr 14 07:42:56 2020 daemon.info unbound: [7752:0] info: 0.065536 0.131072 2 Tue Apr 14 07:42:56 2020 daemon.info unbound: [7752:0] info: 0.131072 0.262144 4 Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI26, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI26 Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI26, subsystem=tty Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: add network interface tun0: event processed Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: event reported: action=add, name=tun0, subsystem=net Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI27, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI27 Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI27, subsystem=tty Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI28, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI28 Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI28, subsystem=tty Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: add network interface TMP_IFB_4_SQM: event processed Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: event reported: action=add, name=TMP_IFB_4_SQM, subsystem=net Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:56 2020 daemon.warn [5195]: Invalid sysfs path read for net/TMP_IFB_4_SQM Tue Apr 14 07:42:56 2020 daemon.notice unbound: [13546:0] notice: init module 0: iterator Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI29, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI29 Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI29, subsystem=tty Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: remove network interface TMP_IFB_4_SQM: event processed Tue Apr 14 07:42:56 2020 user.notice ModemManager: hotplug: event reported: action=remove, name=TMP_IFB_4_SQM, subsystem=net Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI30, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI30 Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI30, subsystem=tty Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: add network interface TMP_IFB_4_SQM: event processed Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: event reported: action=add, name=TMP_IFB_4_SQM, subsystem=net Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI31, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI31 Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI31, subsystem=tty Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:57 2020 daemon.warn [5195]: Invalid sysfs path read for net/TMP_IFB_4_SQM Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:57 2020 daemon.info unbound: [13546:0] info: start of service (unbound 1.10.0). Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: remove network interface TMP_IFB_4_SQM: event processed Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI32, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI32 Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI32, subsystem=tty Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: event reported: action=remove, name=TMP_IFB_4_SQM, subsystem=net Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI33, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI33 Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI33, subsystem=tty Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: add network interface ifb4tun0: event processed Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ifb4tun0, subsystem=net Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI34, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI34 Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI34, subsystem=tty Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI35, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI35 Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI35, subsystem=tty Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI36, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI36 Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI36, subsystem=tty Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI37, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI37 Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI37, subsystem=tty Tue Apr 14 07:42:57 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI38, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI38 Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI38, subsystem=tty Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI39, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI39 Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI39, subsystem=tty Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI40, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI40 Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI40, subsystem=tty Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI41, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI41 Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI41, subsystem=tty Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI42, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI42 Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI42, subsystem=tty Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI43, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI43 Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI43, subsystem=tty Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI44, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI44 Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI44, subsystem=tty Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI45, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI45 Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI45, subsystem=tty Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI46, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI46 Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI46, subsystem=tty Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI47, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI47 Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI47, subsystem=tty Tue Apr 14 07:42:58 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:59 2020 user.notice post-tracking-post-tracking: Set server vps (5xx.xxx.xxx.xxx) route via 192.168.5.1 metric 4 Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI48, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI48 Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI48, subsystem=tty Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI49, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI49 Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI49, subsystem=tty Tue Apr 14 07:42:59 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI50, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI50 Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI50, subsystem=tty Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI51, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI51 Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI51, subsystem=tty Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI52, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI52 Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI52, subsystem=tty Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI53, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI53 Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI53, subsystem=tty Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:59 2020 daemon.info omr-tracker-ss: Shadowsocks is down (can't contact via http 1.1.1.1, 1.0.0.1, 5xx.xxx.xxx.xxx) Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI54, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI54 Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI54, subsystem=tty Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI55, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI55 Tue Apr 14 07:42:59 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI55, subsystem=tty Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI56, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI56 Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI56, subsystem=tty Tue Apr 14 07:43:00 2020 user.notice OMR-VPS: Can't get token, try later Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI57, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI57 Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI57, subsystem=tty Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI58, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI58 Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI58, subsystem=tty Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI59, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI59 Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI59, subsystem=tty Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI60, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI60 Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI60, subsystem=tty Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI61, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI61 Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI61, subsystem=tty Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI62, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI62 Tue Apr 14 07:43:00 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI62, subsystem=tty Tue Apr 14 07:43:01 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:43:01 2020 user.notice omr-bypass: Restart dnsmasq... Tue Apr 14 07:43:01 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=ttyI63, subsystem=tty, sysfspath=/sys/devices/virtual/tty/ttyI63 Tue Apr 14 07:43:01 2020 user.notice ModemManager: hotplug: event reported: action=add, name=ttyI63, subsystem=tty Tue Apr 14 07:43:01 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:43:01 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=teql0, subsystem=net, sysfspath=/sys/devices/virtual/net/teql0 Tue Apr 14 07:43:01 2020 user.notice ModemManager: hotplug: event reported: action=add, name=teql0, subsystem=net Tue Apr 14 07:43:01 2020 daemon.info dnsmasq[3443]: exiting on receipt of SIGTERM Tue Apr 14 07:43:01 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:43:01 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=eth0, subsystem=net, sysfspath=/sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0/net/eth0 Tue Apr 14 07:43:01 2020 user.notice ModemManager: hotplug: event reported: action=add, name=eth0, subsystem=net Tue Apr 14 07:43:01 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:43:01 2020 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses! Tue Apr 14 07:43:01 2020 user.notice ModemManager: hotplug: cached event found: action=add, name=TMP_IFB_4_SQM, subsystem=net, sysfspath=/sys/devices/virtual/net/TMP_IFB_4_SQM Tue Apr 14 07:43:01 2020 user.notice ModemManager: hotplug: event reported: action=add, name=TMP_IFB_4_SQM, subsystem=net Tue Apr 14 07:43:01 2020 user.notice dnsmasq: Allowing 127.0.0.0/8 responses Tue Apr 14 07:43:01 2020 user.notice dnsmasq: Allowing RFC1918 responses for domain plex.direct Tue Apr 14 07:43:01 2020 daemon.warn [5195]: Invalid sysfs path read for net/TMP_IFB_4_SQM Tue Apr 14 07:43:01 2020 user.notice ModemManager: hotplug: error: parent device sysfspath not found Tue Apr 14 07:43:01 2020 user.notice omr-bypass: OMR-ByPass is running Tue Apr 14 07:43:01 2020 daemon.info dnsmasq[16061]: started, version 2.81rc3 cachesize 150 Tue Apr 14 07:43:01 2020 daemon.info dnsmasq[16061]: DNS service limited to local subnets Tue Apr 14 07:43:01 2020 daemon.info dnsmasq[16061]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC no-ID loop-detect inotify dumpfile Tue Apr 14 07:43:01 2020 daemon.info dnsmasq[16061]: using only locally-known addresses for domain test Tue Apr 14 07:43:01 2020 daemon.info dnsmasq[16061]: using only locally-known addresses for domain onion Tue Apr 14 07:43:01 2020 daemon.info dnsmasq[16061]: using only locally-known addresses for domain localhost Tue Apr 14 07:43:01 2020 daemon.info dnsmasq[16061]: using only locally-known addresses for domain local Tue Apr 14 07:43:01 2020 daemon.info dnsmasq[16061]: using only locally-known addresses for domain invalid Tue Apr 14 07:43:01 2020 daemon.info dnsmasq[16061]: using only locally-known addresses for domain bind Tue Apr 14 07:43:01 2020 daemon.info dnsmasq[16061]: using only locally-known addresses for domain use-application-dns.net Tue Apr 14 07:43:01 2020 daemon.info dnsmasq[16061]: using nameserver 127.0.0.1#5353 Tue Apr 14 07:43:01 2020 daemon.info dnsmasq[16061]: using only locally-known addresses for domain lan Tue Apr 14 07:43:01 2020 daemon.info dnsmasq[16061]: read /etc/hosts - 4 addresses Tue Apr 14 07:43:01 2020 daemon.info dnsmasq[16061]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses Tue Apr 14 07:43:01 2020 user.notice Shadowsocks: Rules DOWN Tue Apr 14 07:43:01 2020 user.notice mptcp: Reloading mptcp config due to ifup of omrvpn (tun0) Tue Apr 14 07:43:02 2020 daemon.notice procd: /etc/rc.d/S99omr-bypass: Another app is currently holding the xtables lock. Perhaps you want to use the -w option? Tue Apr 14 07:43:03 2020 user.notice omr-bypass: Restart dnsmasq... Tue Apr 14 07:43:03 2020 daemon.info dnsmasq[16061]: exiting on receipt of SIGTERM Tue Apr 14 07:43:03 2020 user.notice OMR-VPS: Can't get token, try later Tue Apr 14 07:43:03 2020 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses! Tue Apr 14 07:43:03 2020 user.notice dnsmasq: Allowing 127.0.0.0/8 responses Tue Apr 14 07:43:03 2020 user.notice dnsmasq: Allowing RFC1918 responses for domain plex.direct Tue Apr 14 07:43:03 2020 daemon.info dnsmasq[16342]: started, version 2.81rc3 cachesize 150 Tue Apr 14 07:43:03 2020 user.notice omr-bypass: OMR-ByPass is running Tue Apr 14 07:43:03 2020 daemon.info dnsmasq[16342]: DNS service limited to local subnets Tue Apr 14 07:43:03 2020 daemon.info dnsmasq[16342]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC no-ID loop-detect inotify dumpfile Tue Apr 14 07:43:03 2020 daemon.info dnsmasq[16342]: using only locally-known addresses for domain test Tue Apr 14 07:43:03 2020 daemon.info dnsmasq[16342]: using only locally-known addresses for domain onion Tue Apr 14 07:43:03 2020 daemon.info dnsmasq[16342]: using only locally-known addresses for domain localhost Tue Apr 14 07:43:03 2020 daemon.info dnsmasq[16342]: using only locally-known addresses for domain local Tue Apr 14 07:43:03 2020 daemon.info dnsmasq[16342]: using only locally-known addresses for domain invalid Tue Apr 14 07:43:03 2020 daemon.info dnsmasq[16342]: using only locally-known addresses for domain bind Tue Apr 14 07:43:03 2020 daemon.info dnsmasq[16342]: using only locally-known addresses for domain use-application-dns.net Tue Apr 14 07:43:03 2020 daemon.info dnsmasq[16342]: using nameserver 127.0.0.1#5353 Tue Apr 14 07:43:03 2020 daemon.info dnsmasq[16342]: using only locally-known addresses for domain lan Tue Apr 14 07:43:03 2020 daemon.info dnsmasq[16342]: read /etc/hosts - 4 addresses Tue Apr 14 07:43:03 2020 daemon.info dnsmasq[16342]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses Tue Apr 14 07:43:04 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Done Tue Apr 14 07:43:06 2020 user.notice post-tracking-post-tracking: Tunnel up : Replace default route by 10.255.255.1 dev tun0 Tue Apr 14 07:43:12 2020 daemon.info omr-tracker-ss: Server (5xx.xxx.xxx.xxx) seems down, no answer to ping Tue Apr 14 07:43:22 2020 user.notice post-tracking-post-tracking: Can't find Shadowsocks, restart it... Tue Apr 14 07:43:22 2020 daemon.err omr-tracker[10251]: Command failed: Not found Tue Apr 14 07:43:22 2020 user.notice Shadowsocks: Rules UP Tue Apr 14 07:43:22 2020 user.notice Shadowsocks: Reload omr-bypass rules Tue Apr 14 07:43:22 2020 daemon.info omr-tracker-ss: Shadowsocks is down (can't contact via http 1.1.1.1, 1.0.0.1, 5xx.xxx.xxx.xxx, 5xx.xxx.xxx.xxx, 5xx.xxx.xxx.xxx) Tue Apr 14 07:43:22 2020 user.notice omr-bypass: Starting OMR-ByPass... Tue Apr 14 07:43:24 2020 user.notice omr-bypass: Reload dnsmasq... Tue Apr 14 07:43:24 2020 daemon.info dnsmasq[16342]: read /etc/hosts - 4 addresses Tue Apr 14 07:43:24 2020 daemon.info dnsmasq[16342]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses Tue Apr 14 07:43:24 2020 user.notice omr-bypass: OMR-ByPass is running Tue Apr 14 07:43:24 2020 user.notice Shadowsocks: Rules DOWN Tue Apr 14 07:43:24 2020 user.info : using tcp fast open Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17684]: enable TCP no-delay Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17684]: resolving hostname to IPv6 address first Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17684]: initializing ciphers... aes-256-gcm Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17684]: listening at 0.0.0.0:1100 Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17684]: tcp port reuse enabled Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17684]: UDP relay enabled Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17684]: udp port reuse enabled Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17684]: running from root user Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-local[17683]: using tcp fast open Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-local[17683]: enable TCP no-delay Tue Apr 14 07:43:24 2020 user.info : using tcp fast open Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17685]: enable TCP no-delay Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17685]: resolving hostname to IPv6 address first Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17685]: initializing ciphers... aes-256-gcm Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17685]: listening at 0.0.0.0:1100 Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17685]: tcp port reuse enabled Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17685]: UDP relay enabled Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17685]: udp port reuse enabled Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-redir[17685]: running from root user Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-local[17683]: initializing ciphers... aes-256-gcm Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-local[17683]: listening at 127.0.0.1:1111 Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-local[17683]: tcp port reuse enabled Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-local[17683]: udprelay enabled Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-local[17683]: udp port reuse enabled Tue Apr 14 07:43:24 2020 daemon.info /usr/bin/ss-local[17683]: running from root user Tue Apr 14 07:43:28 2020 daemon.notice procd: /etc/rc.d/S99openmptcprouter-vps: % Total % Received % Xferd Average Speed Time Time Time Current Tue Apr 14 07:43:28 2020 daemon.notice procd: /etc/rc.d/S99openmptcprouter-vps: Dload Upload Total Spent Left Speed Tue Apr 14 07:43:28 2020 daemon.err /usr/bin/ss-local[17683]: getpeername: Socket not connected Tue Apr 14 07:43:31 2020 daemon.notice procd: /etc/rc.d/S99openmptcprouter-vps: 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:03 --:--:-- 0 Tue Apr 14 07:43:31 2020 daemon.notice procd: /etc/rc.d/S99openmptcprouter-vps: curl: (28) Connection timed out after 3001 milliseconds Tue Apr 14 07:43:31 2020 user.notice OMR-VPS: Can't get token, try later (can't ping server, no server API answer) Tue Apr 14 07:43:31 2020 user.notice Shadowsocks: Rules UP Tue Apr 14 07:43:32 2020 user.notice Shadowsocks: Reload omr-bypass rules Tue Apr 14 07:43:32 2020 user.notice omr-bypass: Starting OMR-ByPass... Tue Apr 14 07:43:33 2020 user.notice omr-bypass: Reload dnsmasq... Tue Apr 14 07:43:33 2020 daemon.info dnsmasq[16342]: read /etc/hosts - 4 addresses Tue Apr 14 07:43:33 2020 daemon.info dnsmasq[16342]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses Tue Apr 14 07:43:33 2020 user.notice omr-bypass: OMR-ByPass is running Tue Apr 14 07:43:34 2020 daemon.info procd: - init complete - Tue Apr 14 07:43:34 2020 daemon.info vnstatd[18984]: No interfaces found in database, adding available interfaces... Tue Apr 14 07:43:34 2020 daemon.info vnstatd[18984]: Interface "ifb4tun0" added with 1000 Mbit bandwidth limit. Tue Apr 14 07:43:34 2020 daemon.info vnstatd[18984]: Interface "wan2" added with 1000 Mbit bandwidth limit. Tue Apr 14 07:43:34 2020 daemon.info vnstatd[18984]: Interface "wan1" added with 1000 Mbit bandwidth limit. Tue Apr 14 07:43:34 2020 daemon.info vnstatd[18984]: Interface "eth0" added with 1000 Mbit bandwidth limit. Tue Apr 14 07:43:34 2020 daemon.info vnstatd[18984]: Interface "ifb1" added with 1000 Mbit bandwidth limit. Tue Apr 14 07:43:34 2020 daemon.info vnstatd[18984]: Interface "teql0" added with 1000 Mbit bandwidth limit. Tue Apr 14 07:43:34 2020 daemon.info vnstatd[18984]: Interface "tun0" added with 10 Mbit bandwidth limit. Tue Apr 14 07:43:34 2020 daemon.info vnstatd[18984]: Interface "ifb0" added with 1000 Mbit bandwidth limit. Tue Apr 14 07:43:34 2020 daemon.info vnstatd[18984]: -> 8 new interfaces found. Tue Apr 14 07:43:34 2020 daemon.info vnstatd[18984]: Limits can be modified using the configuration file. See "man vnstat.conf". Tue Apr 14 07:43:34 2020 daemon.info vnstatd[18984]: Unwanted interfaces can be removed from monitoring with "vnstat --remove". Tue Apr 14 07:43:34 2020 daemon.info vnstatd[18984]: Info: vnStat daemon 2.4 started. (pid:18984 uid:0 gid:0 64-bit) Tue Apr 14 07:43:34 2020 daemon.info vnstatd[18984]: Info: Monitoring (8): wan2 (1000 Mbit) wan1 (1000 Mbit) tun0 (10 Mbit) teql0 (1000 Mbit) ifb4tun0 (1000 Mbit) ifb1 (1000 Mbit) ifb0 (1000 Mbit) eth0 (1000 Mbit) Tue Apr 14 07:43:38 2020 daemon.info omr-tracker-ss: Server (5xx.xxx.xxx.xxx) seems down, no answer to ping Tue Apr 14 07:43:40 2020 user.notice OMR-VPS: Can't get token, try later (can't ping server, no server API answer) Tue Apr 14 07:43:46 2020 daemon.err /usr/bin/ss-local[17683]: getpeername: Socket not connected Tue Apr 14 07:43:46 2020 daemon.info omr-tracker-ss: Shadowsocks is down (can't contact via http 1.1.1.1, 1.0.0.1, 5xx.xxx.xxx.xxx, 5xx.xxx.xxx.xxx, 5xx.xxx.xxx.xxx, 198.27.92.1) Tue Apr 14 07:43:46 2020 user.notice Shadowsocks: Rules DOWN Tue Apr 14 07:43:50 2020 user.notice OMR-VPS: Can't get token, try later (can't ping server, no server API answer) Tue Apr 14 07:43:50 2020 daemon.err /usr/bin/ss-local[17683]: getpeername: Socket not connected Tue Apr 14 07:43:59 2020 user.notice OMR-VPS: Can't get token, try later (can't ping server, no server API answer) Tue Apr 14 07:44:00 2020 daemon.info omr-tracker-ss: Server (5xx.xxx.xxx.xxx) seems down, no answer to ping Tue Apr 14 07:44:08 2020 daemon.err /usr/bin/ss-local[17683]: getpeername: Socket not connected Tue Apr 14 07:44:08 2020 user.notice OMR-VPS: Can't get token, try later (can't ping server, no server API answer) Tue Apr 14 07:44:10 2020 user.notice post-tracking-post-tracking: Set server vps (5xx.xxx.xxx.xxx) default route via 192.168.0.1 Tue Apr 14 07:44:16 2020 daemon.err /usr/bin/ss-local[17683]: getpeername: Socket not connected Tue Apr 14 07:44:20 2020 user.notice OMR-VPS: Can't get token, try later (can't ping server, no server API answer) Tue Apr 14 07:44:24 2020 daemon.err /usr/bin/ss-local[17683]: getpeername: Socket not connected Tue Apr 14 07:44:29 2020 user.notice OMR-VPS: Can't get token, try later (can't ping server, no server API answer) Tue Apr 14 07:44:33 2020 daemon.err /usr/bin/ss-local[17683]: getpeername: Socket not connected Tue Apr 14 07:44:40 2020 user.notice OMR-VPS: Can't get token, try later (can't ping server, no server API answer) Tue Apr 14 07:44:41 2020 daemon.err /usr/bin/ss-local[17683]: getpeername: Socket not connected Tue Apr 14 07:44:49 2020 daemon.err /usr/bin/ss-local[17683]: getpeername: Socket not connected Tue Apr 14 07:44:50 2020 user.notice OMR-VPS: Can't get token, try later (can't ping server, no server API answer) Tue Apr 14 07:44:57 2020 daemon.err /usr/bin/ss-local[17683]: getpeername: Socket not connected Tue Apr 14 07:45:01 2020 user.notice OMR-VPS: Can't get token, try later (can't ping server, no server API answer) Tue Apr 14 07:45:02 2020 daemon.info omr-tracker-ss: Shadowsocks is up (can contact via http 5xx.xxx.xxx.xxx) Tue Apr 14 07:45:02 2020 daemon.info omr-tracker-ss: Reload Shadowsocks rules Tue Apr 14 07:45:02 2020 user.notice Shadowsocks: Rules UP Tue Apr 14 07:45:03 2020 user.notice Shadowsocks: Reload omr-bypass rules Tue Apr 14 07:45:03 2020 user.notice omr-bypass: Starting OMR-ByPass... Tue Apr 14 07:45:05 2020 user.notice omr-bypass: Reload dnsmasq... Tue Apr 14 07:45:05 2020 daemon.info dnsmasq[16342]: read /etc/hosts - 4 addresses Tue Apr 14 07:45:05 2020 daemon.info dnsmasq[16342]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses Tue Apr 14 07:45:05 2020 user.notice omr-bypass: OMR-ByPass is running Tue Apr 14 08:00:00 2020 cron.err crond[4504]: USER root pid 7355 cmd /etc/init.d/vnstat_backup backup Tue Apr 14 08:02:06 2020 daemon.err /usr/bin/ss-redir[17684]: server recv: Operation timed out Tue Apr 14 08:02:06 2020 daemon.err /usr/bin/ss-redir[17685]: server recv: Host is unreachable Tue Apr 14 08:03:38 2020 daemon.err /usr/bin/ss-redir[17684]: server recv: Host is unreachable Tue Apr 14 08:04:04 2020 daemon.err /usr/bin/ss-redir[17684]: server recv: Host is unreachable Tue Apr 14 08:23:08 2020 daemon.err uhttpd[4942]: luci: accepted login on / for root from 192.168.100.12 Tue Apr 14 08:28:16 2020 user.notice post-tracking-post-tracking: Change master interface from wan1 (84 ms) to wan2 (43 ms) Tue Apr 14 08:28:18 2020 user.notice post-tracking-post-tracking: Change master interface from wan2 (43 ms) to wan1 (12 ms) Tue Apr 14 08:42:30 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Tue Apr 14 08:42:32 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Done Tue Apr 14 08:42:41 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Tue Apr 14 08:42:43 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Done Tue Apr 14 08:44:05 2020 daemon.err /usr/bin/ss-redir[17684]: server recv: Operation timed out Tue Apr 14 08:44:10 2020 daemon.err /usr/bin/ss-redir[17684]: server recv: Operation timed out Tue Apr 14 08:44:26 2020 daemon.err /usr/bin/ss-redir[17684]: server recv: Operation timed out Tue Apr 14 08:44:51 2020 daemon.err /usr/bin/ss-redir[17685]: server recv: Operation timed out Tue Apr 14 09:42:09 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Tue Apr 14 09:42:11 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Tue Apr 14 09:42:14 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Done Tue Apr 14 09:42:16 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Done Tue Apr 14 10:00:00 2020 cron.err crond[4504]: USER root pid 30369 cmd /etc/init.d/vnstat_backup backup Tue Apr 14 10:15:14 2020 daemon.err /usr/bin/ss-redir[17684]: send: Connection reset by peer Tue Apr 14 10:41:43 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Tue Apr 14 10:41:45 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Done Tue Apr 14 10:41:47 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Tue Apr 14 10:41:49 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Done Tue Apr 14 11:41:18 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Tue Apr 14 11:41:20 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Done Tue Apr 14 11:41:21 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Tue Apr 14 11:41:23 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Done Tue Apr 14 12:00:00 2020 cron.err crond[4504]: USER root pid 9956 cmd /etc/init.d/vnstat_backup backup Tue Apr 14 12:16:36 2020 daemon.err /usr/bin/ss-local[17683]: getpeername: Socket not connected Tue Apr 14 12:19:35 2020 daemon.err /usr/bin/ss-local[17683]: getpeername: Socket not connected Tue Apr 14 12:40:53 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Tue Apr 14 12:40:56 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Done Tue Apr 14 12:40:58 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Tue Apr 14 12:41:00 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Done Tue Apr 14 12:45:54 2020 daemon.err /usr/bin/ss-local[17683]: getpeername: Socket not connected Tue Apr 14 13:40:29 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Tue Apr 14 13:40:31 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Done Tue Apr 14 13:40:33 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Tue Apr 14 13:40:36 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Done Tue Apr 14 14:00:00 2020 cron.err crond[4504]: USER root pid 21941 cmd /etc/init.d/vnstat_backup backup Tue Apr 14 14:13:16 2020 daemon.err uhttpd[4942]: luci: accepted login on / for root from 192.168.100.12 Tue Apr 14 14:39:58 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Tue Apr 14 14:40:01 2020 user.notice post-tracking-post-tracking: Get status and settings for wan2... Done Tue Apr 14 14:40:09 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Tue Apr 14 14:40:12 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Done Tue Apr 14 14:41:00 2020 user.notice omr-tracker: Launching... Tue Apr 14 14:41:00 2020 user.notice omr-tracker: Launched Tue Apr 14 14:41:02 2020 user.notice omr-tracker: Launching... Tue Apr 14 14:41:02 2020 user.notice omr-tracker: Launched Tue Apr 14 14:41:04 2020 daemon.info omr-tracker-ss: Shadowsocks is up (can contact via http 1.1.1.1) Tue Apr 14 14:41:07 2020 daemon.info glorytun: starting glorytun vpn instance vpn Tue Apr 14 14:41:18 2020 user.notice post-tracking-post-tracking: wan1 switched off because gateway down and ping from 192.168.0.11 error (4.2.2.1,8.8.8.8,4.2.2.1,8.8.8.8) Tue Apr 14 14:41:18 2020 user.notice post-tracking-post-tracking: Delete default route via 192.168.0.1 dev wan1 Tue Apr 14 14:53:14 2020 daemon.err /usr/bin/ss-redir[17685]: server recv: Operation timed out Tue Apr 14 14:54:23 2020 user.notice omr-tracker: Launching... Tue Apr 14 14:54:24 2020 user.notice omr-tracker: Launched Tue Apr 14 14:54:25 2020 user.notice omr-tracker: Launching... Tue Apr 14 14:54:25 2020 user.notice omr-tracker: Launched Tue Apr 14 14:54:26 2020 daemon.info glorytun: starting glorytun vpn instance vpn Tue Apr 14 14:54:28 2020 daemon.info omr-tracker-ss: Shadowsocks is up (can contact via http 1.1.1.1) Tue Apr 14 14:54:42 2020 user.notice post-tracking-post-tracking: wan1 switched off because gateway down and ping from 192.168.0.11 error (4.2.2.1,8.8.8.8,4.2.2.1,8.8.8.8) Tue Apr 14 14:54:42 2020 user.notice post-tracking-post-tracking: Delete default route via 192.168.0.1 dev wan1 Tue Apr 14 14:59:58 2020 user.notice post-tracking-post-tracking: Set server vps (5xx.xxx.xxx.xxx) default route via 192.168.0.1 Tue Apr 14 14:59:58 2020 user.notice post-tracking-post-tracking: Set server vps (5xx.xxx.xxx.xxx) route via 192.168.0.1 metric 3 Tue Apr 14 14:59:58 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Tue Apr 14 15:00:02 2020 user.notice post-tracking-post-tracking: Get status and settings for wan1... Done Tue Apr 14 15:00:35 2020 daemon.err /usr/bin/ss-redir[17685]: remote recv: Connection reset by peer Tue Apr 14 15:00:37 2020 user.notice post-tracking-post-tracking: wan1 switched off because gateway down and ping from 192.168.0.11 error (8.8.8.8,4.2.2.1,8.8.8.8,4.2.2.1) Tue Apr 14 15:00:37 2020 user.notice post-tracking-post-tracking: Delete default route via 192.168.0.1 dev wan1 Tue Apr 14 15:01:08 2020 daemon.err /usr/bin/ss-redir[17685]: remote recv: Connection reset by peer Tue Apr 14 15:04:4

Ysurac commented 4 years ago

As log said, gateway of wan1 doesn't answer to ping and not possible to ping via wan1 the only 2 IPs available in omr-tracker (why only 2 ips ?).

bernic commented 4 years ago

I first left the default setting but then added my VSP I did not copy past the line were the ip of my VSP appears. the result was the same not possible to ping However I do not understand then why wan 1 has routed 1.5Gb of data vs 200 for wan2

De : Ycarus (Yannick Chabanois) notifications@github.com Envoyé : mardi 14 avril 2020 17:45 À : Ysurac/openmptcprouter openmptcprouter@noreply.github.com Cc : bernic bayarder@hotmail.com; Author author@noreply.github.com Objet : Re: [Ysurac/openmptcprouter] Wan1 is reported as DOWN but isn't (#966)

As log said, gateway of wan1 doesn't answer to ping and not possible to ping via wan1 the only 2 IPs available in omr-tracker (why only 2 ips ?).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Ysurac/openmptcprouter/issues/966#issuecomment-613583913, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABPRKAAOIAP4AHN3ZJTXZ43RMSOLRANCNFSM4MHH2JIA.

bernic commented 4 years ago

I tried to ping wan 1 (192.168.0.1) from my netgear router -> no answer I restarted OMR and tried again -> answer ok

but at the same time in the log I get that Tue Apr 14 18:10:42 2020 user.notice post-tracking-post-tracking: omrvpn down. Replace default route by 192.168.0.1 dev wan1 Tue Apr 14 18:10:44 2020 user.notice post-tracking-post-tracking: wan1 switched off because gateway down and ping from 192.168.0.11 error (4.2.2.1,8.8.8.8,4.2.2.1,8.8.8.8) Tue Apr 14 18:10:44 2020 user.notice post-tracking-post-tracking: Delete default route via 192.168.0.1 dev wan1

I tried to ping from my router and no issue (yet - I guess that at some point it will not get any answer as before I restarted OMR)

De : Ycarus (Yannick Chabanois) notifications@github.com Envoyé : mardi 14 avril 2020 17:45 À : Ysurac/openmptcprouter openmptcprouter@noreply.github.com Cc : bernic bayarder@hotmail.com; Author author@noreply.github.com Objet : Re: [Ysurac/openmptcprouter] Wan1 is reported as DOWN but isn't (#966)

As log said, gateway of wan1 doesn't answer to ping and not possible to ping via wan1 the only 2 IPs available in omr-tracker (why only 2 ips ?).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Ysurac/openmptcprouter/issues/966#issuecomment-613583913, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABPRKAAOIAP4AHN3ZJTXZ43RMSOLRANCNFSM4MHH2JIA.

bernic commented 4 years ago

also note that my router is on the OMR network (with its wan ip set on 192.168.100.12)

De : Ycarus (Yannick Chabanois) notifications@github.com Envoyé : mardi 14 avril 2020 17:45 À : Ysurac/openmptcprouter openmptcprouter@noreply.github.com Cc : bernic bayarder@hotmail.com; Author author@noreply.github.com Objet : Re: [Ysurac/openmptcprouter] Wan1 is reported as DOWN but isn't (#966)

As log said, gateway of wan1 doesn't answer to ping and not possible to ping via wan1 the only 2 IPs available in omr-tracker (why only 2 ips ?).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Ysurac/openmptcprouter/issues/966#issuecomment-613583913, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABPRKAAOIAP4AHN3ZJTXZ43RMSOLRANCNFSM4MHH2JIA.

bernic commented 4 years ago

I am also easily accessing http://192.168.5.1 the LTE router interface but never the wire router interface http://192.168.0.1http://192.168.5.1

De : Ycarus (Yannick Chabanois) notifications@github.com Envoyé : mardi 14 avril 2020 17:45 À : Ysurac/openmptcprouter openmptcprouter@noreply.github.com Cc : bernic bayarder@hotmail.com; Author author@noreply.github.com Objet : Re: [Ysurac/openmptcprouter] Wan1 is reported as DOWN but isn't (#966)

As log said, gateway of wan1 doesn't answer to ping and not possible to ping via wan1 the only 2 IPs available in omr-tracker (why only 2 ips ?).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Ysurac/openmptcprouter/issues/966#issuecomment-613583913, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABPRKAAOIAP4AHN3ZJTXZ43RMSOLRANCNFSM4MHH2JIA.

Ysurac commented 4 years ago

I understand nothing to your network now...

bernic commented 4 years ago

I don't know if it makes sens:

[cid:03d1c8b8-fa0f-4172-bb0f-2c548f3ac0dd]

De : Ycarus (Yannick Chabanois) notifications@github.com Envoyé : mardi 14 avril 2020 18:50 À : Ysurac/openmptcprouter openmptcprouter@noreply.github.com Cc : bernic bayarder@hotmail.com; Author author@noreply.github.com Objet : Re: [Ysurac/openmptcprouter] Wan1 is reported as DOWN but isn't (#966)

I understand nothing to your network now...

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Ysurac/openmptcprouter/issues/966#issuecomment-613618377, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABPRKAGS5I6GOOEUFUYDP3LRMSWAFANCNFSM4MHH2JIA.

bernic commented 4 years ago

though I am not sure the lte router get this 192.168.0.16 adress I just happen to see it on the sagemcom modem interface as there is only 3 devices listed on it: -the netgear router on which I temporarily ste the wan ip to 192.168.0.12 to access the sagemcom interface (otherwise no access) -OMR and I can see a 3rd on with this ip 192.168.0.16 I supposed it was the LTE router though I never did set this adress my self and in the router the only ip that I set is 192.168.5.1 So I am a bit surprised I will double check with the mac adress

De : Ycarus (Yannick Chabanois) notifications@github.com Envoyé : mardi 14 avril 2020 18:50 À : Ysurac/openmptcprouter openmptcprouter@noreply.github.com Cc : bernic bayarder@hotmail.com; Author author@noreply.github.com Objet : Re: [Ysurac/openmptcprouter] Wan1 is reported as DOWN but isn't (#966)

I understand nothing to your network now...

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Ysurac/openmptcprouter/issues/966#issuecomment-613618377, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABPRKAGS5I6GOOEUFUYDP3LRMSWAFANCNFSM4MHH2JIA.

Ysurac commented 4 years ago

I think the schema is missing.

bernic commented 4 years ago

Here is my network schematic (hope you can see it):

Mean while I rebooted OMR but did not turn on the 4G modem router and since then the SAGEMCOM MODEM ROUTER has been online all along with no issue, I can even access its interface to change the settings So I start to believe there is an issue when both Modems are on. when both are on I have access to both for only a short time after which I can only access the 4G LTE modem. Pinging to or through SAGEMCOM seems not to work but the interface also reports more data going through SAGEMCOM modem than 4G modem

At the same time if I change the Wan of my tomato router to 192.168.0.1 to be able to reach the sagemcom modem I notice that the dhcp server is leasing 3 ip: 192.168.0.11 (OMR) 192.168.0.12 (tomato router) 192.168.0.16 ??? only the 4G LTE is plugged on top of OMR and tomato router, but this adress could be given to a service of SAGEMCOM (like dlna server,... though I deactivated all the services I found)

[cid:34a26617-c623-43eb-8c90-3b1330ba9c73]

De : Ycarus (Yannick Chabanois) notifications@github.com Envoyé : mercredi 15 avril 2020 07:35 À : Ysurac/openmptcprouter openmptcprouter@noreply.github.com Cc : bernic bayarder@hotmail.com; Author author@noreply.github.com Objet : Re: [Ysurac/openmptcprouter] Wan1 is reported as DOWN but isn't (#966)

I think the schema is missing.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Ysurac/openmptcprouter/issues/966#issuecomment-613870180, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABPRKAEIDH3ZH6FEU2FHE3LRMVPVFANCNFSM4MHH2JIA.

bnhf commented 4 years ago

My setting: 1 SAGEMCOM modem/router (=WAN1) 1 NETGEAR LTE modem LB2120 (=WAN2) 1 Atom nuc running OMR 1 netgear 3500WRL running advance tomato

All above network appliances are connected via ethernet to the SAGEMCOM modem

All connected devices of the house (like computers,NAS...) are connected through the Netgear 3500WRL

I'll suggest that some, if not all, of your issues are related to the way you're making your connections. Given that OMR is a router too, you need to separate your LAN and WAN traffic, either physically (using separate adapters), or virtually (using VLANs or Macvlan).

If your OMR router has sufficient Ethernet ports, you should make your connections like so:

bernic network

If your OMR router doesn't have sufficient Ethernet ports then you could use an unmanaged switch to physically connect everything, but then you'll need to setup VLANs or Macvlan to keep the traffic sorted. Trying to use the SAGEMCOM router as that switch is likely to cause issues.

bernic commented 4 years ago

Yes I thought so but I have no spare switch... and only one physical interface on the OMR

If I can get a switch, how should I set MacVlan, from what I saw they are already 2 macvlan attributed by ORM for each of the wan interface aren't they?

is there some doc you would recommend me to make this setup?

anyway a big thank you for your help

De : bnhf notifications@github.com Envoyé : mercredi 15 avril 2020 15:44 À : Ysurac/openmptcprouter openmptcprouter@noreply.github.com Cc : bernic bayarder@hotmail.com; Author author@noreply.github.com Objet : Re: [Ysurac/openmptcprouter] Wan1 is reported as DOWN but isn't (#966)

My setting: 1 SAGEMCOM modem/router (=WAN1) 1 NETGEAR LTE modem LB2120 (=WAN2) 1 Atom nuc running OMR 1 netgear 3500WRL running advance tomato

All above network appliances are connected via ethernet to the SAGEMCOM modem

All connected devices of the house (like computers,NAS...) are connected through the Netgear 3500WRL

I'll suggest that some, if not all, of your issues are related to the way you're making your connections. Given that OMR is a router too, you need to separate your LAN and WAN traffic, either physically (using separate adapters), or virtually (using VLANs or Macvlan).

If your OMR router has sufficient Ethernet ports, you should make your connections like so:

[bernic network]https://user-images.githubusercontent.com/41088895/79355561-aeea5680-7ef2-11ea-9eea-e05822994eab.png

If your OMR router doesn't have sufficient Ethernet ports then you could use an unmanaged switch to physically connect everything, but then you'll need to setup VLANs or Macvlan to keep the traffic sorted. Trying to use the SAGEMCOM router as that switch is likely to cause issues.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Ysurac/openmptcprouter/issues/966#issuecomment-614117879, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABPRKAHZW66DQIILYQEQXFDRMXI6HANCNFSM4MHH2JIA.

bnhf commented 4 years ago

If I can get a switch, how should I set MacVlan, from what I saw they are already 2 macvlan attributed by ORM for each of the wan interface aren't they?

Macvlan allows you to create virtual adapters that share physical interfaces. So you could have virtual adapters named wan1 and wan2 (not to be confused with the network interfaces of the same name) each assigned to physical adapter eth0. Theoretically, you could also have a virtual adapter called lan assign to that same eth0, though I haven't tried it.

Under Network - Interfaces - LAN, then change the physical adapter assignment to the virtual adapter named lan. Re-run the OMR Wizard, and change the interface assignment of WAN1 to wan1, and WAN2 to wan2. Check that the IP addresses of the gateway routers are correct, and assign a static address to each in that gateway's same subnet. I think you'll find you can now turn off DHCP on the SAGEMCOM and LTE routers without the stability issues you reported previously.

bnhf commented 4 years ago

Theoretically, you could also have a virtual adapter called lan assign to that same eth0, though I haven't tried it.

Just wanted to expand on this a little bit. When I've used Macvlan, I've always had two adapters, one for LAN and one for all WANs. As I said in my previous post, I believe you can make it work with a single Etherent port too using Macvlan -- but maybe @Ysurac or somebody that has such a configuration in use can confirm this.

Ysurac commented 4 years ago

Yes, macvlan can be used on a single ethernet port (like on RPI).

bernic commented 4 years ago

HI thank you for the answer What I meant is I think everything is already correctly set and was wondering if I missed something, but from your answer I think I did not miss anything. I have a lan and 2 wan interfaces already set If I con under MacVlan menu I can see that eth0 is assigned wan1 and wan2 I can see I have 3 different MAc adress for my one and only ethernet port: the lan mac adress and the 2 macvlan adresses. As for the Dhcp servers I had already deactivated all dhcp server except on the tomato router and SAGEMCOM modem/router I have further deactivated the SAGEMCOM dhcp server - no more dhcp except for the tomato router

So anyway I found a switch and plugged every thing on it : The neatgear tomato router The SAGEMCOM modem router The 4G LTE modem router the atom nuc OMR

and I could see and access all these devices from any computer behind the tomato router !!! Great... Except that The SAGEMCOM is still reported as down from OMR interface and in the SAGEMCOM interface the wan interface is reported as ip 0.0.0.0 with 255.0.0.0 as subnet masq Very stange because I can use the phone plugged on the modem without issue, so it must some how be connected. I suppose there are some Vlan behind it that mangle things up.

I made a test: I restarted SAGEMCOM modem : no difference I turned off the 4G modem and restarted the SAGEMCOM modem -> no more issue with SAGEMCOM

I turned the 4G modem back on -> back to previous state no more ping no more access to SAGEMCOM

But now I looked at the routing table and I think that Something is definitively going wrong [cid:image002.png@01D614B9.84CBC3A0] (The 198.168.1.1 is now the 4G router adress)

De : bnhf notifications@github.com Envoyé : mercredi 15 avril 2020 22:02 À : Ysurac/openmptcprouter openmptcprouter@noreply.github.com Cc : bernic bayarder@hotmail.com; Author author@noreply.github.com Objet : Re: [Ysurac/openmptcprouter] Wan1 is reported as DOWN but isn't (#966)

If I can get a switch, how should I set MacVlan, from what I saw they are already 2 macvlan attributed by ORM for each of the wan interface aren't they?

Macvlan allows you to create virtual adapters that share physical interfaces. So you could have virtual adapters named wan1 and wan2 (not to be confused with the network interfaces of the same name) each assigned to physical adapter eth0. Theoretically, you could also have a virtual adapter called lan assign to that same eth0, though I haven't tried it.

Under Network - Interfaces - LAN, then change the physical adapter assignment to the virtual adapter named lan. Re-run the OMR Wizard, and change the interface assignment of WAN1 to wan1, and WAN2 to wan2. Check that the IP addresses of the gateway routers are correct, and assign a static address to each in that gateway's same subnet. I think you'll find you can now turn off DHCP on the SAGEMCOM and LTE routers without the stability issues you reported previously.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Ysurac/openmptcprouter/issues/966#issuecomment-614302421, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABPRKACV4TUPXQW2YQDEXBTRMYVIBANCNFSM4MHH2JIA.

bernic commented 4 years ago

I have these warning in the SAGEMCOM modem at same time

16/04/2020 à 23:14:54 DHCP WARNING - Non-critical field invalid in response ;CM-MAC=f4:6b:ef:5a:66:f0;CMTS-MAC=00:01:5c:87:59:a5;CM-QOS=1.1;CM-VER=... 17/04/2020 à 12:18:11 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=f4:6b:ef:5a:66:f0;CMTS-MAC=00:01:5c:87:59:a5;CM-QOS=1.1;CM-VER=3.0; Even when removing my tomato router and Following the doc exactly I get same result Wan1 is lost The doc suppose we run OMR on a Raspberry Pi so I suppose this means it only has one physical port unless you add a shield. So I suppose I should be in the same configuration then.

If I go in the OMR interface and restart wan1 interface I can reconnect to wan1 as normal but it only last a few seconds

Provenance : Courrierhttps://go.microsoft.com/fwlink/?LinkId=550986 pour Windows 10

De : Eric Bayardmailto:bayarder@hotmail.com Envoyé le :vendredi 17 avril 2020 13:10 À : Ysurac/openmptcproutermailto:reply@reply.github.com Objet :RE: [Ysurac/openmptcprouter] Wan1 is reported as DOWN but isn't (#966)

HI thank you for the answer What I meant is I think everything is already correctly set and was wondering if I missed something, but from your answer I think I did not miss anything. I have a lan and 2 wan interfaces already set If I con under MacVlan menu I can see that eth0 is assigned wan1 and wan2 I can see I have 3 different MAc adress for my one and only ethernet port: the lan mac adress and the 2 macvlan adresses. As for the Dhcp servers I had already deactivated all dhcp server except on the tomato router and SAGEMCOM modem/router I have further deactivated the SAGEMCOM dhcp server - no more dhcp except for the tomato router

So anyway I found a switch and plugged every thing on it : The neatgear tomato router The SAGEMCOM modem router The 4G LTE modem router the atom nuc OMR

and I could see and access all these devices from any computer behind the tomato router !!! Great... Except that The SAGEMCOM is still reported as down from OMR interface and in the SAGEMCOM interface the wan interface is reported as ip 0.0.0.0 with 255.0.0.0 as subnet masq Very stange because I can use the phone plugged on the modem without issue, so it must some how be connected. I suppose there are some Vlan behind it that mangle things up.

I made a test: I restarted SAGEMCOM modem : no difference I turned off the 4G modem and restarted the SAGEMCOM modem -> no more issue with SAGEMCOM

I turned the 4G modem back on -> back to previous state no more ping no more access to SAGEMCOM

But now I looked at the routing table and I think that Something is definitively going wrong [cid:image005.png@01D614C1.B1C8D160] (The 198.168.1.1 is now the 4G router adress)

De : bnhf notifications@github.com Envoyé : mercredi 15 avril 2020 22:02 À : Ysurac/openmptcprouter openmptcprouter@noreply.github.com Cc : bernic bayarder@hotmail.com; Author author@noreply.github.com Objet : Re: [Ysurac/openmptcprouter] Wan1 is reported as DOWN but isn't (#966)

If I can get a switch, how should I set MacVlan, from what I saw they are already 2 macvlan attributed by ORM for each of the wan interface aren't they?

Macvlan allows you to create virtual adapters that share physical interfaces. So you could have virtual adapters named wan1 and wan2 (not to be confused with the network interfaces of the same name) each assigned to physical adapter eth0. Theoretically, you could also have a virtual adapter called lan assign to that same eth0, though I haven't tried it.

Under Network - Interfaces - LAN, then change the physical adapter assignment to the virtual adapter named lan. Re-run the OMR Wizard, and change the interface assignment of WAN1 to wan1, and WAN2 to wan2. Check that the IP addresses of the gateway routers are correct, and assign a static address to each in that gateway's same subnet. I think you'll find you can now turn off DHCP on the SAGEMCOM and LTE routers without the stability issues you reported previously.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Ysurac/openmptcprouter/issues/966#issuecomment-614302421, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABPRKACV4TUPXQW2YQDEXBTRMYVIBANCNFSM4MHH2JIA.

bernic commented 4 years ago

So now I found a usb hub with a ethernet plug I plugged it in OMR and it was recognized straight away as eth1 So I set lan on eth0 And wan1 and wan2 on eth1

My network now looks like : [cid:image003.png@01D614C7.6E1B5220]

But exact same issue Wan1 unreachable… well if I restart it, it is reachable for a few second

Provenance : Courrierhttps://go.microsoft.com/fwlink/?LinkId=550986 pour Windows 10

De : Ycarus (Yannick Chabanois)mailto:notifications@github.com Envoyé le :jeudi 16 avril 2020 16:24 À : Ysurac/openmptcproutermailto:openmptcprouter@noreply.github.com Cc : bernicmailto:bayarder@hotmail.com; Authormailto:author@noreply.github.com Objet :Re: [Ysurac/openmptcprouter] Wan1 is reported as DOWN but isn't (#966)

Yes, macvlan can be used on a single ethernet port (like on RPI).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Ysurac/openmptcprouter/issues/966#issuecomment-614685805, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABPRKAB5TQF3VUUY4EVZH4LRM4IJ3ANCNFSM4MHH2JIA.

bernic commented 4 years ago

Ok I think I found a solution I separated both wan on different physical interfaces

Now my network is

Eth0 lan and wan2 plugged on the switch Eth1 wan1 dirctly pluggedon SAGEMCOM

Both are now reported up and running

I just have a warning that vpn tunel is down on OMR what would that mean/ Imply ?

Thank you

Provenance : Courrierhttps://go.microsoft.com/fwlink/?LinkId=550986 pour Windows 10

De : Ycarus (Yannick Chabanois)mailto:notifications@github.com Envoyé le :jeudi 16 avril 2020 16:24 À : Ysurac/openmptcproutermailto:openmptcprouter@noreply.github.com Cc : bernicmailto:bayarder@hotmail.com; Authormailto:author@noreply.github.com Objet :Re: [Ysurac/openmptcprouter] Wan1 is reported as DOWN but isn't (#966)

Yes, macvlan can be used on a single ethernet port (like on RPI).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/Ysurac/openmptcprouter/issues/966#issuecomment-614685805, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABPRKAB5TQF3VUUY4EVZH4LRM4IJ3ANCNFSM4MHH2JIA.

Ysurac commented 4 years ago

Check that time on VPS and router part are the same.

github-actions[bot] commented 4 years ago

This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 5 days

github-actions[bot] commented 4 years ago

This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 5 days