Re[2]: Two interfaces on the same network

• Previous message: Kris Kennaway: "Re: HEADSUP! netgraph Metadata changing."
• Maybe in reply to: AL Chane: "Two interfaces on the same network"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Thu, 10 Jun 2004 16:02:12 +0300
To: freebsd-net@freebsd.org

Здравствуйте, .

---------- Пересылаемое письмо ----------
От: Ilya B. <dia@podolsk.net>
К: Roman Kurakin <rik@cronyx.ru>
А также к:
Время создания: Thu, 10 Jun 2004 16:00:43 +0300
Тема: Two interfaces on the same network
Прикрепленные файлы: <нет>

Здравствуйте, Roman.

Вы писали 9 июня 2004 г., 13:04:40:

RK> 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.

RK> I don't know how in linux, probably the same, but I didn't setup it on
RK> linux.
RK> In FreeBSD you could do this via bridging. If you turn on bridging you just
RK> need to assign IP to one of the interfaces. Also do not forget to turn
RK> on forwarding.
RK> All side effects could be fixed by firewall rules.

RK> By the way it would be better if you choose other list, cause this one
RK> is for freebsd
RK> not for linux. I am not sure if this violates policy of this list but
RK> for sure you would be
RK> less lucky here.

RK> 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"
>>
>>

RK> _______________________________________________
RK> freebsd-net@freebsd.org mailing list
RK> http://lists.freebsd.org/mailman/listinfo/freebsd-net
RK> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"

In FreeBSD works next sheme:
su-2.05b# ifconfig
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 213.85.29.138 netmask 0xfffffff0 broadcast 213.85.29.143
        inet6 fe80::202:a5ff:fe41:ccd6%fxp0 prefixlen 64 scopeid 0x1
        inet 213.85.29.130 netmask 0xffffffff broadcast 213.85.29.130
        ether 00:02:a5:41:cc:d6
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active

But aliased IP adress couldn't be a gateway.

-- 
С уважением,
 Ilya                          mailto:dia@podolsk.net
---------- Конец пересылаемого письма ----------
-- 
С уважением,
 Ilya                          mailto:dia@podolsk.net
_______________________________________________
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"

• Previous message: Kris Kennaway: "Re: HEADSUP! netgraph Metadata changing."
• Maybe in reply to: AL Chane: "Two interfaces on the same network"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]