DHCPDISCOVER ... and Assigning an IP address to a Network Drive problems --SOLVED--

Rashkae ubuntu at tigershaunt.com
Tue Jan 19 03:00:34 UTC 2010


Jay Ridgley wrote:

> 
> Below shows the network setup...
> 
> cdjsys at mateo:/etc/init.d$ arp
> Address                  HWtype  HWaddress         Flags Mask Iface
> nomad                    ether   00:08:74:49:06:08   C        eth1
> polar                    ether   00:A0:CC:26:CB:BD   C        eth1
> ursa                     ether   00:1A:A0:99:D0:90   C        eth1
> cpe-70-112-96-1.austin.  ether   00:1D:A2:E8:41:05   C        eth0
> 192.168.139.5            ether   00:90:A9:6E:27:24   C        eth1
>        ^
>        +----- That is my WD  MBWE
> 
> After digging and digging I found a way to assign an IP address and a 
> host name from the hardware (MAC) address in the dhcp3.conf file. Once I 
> was able to determine the mac address, that was the key! So getting 
> dhcp3-server up and running gave me the mac address. Then I was able to 
> set the configuration file as follows:
> 
> # DHCP configuration generated by Firestarter
> # Addition of host koala by CDJSYS 01/18/2010 from Chapter 3 of
> # www.linuxhomenetworking.com
> 
> ddns-update-style interim;
> ignore client-updates;
> 
> subnet 192.168.139.0 netmask 255.255.255.0 {
>          option routers 192.168.139.2;
>          option subnet-mask 255.255.255.0;
>          option domain-name-servers 24.93.41.128, 24.93.41.127;
>          option ip-forwarding off;
> }
> host koala{
>          hardware ethernet 00:90:a9:6e:27:24;
>          fixed-address 192.168.139.5;
> }
> 
> At this point I was able to login and permanently assign the name and 
> static IP to the device. I then removed the DHCP Configuration 
> information from Firestarter and simply added koala with 192.168.139.5 
> to my /etc/hosts files on ALL my systems and rebooted without 
> dhcp3-server being invoked.
> 
> It appears to be working well at this point.
> 
> Cheers,
> Jay
> 

I'm glad you got it working.  This is just FYI and for posterity.

There really was no need no need to uncover the device's MAC address.
All you needed do was create a small range of IP address ins the DHCPD
server to bootstrap the process.  Example:


 subnet 192.168.139.0 netmask 255.255.255.0 {
    range 192.168.139.200 192.168.139.220;
          option routers 192.168.139.2;
          option subnet-mask 255.255.255.0;
          option domain-name-servers 24.93.41.128, 24.93.41.127;
          option ip-forwarding off;
 }

That would assign any DHCP device on your network an IP address within
the range of 200 and 220 (so simply do not use those addresses in your
static assigned addresses.).  You can see what address has recently been
given out by examining the /var/log/messages file on the DHCPD server.
Once the device was on your network, you could have connected to it and
manually assign a static ip of your choice.

If you really are only using this as a bootstrap method, there is no
need to include the routers, domain-name-servers options.. However, you
may want to simply leave that configuration in place in case you ever
get a guest system.. (ex: a friend's notebook you want to connect to the
internet.)




More information about the ubuntu-users mailing list