I'm trying to replace a 10BaseT DLink hub with a 100 Base TX DSS 5+
switch.  DHCP doesn't work anymore.

The server is on one end connected via an FA311 netgear card.  From
there, a 100' Cat5e cable runs to the switch in the attic.  Then I 
go to Cat5 STP cable for an additional 90' outside, underground,
and back above ground into the next building.  The diskless machine
that boots via floppy is on the far end.  A 190' run made up of a
100' and a 90' run seems to be within the range limitations for
100BaseTX.  Then again, the cable is shallowly buried and could
be getting weathered.

I see DHCPDISCOVER and DHCPOFFER, but nothing past that.

Dec 27 20:32:36 
goose dhcpd: DHCPDISCOVER from 00:02:e3:02:46:37 via eth2
Dec 27 20:32:36 
goose dhcpd: DHCPOFFER on 192.168.4.17 to 00:02:e3:02:46:37 via eth2

Most of my dhcpd.conf follows:

failover peer "dhcp"
{
   primary;
   address 192.168.5.2;
   port 647;

   peer address 192.168.5.1;
   peer port 647;
   max-response-delay 60;
   max-unacked-updates 10;
   mclt 600;
   split 128;
   load balance max seconds 3;

   peer address 192.168.5.4;
}



ddns-update-style none;
authoritative;
allow booting;
next-server 192.168.5.2;



# %%% wifi-2 %%%
shared-network WIFI-2
{
     subnet 192.168.4.0 netmask 255.255.255.240
     {
            option domain-name "w2.robinson-west.pri";
            option domain-name-servers 192.168.4.2;
            option routers 192.168.4.2;
            option broadcast-address 192.168.4.15;
            option ntp-servers 192.168.4.2;
     }

     subnet 192.168.4.16 netmask 255.255.255.240
     {
            option domain-name "w2.robinson-west.pri";
            option domain-name-servers 192.168.4.18;
            option routers 192.168.4.18;
            option broadcast-address 192.168.4.31;
            option ntp-servers 192.168.4.18;
     }

     # %%% wifi-2 network segment 1 %%%
     group
     {
           use-host-decl-names on;
           next-server 192.168.4.2;

           host dodo.w2.robinson-west.pri
           {
              hardware ethernet 00:02:E3:14:1C:94;
              fixed-address 192.168.4.1;
              option root-path "192.168.4.2:/nfsroot/dodo";
              filename="\dodo.nbi";
           }
      }
      # %%% wifi-2 network segment 1 %%%

      # %%% wifi-2 network segment 2 %%%
      group
      {
           use-host-decl-names on;
           next-server 192.168.4.18;

           host condor.w2.robinson-west.pri
           {
              hardware ethernet 00:02:E3:02:46:37;
              fixed-address 192.168.4.17;
              option root-path "192.168.4.18:/nfsroot/condor";
              filename="\condor.nbi";
           }
      }
      # %%% wifi-2 network segment 2 %%%
}
# %%% wifi-2 %%%



# %%% local lan %%%
shared-network LAN-1
{
     subnet 192.168.5.0 netmask 255.255.255.0
     {
        pool
        {
          failover peer "dhcp";
          range 192.168.5.129 192.168.5.254;
          deny dynamic bootp clients;
        }

        option routers 192.168.5.6;
        option domain-name-servers 192.168.5.1, 192.168.5.4;
        option domain-name "robinson-west.com";
        option broadcast-address 192.168.5.255;
        option ntp-servers 192.168.5.2;
     }

group
{
...
# This is populated by host records...
}
# %%% local lan %%%
}
...
# I define the Internet subnet...

The other diskless machine on another nic off of the same server, dodo,
boots just fine by the way.  Is something obviously wrong in my dhcp
config file or am I looking at a problem with the switch?  DHCP worked
when I was using a 10BaseT hub which makes me wonder if the line can't
support 100baseTX.

_______________________________________________
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Reply via email to