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

Glorytun Read operation time out. Tunnel down for very short time. #695

Closed Marctraider closed 4 years ago

Marctraider commented 4 years ago

Expected Behavior

Glorytun-udp not malfunctioning/

Actual Behavior

Glorytun-udp malfunctioning and DC?

I wonder if this is a bug with glorytun tho? I dont know why else it would do it. There was no latency increase before it happened either. just totally random.

I run OMR with this in mind: As little as much in background that intentionally disable connection, everything is fixed as much as possible with the idea 'Everything always runs and connected'. Because I dont care for max aggregation speed and I dont care for fallback tech. Both two connections i use now are pretty solid and there is no need for me for fallback option. Hence i disabled Tracker's and all the other gunk.

This might look like a glorytun-udp issue? Not sure...

From client side (Windows)

2019/10/14 03:34:59.097 : Reply[16584] from 8.8.8.8: bytes=32 time=27.0 ms TTL=55 2019/10/14 03:35:00.127 : Reply[16585] from 8.8.8.8: bytes=32 time=29.3 ms TTL=55 2019/10/14 03:35:01.164 : Reply[16586] from 8.8.8.8: bytes=32 time=35.7 ms TTL=55 2019/10/14 03:35:02.199 : Reply[16587] from 8.8.8.8: bytes=32 time=34.9 ms TTL=55 2019/10/14 03:35:03.227 : Reply[16588] from 8.8.8.8: bytes=32 time=27.2 ms TTL=55 2019/10/14 03:35:04.257 : Reply[16589] from 8.8.8.8: bytes=32 time=28.6 ms TTL=55 2019/10/14 03:35:06.257 : 8.8.8.8: request timed out 2019/10/14 03:35:07.258 : 8.8.8.8: request timed out 2019/10/14 03:35:08.258 : 8.8.8.8: request timed out 2019/10/14 03:35:09.259 : 8.8.8.8: request timed out 2019/10/14 03:35:10.259 : 8.8.8.8: request timed out 2019/10/14 03:35:11.260 : 8.8.8.8: request timed out 2019/10/14 03:35:12.260 : 8.8.8.8: request timed out 2019/10/14 03:35:13.261 : 8.8.8.8: request timed out 2019/10/14 03:35:14.261 : 8.8.8.8: request timed out 2019/10/14 03:35:15.261 : 8.8.8.8: request timed out 2019/10/14 03:35:16.262 : 8.8.8.8: request timed out 2019/10/14 03:35:17.264 : 8.8.8.8: request timed out 2019/10/14 03:35:18.265 : 8.8.8.8: request timed out 2019/10/14 03:35:19.265 : 8.8.8.8: request timed out 2019/10/14 03:35:20.266 : 8.8.8.8: request timed out 2019/10/14 03:35:21.266 : 8.8.8.8: request timed out 2019/10/14 03:35:22.266 : 8.8.8.8: request timed out 2019/10/14 03:35:22.295 : Reply[16607] from 8.8.8.8: bytes=32 time=29.1 ms TTL=55 2019/10/14 03:35:23.309 : Reply[16608] from 8.8.8.8: bytes=32 time=12.9 ms TTL=55 2019/10/14 03:35:24.322 : Reply[16609] from 8.8.8.8: bytes=32 time=13.0 ms TTL=55 2019/10/14 03:35:25.336 : Reply[16610] from 8.8.8.8: bytes=32 time=12.9 ms TTL=55

VPS side: Oct 14 03:30:27 dedicated kernel: [102910.981053] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:30:53 dedicated kernel: [102936.914208] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:77:e5:ff:08:00 SRC=195.14.171.42 DST=89.207.131.164 LEN=52 TOS=0x00 PREC=0x00 TTL=117 ID=28840 DF PROTO=TCP SPT=62567 DPT=3389 WINDOW=8192 RES=0x00 SYN URGP=0 Oct 14 03:30:55 dedicated kernel: [102938.758770] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:30:56 dedicated kernel: [102939.914528] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:77:e5:ff:08:00 SRC=195.14.171.42 DST=89.207.131.164 LEN=52 TOS=0x00 PREC=0x00 TTL=117 ID=28911 DF PROTO=TCP SPT=62567 DPT=3389 WINDOW=8192 RES=0x00 SYN URGP=0 Oct 14 03:31:02 dedicated kernel: [102945.914653] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:77:e5:ff:08:00 SRC=195.14.171.42 DST=89.207.131.164 LEN=48 TOS=0x00 PREC=0x00 TTL=117 ID=29036 DF PROTO=TCP SPT=62567 DPT=3389 WINDOW=65535 RES=0x00 SYN URGP=0 Oct 14 03:31:23 dedicated kernel: [102966.548971] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:31:50 dedicated kernel: [102994.327800] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:31:54 dedicated kernel: [102998.068195] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=122.118.195.19 DST=89.207.131.164 LEN=40 TOS=0x08 PREC=0x20 TTL=43 ID=26195 PROTO=TCP SPT=11707 DPT=23 WINDOW=13728 RES=0x00 SYN URGP=0 Oct 14 03:32:07 dedicated kernel: [103011.281170] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=146.88.240.4 DST=89.207.131.164 LEN=68 TOS=0x00 PREC=0x00 TTL=245 ID=54321 PROTO=UDP SPT=55305 DPT=161 LEN=48 Oct 14 03:32:10 dedicated kernel: [103013.966591] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=192.115.165.4 DST=89.207.131.164 LEN=40 TOS=0x08 PREC=0x20 TTL=243 ID=48338 PROTO=TCP SPT=40189 DPT=38636 WINDOW=1024 RES=0x00 SYN URGP=0 Oct 14 03:32:15 dedicated kernel: [103018.823523] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=45.136.110.11 DST=89.207.131.164 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=42733 PROTO=TCP SPT=46210 DPT=1099 WINDOW=1024 RES=0x00 SYN URGP=0 Oct 14 03:32:18 dedicated kernel: [103022.097669] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:32:46 dedicated kernel: [103049.877924] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:33:14 dedicated kernel: [103077.658768] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:33:23 dedicated kernel: [103087.426977] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=185.216.140.252 DST=89.207.131.164 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=55894 PROTO=TCP SPT=50334 DPT=7722 WINDOW=1024 RES=0x00 SYN URGP=0 Oct 14 03:33:42 dedicated kernel: [103105.572643] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:34:09 dedicated kernel: [103133.241725] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:34:33 dedicated kernel: [103157.208637] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=14.55.208.102 DST=89.207.131.164 LEN=40 TOS=0x00 PREC=0x00 TTL=108 ID=256 PROTO=TCP SPT=6000 DPT=3314 WINDOW=16384 RES=0x00 SYN URGP=0 Oct 14 03:34:35 dedicated kernel: [103159.260039] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:77:e5:ff:08:00 SRC=45.136.109.186 DST=89.207.131.164 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=36932 PROTO=TCP SPT=46306 DPT=4498 WINDOW=1024 RES=0x00 SYN URGP=0 Oct 14 03:34:37 dedicated kernel: [103160.997817] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:35:01 dedicated kernel: [103185.386338] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=89.207.91.117 DST=89.207.131.164 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=19849 DF PROTO=TCP SPT=5698 DPT=8291 WINDOW=14600 RES=0x00 SYN URGP=0 Oct 14 03:35:05 dedicated kernel: [103188.769404] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:35:33 dedicated kernel: [103216.535748] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:35:33 dedicated kernel: [103217.388879] IPv4: martian source 10.255.255.2 from 10.255.255.1, on dev gt-tun0 Oct 14 03:35:39 dedicated kernel: [103222.697274] IPv4: martian source 10.255.255.2 from 10.255.255.1, on dev gt-tun0 Oct 14 03:35:44 dedicated kernel: [103227.598751] IPv4: martian source 10.255.255.2 from 10.255.255.1, on dev gt-tun0 Oct 14 03:35:49 dedicated kernel: [103232.464510] IPv4: martian source 10.255.255.2 from 10.255.255.1, on dev gt-tun0 Oct 14 03:35:54 dedicated kernel: [103237.698075] IPv4: martian source 10.255.255.2 from 10.255.255.1, on dev gt-tun0 Oct 14 03:35:59 dedicated kernel: [103242.788671] IPv4: martian source 10.255.255.2 from 10.255.255.1, on dev gt-tun0 Oct 14 03:36:00 dedicated kernel: [103243.949226] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:77:e5:ff:08:00 SRC=37.49.231.104 DST=89.207.131.164 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=51491 PROTO=TCP SPT=54719 DPT=50802 WINDOW=1024 RES=0x00 SYN URGP=0 Oct 14 03:36:00 dedicated kernel: [103244.325756] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:36:04 dedicated kernel: [103247.758005] IPv4: martian source 10.255.255.2 from 10.255.255.1, on dev gt-tun0 Oct 14 03:36:09 dedicated kernel: [103252.635148] IPv4: martian source 10.255.255.2 from 10.255.255.1, on dev gt-tun0 Oct 14 03:36:13 dedicated kernel: [103257.420483] IPv4: martian source 10.255.255.2 from 10.255.255.1, on dev gt-tun0 Oct 14 03:36:28 dedicated kernel: [103272.107403] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:36:56 dedicated kernel: [103299.872295] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:37:24 dedicated kernel: [103327.650172] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:37:34 dedicated kernel: [103337.694748] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:77:e5:ff:08:00 SRC=77.247.110.222 DST=89.207.131.164 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=22949 PROTO=TCP SPT=51634 DPT=82 WINDOW=1024 RES=0x00 SYN URGP=0 Oct 14 03:37:39 dedicated kernel: [103343.159582] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=107.173.67.161 DST=89.207.131.164 LEN=40 TOS=0x08 PREC=0x20 TTL=241 ID=57841 PROTO=TCP SPT=48112 DPT=1433 WINDOW=1024 RES=0x00 SYN URGP=0 Oct 14 03:37:47 dedicated kernel: [103350.504852] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=89.207.66.63 DST=89.207.131.164 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=21900 DF PROTO=TCP SPT=52238 DPT=23 WINDOW=14600 RES=0x00 SYN URGP=0 Oct 14 03:37:51 dedicated kernel: [103355.425114] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:38:15 dedicated kernel: [103379.344263] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=18.188.161.180 DST=89.207.131.164 LEN=60 TOS=0x00 PREC=0x00 TTL=38 ID=64651 DF PROTO=TCP SPT=40728 DPT=30303 WINDOW=29200 RES=0x00 SYN URGP=0 Oct 14 03:38:16 dedicated kernel: [103380.342151] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=18.188.161.180 DST=89.207.131.164 LEN=60 TOS=0x00 PREC=0x00 TTL=38 ID=64652 DF PROTO=TCP SPT=40728 DPT=30303 WINDOW=29200 RES=0x00 SYN URGP=0 Oct 14 03:38:18 dedicated kernel: [103382.346164] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=18.188.161.180 DST=89.207.131.164 LEN=60 TOS=0x00 PREC=0x00 TTL=38 ID=64653 DF PROTO=TCP SPT=40728 DPT=30303 WINDOW=29200 RES=0x00 SYN URGP=0 Oct 14 03:38:19 dedicated kernel: [103383.202760] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:38:22 dedicated kernel: [103386.354075] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=18.188.161.180 DST=89.207.131.164 LEN=60 TOS=0x00 PREC=0x00 TTL=38 ID=64654 DF PROTO=TCP SPT=40728 DPT=30303 WINDOW=29200 RES=0x00 SYN URGP=0 Oct 14 03:38:32 dedicated kernel: [103396.416289] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=18.223.205.54 DST=89.207.131.164 LEN=60 TOS=0x00 PREC=0x00 TTL=38 ID=36759 DF PROTO=TCP SPT=53428 DPT=30303 WINDOW=29200 RES=0x00 SYN URGP=0 Oct 14 03:38:39 dedicated kernel: [103402.759000] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=159.203.201.127 DST=89.207.131.164 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=54321 PROTO=TCP SPT=35099 DPT=26 WINDOW=65535 RES=0x00 SYN URGP=0 Oct 14 03:38:47 dedicated kernel: [103410.980638] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:38:52 dedicated kernel: [103415.506109] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:77:e5:ff:08:00 SRC=54.169.169.11 DST=89.207.131.164 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=27594 DF PROTO=TCP SPT=39476 DPT=30303 WINDOW=26883 RES=0x00 SYN URGP=0 Oct 14 03:38:53 dedicated kernel: [103416.503543] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:77:e5:ff:08:00 SRC=54.169.169.11 DST=89.207.131.164 LEN=60 TOS=0x00 PREC=0x00 TTL=46 ID=27595 DF PROTO=TCP SPT=39476 DPT=30303 WINDOW=26883 RES=0x00 SYN URGP=0 Oct 14 03:38:53 dedicated kernel: [103416.726595] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=60.12.215.85 DST=89.207.131.164 LEN=40 TOS=0x08 PREC=0x20 TTL=42 ID=46725 PROTO=TCP SPT=34284 DPT=22 WINDOW=1004 RES=0x00 SYN URGP=0 Oct 14 03:39:15 dedicated kernel: [103438.762642] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0 Oct 14 03:39:23 dedicated OMR-Service: Restart Glorytun and networkd Oct 14 03:39:23 dedicated kernel: [103447.211843] Shorewall:FORWARD:REJECT:IN=eth0 OUT=eth0 MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=52.157.222.127 DST=10.255.255.2 LEN=104 TOS=0x00 PREC=0x00 TTL=52 ID=64008 DF PROTO=UDP SPT=30035 DPT=3074 LEN=84 Oct 14 03:39:23 dedicated kernel: [103447.228992] Shorewall:FORWARD:REJECT:IN=eth0 OUT=eth0 MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=52.157.222.127 DST=10.255.255.2 LEN=119 TOS=0x00 PREC=0x00 TTL=52 ID=64009 DF PROTO=UDP SPT=30035 DPT=3074 LEN=99 Oct 14 03:39:23 dedicated kernel: [103447.243704] Shorewall:FORWARD:REJECT:IN=eth0 OUT=eth0 MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=52.157.222.127 DST=10.255.255.2 LEN=135 TOS=0x00 PREC=0x00 TTL=52 ID=64013 DF PROTO=UDP SPT=30035 DPT=3074 LEN=115 Oct 14 03:39:23 dedicated kernel: [103447.261450] Shorewall:FORWARD:REJECT:IN=eth0 OUT=eth0 MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=52.157.222.127 DST=10.255.255.2 LEN=119 TOS=0x00 PREC=0x00 TTL=52 ID=64016 DF PROTO=UDP SPT=30035 DPT=3074 LEN=99 Oct 14 03:39:23 dedicated kernel: [103447.276939] Shorewall:FORWARD:REJECT:IN=eth0 OUT=eth0 MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=52.157.222.127 DST=10.255.255.2 LEN=119 TOS=0x00 PREC=0x00 TTL=52 ID=64020 DF PROTO=UDP SPT=30035 DPT=3074 LEN=99 Oct 14 03:39:23 dedicated kernel: [103447.291332] Shorewall:FORWARD:REJECT:IN=eth0 OUT=eth0 MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=52.157.222.127 DST=10.255.255.2 LEN=119 TOS=0x00 PREC=0x00 TTL=52 ID=64023 DF PROTO=UDP SPT=30035 DPT=3074 LEN=99 Oct 14 03:39:23 dedicated kernel: [103447.307610] Shorewall:FORWARD:REJECT:IN=eth0 OUT=eth0 MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=52.157.222.127 DST=10.255.255.2 LEN=119 TOS=0x00 PREC=0x00 TTL=52 ID=64024 DF PROTO=UDP SPT=30035 DPT=3074 LEN=99 Oct 14 03:39:23 dedicated kernel: [103447.326811] Shorewall:FORWARD:REJECT:IN=eth0 OUT=eth0 MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=52.157.222.127 DST=10.255.255.2 LEN=203 TOS=0x00 PREC=0x00 TTL=52 ID=64028 DF PROTO=UDP SPT=30035 DPT=3074 LEN=183 Oct 14 03:39:23 dedicated kernel: [103447.339313] Shorewall:FORWARD:REJECT:IN=eth0 OUT=eth0 MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=52.157.222.127 DST=10.255.255.2 LEN=151 TOS=0x00 PREC=0x00 TTL=52 ID=64030 DF PROTO=UDP SPT=30035 DPT=3074 LEN=131 Oct 14 03:39:23 dedicated kernel: [103447.355544] Shorewall:FORWARD:REJECT:IN=eth0 OUT=eth0 MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=52.157.222.127 DST=10.255.255.2 LEN=151 TOS=0x00 PREC=0x00 TTL=52 ID=64031 DF PROTO=UDP SPT=30035 DPT=3074 LEN=131 Oct 14 03:39:23 dedicated kernel: [103447.371585] Shorewall:FORWARD:REJECT:IN=eth0 OUT=eth0 MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=52.157.222.127 DST=10.255.255.2 LEN=151 TOS=0x00 PREC=0x00 TTL=52 ID=64034 DF PROTO=UDP SPT=30035 DPT=3074 LEN=131 Oct 14 03:39:23 dedicated kernel: [103447.387781] Shorewall:FORWARD:REJECT:IN=eth0 OUT=eth0 MAC=00:25:90:3c:c1:c8:50:eb:1a:80:09:9f:08:00 SRC=52.157.222.127 DST=10.255.255.2 LEN=183 TOS=0x00 PREC=0x00 TTL=52 ID=64037 DF PROTO=UDP SPT=30035 DPT=3074 LEN=163 Oct 14 03:39:42 dedicated kernel: [103466.252884] Shorewall:net-fw:DROP:IN=eth0 OUT= MAC=00:25:90:3c:c1:c8:50:eb:1a:77:e5:ff:08:00 SRC=51.91.212.81 DST=89.207.131.164 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=54321 PROTO=TCP SPT=51136 DPT=587 WINDOW=65535 RES=0x00 SYN URGP=0 Oct 14 03:39:43 dedicated kernel: [103466.544364] IPv4: martian source 61.164.36.105 from 192.168.100.249, on dev gt-tun0

Mhh... it seem VPS glorytun restarted randomly? Mayhbe this is the cause.. i saw this later... I see zero reason why VPS glorytun should ever restart at random?

Steps to Reproduce the Problem

  1. Just stay online for few days. (uptime in this case little over a day.
    1. Run without OMS tracker and all the stuffs (Except OMRVPN otherwise vpn doesnt start on reboot?)
    2. Both aggregated connections were fine during this time, MPTCP and TCP connections all stayed alive.

Specifications

Log, pay attention to this section:

Mon Oct 14 03:33:07 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:33:07 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:35:26 2019 daemon.err glorytun[15724]: read: Operation timed out Mon Oct 14 03:35:26 2019 daemon.info glorytun[15724]: STOPPED tun0 Mon Oct 14 03:35:27 2019 daemon.err glorytun[15724]: 89.207.131.164.65001: connected Mon Oct 14 03:35:28 2019 daemon.info glorytun[15724]: STARTED tun0 Mon Oct 14 03:35:37 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:35:37 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:36:28 2019 user.notice post-tracking-post-tracking: Get status and settings for wan2... Mon Oct 14 03:37:20 2019 user.notice post-tracking-post-tracking: Get status and settings for wan2... Done

Full:

Mon Oct 14 00:50:33 2019 user.notice post-tracking-post-tracking: Get status and settings for wan1... Done Mon Oct 14 00:53:00 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 00:53:00 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 00:55:30 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 00:55:30 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 00:58:00 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 00:58:00 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:00:30 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:00:30 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:03:01 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:03:01 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:05:31 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:05:31 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:08:01 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:08:01 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:09:31 2019 daemon.notice netifd: wan3 (4214): udhcpc: sending renew to 46.231.22.42 Mon Oct 14 01:09:31 2019 daemon.notice netifd: wan3 (4214): udhcpc: lease of 192.145.56.17 obtained, lease time 25200 Mon Oct 14 01:10:31 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:10:31 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:13:01 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:13:01 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:15:31 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:15:31 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:18:01 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:18:01 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:20:31 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:20:31 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:23:02 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:23:02 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:25:32 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:25:32 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:28:02 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:28:02 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:30:32 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:30:32 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:33:02 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:33:02 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:35:22 2019 user.notice post-tracking-post-tracking: Get status and settings for wan2... Mon Oct 14 01:35:32 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:35:32 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:36:18 2019 user.notice post-tracking-post-tracking: Get status and settings for wan2... Done Mon Oct 14 01:38:02 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:38:02 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:40:32 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:40:32 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:43:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:43:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:45:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:45:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:48:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:48:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:50:20 2019 user.notice post-tracking-post-tracking: Get status and settings for wan1... Mon Oct 14 01:50:31 2019 user.notice post-tracking-post-tracking: Get status and settings for wan1... Done Mon Oct 14 01:50:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:50:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:53:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:53:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:55:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:55:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 01:58:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 01:58:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:00:00 2019 cron.err crond[3675]: USER root pid 22801 cmd /etc/init.d/vnstat_backup backup Mon Oct 14 02:00:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:00:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:03:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:03:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:05:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:05:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:08:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:08:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:08:13 2019 daemon.info dnsmasq-dhcp[3240]: DHCPREQUEST(br-lan) 192.168.100.101 f4:b5:20:14:dd:39 Mon Oct 14 02:08:13 2019 daemon.info dnsmasq-dhcp[3240]: DHCPACK(br-lan) 192.168.100.101 f4:b5:20:14:dd:39 NUC Mon Oct 14 02:10:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:10:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:13:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:13:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:15:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:15:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:18:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:18:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:20:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:20:33 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:23:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:23:03 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:25:34 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:25:34 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:28:04 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:28:04 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:30:34 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:30:34 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:33:04 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:33:04 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:35:34 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:35:34 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:35:51 2019 user.notice post-tracking-post-tracking: Get status and settings for wan2... Mon Oct 14 02:36:43 2019 user.notice post-tracking-post-tracking: Get status and settings for wan2... Done Mon Oct 14 02:38:04 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:38:04 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:40:34 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:40:34 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:42:57 2019 daemon.info dnsmasq-dhcp[3240]: DHCPREQUEST(br-lan) 192.168.100.100 2c:4d:54:4d:b9:ff Mon Oct 14 02:42:57 2019 daemon.info dnsmasq-dhcp[3240]: DHCPACK(br-lan) 192.168.100.100 2c:4d:54:4d:b9:ff Marctraider-PC Mon Oct 14 02:43:04 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:43:04 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:45:35 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:45:35 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:48:05 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:48:05 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:50:19 2019 user.notice post-tracking-post-tracking: Get status and settings for wan1... Mon Oct 14 02:50:29 2019 user.notice post-tracking-post-tracking: Get status and settings for wan1... Done Mon Oct 14 02:50:35 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:50:35 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:53:05 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:53:05 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:55:35 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:55:35 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 02:58:05 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 02:58:05 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:00:35 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:00:35 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:03:05 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:03:05 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:05:36 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:05:36 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:08:06 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:08:06 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:10:36 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:10:36 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:13:06 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:13:06 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:15:36 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:15:36 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:18:06 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:18:06 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:20:36 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:20:36 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:23:06 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:23:06 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:25:36 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:25:36 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:28:07 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:28:07 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:30:37 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:30:37 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:33:07 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:33:07 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:35:26 2019 daemon.err glorytun[15724]: read: Operation timed out Mon Oct 14 03:35:26 2019 daemon.info glorytun[15724]: STOPPED tun0 Mon Oct 14 03:35:27 2019 daemon.err glorytun[15724]: 89.207.131.164.65001: connected Mon Oct 14 03:35:28 2019 daemon.info glorytun[15724]: STARTED tun0 Mon Oct 14 03:35:37 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:35:37 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:36:28 2019 user.notice post-tracking-post-tracking: Get status and settings for wan2... Mon Oct 14 03:37:20 2019 user.notice post-tracking-post-tracking: Get status and settings for wan2... Done Mon Oct 14 03:38:07 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:38:07 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:39:23 2019 daemon.info glorytun[15724]: STOPPED tun0 Mon Oct 14 03:39:24 2019 daemon.err glorytun[15724]: 89.207.131.164.65001: connected Mon Oct 14 03:39:24 2019 daemon.info glorytun[15724]: STARTED tun0 Mon Oct 14 03:40:37 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:40:37 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:43:07 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:43:07 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:45:37 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:45:37 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:48:08 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:48:08 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:49:56 2019 user.notice post-tracking-post-tracking: Get status and settings for wan1... Mon Oct 14 03:50:06 2019 user.notice post-tracking-post-tracking: Get status and settings for wan1... Done Mon Oct 14 03:50:38 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:50:38 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:53:08 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:53:08 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:55:38 2019 daemon.notice netifd: wan2 (4216): udhcpc: sending renew to 192.168.1.1 Mon Oct 14 03:55:38 2019 daemon.notice netifd: wan2 (4216): udhcpc: lease of 91.141.139.197 obtained, lease time 300 Mon Oct 14 03:56:52 2019 daemon.err uhttpd[4292]: luci: accepted login on / for root from 192.168.100.100

Ysurac commented 4 years ago

There is a script on the VPS that check if the VPN is working. If it can't ping the other end then it's restarted. It's the omr services.

Marctraider commented 4 years ago

Then I have to disable the VPS side tracker as well as everything was working just fine.

I think this tracker is not fool proof enough, how can i disable vps side? Systemctl?

Ysurac commented 4 years ago

The script work as expected : client end doesn't answer to ping, restart VPN because there is a problem. You can use systemctl to disable it, this will also disable 6in4 tunnel update.

Marctraider commented 4 years ago

Thanks.