Yves, Thanks for the reply. That matches what I just figured out. Just have to try it on the unit and see what happens.
On Fri, Feb 20, 2015 at 1:46 PM, Yves Dorfsman <y...@zioup.com> wrote: > On 2015-02-20 11:16, john boris wrote: > > > > If the Lightsout port is given the 172.10.5.30 IP with a netmask of > > 255.255.248.0 and a route to 172.10.10.1 would that allow someone > coming in > > from the central site to see it? > > > > We are experimenting with this and can talk off line if need be. Also any > > pointers to a good explanation of setting up routes across multiple > subnets > > would be appreciated. > > Use an ipv4 subnet calculator! > > The range of addresses in the 172.10.10.0/23 is 172.10.10.1 to > 172.10.11.254. > > The range of addresses in the 172.10.0.0/21 subnet is 172.10.0.1 to > 172.10.7.254. > > You need to make sure that there isn't any overlap (otherwise routing no > longer makes any sense), there is no overlap here = good. > > Comms to any address in that range will be local, comms to addresses > outside > that range will be forwarded to a router. You have to have a router (could > be > one of your server acting as a router) on that subnet. 172.10.10.1 is > outside > of that range, so you need a routing device from your subnet to the central > router. > > -- > http://yves.zioup.com > gpg: 4096R/32B0F416 > > _______________________________________________ > Tech mailing list > Tech@lists.lopsa.org > https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech > This list provided by the League of Professional System Administrators > http://lopsa.org/ > -- John J. Boris, Sr. Head Freshmen Football Coach Camden Catholic High School
_______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
