Alkis Georgopoulos skrev: > Στις 12-01-2010, ημέρα Τρι, και ώρα 09:06 +0100, ο/η Verner Kjærsgaard > έγραψε: >> Say the eth0 server IP is 192.168.0.10, I could then configure the other >> 3 interfaces like >> >> eth1: 192.168.0.11, >> eth2: 192.168.0.12, >> eth3: 192.168.0.13 > > Ethernet bonding would be easier to manage, and would provide better > load balancing and failover: > https://help.ubuntu.com/community/UbuntuLTSP/Trunking > > I had a lab with 4 x 100mbps NICs on the server for about 6 months, > before I upgraded it to gigabit, and bonding made things almost 4x > faster. >
- thank you for your answers! - just to clarify... - I've got 4 24-port switches that connects to all the clients. 100Mbit ports to the clients, 1000Mbit to the server. As of now they are just connected to each other, leaving three of them in a poor state as they are not even properly uplinked (not my fault, they didn't buy swithes with 1000Mbit uplink ports...). - my idea is to connect each switch to its own netcard on the server... - is this a correct approach? -- ------------------------------ Med venlig hilsen/Best regards Verner Kjærsgaard ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
