Re: Two interfaces on the same network

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



To make sure I understand the whole picture, as it appears close... The
camera is directly connected to what is running Linux and the object
running linux would be mounted up on the wall along with the camera?  If
that is correct, why not simply stay on wireless and not have a wired
component?  Wireless speed should be faster than your Internet
connection for http access so the difference in speed should not affect
your internet viewing audience.

On Thu, 2004-06-10 at 23:30, AL Chane wrote:
> Larry Brown æå:
> > Why do you have a wireless connection to the same device you have a
> > wired connection to?  You should be able to have wireless devices
> > connect to your "Wireless AP Router" which should provide an IP address
> > to the wireless device on the 172.20.1.0 network.  
> 
> >>_________eth0 172.20.1.30   _______________
> >>|#1 PC  |-----------------> |Wireless AP  |
> >>|Linux  |                   |Router       |->ADSL->Internet
> >>|Http   |eth1 172.20.1.31   |172.20.1.254 |
> >>|Server |...wireless......> |_____________|
> >>|_______|                        ^
> >>                                 |
> >>__________                       |
> >>|#2 PC   |                       |
> >>|Windows |NIC 172.20.1.32        |
> >>|Http    |-----------------------|
> >>|client  |
> >>|________|
> >>
> 
> Yeah, it may sound redundant, but it could happen in my case.
> My Linux box is an embeded IP camera with Http server built-in so
> clinet PC #2 can use brower with IP address (172.20.1.30/31)to
> access it.
> 
> At very first time, users need to use wired ethernet to configure
> IP Cam's wireless setting (SSID,WEP, etc) to make wireless connection
> work. At this time, two interfaces in the same subnet exists. Then users
> might just unplug ethernet and put IP camera on the wall without
> ethernet cable. But now Linux box's route table still have
> (eth0 wired) for same subnet, so traffic won't go thru wireless eth1
> unless wired eth0 is brought down or have subnet changed to make
> traffic pass thru wireless eth1. Otherwise, users might think wireless
> eth1 function doesn't work at all.
> 
> 
> thanks,
> 
> AL
> 


-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux