[K12OSN] Installing Multiple network cards Centos

David Hopkins dahopkins429 at gmail.com
Fri Feb 5 16:05:13 UTC 2010


James,

It can be done with channel bonding and probably by just adding the card as
a second card on a new 192 network.  IMHO James Kinney is the person that
really knows the channel bonding setup with K12LTSP CentOS (Sorry for
putting JK on the spot).  Google for chanel bonding.  I'd pick channel
bonding as the way to go.

But ... as for a second network, that should be possible by adding another
network. Below is how my dhcpd-k12ltsp.conf file is set up on a system I
have.  It handles dhcp on the main network (10.) for the Windows systems,
and also is still the dhcp server for the thin clients on 192.168.0.x
network.  I suppose you could change my Desktop section (10.) to be a
different 192.168.1.x network by just copying the workstation section and
changing the IP addresses, then add the correct entries in /etc/hosts and
have it also work.  Then, again, that might break everything.  I do know
that this setup works very well for me and I am using samba as a PDC
(10.179.2.9) with this DHCP setup.

dhcpd-k12ltsp with two networks:

default-lease-time            86400;
max-lease-time                86400;
ddns-update-style none;
allow booting;
allow bootp;

   option option-128 code 128 = string;
   option option-129 code 129 = text;
   option option-221 code 221 = text;

shared-network DESKTOPS {

     option subnet-mask                255.255.0.0;
     option broadcast-address       10.179.0.255;
     option routers                         10.179.1.1;
     option netbios-name-servers       10.179.2.9;
     option netbios-node-type          2;
     option domain-name-servers        10.179.2.6;
     option domain-name                "ncs.k12.de.us";

  subnet 10.179.0.0 netmask 255.255.0.0 {
     range 10.179.3.100 10.179.3.253;
     #use-host-decl-names       on;
     get-lease-hostnames       true;

     option log-servers        10.179.2.12;
  }
}

shared-network WORKSTATIONS {

   option subnet-mask               255.255.255.0;
   option broadcast-address         192.168.0.255;
   option routers                   192.168.0.254;
   option routers                   192.168.0.254;
   option domain-name-servers       192.168.0.254;
   option domain-name               "ltsp";
   next-server                      192.168.0.254;
   option root-path                 "192.168.0.254:/opt/ltsp/i386";

  subnet 192.168.0.0 netmask 255.255.255.0 {

     range dynamic-bootp 192.168.0.005 192.168.0.125;
     #use-host-decl-names       on;
     get-lease-hostnames       true;

     option log-servers        192.168.0.254;

     # trick from Peter Rundle <peter.rundle at au.interpath.net>
     # newer Macs
     if substring (option vendor-class-identifier, 0, 9) = "AAPLBSDPC"
     {
        filename      "yaboot";
        option vendor-class-identifier "AAPLBSDPC";
     }
     # really old iMacs
     elsif substring (option option-221, 0, 5) = "Apple"
     {
        filename      "yaboot";
        option vendor-class-identifier "AAPLBSDPC";
     }
     # Intel PXE
     elsif substring (option vendor-class-identifier, 0, 9) = "PXEClient"
     {
        # NOTE: kernels are specified in /tftpboot/lts/pxe/pxelinux.cfg/
        filename      "/lts/pxe/pxelinux.0";
     }
     # default to an i386 BOOTP image
     else
        {
        filename      "/lts/vmlinuz.ltsp";
     }

     if substring (option vendor-class-identifier, 20, 3) = "ppc" {
        option root-path "192.168.0.254:/opt/ltsp/ppc";
     } else {
        option root-path "192.168.0.254:/opt/ltsp/i386";
     }
  }
}

# example configurations for specifying specific kernels to specific clients
group   {
    use-host-decl-names       on;
    option log-servers        192.168.0.254;

    host ws001 {
        hardware ethernet     00:40:63:cb:08:88;
        fixed-address         192.168.0.1;
        filename      "/lts/pxe/pxelinux.0";
    }
}

On Fri, Feb 5, 2010 at 10:38 AM, James Huffman <cwerks at yahoo.com> wrote:

> I am trying to install another network card to handle terminal traffic
> better. Is it possible to add a second card to the terminals? (Would this be
> 2 networks?) this is the only option I think I have other that running a (3
> deep) daisy chain that is really slowwww...It seems to me that it should be,
> but alas, I can not find a way...I am running Centos. If this is an option,
> can someone please either tell me how or at least send me to a tutorial on
> this subject?
>
> Thanks!
>
> Jim Huffman
>
> _______________________________________________
> 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/20100205/cc7702ec/attachment.htm>


More information about the K12OSN mailing list