From owner-freebsd-net@FreeBSD.ORG Wed Jun 9 10:11:14 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04DB316A4CE for ; Wed, 9 Jun 2004 10:11:14 +0000 (GMT) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F8EA43D2F for ; Wed, 9 Jun 2004 10:11:13 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru id i59A85sW035729 for freebsd-net@freebsd.org.checked; (8.12.8/vak/2.1) Wed, 9 Jun 2004 14:08:05 +0400 (MSD) (envelope-from rik@cronyx.ru) Received: from cronyx.ru (hi.cronyx.ru [144.206.181.94]) by hanoi.cronyx.ru with ESMTP id i59A5uji035624; (8.12.8/vak/2.1) Wed, 9 Jun 2004 14:05:56 +0400 (MSD) (envelope-from rik@cronyx.ru) Message-ID: <40C6E0B8.2090502@cronyx.ru> Date: Wed, 09 Jun 2004 14:04:40 +0400 From: Roman Kurakin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: AL Chane References: <40C68254.7040501@issc.com.tw> <40C6A56A.5040105@cronyx.ru> <40C6B144.5040203@issc.com.tw> In-Reply-To: <40C6B144.5040203@issc.com.tw> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org Subject: Re: Two interfaces on the same network X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jun 2004 10:11:14 -0000 AL Chane wrote: >> AL Chane: >> >>> Hi, there: >>> >>> I have two interfaces on my linux PC in the same network: >>> >>>> ifconfig eth0 172.20.1.30 netmask 255.255.255.0 >>>> ifconfig eth1 172.20.1.31 netmask 255.255.255.0 >>>> >>> Another Windows PC with IP 172.20.1.32 netmask 255.255.255.0 >>> >>> I found that in the same network, Linux PC only use one interface >>> eth0 for outbound/inbound traffics no matter what. Even if I use >>> Windows >>> PC (172.20.1.32) to ping Linux PC's eth1 (172.20.1.31), Linux still use >>> eth0 to reply. That is, if I unplug eth0's wire, eth1 won't work too. >>> >>> Does anyone have the same issue on how to make two interfaces >>> work in the same network? I search 2003 archive, some said it can be >>> done by set second interface (eth1) netmask to 255.255.255.255, but >>> i tried and it doesn't work for me. >>> >>> Helps from you are highly appreciated! >>> >> Are they on the same wire? If so, why do you need such configuretion? >> >> rik > > > no, eth0 is wired ethernet. eth1 is wireless. > > 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 it by either ethernet or > wireless. I don't know how in linux, probably the same, but I didn't setup it on linux. In FreeBSD you could do this via bridging. If you turn on bridging you just need to assign IP to one of the interfaces. Also do not forget to turn on forwarding. All side effects could be fixed by firewall rules. By the way it would be better if you choose other list, cause this one is for freebsd not for linux. I am not sure if this violates policy of this list but for sure you would be less lucky here. rik > > 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. > In addition, in the same LAN, clients access thru wireless might > want switch back to wired access due to heavy wireless > traffic/wireless performance (sometimes choppy) > > Thanks :) > > AL Chane > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > >