John Haxby wrote:Ok, I investigated a bit further...in fact all the traffic for eth0 is redirected to eth1! Where can I change this?
Steven Moix wrote:I was surprised too, but it works...the problem is that it needs to be on the same network :/
Hello all, I have a little problem with my webserver, first of all, here is my network configuration:
Internet----Firewall/NAT----Switch----Weserver and Backup server
Webserver has 2 NIC: eth0: 192.168.1.200/24 eth1: 192.168.1.100/24 NAT rule on firewall: forward public IP to 192.168.1.200
Every night, I backup my server using eth1 (configured it in my backup software) and this works well.
The problem is the use of eth0: when I browse on a website hosted on my server from a computer at home, the request goes to eth0 (as configured in my firewall), but the return datas are sent through eth1 (it should of course be eth0)! Look at the ifconfig just after: eth0 TX is just 128Kb and all the traffic is gone through eth1 :-(
I'm surprised that it works at all -- except that I know that the routing stuff occasionally seems sentient :-) If you put eth0 and eth1 on separate networks, e.g. 192.168.1.100/24 and 192.168.2.100/24 (and change other machines correspondingly) then it should all work properly as their won't be any routing ambiguities.
jch
I tried this by pinging with a large packet size. I can ping 192.168.1.100 (eth1) and 192.168.1.200 (eth0) and the traffic on eth0 isn't increasing, but the traffic on eth1 is the sum of the 2 interfaces :-/
-- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
