Dear All,
I have just recently made a fresh install of ClearOS 7.2 on my Proliant Microserver GEN 8 after few years of using 5.2, and now the issues:
1. I am using Multi-Wan, one stable land connection and one LTE, sometimes webpages load very slowly even after specifying that port 80 destination traffic should be router via stable land connection
2. After a day my webconfig changed its language by itself - it's set to Polish, but it's mixed now, some buttons are Polish, but most of the content is englisH?
3. In Resource Report there are just "Nothing to report..." instead of charts, a day before it worked flawlessly, and I have made no changes
4. I'm getting a ton of
" User clearconsole logged out via login 2017-03-02 10:15:45
User clearconsole logged in via login 2017-03-02 10:15:45"
informational events, it was over 14k events in the past 12h.
I would greatly appreciate any help, thank you for responses in advance.
EDIT: Now I see that my install somehow updated itself to 7.3... is there a way to rollback to a stable release?
I have just recently made a fresh install of ClearOS 7.2 on my Proliant Microserver GEN 8 after few years of using 5.2, and now the issues:
1. I am using Multi-Wan, one stable land connection and one LTE, sometimes webpages load very slowly even after specifying that port 80 destination traffic should be router via stable land connection
2. After a day my webconfig changed its language by itself - it's set to Polish, but it's mixed now, some buttons are Polish, but most of the content is englisH?
3. In Resource Report there are just "Nothing to report..." instead of charts, a day before it worked flawlessly, and I have made no changes
4. I'm getting a ton of
" User clearconsole logged out via login 2017-03-02 10:15:45
User clearconsole logged in via login 2017-03-02 10:15:45"
informational events, it was over 14k events in the past 12h.
I would greatly appreciate any help, thank you for responses in advance.
EDIT: Now I see that my install somehow updated itself to 7.3... is there a way to rollback to a stable release?
Share this post:
Responses (22)
-
Accepted Answer
Tony Ellis wrote:
For bonding read and digest https://www.kernel.org/doc/Documentation/networking/bonding.txt - there are many 'modes'
Presumably you connecting the two interfaces to a switch that supports bonding, and from the switch to your LAN devices?
Well, to be honest I had something like windows "nic teaming" in mind.
The idea would be if I got e.g. external connections speed combined exceeding 1gbit then if one client would utilise the entirety of one gateway nic, then the other would take up the task to provide bandwith to other clients seamlessly.
I'm not sure that switch does support such mode, my switch is DGS-1210-52
Sorry for such a late response. -
Accepted Answer
For bonding read and digest https://www.kernel.org/doc/Documentation/networking/bonding.txt - there are many 'modes'
Presumably you connecting the two interfaces to a switch that supports bonding, and from the switch to your LAN devices? -
Accepted Answer
Nick Howitt wrote:
Can I just clarify, do you mean bond or bridge your interfaces? If you meant bridging (just putting both NIC's on the same LAN subnet), see here.
I would ideally like to link 2 LAN interfaces to handle gateway load of connections from lan to internet in a seamless manner
(Both would just work under 1 IP Address and load balance between themselves) -
Accepted Answer
Can I just clarify, do you mean bond or bridge your interfaces? If you meant bridging (just putting both NIC's on the same LAN subnet), see here. -
Accepted Answer
-
Accepted Answer
Tony Ellis wrote:
Thanks - that looks good.
Are web-pages loading OK? Syswatch stopped recording multiple ping failures? - or still problems...
Thank you for all the help, for now it's good
I will monitor the situation further.
Is there any easy way to bond the 2 internal interfaces? (In windows server it's like 3 clicks away
) -
Accepted Answer
-
Accepted Answer
Yes, that's better than how they are configured now... You are susceptible with all these ping failures to syswatch restarting and dropping connections temporarily...
Reading your first append again I see you are really on 7.3 now... Can you run "ip route show table 250" when you have updated your network.
Table 250 may not have shown in the output you provided as a result of the two unused interfaces... or ???
Another thought - what does "netstat -r" show? (after re-config)
[root@router ~]# ip route show table 250
default proto static
nexthop via 89.72.50.1 dev enp9s0f0 weight 3
nexthop via 192.168.1.1 dev enp9s0f1 weight 1
[root@router ~]#
and the netstat:
[root@router ~]# netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
default 192.168.1.1 0.0.0.0 UG 0 0 0 enp9s0f1
89.72.50.0 0.0.0.0 255.255.254.0 U 0 0 0 enp9s0f0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eno1
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eno2
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp9s0f1
[root@router ~]#
-
Accepted Answer
So for now as far as I understand I should set unused interfaces as internal?
Yes, that's better than how they are configured now... You are susceptible with all these ping failures to syswatch restarting and dropping connections temporarily...
Reading your first append again I see you are really on 7.3 now... Can you run "ip route show table 250" when you have updated your network.
Table 250 may not have shown in the output you provided as a result of the two unused interfaces... or ???
Another thought - what does "netstat -r" show? (after re-config) -
Accepted Answer
Nick Howitt wrote:
I presume ifcfg-enp10s0f0 and ifcfg-enp10s0f1are unused NIC's. Clearly they are upsetting syswatch so can you try setting them to LAN on different subnets?
Also, but possibly not relevant, the configuration of eno1 and eno2 does not look right as they both share the same LAN subnet.Tony Ellis wrote:
Nick is spot-on - never have configured unused WAN ports with Multi-WAN. Also agree re. LAN ports on same sub-net - in this case the lower of the two IPs is the one that the system will attempt to use...
The output from "ip route show table all | awk '/default/ && /table/' | egrep -v 'prohibit|error|proto'" has me perplexed - there is no table 250...
Seems to indicate yours is missing or you are really running ClearOS 6.x. (you indicated 7.2) What is the output of "ip route show table 250" ?
Example output from ClearOS 7.x multi-wan system
[root@alex mrtg]# ip route show table all | awk '/default/ && /table/' | egrep -v 'prohibit|error|proto'
default via 192.168.6.1 dev enp0s10 table 100
default via 192.168.2.35 dev enp0s18 table 101
default via 192.168.2.35 dev enp0s18 table 250
[root@alex mrtg]# ip route show table 250
default via 192.168.2.35 dev enp0s18
Example from ClearOS 6.x multi-wan system
[root@may ~]# ip route show table all | awk '/default/ && /table/' | egrep -v 'prohibit|error|proto'
default via 192.168.4.1 dev eth0 table 100
default via 192.168.0.1 dev eth2 table 101
[root@may ~]# ip route show table 250
default proto static
nexthop via 192.168.4.1 dev eth0 weight 1
nexthop via 192.168.0.1 dev eth2 weight 200
Let me explain my idea for the config at hand
So ideally I tried to make this config in a configure and forget manner, thus interface setup.
Ideally what I wanted:
2 onboard NIC's bonded for internal lan Gateway
4 external NIC's for external interfaces (that is the general destination I'm going for, I'm in the middle of negotiating additional connections from different ISP's)
Haven't yet had time to bond 2 onboard NIC's as it seems it's quite a bit of work, that's why both are on the same subnet - one is static IP, which serves as gateway, dhcp server and etc. and the other one just uses the config from the first one. - Both are on the same LAN, second one is currently unused.
As for 6.x clearos, I'm sure I have made the install from 7.2 clearos ISO downloaded from the site at 23rd Feb - I do not know why does the config look that way
So for now as far as I understand I should set unused interfaces as internal? -
Accepted Answer
Nick is spot-on - never have configured unused WAN ports with Multi-WAN. Also agree re. LAN ports on same sub-net - in this case the lower of the two IPs is the one that the system will attempt to use...
The output from "ip route show table all | awk '/default/ && /table/' | egrep -v 'prohibit|error|proto'" has me perplexed - there is no table 250...
Seems to indicate yours is missing or you are really running ClearOS 6.x. (you indicated 7.2) What is the output of "ip route show table 250" ?
Example output from ClearOS 7.x multi-wan system
[root@alex mrtg]# ip route show table all | awk '/default/ && /table/' | egrep -v 'prohibit|error|proto'
default via 192.168.6.1 dev enp0s10 table 100
default via 192.168.2.35 dev enp0s18 table 101
default via 192.168.2.35 dev enp0s18 table 250
[root@alex mrtg]# ip route show table 250
default via 192.168.2.35 dev enp0s18
Example from ClearOS 6.x multi-wan system
[root@may ~]# ip route show table all | awk '/default/ && /table/' | egrep -v 'prohibit|error|proto'
default via 192.168.4.1 dev eth0 table 100
default via 192.168.0.1 dev eth2 table 101
[root@may ~]# ip route show table 250
default proto static
nexthop via 192.168.4.1 dev eth0 weight 1
nexthop via 192.168.0.1 dev eth2 weight 200
-
Accepted Answer
-
Accepted Answer
Dear Tony,
Thank you for your answer, I can only configure the secondary LTE connection to normal "NAT" mode, here are the results after such change:
[root@router ~]# ip -4 address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
inet 192.168.0.1/24 brd 192.168.0.255 scope global eno1
valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
inet 192.168.0.199/24 brd 192.168.0.255 scope global dynamic eno2
valid_lft 3850sec preferred_lft 3850sec
4: enp9s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
inet 89.72.xx.xx/23 brd 255.255.255.255 scope global dynamic enp9s0f0
valid_lft 145985sec preferred_lft 145985sec
5: enp9s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
inet 192.168.1.51/24 brd 192.168.1.255 scope global dynamic enp9s0f1
valid_lft 86202sec preferred_lft 86202sec
[root@router ~]# ip route show table all | awk '/default/ && /table/' | egrep -v 'prohibit|error|proto'
default via 89.72.50.1 dev enp9s0f0 table 100
default via 192.168.1.1 dev enp9s0f1 table 101
Working on the syswatch log, waiting for failures, will edit post once done
EDIT: Syswatch log:
Thu Mar 30 12:15:02 2017 info: system - syswatch terminated
Thu Mar 30 12:15:02 2017 info: system - syswatch started
Thu Mar 30 12:15:02 2017 info: config - IP referrer disabled in multi-WAN
Thu Mar 30 12:15:02 2017 info: config - IP referrer tool is installed
Thu Mar 30 12:15:02 2017 info: config - debug level - 0
Thu Mar 30 12:15:02 2017 info: config - retries - 3
Thu Mar 30 12:15:02 2017 info: config - heartbeat - 15
Thu Mar 30 12:15:02 2017 info: config - interval - 20 seconds
Thu Mar 30 12:15:02 2017 info: config - offline interval - 10 seconds
Thu Mar 30 12:15:02 2017 info: config - referrer IP detection - disabled
Thu Mar 30 12:15:02 2017 info: config - ping server auto-detect - enabled
Thu Mar 30 12:15:02 2017 info: config - try pinging gateway - yes
Thu Mar 30 12:15:02 2017 info: config - number of external networks - 4
Thu Mar 30 12:15:02 2017 info: config - monitoring external network - enp10s0f0
Thu Mar 30 12:15:02 2017 info: config - monitoring external network - enp9s0f0
Thu Mar 30 12:15:02 2017 info: config - monitoring external network - enp9s0f1
Thu Mar 30 12:15:02 2017 info: config - monitoring external network - enp10s0f1
Thu Mar 30 12:15:02 2017 info: config - number of standby networks - 0
Thu Mar 30 12:15:02 2017 info: info - loading network configuration
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp10s0f0 - config: ifcfg-enp10s0f0
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp10s0f0 - onboot: enabled
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp10s0f0 - type: dhcp
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp10s0f0 - wifi: disabled
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp9s0f0 - config: ifcfg-enp9s0f0
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp9s0f0 - onboot: enabled
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp9s0f0 - type: dhcp
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp9s0f0 - wifi: disabled
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp9s0f1 - config: ifcfg-enp9s0f1
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp9s0f1 - onboot: enabled
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp9s0f1 - type: dhcp
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp9s0f1 - wifi: disabled
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp10s0f1 - config: ifcfg-enp10s0f1
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp10s0f1 - onboot: enabled
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp10s0f1 - type: dhcp
Thu Mar 30 12:15:02 2017 info: info - network configuration for enp10s0f1 - wifi: disabled
Thu Mar 30 12:15:02 2017 info: enp10s0f0 - network - IP address - unknown
Thu Mar 30 12:15:02 2017 info: enp10s0f0 - network - gateway - unknown
Thu Mar 30 12:15:02 2017 info: enp10s0f0 - network - type - to be determined
Thu Mar 30 12:15:02 2017 info: enp9s0f0 - network - IP address - 89.72.xx.xx
Thu Mar 30 12:15:02 2017 info: enp9s0f0 - network - gateway - 89.72.50.1
Thu Mar 30 12:15:02 2017 info: enp9s0f0 - network - type - public IP range
Thu Mar 30 12:15:02 2017 info: enp9s0f1 - network - IP address - 192.168.1.51
Thu Mar 30 12:15:02 2017 info: enp9s0f1 - network - gateway - 192.168.1.1
Thu Mar 30 12:15:02 2017 info: enp9s0f1 - network - type - private IP range
Thu Mar 30 12:15:03 2017 info: enp10s0f1 - network - IP address - unknown
Thu Mar 30 12:15:03 2017 info: enp10s0f1 - network - gateway - unknown
Thu Mar 30 12:15:03 2017 info: enp10s0f1 - network - type - to be determined
Thu Mar 30 12:15:03 2017 info: enp10s0f0 - ping check - no IP available
Thu Mar 30 12:15:03 2017 info: enp10s0f1 - ping check - no IP available
Thu Mar 30 12:15:03 2017 info: enp10s0f0 - restarting DHCP connection
Thu Mar 30 12:15:09 2017 info: enp10s0f1 - restarting DHCP connection
Thu Mar 30 12:15:15 2017 info: system - changing active WAN list - enp9s0f1 enp9s0f0 (was startup)
Thu Mar 30 12:15:15 2017 info: system - current WANs in use - enp9s0f1 enp9s0f0
Thu Mar 30 12:15:15 2017 info: system - restarting firewall
Thu Mar 30 12:15:16 2017 info: system - updating intrusion prevention whitelist
Thu Mar 30 12:15:16 2017 info: system - adding ping server 54.152.208.245
Thu Mar 30 12:15:16 2017 info: system - adding ping server 8.8.8.8
Thu Mar 30 12:15:16 2017 info: system - adding DNS server 8.8.8.8
Thu Mar 30 12:15:16 2017 info: system - adding DNS server 8.8.4.4
Thu Mar 30 12:15:16 2017 info: system - reloading intrusion prevention system
Thu Mar 30 12:15:19 2017 info: system - dynamic DNS updated
Thu Mar 30 12:15:29 2017 info: enp10s0f0 - ping check - no IP available
Thu Mar 30 12:15:29 2017 info: enp10s0f1 - ping check - no IP available
Thu Mar 30 12:15:29 2017 info: enp10s0f0 - restarting DHCP connection
Thu Mar 30 12:15:35 2017 info: enp10s0f1 - restarting DHCP connection
Thu Mar 30 12:15:51 2017 info: enp10s0f0 - ping check - no IP available
Thu Mar 30 12:15:51 2017 info: enp10s0f1 - ping check - no IP available
Thu Mar 30 12:15:51 2017 info: enp10s0f0 - restarting DHCP connection
Thu Mar 30 12:15:58 2017 info: enp10s0f1 - restarting DHCP connection
Thu Mar 30 12:16:14 2017 info: enp10s0f0 - ping check - no IP available
Thu Mar 30 12:16:14 2017 info: enp10s0f1 - ping check - no IP available
Thu Mar 30 12:16:14 2017 info: enp10s0f0 - restarting DHCP connection
Thu Mar 30 12:16:21 2017 info: enp10s0f1 - restarting DHCP connection
Thu Mar 30 12:16:37 2017 info: enp10s0f0 - ping check - no IP available
Thu Mar 30 12:16:37 2017 info: enp10s0f1 - ping check - no IP available
Thu Mar 30 12:16:37 2017 info: enp10s0f0 - restarting DHCP connection
Thu Mar 30 12:16:43 2017 info: enp10s0f1 - restarting DHCP connection
Thu Mar 30 12:17:00 2017 info: enp10s0f0 - ping check - no IP available
Thu Mar 30 12:17:00 2017 info: enp10s0f1 - ping check - no IP available
Thu Mar 30 12:17:00 2017 info: enp10s0f0 - restarting DHCP connection
Thu Mar 30 12:17:06 2017 info: enp10s0f1 - restarting DHCP connection
Thu Mar 30 12:17:22 2017 info: enp10s0f0 - ping check - no IP available
Thu Mar 30 12:17:23 2017 info: enp10s0f1 - ping check - no IP available
Thu Mar 30 12:17:23 2017 info: enp10s0f0 - restarting DHCP connection
Thu Mar 30 12:17:29 2017 info: enp10s0f1 - restarting DHCP connection
Thu Mar 30 12:17:45 2017 info: enp10s0f0 - ping check - no IP available
Thu Mar 30 12:17:45 2017 info: enp10s0f1 - ping check - no IP available
Thu Mar 30 12:17:45 2017 info: enp10s0f0 - restarting DHCP connection
Thu Mar 30 12:17:52 2017 info: enp10s0f1 - restarting DHCP connection
Thu Mar 30 12:18:08 2017 info: enp10s0f0 - ping check - no IP available
Thu Mar 30 12:18:08 2017 info: enp10s0f1 - ping check - no IP available
Thu Mar 30 12:18:08 2017 info: enp10s0f0 - restarting DHCP connection
Thu Mar 30 12:18:14 2017 info: enp10s0f1 - restarting DHCP connection
Thu Mar 30 12:18:31 2017 info: enp10s0f0 - ping check - no IP available
Thu Mar 30 12:18:31 2017 info: enp10s0f1 - ping check - no IP available
Thu Mar 30 12:18:31 2017 info: enp10s0f0 - restarting DHCP connection
Thu Mar 30 12:18:37 2017 info: enp10s0f1 - restarting DHCP connection
Thu Mar 30 12:18:53 2017 info: enp10s0f0 - ping check - no IP available
Thu Mar 30 12:18:53 2017 info: enp10s0f1 - ping check - no IP available
Thu Mar 30 12:18:53 2017 info: enp10s0f0 - restarting DHCP connection
Thu Mar 30 12:19:00 2017 info: enp10s0f1 - restarting DHCP connection
Thu Mar 30 12:19:16 2017 info: enp10s0f0 - ping check - no IP available
Thu Mar 30 12:19:16 2017 info: enp10s0f1 - ping check - no IP available
Thu Mar 30 12:19:16 2017 info: enp10s0f0 - restarting DHCP connection
Thu Mar 30 12:19:22 2017 info: enp10s0f1 - restarting DHCP connection
Thu Mar 30 12:19:39 2017 info: enp10s0f0 - ping check - no IP available
Thu Mar 30 12:19:39 2017 info: enp10s0f1 - ping check - no IP available
Thu Mar 30 12:19:39 2017 info: enp10s0f0 - restarting DHCP connection
Thu Mar 30 12:19:45 2017 info: enp10s0f1 - restarting DHCP connection
Thu Mar 30 12:20:01 2017 info: enp10s0f0 - ping check - no IP available
Thu Mar 30 12:20:02 2017 info: enp10s0f1 - ping check - no IP available
Thu Mar 30 12:20:02 2017 info: enp10s0f0 - restarting DHCP connection
Thu Mar 30 12:20:08 2017 info: enp10s0f1 - restarting DHCP connection
Thu Mar 30 12:20:24 2017 info: enp10s0f0 - ping check - no IP available
Thu Mar 30 12:20:24 2017 info: enp10s0f1 - ping check - no IP available
Thu Mar 30 12:20:24 2017 info: enp10s0f0 - restarting DHCP connection
Thu Mar 30 12:20:31 2017 info: enp10s0f1 - restarting DHCP connection
Thu Mar 30 12:20:47 2017 info: system - heartbeat...
-
Accepted Answer
Yuk! - both interfaces in trouble - what percentage of the time are they in that state?
As a test are you able to set both modem/routers on your external interfaces to NAT mode and then set them up together with your ClearOS box to provide private address range static ips to the ClearOS multiwan interfaces. Each ClearOS external interface will need to be on a different sub-net and also each different to all of your internal sub-nets. Be sure to check the default routes and DNS servers are correctly setup.
If you are able to do this can you provide the output from the commands below... if you cannot do the test - can you show the results anyway...
# ip -4 address
# ip route show table all | awk '/default/ && /table/' | egrep -v 'prohibit|error|proto'
and an extract from syswatch from the time you run "systemctl restart syswatch.service" until you either we have "info: system - heartbeat..." or a few lines of ping failures. -
Accepted Answer
Tony Ellis wrote:
Do do you have any ping failures in /var/log/syswatch" - an example
Tue Dec 20 19:27:00 2016 info: eth2 - ping check on server #1 failed - 8.8.4.4
Tue Dec 20 19:27:05 2016 info: eth2 - ping check on server #2 failed - 61.9.173.37
Tue Dec 20 19:27:05 2016 warn: eth2 - connection warning
Hmm, I will paste some lines, there are several fails:
Tue Mar 28 14:33:06 2017 warn: enp9s0f1 - connection warning
Tue Mar 28 14:33:06 2017 info: enp10s0f1 - ping check - no IP available
Tue Mar 28 14:33:06 2017 info: enp10s0f0 - restarting DHCP connection
Tue Mar 28 14:33:12 2017 info: enp10s0f1 - restarting DHCP connection
Tue Mar 28 14:33:28 2017 info: system - heartbeat...
Tue Mar 28 14:36:13 2017 warn: system - dynamic DNS update failed - see system log
Tue Mar 28 14:36:13 2017 info: system - DNS update will try again on next heartbeat
Tue Mar 28 14:36:13 2017 info: enp10s0f0 - ping check - no IP available
Tue Mar 28 14:36:15 2017 info: enp9s0f1 - ping check on server #1 passed - 8.8.8.8
Tue Mar 28 14:36:15 2017 info: enp10s0f1 - ping check - no IP available
Tue Mar 28 14:36:15 2017 info: enp10s0f0 - restarting DHCP connection
Tue Mar 28 14:36:22 2017 info: enp10s0f1 - restarting DHCP connection
Tue Mar 28 14:36:38 2017 info: enp10s0f0 - ping check - no IP available
Tue Mar 28 14:36:38 2017 info: enp10s0f1 - ping check - no IP available
Tue Mar 28 14:36:38 2017 info: enp10s0f0 - restarting DHCP connection
Tue Mar 28 14:36:44 2017 info: enp10s0f1 - restarting DHCP connection
Tue Mar 28 14:37:01 2017 info: enp10s0f0 - ping check - no IP available
Tue Mar 28 14:37:03 2017 debug: enp9s0f1 - ping check on server #1 failed - 8.8.8.8 (ping size: 1)
Tue Mar 28 14:37:05 2017 info: enp9s0f1 - ping check on server #1 failed - 8.8.8.8
Tue Mar 28 14:37:12 2017 info: enp9s0f1 - ping check on server #2 failed - 54.152.208.245
It's a hit and miss, some passess, some fails -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Nick Howitt wrote:
What IP is ClearOS getting from the Dlink when it is in bridge mode? Does ClearOS work when the router is not in bridge mode?
It gets external IP address, I haven't tried switching the D-Link to normal mode, should I try it?
EDIT: There's a development, when I route e.g. HTTP traffic staticly through LTE it works, but still sometimes I get pages that won't load for some time. DNS's are set per previous tip to google.
EDIT2: Even in the WebUI some apps get this: "Additional Info Connection failure." -
Accepted Answer
-
Accepted Answer
Ok, so now there's another issue:
As stated before I have 2 ISP's connected to the ClearOS machine.
LTE via DWR-921 D-Link router in bridge mode and land connection.
Both are DHCP, however the LTE connection does not accept any traffic - when connecting to the D-Link via other device (cos unplugged, laptop plugged in) the internet connection works just fine.
Multi-Wan says connection is in-use and online.
I have set weight of land line to 3 and LTE to 1.
Do you have any tips as to how to solve this issue?
EDIT: What I have meant is that no inside to outside traffic goes through LTE connection, and sometimes there's loss of packets. -
Accepted Answer
Hello!
I greatly appreciate your answer, thank you.
Ad. 1 Per your instruction I have changed DNS's to 8.8.8.8 and 8.8.4.4 - will monitor the connection behaviour.
Output of the command:
03:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5720 Gigabit Ethernet PCIe
Subsystem: Hewlett-Packard Company Device 2133
Kernel driver in use: tg3
Kernel modules: tg3
03:00.1 Ethernet controller: Broadcom Limited NetXtreme BCM5720 Gigabit Ethernet PCIe
Subsystem: Hewlett-Packard Company Device 2133
Kernel driver in use: tg3
Kernel modules: tg3
--
09:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
Subsystem: Intel Corporation Gigabit ET Quad Port Server Adapter
Kernel driver in use: igb
Kernel modules: igb
09:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
Subsystem: Intel Corporation Gigabit ET Quad Port Server Adapter
Kernel driver in use: igb
Kernel modules: igb
0a:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
Subsystem: Intel Corporation Gigabit ET Quad Port Server Adapter
Kernel driver in use: igb
Kernel modules: igb
0a:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
Subsystem: Intel Corporation Gigabit ET Quad Port Server Adapter
Kernel driver in use: igb
Kernel modules: igb
Ad. 2 It worked, you're the best!
Ad. 3 didn't help
Ad. 4 Taking a read right now! -
Accepted Answer
Sorry you're having problems. Unfortunately there is no way to roll back to 7.2 but there is no real reason why 7.3 is unstable. ClearOS will update itself automatically to the latest stable release unless you specifically turn the feature off.
1 - Presumably your two WAN connections use different ISP's. What have you set your external DNS resolvers to? Generally with MultiWAN it is better to use a public DNS service such as OpenDNS or Google DNS. I don't think NIC drivers are an issue with your machine, but just in case, can you give the output to "lspci -k | grep Eth -A 3"?
2 - I don't know, but can you try selecting a different language then switching back to Polish?
3 - Can you perhaps try restarting the webconfig "service webconfig restart". I can't remember which package drives the resource report
4 - Chatty logs are an annoying feature of 7.x (and some of it is inherited from Centos/RHEL). Have a look at this thread for some ideas.
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »