Hi folks
I have a strange situation. My ClearOS 5.2 machine has two NICs eth0 and eth1 with two fix IP addresses from the server farm.
The networksetings are in "gateway mode" and both NICx are set up as external.
eth0 with IP0 serves one web page www.page1.com
eth0 wiht IP1 serves the second web page www.page2.com
eth0 had never problems. The web site is always accessable
eth1 while the IP still answers ping packages it often blocks the traffic on all testet ports (ssh, http, https, smtp, 81, 83)
restaring the network with solves the problem:
since the server also looses emails to people written to email@page2.com it becomes very annoying.
I stopped the intrusion detecten and prevention system services - but it still has the same problem.
PLEASE HELP. About 50 volunteers work on this system.
Greetings - Achim
I have a strange situation. My ClearOS 5.2 machine has two NICs eth0 and eth1 with two fix IP addresses from the server farm.
The networksetings are in "gateway mode" and both NICx are set up as external.
eth0 with IP0 serves one web page www.page1.com
eth0 wiht IP1 serves the second web page www.page2.com
eth0 had never problems. The web site is always accessable
eth1 while the IP still answers ping packages it often blocks the traffic on all testet ports (ssh, http, https, smtp, 81, 83)
restaring the network with solves the problem:
service network restartsince the server also looses emails to people written to email@page2.com it becomes very annoying.
I stopped the intrusion detecten and prevention system services - but it still has the same problem.
PLEASE HELP. About 50 volunteers work on this system.
Greetings - Achim
In Multiwan
Share this post:
Responses (9)
-
Accepted Answer
Two other thoughts.
1 - try disabling syswatch with a "service syswatch stop". If that works stop it running at boot with "chkconfig syswatch off"
2 - I don't think you are gaining much using a second NIC as they are both wired back to the same point. Remove the second NIC and set up a virtual IP on the first interface with the IP address you are using on the second. -
Accepted Answer
Thanks, Tony.
The only other thing I can think of is to insert a router between eth1 and the server farm. It will give you double-nat which is not ideal
but will give eth1 a completely different WAN IP and gateway. No promises, though. I think other firewall distro's solved this problem and I have no idea if 6.x solved it or not.
If you're into software hacking, purely guessing, but you may need to hack the syswatch routine to use a different set of ping servers on each interface then force the routing to these ping servers through different interfaces. Also the arping command supports interfaces but can only ping the gateway. -
Accepted Answer
Achim - the work I did with multi-wan on 5.2 will not help you. It was aimed at making the use of private sub-nets on the WAN interfaces more reliable, with each sub-net being different; i.e. modems for two different ISPs doing NAT. I have never seen multi-wan work well where both interfaces are on the same sub-net, other than using iptables to dedicate different ports to each interface so their is no overlap. This, of course, is not what you are trying to do... -
Accepted Answer
-
Accepted Answer
[root@peter ~]# ifconfig | grep eth -A 1
eth0 Link encap:Ethernet Hardware Adresse 00:0C:29:98:E6:C8
inet Adresse:aa.bb.cc.179 Bcast:aa.bb.cc.191 Maske:255.255.255.240
--
eth1 Link encap:Ethernet Hardware Adresse 00:0C:29:98:E6
2
inet Adresse:aa.bb.cc.189 Bcast:aa.bb.cc.191 Maske:255.255.255.240
[root@peter log]# tail -n 10 /var/log/syswatch
Fri Jul 3 19:03:15 2015 info: eth0 - ping check on server #1 failed - 69.90.141.72
Fri Jul 3 19:03:18 2015 info: eth0 - ping check on server #2 passed - 67.18.166.2
Fri Jul 3 19:03:40 2015 info: eth1 - ping check on server #1 failed - 69.90.141.72
Fri Jul 3 19:03:44 2015 info: eth1 - ping check on server #2 passed - 67.18.166.2
Fri Jul 3 19:03:46 2015 info: eth0 - ping check on server #1 failed - 69.90.141.72
Fri Jul 3 19:03:49 2015 info: eth0 - ping check on server #2 passed - 67.18.166.2
Fri Jul 3 19:04:11 2015 info: eth1 - ping check on server #1 failed - 69.90.141.72
Fri Jul 3 19:04:14 2015 info: eth1 - ping check on server #2 passed - 67.18.166.2
Fri Jul 3 19:04:16 2015 info: eth0 - ping check on server #1 failed - 69.90.141.72
Fri Jul 3 19:04:19 2015 info: eth0 - ping check on server #2 passed - 67.18.166.2
something else: I made changes on the master.cf of postfix
[...]
page1.com unix - - n - - smtp
-o smtp_bind_address=aa.bb.cc.189
-o smtp_helo_name=page1.com
-o syslog_name=postfix-page1_com
-o smtpd_tls_security_level=may
page2.com unix - - n - - smtp
-o smtp_bind_address=aa.bb.cc.179
-o smtp_helo_name=page2.com
-o syslog_name=postfix-page2_com
-o smtpd_tls_security_level=may
[...]
I did this for emails forom user@page1.com and user@page1.com not to be send from the same IP
I assume this is not the cause of the problem...
Thanks Nick! This is great -
Accepted Answer
-
Accepted Answer
[root@peter ~]# lspci -v | grep Eth
02:00.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 01)
02:02.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 01)
[root@peter ~]# grep eth /etc/modprobe.conf
alias eth0 e1000
alias eth1 e1000
[root@peter ~]# uname -r
2.6.18-308.1.1.v5
thanks for the reply -
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 »