[K12OSN] LTSP server with 3 NICs?

Sun Dec 21 01:32:19 UTC 2008

Hi Paul,

Actually, Layer 2 in the Ethernet context is "bridging", and "routing" 
is specific to Layer 3.  :-)

In the case of LTSP, the LTSP server would itself be the router, so the 
3750's routing engine (we use tons of those in my district, they're 
indeed very nice!) wouldn't need to come into play.  That said, we do 
use inter-VLAN routing to keep the "open SSID" wireless network away 
from anything on the school LAN while still providing Internet 
connectivity (Internet Web and DNS only).  VLANs are indeed very cool 
and very useful, and I love 'em.

--TP
_______________________________
Do you GNU <http://www.gnu.org>?
Microsoft Free since 2003 <http://www.cmosnetworks.com>--the ultimate 
antivirus protection!

Paul VanGundy wrote:
> Terrell,
>
> Ok. I specifically mentioned layer 3 routing because it can do inter
> VLAN routing where as layer 2 routing can not do inter VLAN routing
> (ie Cisco 3750s can while 2950s can not). Inter VLAN routing is what
> you may (or may not) want when segmenting a network.
>
> /paul
>
> 2008/12/20 "Terrell Prudé Jr." <microman at cmosnetworks.com>:
>   
>> 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
>> _______________________________
>> Do you GNU?
>> Microsoft Free since 2003--the ultimate antivirus protection!
>>
>>
>> Paul VanGundy wrote:
>>
>> 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 <joseph.bishay at gmail.com>
>> wrote:
>>
>>
>> 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
>> <pvangundy at bradfordnetworks.com> wrote:
>>
>>
>> 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 <joseph.bishay at gmail.com>
>> wrote:
>>
>>
>> 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
>> K12OSN at redhat.com
>> https://www.redhat.com/mailman/listinfo/k12osn
>> For more info see <http://www.k12os.org>
>>
>>
>>
>> --
>> 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
>> K12OSN at redhat.com
>> https://www.redhat.com/mailman/listinfo/k12osn
>> For more info see <http://www.k12os.org>
>>
>>
>>
>> _______________________________________________
>> K12OSN mailing list
>> K12OSN at redhat.com
>> https://www.redhat.com/mailman/listinfo/k12osn
>> For more info see <http://www.k12os.org>
>>
>>
>>
>>
>>
>> _______________________________________________
>> K12OSN mailing list
>> K12OSN at redhat.com
>> https://www.redhat.com/mailman/listinfo/k12osn
>> For more info see <http://www.k12os.org>
>>
>>     
>
>
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/k12osn/attachments/20081220/77a99dd0/attachment.htm>