Two interfaces on the same network

[Al]

eth0(wired) and eth1(wireless) work fine in the different network. But
not work correctly in the same network.
 
My problem is:
 
On my linux device:
>ifconfig eth0 172.20.1.30 netmask 255.255.255.0
>ifconfig eth1 172.20.1.31 netmask 255.255.255.0
 
Another PC has IP 172.20.1.32
 
They are connected with a Hub.
 
When PC with IP 172.20.1.32 use browser to access
http://172.20.1.31, linux device reply by eth0, not eth1.(by sinffer)
That is, linux device seems only to use eth0 (first brought up)
when all interfaces are in the same network. Packets won't
be passed thru eth1 even if I intend to do so. If eth0 wire is unplug,
eth1 won't work too since linux only use eth0 if eth0/eth1 are in the same network.
 
Thanks,
 
AL Chane
 
 
 

	-----Original Message----- 
	From: redhat-list-bounces at redhat.com 代理 Larry Brown 
	Sent: 2004/6/9 [星期三] 下午 10:33 
	To: General Red Hat Linux discussion list 
	Cc: 
	Subject: Re: Two interfaces on the same network
	
	

	I'm still not sure why your two networks wireless and wired cannot have
	different networks.  If you do not have a wireless node on your wired
	network to allow wireless users onto the wired network, simply set your
	wireless interface to one subnet, the wired to another network and allow
	routing of packets between the two networks.  No?
	
	.> My application is an IP Camera with two interfaces (eth0 is wired
	> ethernet, eth1 is wireless) running on uClinux. IP Camera provides
	> an Http server so clinet browers can access by either ethernet or wireless.
	>
	> Two interfaces work fine with different networks, but have probem
	> to work in the same network as I described in the previous message.
	>
	> The situation I might have is like this:
	>
	>     Users need first to use ethernet (eth0) to access http server
	>     to setup wireless(eth1) like SSID, WEP. Once wireless is setup,
	>     two interface eth0/eth1 with two IPS exist in the same network.
	>     If user unplug the ethernet wire, wireless won't work unless
	>     I make ethernet down or change ethernet IP to different network.
	>     This step might not be friendly for ordinary users.
	>
	> Thanks :)
	>
	> AL Chane