Hi Tony and Nick, I am just available to reply, yes I will give it a try to the PPPoE as soon as posible, maybe tomorrow afternoon.

Now it makes complete sense about the dropping on the conection with the PPPoE, I am almost sure that it will now work.

Thank you again for all you advice!

Best wishes!

I think I got it!

I changed the ping servers, put googleDNS and openDNS, restarted syswatch (the logs show it failed and sometimes it passed the ping server check on both servers)...

Then I tried pinging google using eth2, it started pinging but loosing packets for moments, then pinging again, so I changed the cable as Tony suggested on 1) and boila! the pinging was permanent! So maybe the cable was faulty?

The thing that confuses me is how it worked on pppoe and the modem on bridge mode?

But nonetheless, it is working now!

Thank you Tony, Duncan and Nick for your support, I am sincerely grateful!

Thank you Tony and Duncan for replying...

This is Tony's request:

[root@gateway ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth2
DEVICE=eth2
TYPE="Ethernet"
ONBOOT="yes"
USERCTL="no"
BOOTPROTO="static"
IPADDR="192.168.10.2"
NETMASK="255.255.255.0"
GATEWAY="192.168.10.1"

[root@gateway ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1
TYPE="Ethernet"
ONBOOT="yes"
USERCTL="no"
BOOTPROTO="static"
HWADDR="F8:1A:67:04:4E:F5"
DNS1="192.168.20.1"
DNS2="8.8.8.8"
IPADDR="192.168.20.201"
NETMASK="255.255.255.0"
GATEWAY="192.168.20.1"

Note: yesterday I manually added HWADDR, DNS1 and DNS2 in both files, then restarted network but nothing happened. Then I this other tests so the eth2 file was regenerated, that is why you don't see those lines in the eth2 file now. Eth1 is working fine as usual.

ifconfig full output:

eth1 Link encap:Ethernet HWaddr F8:1A:67:04:4E:F5
inet addr:192.168.20.201 Bcast:192.168.20.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:23150537 errors:0 dropped:0 overruns:0 frame:0
TX packets:385889 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2673715256 (2.4 GiB) TX bytes:71351441 (68.0 MiB)
Interrupt:28 Base address:0x2000

eth2 Link encap:Ethernet HWaddr B0:48:7A:83:21:E4
inet addr:192.168.10.2 Bcast:192.168.10.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10788 errors:0 dropped:0 overruns:0 frame:0
TX packets:17900 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1287085 (1.2 MiB) TX bytes:789296 (770.7 KiB)
Interrupt:16 Base address:0xcc00

this is syswatch log since restart:

Fri Nov 25 10:22:50 2016 info: system - syswatch terminated
Fri Nov 25 10:22:50 2016 info: system - syswatch started
Fri Nov 25 10:22:50 2016 info: config - IP referrer disabled in multi-WAN
Fri Nov 25 10:22:50 2016 info: config - IP referrer tool is installed
Fri Nov 25 10:22:50 2016 info: config - debug level - 0
Fri Nov 25 10:22:50 2016 info: config - retries - 3
Fri Nov 25 10:22:50 2016 info: config - heartbeat - 15
Fri Nov 25 10:22:50 2016 info: config - interval - 20 seconds
Fri Nov 25 10:22:50 2016 info: config - offline interval - 10 seconds
Fri Nov 25 10:22:50 2016 info: config - referrer IP detection - disabled
Fri Nov 25 10:22:50 2016 info: config - ping server auto-detect - enabled
Fri Nov 25 10:22:50 2016 info: config - try pinging gateway - yes
Fri Nov 25 10:22:50 2016 info: config - number of external networks - 2
Fri Nov 25 10:22:50 2016 info: config - monitoring external network - eth2
Fri Nov 25 10:22:50 2016 info: config - monitoring external network - eth1
Fri Nov 25 10:22:50 2016 info: info - loading network configuration
Fri Nov 25 10:22:50 2016 info: info - network configuration for eth2 - config: ifcfg-eth2
Fri Nov 25 10:22:50 2016 info: info - network configuration for eth2 - onboot: enabled
Fri Nov 25 10:22:50 2016 info: info - network configuration for eth2 - type: static
Fri Nov 25 10:22:50 2016 info: info - network configuration for eth2 - wifi: disabled
Fri Nov 25 10:22:50 2016 info: info - network configuration for eth2 - gateway: 192.168.10.1
Fri Nov 25 10:22:50 2016 info: info - network configuration for eth1 - config: ifcfg-eth1
Fri Nov 25 10:22:50 2016 info: info - network configuration for eth1 - onboot: enabled
Fri Nov 25 10:22:50 2016 info: info - network configuration for eth1 - type: static
Fri Nov 25 10:22:50 2016 info: info - network configuration for eth1 - wifi: disabled
Fri Nov 25 10:22:50 2016 info: info - network configuration for eth1 - gateway: 192.168.20.1
Fri Nov 25 10:22:50 2016 info: eth2 - network - IP address - 192.168.10.2
Fri Nov 25 10:22:50 2016 info: eth2 - network - gateway - 192.168.10.1
Fri Nov 25 10:22:50 2016 info: eth2 - network - type - private IP range
Fri Nov 25 10:22:50 2016 info: eth1 - network - IP address - 192.168.20.201
Fri Nov 25 10:22:50 2016 info: eth1 - network - gateway - 192.168.20.1
Fri Nov 25 10:22:50 2016 info: eth1 - network - type - private IP range
Fri Nov 25 10:22:52 2016 info: eth2 - ping check on gateway failed - 192.168.10.1
Fri Nov 25 10:22:54 2016 info: eth2 - ping check on server #1 failed - 8.8.8.8
Fri Nov 25 10:22:59 2016 info: eth2 - ping check on server #2 failed - 54.152.208.245
Fri Nov 25 10:22:59 2016 warn: eth2 - connection is down
Fri Nov 25 10:23:01 2016 info: eth2 - waiting for static IP reconnect
Fri Nov 25 10:23:01 2016 info: system - changing active WAN list - eth1 (was startup)
Fri Nov 25 10:23:01 2016 info: system - current WANs in use - eth1
Fri Nov 25 10:23:01 2016 info: system - restarting firewall
Fri Nov 25 10:23:02 2016 info: system - updating intrusion prevention whitelist
Fri Nov 25 10:23:02 2016 info: system - adding ping server 54.152.208.245
Fri Nov 25 10:23:02 2016 info: system - adding ping server 8.8.8.8
Fri Nov 25 10:23:02 2016 info: system - adding DNS server 192.168.20.1
Fri Nov 25 10:23:02 2016 info: system - adding DNS server 201.217.1.230
Fri Nov 25 10:23:02 2016 info: system - adding DNS server 8.8.8.8
Fri Nov 25 10:23:02 2016 info: system - reloading intrusion prevention system
Fri Nov 25 10:23:08 2016 info: system - dynamic DNS updated
Fri Nov 25 10:23:20 2016 info: eth2 - ping check on gateway failed - 192.168.10.1
Fri Nov 25 10:23:22 2016 info: eth2 - ping check on server #1 failed - 8.8.8.8
Fri Nov 25 10:23:27 2016 info: eth2 - ping check on server #2 failed - 54.152.208.245
Fri Nov 25 10:23:27 2016 warn: eth2 - connection is down
Fri Nov 25 10:23:30 2016 info: eth2 - waiting for static IP reconnect
Fri Nov 25 10:23:42 2016 info: eth2 - ping check on gateway failed - 192.168.10.1
Fri Nov 25 10:23:44 2016 info: eth2 - ping check on server #1 failed - 8.8.8.8
Fri Nov 25 10:23:49 2016 info: eth2 - ping check on server #2 failed - 54.152.208.245
Fri Nov 25 10:23:49 2016 warn: eth2 - connection is down
Fri Nov 25 10:23:51 2016 info: eth2 - waiting for static IP reconnect

I don't know where that 54.152.208.245 is coming from...

OK,

I have installed de r8168 driver. Now this is the lspci command

[root@gateway ~]# lspci -k | grep Eth -A 3
01:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet (rev c0)
Subsystem: ASUSTeK Computer Inc. Device 847e
Kernel driver in use: atl1c
Kernel modules: atl1c
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
Subsystem: TP-LINK Technologies Co., Ltd. TG-3468 Gigabit PCI Express Network Adapter
Kernel driver in use: r8168
Kernel modules: r8168
03:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC
Kernel driver in use: r8169
Kernel modules: r8169

Sadly, the issue persists.

Multiwan page still shows eth2 as offline - not in use.

oh, ok

2. with -A 2 it shows nothing about the gateway

this is what it show with "ip route", I dont know if there is another command for the routing table.

[root@gateway ~]# ip route
10.8.10.2 dev tun1 proto kernel scope link src 10.8.10.1
10.8.0.2 dev tun0 proto kernel scope link src 10.8.0.1
192.168.20.0/24 dev eth1 proto kernel scope link src 192.168.20.201
10.8.0.0/24 via 10.8.0.2 dev tun0
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1
10.8.10.0/24 via 10.8.10.2 dev tun1
192.168.10.0/24 dev eth2 proto kernel scope link src 192.168.10.2
default via 192.168.20.1 dev eth1


5.

[root@gateway ~]# lspci -k | grep Eth -A 3
01:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet (rev c0)
Subsystem: ASUSTeK Computer Inc. Device 847e
Kernel driver in use: atl1c
Kernel modules: atl1c
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
Subsystem: TP-LINK Technologies Co., Ltd. TG-3468 Gigabit PCI Express Network Adapter
Kernel driver in use: r8169
Kernel modules: r8169
03:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC
Kernel driver in use: r8169
Kernel modules: r8169

Hello Nick, thanks for the reply.

1. Yes, the modem work fine when I connect a workstation directly to one LAN port.

2.

[root@gateway ~]# ifconfig | grep HWa -A 1
eth0 Link encap:Ethernet HWaddr BC:AE:C5:50:7D:30
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
--
eth1 Link encap:Ethernet HWaddr F8:1A:67:04:4E:F5
inet addr:192.168.20.201 Bcast:192.168.20.255 Mask:255.255.255.0
--
eth2 Link encap:Ethernet HWaddr B0:48:7A:83:21:E4
inet addr:192.168.10.2 Bcast:192.168.10.255 Mask:255.255.255.0
--
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
--
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.10.1 P-t-P:10.8.10.2 Mask:255.255.255.255


[root@gateway ~]# cat /etc/resolv-peerdns.conf
; generated by /sbin/dhclient-script
nameserver 192.168.10.1
nameserver 192.168.20.1


3.The eth2 interface is up. What I think is causing the issue is that like it is "offline" / "not in use" by the multiwan, then eth2 has no network traffic, but the interface is up.

If I try to ping from eth2 to the modem, I have nothing.

[root@gateway ~]# ping -I 192.168.10.2 192.168.10.1
PING 192.168.10.1 (192.168.10.1) from 192.168.10.2 : 56(84) bytes of data.
From 192.168.10.2 icmp_seq=2 Destination Host Unreachable
From 192.168.10.2 icmp_seq=3 Destination Host Unreachable
From 192.168.10.2 icmp_seq=4 Destination Host Unreachable


4. The lights are correct and the connection is present.

5. The lspci returns nothing.

[root@gateway ~]# uname -r
2.6.32-573.26.1.v6.x86_64

Multiwan shows eth2 interface offline

Hello,

I am using ClearOS Community 6.7 (Final). My network is as follows: eth0 is my LAN interface (192.168.0.1), eth1 is one ethernet WAN interface (192.168.20.201) and eth2 is another WAN interface (192.168.10.2).

Eth1 is connected through fiber to one ISP and is working fine.

Eth2 is connect to a Kaiomy ADSL modem, the modem LAN IP is 192.168.10.1, it is configured PPPoE/PPPoA with all the settings as my ISP told me (user, pass, MTU, etc.)

The issue is that Multiwan always shows the eth2 as offline. There is something else I have to do to make it go online? like routing, NAT, or anything else? in my box or in the modem?

Any help will be greatly appreciated!

P.S.: in the past I had set up the modem as Bridge Mode and the ClearOS eth2 as external PPPoE, the ppp0 interface was created and the multiwan was working just fine, with both interfaces online and good. The problem was that the ppp0 renewed the dynamic IP usually every 3 minutes, sometimes 1 minutes and sometimes 5, but it was constantly renewed, so I decided to change it to the setup I have explained in the message, that way the dynamic IP in the modem is the same for hours, even days.