<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> I agree, and that's how I've done it. Matter of fact, in our schools, I have to, given that our thin clients may be spread out through the school. VLANs save my hiney then. I can just dedicate one VLAN per thin-client segment, and boom, I'm off to the races. Layer 3 (aka "routing") would be done by the K12LTSP server for anything on the thin-client segment, so that's taken care of. --TP <div class="moz-signature">_______________________________ Do you <a href="http://www.gnu.org">GNU</a>? <a href="http://www.cmosnetworks.com">Microsoft Free since 2003</a>--the ultimate antivirus protection! </div> Paul VanGundy wrote: <blockquote cite="mid:33e277440812200326v2887a84cq4181798ebfdda81d@mail.gmail.com" type="cite"> <pre wrap="">Joseph, Continue on the path that works for you. It sounds like people go the route you have chosen. However, VLANs would work and don't need to be used JUST for breaking down large networks. This would work perfectly especially if you were doing layer 3 routing. There is no scalability issues as mentioned before...except hardware (ie you can't do VLANs on your hardware or your hardware doesn't support enough VLAN creations for the size of your network). I would be happy to discuss this with anyone if someone wished to pursue this route and had questions. /paul On Fri, Dec 19, 2008 at 10:56 AM, Joseph Bishay <a class="moz-txt-link-rfc2396E" href="mailto:joseph.bishay@gmail.com"><joseph.bishay@gmail.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Hello, 802.1q, or as I understand it -- VLANS -- would also do the same idea so to speak. The issue is the hardware. We don't have anything that is capable of doing VLANS. I thought since this isn't the case of a large single network that I'm trying to break up into two smaller virtual networks, but rather two distinct rooms that are coming together, I could use the 2 NICs to resolve it? Joseph On Fri, Dec 19, 2008 at 8:20 AM, Paul VanGundy <a class="moz-txt-link-rfc2396E" href="mailto:pvangundy@bradfordnetworks.com"><pvangundy@bradfordnetworks.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Joseph, Would 802.1q be a better solution instead of having two cards to separate two environments and a third NIC to act as your access to the outside world? /paul On Fri, Dec 19, 2008 at 12:30 AM, Joseph Bishay <a class="moz-txt-link-rfc2396E" href="mailto:joseph.bishay@gmail.com"><joseph.bishay@gmail.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Hello, How are you? I hope you are all doing well. I figure after lurking for a while it was time to get all my questions out. :) It ends up that our new LTSP network has two groups of clients (currently existing LTSP room A and a new room of thin clients in room B). Each room has a switch. There are 2 cables that then run from room A and B to a common server room where the LTSP server is. Originally the LTSP server was in room A serving only that room. Our LTSP server has 3 network cards. Currently one of those cards is not active. The second NIC plugs into the switch for the thin clients and the last NIC plugs into the router for Internet access. How do I activate that 3rd NIC card as a second thin client card? That way NIC A serves room A and NIC B serves room B and NIC C access the internet for room A & B? I wasn't able to search for this because I didn't know what this process was called -- I didn't think it was network bonding. Thank you. Joseph _______________________________________________ K12OSN mailing list <a class="moz-txt-link-abbreviated" href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</a> For more info see <a class="moz-txt-link-rfc2396E" href="http://www.k12os.org"><http://www.k12os.org></a> </pre> </blockquote> <pre wrap=""> -- Paul VanGundy Senior Network Engineer BRADFORD NETWORKS Toll Free: 1-866-990-3799 Office: 1-603-717-9361 Fax: 1-603-228-6420 SC Magazine "Innovator of the Year" 2007 & 2008 NOTICE REGARDING CONFIDENTIAL COMMUNICATION: The information in this electronic message is confidential and may be privileged, and is intended only for the recipient(s) listed above. If you are neither the intended recipient(s) nor a person responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any use, dissemination, distribution or reproduction of this communication is strictly prohibited. If you have received this communication in error, please immediately notify Bradford Networks, Inc. at (603) 228-5300. Thank you. _______________________________________________ K12OSN mailing list <a class="moz-txt-link-abbreviated" href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</a> For more info see <a class="moz-txt-link-rfc2396E" href="http://www.k12os.org"><http://www.k12os.org></a> </pre> </blockquote> <pre wrap="">_______________________________________________ K12OSN mailing list <a class="moz-txt-link-abbreviated" href="mailto:K12OSN@redhat.com">K12OSN@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/k12osn">https://www.redhat.com/mailman/listinfo/k12osn</a> For more info see <a class="moz-txt-link-rfc2396E" href="http://www.k12os.org"><http://www.k12os.org></a> </pre> </blockquote> <pre wrap=""> </pre> </blockquote> </body> </html>