Forums

Resolved
0 votes
Dear All,
I am getting internet down (inbound and outbound) issue, while syswatch ping failed to dns (8.8.8.8).
My interent connection down at 05:34 AM and restore when I have unpluged the eth1 cable from the Gateway netwrork port at 09:45 AM. please see the syswatch log below:


Wed Jul 11 05:30:47 2018 info: system - heartbeat...
Wed Jul 11 05:33:11 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 05:33:14 2018 info: eth1 - ping check on server #2 passed - 54.152.208.245
Wed Jul 11 05:33:34 2018 info: eth1 - ping check on server #1 passed - 8.8.8.8
Wed Jul 11 05:35:55 2018 info: system - heartbeat...
Wed Jul 11 05:40:58 2018 info: system - heartbeat...
Wed Jul 11 05:46:00 2018 info: system - heartbeat...
Wed Jul 11 05:51:02 2018 info: system - heartbeat...
Wed Jul 11 05:56:05 2018 info: system - heartbeat...
Wed Jul 11 06:01:07 2018 info: system - heartbeat...
Wed Jul 11 06:06:09 2018 info: system - heartbeat...
Wed Jul 11 06:11:12 2018 info: system - heartbeat...
Wed Jul 11 06:16:14 2018 info: system - heartbeat...
Wed Jul 11 06:21:16 2018 info: system - heartbeat...
Wed Jul 11 06:26:19 2018 info: system - heartbeat...
Wed Jul 11 06:31:21 2018 info: system - heartbeat...
Wed Jul 11 06:36:23 2018 info: system - heartbeat...
Wed Jul 11 06:41:25 2018 info: system - heartbeat...
Wed Jul 11 06:46:28 2018 info: system - heartbeat...
Wed Jul 11 06:51:30 2018 info: system - heartbeat...
Wed Jul 11 06:56:32 2018 info: system - heartbeat...
Wed Jul 11 07:01:35 2018 info: system - heartbeat...
Wed Jul 11 07:04:39 2018 info: eth2 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 07:04:42 2018 info: eth2 - ping check on server #2 passed - 54.152.208.245
Wed Jul 11 07:05:02 2018 info: eth2 - ping check on server #1 passed - 8.8.8.8
Wed Jul 11 07:06:43 2018 info: system - heartbeat...
Wed Jul 11 07:11:45 2018 info: system - heartbeat...
Wed Jul 11 07:16:47 2018 info: system - heartbeat...
Wed Jul 11 07:20:51 2018 info: eth2 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 07:20:54 2018 info: eth2 - ping check on server #2 passed - 54.152.208.245
Wed Jul 11 07:21:15 2018 info: eth2 - ping check on server #1 passed - 8.8.8.8
Wed Jul 11 07:21:55 2018 info: system - heartbeat...
Wed Jul 11 07:26:57 2018 info: system - heartbeat...
Wed Jul 11 07:31:59 2018 info: system - heartbeat...
Wed Jul 11 07:37:02 2018 info: system - heartbeat...
Wed Jul 11 07:42:04 2018 info: system - heartbeat...
Wed Jul 11 07:47:06 2018 info: system - heartbeat...
Wed Jul 11 07:52:09 2018 info: system - heartbeat...
Wed Jul 11 07:57:11 2018 info: system - heartbeat...
Wed Jul 11 08:02:13 2018 info: system - heartbeat...
Wed Jul 11 08:07:16 2018 info: system - heartbeat...
Wed Jul 11 08:12:18 2018 info: system - heartbeat...
Wed Jul 11 08:17:20 2018 info: system - heartbeat...
Wed Jul 11 08:22:23 2018 info: system - heartbeat...
Wed Jul 11 08:25:46 2018 info: eth2 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 08:25:49 2018 info: eth2 - ping check on server #2 passed - 54.152.208.245
Wed Jul 11 08:26:09 2018 info: eth2 - ping check on server #1 passed - 8.8.8.8
Wed Jul 11 08:27:30 2018 info: system - heartbeat...
Wed Jul 11 08:32:32 2018 info: system - heartbeat...
Wed Jul 11 08:37:34 2018 info: system - heartbeat...
Wed Jul 11 08:42:37 2018 info: system - heartbeat...
Wed Jul 11 08:47:39 2018 info: system - heartbeat...
Wed Jul 11 08:52:41 2018 info: system - heartbeat...
Wed Jul 11 08:57:44 2018 info: system - heartbeat...
Wed Jul 11 09:02:46 2018 info: system - heartbeat...
Wed Jul 11 09:07:48 2018 info: system - heartbeat...
Wed Jul 11 09:12:12 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:12:16 2018 info: eth1 - ping check on server #2 passed - 54.152.208.245
Wed Jul 11 09:12:36 2018 info: eth1 - ping check on server #1 passed - 8.8.8.8
Wed Jul 11 09:12:56 2018 info: system - heartbeat...
Wed Jul 11 09:17:58 2018 info: system - heartbeat...
Wed Jul 11 09:23:01 2018 info: system - heartbeat...
Wed Jul 11 09:28:03 2018 info: system - heartbeat...
Wed Jul 11 09:28:25 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:28:28 2018 info: eth1 - ping check on server #2 passed - 54.152.208.245
Wed Jul 11 09:28:51 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:28:55 2018 info: eth1 - ping check on server #2 passed - 54.152.208.245
Wed Jul 11 09:29:15 2018 info: eth1 - ping check on server #1 passed - 8.8.8.8
Wed Jul 11 09:33:16 2018 info: system - heartbeat...
Wed Jul 11 09:38:19 2018 info: system - heartbeat...
Wed Jul 11 09:39:21 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:39:26 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:39:26 2018 warn: eth1 - connection warning
Wed Jul 11 09:39:38 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:39:40 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:39:45 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:39:45 2018 warn: eth1 - connection warning
Wed Jul 11 09:39:58 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:40:00 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:40:05 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:40:05 2018 warn: eth1 - connection is down
Wed Jul 11 09:40:07 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:40:07 2018 info: system - changing active WAN list - eth2 (was eth1 eth2)
Wed Jul 11 09:40:07 2018 info: system - current WANs in use - eth2
Wed Jul 11 09:40:07 2018 info: system - restarting firewall
Wed Jul 11 09:41:41 2018 info: system - updating intrusion prevention whitelist
Wed Jul 11 09:41:41 2018 info: system - adding ping server 54.152.208.245
Wed Jul 11 09:41:41 2018 info: system - adding ping server 8.8.8.8
Wed Jul 11 09:41:41 2018 info: system - adding DNS server 8.8.8.8
Wed Jul 11 09:41:41 2018 info: system - adding DNS server 208.67.222.222
Wed Jul 11 09:41:41 2018 info: system - adding DNS server 203.112.194.243
Wed Jul 11 09:41:44 2018 info: system - dynamic DNS updated
Wed Jul 11 09:41:56 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:41:58 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:42:03 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:42:03 2018 warn: eth1 - connection is down
Wed Jul 11 09:42:05 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:42:17 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:42:19 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:42:24 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:42:24 2018 warn: eth1 - connection is down
Wed Jul 11 09:42:26 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:42:38 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:42:40 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:42:45 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:42:45 2018 warn: eth1 - connection is down
Wed Jul 11 09:42:47 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:43:00 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:43:02 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:43:07 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:43:07 2018 warn: eth1 - connection is down
Wed Jul 11 09:43:09 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:43:21 2018 info: eth2 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:43:24 2018 info: eth2 - ping check on server #2 passed - 54.152.208.245
Wed Jul 11 09:43:26 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:43:28 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:43:33 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:43:33 2018 warn: eth1 - connection is down
Wed Jul 11 09:43:35 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:43:46 2018 info: eth2 - ping check on server #1 passed - 8.8.8.8
Wed Jul 11 09:43:48 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:43:50 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:43:55 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:43:55 2018 warn: eth1 - connection is down
Wed Jul 11 09:43:57 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:44:09 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:44:11 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:44:16 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:44:16 2018 warn: eth1 - connection is down
Wed Jul 11 09:44:18 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:44:31 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:44:33 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:44:38 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:44:38 2018 warn: eth1 - connection is down
Wed Jul 11 09:44:40 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:44:52 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:44:54 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:44:59 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:44:59 2018 warn: eth1 - connection is down
Wed Jul 11 09:45:01 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:45:12 2018 info: system - heartbeat...
Wed Jul 11 09:45:14 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:45:16 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:45:21 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:45:21 2018 warn: eth1 - connection is down
Wed Jul 11 09:45:23 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:45:35 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:45:37 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:45:42 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:45:42 2018 warn: eth1 - connection is down
Wed Jul 11 09:45:44 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:45:57 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:45:59 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:46:04 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:46:04 2018 warn: eth1 - connection is down
Wed Jul 11 09:46:06 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:46:18 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:46:20 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:46:25 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:46:25 2018 warn: eth1 - connection is down
Wed Jul 11 09:46:27 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:46:40 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:46:42 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:46:47 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:46:47 2018 warn: eth1 - connection is down
Wed Jul 11 09:46:49 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:47:01 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:47:03 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:47:08 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:47:08 2018 warn: eth1 - connection is down
Wed Jul 11 09:47:10 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:47:22 2018 info: eth1 - ping check on gateway failed - 180.222.222.57
Wed Jul 11 09:47:24 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 09:47:29 2018 info: eth1 - ping check on server #2 failed - 54.152.208.245
Wed Jul 11 09:47:29 2018 warn: eth1 - connection is down
Wed Jul 11 09:47:31 2018 info: eth1 - waiting for static IP reconnect
Wed Jul 11 09:47:42 2018 info: eth1 - ping check on server #1 passed - 8.8.8.8
Wed Jul 11 09:47:42 2018 info: system - changing active WAN list - eth1 eth2 (was eth2)
Wed Jul 11 09:47:42 2018 info: system - current WANs in use - eth1 eth2
Wed Jul 11 09:47:42 2018 info: system - restarting firewall
Wed Jul 11 09:51:55 2018 info: system - updating intrusion prevention whitelist
Wed Jul 11 09:51:55 2018 info: system - adding ping server 54.152.208.245
Wed Jul 11 09:51:55 2018 info: system - adding ping server 8.8.8.8
Wed Jul 11 09:51:55 2018 info: system - adding DNS server 8.8.8.8
Wed Jul 11 09:51:55 2018 info: system - adding DNS server 208.67.222.222
Wed Jul 11 09:51:55 2018 info: system - adding DNS server 203.112.194.243
Wed Jul 11 09:51:59 2018 info: system - dynamic DNS updated
Wed Jul 11 09:54:42 2018 info: system - heartbeat...
Wed Jul 11 09:59:47 2018 info: system - heartbeat...
Wed Jul 11 10:04:53 2018 info: system - heartbeat...
Wed Jul 11 10:10:00 2018 info: system - heartbeat...
Wed Jul 11 10:15:07 2018 info: system - heartbeat...
Wed Jul 11 10:15:51 2018 info: eth1 - ping check on server #1 failed - 8.8.8.8
Wed Jul 11 10:15:54 2018 info: eth1 - ping check on server #2 passed - 54.152.208.245
Wed Jul 11 10:16:15 2018 info: eth1 - ping check on server #1 passed - 8.8.8.8
Wed Jul 11 10:20:23 2018 info: system - heartbeat...
Wed Jul 11 10:25:33 2018 info: system - heartbeat...
Wed Jul 11 10:30:41 2018 info: system - heartbeat...
Wed Jul 11 10:35:52 2018 info: system - heartbeat...


below is the clearos gateway config details:


[root@GWSVR ~]# uname -r
2.6.32-696.20.1.v6.i686
[root@GWSVR ~]# cat /etc/clearos/multiwan.conf
MULTIPATH="on"
MULTIPATH_WEIGHTS="eth1|4 eth2|2"
EXTIF_BACKUP=""
[root@GWSVR ~]# cat /etc/clearos/network.conf
# Network mode
MODE="gateway"

# Network interface roles
EXTIF="eth1 eth2"
LANIF="eth0"
DMZIF="eth4"
HOTIF=""

# Domain and Internet Hostname
DEFAULT_DOMAIN="impulsebd.local"
INTERNET_HOSTNAME="internal.impulsebd.local"

# Extra LANS
EXTRALANS=""
[root@GWSVR ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:C0:9F:29:0C:C2
inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:765228230 errors:0 dropped:28088 overruns:0 frame:0
TX packets:944967873 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2207238320 (2.0 GiB) TX bytes:4172393058 (3.8 GiB)

eth0:0 Link encap:Ethernet HWaddr 00:C0:9F:29:0C:C2
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth1 Link encap:Ethernet HWaddr 00:22:3F:E2:BC:99
inet addr:180.222.222.58 Bcast:180.222.222.63 Mask:255.255.255.248
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:632692483 errors:0 dropped:0 overruns:0 frame:0
TX packets:496432659 errors:19 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:531789366510 (495.2 GiB) TX bytes:190213369507 (177.1 GiB)

eth2 Link encap:Ethernet HWaddr 28:10:7B:C2:60:09
inet addr:117.111.111.146 Bcast:117.111.111.151 Mask:255.255.255.248
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:308235244 errors:0 dropped:0 overruns:0 frame:0
TX packets:233970134 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:287793660712 (268.0 GiB) TX bytes:67295591169 (62.6 GiB)

eth4 Link encap:Ethernet HWaddr 00:1D:0F:0D:B3:65
inet addr:103.40.226.162 Bcast:103.40.226.163 Mask:255.255.255.252
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:12962800 errors:75 dropped:352 overruns:34 frame:0
TX packets:11081243 errors:0 dropped:0 overruns:7 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12405058982 (11.5 GiB) TX bytes:4300914323 (4.0 GiB)
Interrupt:25 Base address:0xe000

imq0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16000 Metric:1
RX packets:405184 errors:0 dropped:0 overruns:0 frame:0
TX packets:405183 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:39446851 (37.6 MiB) TX bytes:39446787 (37.6 MiB)

imq1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

imq2 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

imq3 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16000 Metric:1
RX packets:701635 errors:0 dropped:0 overruns:0 frame:0
TX packets:701610 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:79999517 (76.2 MiB) TX bytes:79997425 (76.2 MiB)

imq4 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16000 Metric:1
RX packets:757269 errors:0 dropped:0 overruns:0 frame:0
TX packets:757242 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:986413110 (940.7 MiB) TX bytes:986376559 (940.6 MiB)

imq5 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

imq6 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

imq7 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16000 Metric:1
RX packets:1257439 errors:0 dropped:0 overruns:0 frame:0
TX packets:1257439 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:1568815015 (1.4 GiB) TX bytes:1568815015 (1.4 GiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:269969238 errors:0 dropped:0 overruns:0 frame:0
TX packets:269969238 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:329479992790 (306.8 GiB) TX bytes:329479992790 (306.8 GiB)

tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.8.0.1 P-t-P:10.8.0.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:277012 errors:0 dropped:0 overruns:0 frame:0
TX packets:391737 errors:0 dropped:30 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:29365062 (28.0 MiB) TX bytes:363954538 (347.0 MiB)

tun1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.8.0.1 P-t-P:10.8.0.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

[root@GWSVR ~]#
Wednesday, July 11 2018, 06:37 AM
Share this post:
Responses (7)
  • Accepted Answer

    Wednesday, July 11 2018, 12:49 PM - #Permalink
    Resolved
    0 votes
    ClearOS 6.x MultiWAN doc is here and here for ClearOS7.x. There is not a lot of documentation. The multiwan app mainly adjusts the routing tables and a bit of the firewall. The connection monitor is the part of syswatch daemon.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, July 11 2018, 10:21 AM - #Permalink
    Resolved
    0 votes
    Thanks Nike,

    I will fix the OpenVPN config.
    meanwhile I have fixed the subnet, now eth1 subnet is 255.255.255.0 which was wrongly same (255.255.255.248) for both ISP.

    could you please point me to learn more regarding MultiWAN?

    kr,
    roman
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, July 11 2018, 09:07 AM - #Permalink
    Resolved
    0 votes
    It is your config which is wrong. You should have two files, /etc/openvpn/clients.conf and /etc/openvpn/clients-tcp.conf. It looks like both have the same "server" line and they should not. Normally for /etc/openvpn/clients-tcp.conf it should be:
    server 10.8.10.0 255.255.255.0
    You can change it but it must not clash with your other LAN or OpenVPN subnets. It is not an ISP issue.

    Also worth checking, but the ifconfig-pool-persist should be different and typically proto in clients .conf is set to udp and in clients-tcp.conf to tcp or tcp-server.
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, July 11 2018, 08:40 AM - #Permalink
    Resolved
    0 votes
    Dear Nick

    Thank you for the replay.

    Could you please point me whats wrong with OpenVPN and do you need any log for OpenVPN?

    I will check with ISP and fix if there is any issue with subnet.

    kr,
    roman
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, July 11 2018, 08:34 AM - #Permalink
    Resolved
    0 votes
    I've deleted your duplicate post. As a new poster your first couple of posts get moderated so don't appear immediately. You should be OK now.

    Your NIC drivers are not any of the known problem ones.

    Looking at you log, eth2 seemed to have connectivity all the time. It occasionally failed the first ping test but always worked on the second. I see nothing in the logs about failing over. I'm afraid I don't know MultiWAN well enough to diagnose.

    BTW it looks like you have tinkered with OpenVPN and have an issue. The two interfaces should be on different subnets - in clients-tcp.conf the subnet is usually 10.8.10.1/24. It does not matter what it is but all interfaces need to be on different subnets.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, July 11 2018, 07:40 AM - #Permalink
    Resolved
    0 votes
    Thanks Nick,

    Actually both case are surprising, why eth2 didn't take over the trafic and why eth1 need to physical disconnct before recover?

    please find the below output from "lspci -k | grep Eth -A 3"


    [root@GWSVR ~]# lspci -k | grep Eth -A 3
    00:02.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
    Subsystem: Dell Device 0135
    Kernel driver in use: e1000
    Kernel modules: e1000
    00:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
    Subsystem: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
    Kernel driver in use: 8139too
    Kernel modules: 8139too, 8139cp
    00:0e.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rage XL PCI (rev 27)
    --
    01:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10)
    Subsystem: Netgear GA311
    Kernel driver in use: r8169
    Kernel modules: r8169
    02:02.0 Ethernet controller: D-Link System Inc DGE-528T Gigabit Ethernet Adapter (rev 10)
    Subsystem: D-Link System Inc DGE-528T PCI Gigabit Ethernet Adapter
    Kernel driver in use: r8169
    Kernel modules: r8169
    [root@GWSVR ~]#
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, July 11 2018, 06:53 AM - #Permalink
    Resolved
    0 votes
    Are you saying that eth2 did not take over all the traffic? Or are you saying eth1 did not recover until the cable was unplugged and re-plugged?
    What is the output of
    lspci -k | grep Eth -A 3
    The reply is currently minimized Show
Your Reply