*** From dhcp-server -- To unsubscribe, see the end of this message. ***

Greetings,

I'm setting up a private network to boot off of DHCP using the ISC
client/server version 3.0-alpha-19990507 on Linux 2.2.x.  The private
network consists of n nodes with 3 ethernet cards (100mbit, gig-e,
myrinet) and one controlling node with 4 ethernet cards (100mbit,
100mbit, gig-e, myrinet).  The first 100mbit for the controlling node
goes out to the world; the other cards are only on the private network
and will never see out past it.  Each type of card on the private
network sits on its own subnet: the 100mbit on 10.0.0.x, the gig-e on
10.0.1.x, and the myrinet on 10.0.2.x (netmask 255.255.255.0.)  What I
want to do is setup a routing table such that all traffic on the
10.0.1.x and the 10.0.2.x subnets stay on their respective subnets and
the 10.0.0.x network will be used as the default for whatever else.  So,
on each of the nodes I want a routing table that looks something like
this (this example being for a node with an IP of 10.0.x.2):

Kernel IP routing table
Destination   Gateway       Genmask         Flags Metric Ref    Use
Iface
10.0.1.0      10.0.1.2      255.255.255.0   UG    0      0        0 eth1
10.0.2.0      10.0.2.2      255.255.255.0   UG    0      0        0 eth2
10.0.0.0      0.0.0.0       255.255.255.0   U     0      0        0 eth0
127.0.0.0     0.0.0.0       255.0.0.0       U     0      0        0 lo
0.0.0.0       10.0.0.2      0.0.0.0         UG    0      0        0 eth0

Note that I'm using each node as its own gateway because these nodes
will never have to see beyond their own local network.

The problem I'm having is getting this setup.  If I use a dhcpd.conf
that looks like this (the server sits on 10.0.x.1):

subnet 10.0.0.0 netmask 255.255.255.0 {
        filename "/boot/install.ks";
        server-name "10.0.0.1";

        option broadcast-address 10.0.0.255;
        option subnet-mask 255.255.255.0;
}

subnet 10.0.1.0 netmask 255.255.255.0 {
        filename "/boot/install.ks";
        server-name "10.0.1.1";

        option broadcast-address 10.0.1.255;
        option subnet-mask 255.255.255.0;
}

subnet 10.0.2.0 netmask 255.255.255.0 {
        filename "/boot/install.ks";
        server-name "10.0.2.1";

        option broadcast-address 10.0.2.255;
        option subnet-mask 255.255.255.0;
}

group {
        use-host-decl-names on;

        host node1 {
                hardware ethernet ...;
                fixed-address 10.0.0.2;

                option routers 10.0.0.2;
        }
        ...
}

group {
        host node1g {
                hardware ethernet ...;
                fixed-address 10.0.1.2;

                option static-routes 10.0.1.0 10.0.1.2;
        }
}

group {
        host node1m {
                hardware ethernet ...;
                fixed address 10.0.2.2;

                option static-routes 10.0.2.0 10.0.2.2;
        }
}

I'll get a routing table that looks like this:

Kernel IP routing table
Destination   Gateway       Genmask         Flags Metric Ref    Use
Iface
10.0.0.0      0.0.0.0       255.255.255.0   U     0      0        0 eth0
10.0.1.0      0.0.0.0       255.255.255.0   U     0      0        0 eth1
10.0.2.0      0.0.0.0       255.255.255.0   U     0      0        0 eth2
127.0.0.0     0.0.0.0       255.0.0.0       U     0      0        0 lo
0.0.0.0       10.0.0.1      0.0.0.0         UG    0      0        0 eth0

which isn't what I want.  If I specify routers for the second and third
subnet instead of using the 'static-routes' keyword, I get something
that looks like:

Kernel IP routing table
Destination   Gateway       Genmask         Flags Metric Ref    Use
Iface
10.0.0.0      0.0.0.0       255.255.255.0   U     0      0        0 eth0
10.0.1.0      0.0.0.0       255.255.255.0   U     0      0        0 eth1
10.0.2.0      0.0.0.0       255.255.255.0   U     0      0        0 eth2
127.0.0.0     0.0.0.0       255.0.0.0       U     0      0        0 lo
0.0.0.0       10.0.0.2      0.0.0.0         UG    0      0        0 eth0
0.0.0.0       10.0.1.2      0.0.0.0         UG    0      0        0 eth1
0.0.0.0       10.0.2.2      0.0.0.0         UG    0      0        0 eth2

which again is not what I want.

So, can anyone help me out here?  Is this possible with DHCP or should I
just write a little shell script to manipulate the table?  (I'd rather
not as a script would be 'hard-coded'.)

Oh, my dhclient.conf's are blank; using defaults.

Thanks,

--
Jason Holmes


------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED]   Please try to use the web
page first - it will take a long time for your request to be processed by hand.

Archives for this mailing list are available at 
http://www.webnology.com/list-archives/dhcp/dhcp-server

------------------------------------------------------------------------------

Reply via email to