Soldato
- Joined
- 18 Oct 2002
- Posts
- 4,898
I'm running CentOS 6.5 on a HP Microserver, which has 2 network interfaces.
The box is being set up to be used as a Squid reverse proxy.
The interfaces show in CentOS as eth0 and eth1.
eth0 has an IP of 172.16.2.29/16
eth1 has an IP of 172.16.17.10/16
With eth0 physically connected to the network (eth1 unplugged), the machine responds to ping requests for both IP's.
With eth1 physically connected to the network (eth0 unplugged), the machine fails to respond to pings on either IP.
The above tests are done moving the same cable to the other socket - there's nothing different in terms of switch configuration.
If I do ifconfig eth1 down, it still responds to 172.16.17.10.
When I plug/unplug the cables, I get a message in the console showing this on the relevant interface.
It seems to me that it must be something clever that CentOS is doing because the addresses are on the same subnet, but this is undesirable.
When the box is installed, eth1 will be connected to a separate VLAN containing some web servers we don't want on our network. We want our LAN users to hit the eth0 address and this box to proxy the traffic.
The box is being set up to be used as a Squid reverse proxy.
The interfaces show in CentOS as eth0 and eth1.
eth0 has an IP of 172.16.2.29/16
eth1 has an IP of 172.16.17.10/16
With eth0 physically connected to the network (eth1 unplugged), the machine responds to ping requests for both IP's.
With eth1 physically connected to the network (eth0 unplugged), the machine fails to respond to pings on either IP.
The above tests are done moving the same cable to the other socket - there's nothing different in terms of switch configuration.
If I do ifconfig eth1 down, it still responds to 172.16.17.10.
When I plug/unplug the cables, I get a message in the console showing this on the relevant interface.
It seems to me that it must be something clever that CentOS is doing because the addresses are on the same subnet, but this is undesirable.
When the box is installed, eth1 will be connected to a separate VLAN containing some web servers we don't want on our network. We want our LAN users to hit the eth0 address and this box to proxy the traffic.