Hi
We have set up a multi wan setup for our network.
In the IP Settings screen it shows that all devices are connected and working, however in the multi wan screen it shows that one device is offline i.e. the primary device
Interface Network Status Multi-WAN Status Backup Action
em1 Offline Offline Primary
ppp0 Online In Use Backup
We are using version 7 business edition.
I can confirm that the network connection is fine as i have tried to connect a laptop to it without the clearos firewall and it works fine.
Possibly something to do with routes?
Any help would be much appreciated
We have set up a multi wan setup for our network.
In the IP Settings screen it shows that all devices are connected and working, however in the multi wan screen it shows that one device is offline i.e. the primary device
Interface Network Status Multi-WAN Status Backup Action
em1 Offline Offline Primary
ppp0 Online In Use Backup
We are using version 7 business edition.
I can confirm that the network connection is fine as i have tried to connect a laptop to it without the clearos firewall and it works fine.
Possibly something to do with routes?
Any help would be much appreciated
In Multi-WAN
Share this post:
Responses (3)
-
Accepted Answer
This one is going to be beyond my knowledge. You not only have MultiWAN but you also appear to have a fixed IP block. With app-mulitwan installed I'd have expected you to have a bigger routing table with extra tables for each interface, but I can't find the document which shows it......... many minutes later found it!. See if it makes sense and all the tables are present.
As a thought, can you wither watch the pings in and out through the interface with tcpdump and/or try changing your interface IP to 84.43.120.97 (your lowest usable address)? I am curious to know if ClearOS is using the correct IP address when sending the ping and is receiving it correctly.
Out of curiosity is there any reason you are using a virtual interface on em1? There is the 1-to-1 NAT module if you're trying to forward the IP to your LAN. Otherwise I am not sure it is needed.
Similarly what is the purpose of ppp0:200 with the same IP as ppp0?
Are you using IPv6 on your LAN (em2?)? If so, that is also beyond my experience. -
Accepted Answer
Thanks for your reply
We are using 8.8.8.8 and 8.8.4.4
output of ifconfig is:
em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 84.43.120.98 netmask 255.255.255.248 broadcast 84.43.120.103
inet6 fe80::d267:e5ff:fee9:b61a prefixlen 64 scopeid 0x20<link>
ether d0:67:e5:e9:b6:1a txqueuelen 1000 (Ethernet)
RX packets 9125 bytes 657840 (642.4 KiB)
RX errors 0 dropped 5 overruns 0 frame 0
TX packets 6086 bytes 430490 (420.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
em1:200: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 84.43.120.99 netmask 255.255.255.248 broadcast 84.43.120.103
ether d0:67:e5:e9:b6:1a txqueuelen 1000 (Ethernet)
em2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::d267:e5ff:fee9:b61b prefixlen 64 scopeid 0x20<link>
ether d0:67:e5:e9:b6:1b txqueuelen 1000 (Ethernet)
RX packets 715839 bytes 488386230 (465.7 MiB)
RX errors 0 dropped 3 overruns 0 frame 0
TX packets 711111 bytes 149307551 (142.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 46514 bytes 4309033 (4.1 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 46514 bytes 4309033 (4.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
p1p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.1.1 netmask 255.255.255.0 broadcast 10.0.1.255
inet6 fe80::21b:21ff:fe3e:7c08 prefixlen 64 scopeid 0x20<link>
ether 00:1b:21:3e:7c:08 txqueuelen 1000 (Ethernet)
RX packets 2284007 bytes 912069466 (869.8 MiB)
RX errors 0 dropped 74 overruns 0 frame 0
TX packets 1887303 bytes 1542761348 (1.4 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xc5c20000-c5c3ffff
ppp0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1492
inet 176.35.144.17 netmask 255.255.255.255 destination 62.72.136.44
ppp txqueuelen 3 (Point-to-Point Protocol)
RX packets 388287 bytes 238360472 (227.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 375906 bytes 63106192 (60.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ppp0:200: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1492
inet 176.35.144.17 netmask 255.255.255.255 destination 176.35.144.17
ppp txqueuelen 3 (Point-to-Point Protocol)
output of ip route is:
10.0.1.0/24 dev p1p1 proto kernel scope link src 10.0.1.1
62.72.136.44 dev ppp0 proto kernel scope link src 176.35.144.17
84.43.120.96/29 dev em1 proto kernel scope link src 84.43.120.98
output of syswatch
Mon Feb 8 22:09:41 2016 info: system - heartbeat...
Mon Feb 8 22:09:43 2016 info: em1 - ping check on gateway failed - 84.43.122.76
Mon Feb 8 22:09:45 2016 info: em1 - ping check on server #1 failed - 8.8.8.8
Mon Feb 8 22:09:50 2016 info: em1 - ping check on server #2 failed - 54.152.208.245
Mon Feb 8 22:09:50 2016 warn: em1 - connection is down
Mon Feb 8 22:09:52 2016 info: em1 - waiting for static IP reconnect
Mon Feb 8 22:10:04 2016 info: em1 - ping check on gateway failed - 84.43.122.76
Mon Feb 8 22:10:06 2016 info: em1 - ping check on server #1 failed - 8.8.8.8
Mon Feb 8 22:10:11 2016 info: em1 - ping check on server #2 failed - 54.152.208.245
Mon Feb 8 22:10:11 2016 warn: em1 - connection is down
Mon Feb 8 22:10:13 2016 info: em1 - waiting for static IP reconnect
Mon Feb 8 22:10:25 2016 info: em1 - ping check on gateway failed - 84.43.122.76
Mon Feb 8 22:10:27 2016 info: em1 - ping check on server #1 failed - 8.8.8.8
Mon Feb 8 22:10:32 2016 info: em1 - ping check on server #2 failed - 54.152.208.245
Mon Feb 8 22:10:32 2016 warn: em1 - connection is down
Mon Feb 8 22:10:34 2016 info: em1 - waiting for static IP reconnect
Mon Feb 8 22:10:46 2016 info: em1 - ping check on gateway failed - 84.43.122.76
Mon Feb 8 22:10:48 2016 info: em1 - ping check on server #1 failed - 8.8.8.8
-
Accepted Answer
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 »