From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR
Description of problem:
I've got a test machine in my network and the following situation:
Firewall Internal IP: 192.168.1.1
Gateway IP to 192.168.0.0/24 is 192.168.1.2
Test machine has IP 192.168.0.50 (eth0).
I give Test machine 192.168.1.1 (eth1) with ifconfig and then
type "ifconfig eth1 down".
Normal ifconfig output then shows only eth0. With
"ifconfig -a" I can see the IP from eth1 further.
Now, when I want to ping from 192.168.1.1 to 192.168.0.50,
the test machine got the packet (find out with tcpdump)
but doesn't send a reply. It sends the answer to eth1.
When I give eth1 a completly different IP again, the reply
will arrive the Firewall.
Perhaps it's a problem of the kernel, I'm not a developer.
Is it a known bug ?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
From what i understand of your description this is expected behaviour:
You have only shut down the interface but not 'completely' disabled it (via
module unloading, route deletetion etc), so without any iptables or ipchains
rules the interface will still receive packages, but the kernel obviously won't
route them anymore.
And as soon as you give your interface another IP address it automatically
becomes up again and therefore starts to operate again.
I hope i have understood your problem correctly.
Read ya, Phil