DHCPDISCOVER ... and Assigning an IP address to a Network Drive problems --SOLVED--
Jay Ridgley
jridgley2 at austin.rr.com
Tue Jan 19 02:28:45 UTC 2010
Folks,
Thanks to ALL who offered help/suggestions/admonitions/criticisms and/or
advice and pointers. Each was read and put to use...
What I was attempting to do was enable the access to a 1TB Western
Digital MyBook World Edition on my wired network(a small 4 system static
IP based lan) via a hub, since I have no router.
I have the WD MBWE on my net and it has a fixed IP address like I
wanted. This makes a total of 5 systems here at home on my network. My
wife says it should be all I need to keep me happy hardware wise for
some time.
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
--
Jay Ridgley
jridgley2 at austin.rr.com
Registered Linux User ID - 9115
Registered Ubuntu User ID - 23320
More information about the ubuntu-users
mailing list