Using ISC's dhcpd you can run a bootp server that doesn't require hard coding MAC->IP relations. Bootp is also very handy for remotelly loading kernels and remote filesystems automatically. Many network cards are able to use bootp to boot an OS from a server onto a client computer, which is very handy for thin clients.
Le 3 Janvier 2003 14:37, vous avez �crit : > With BOOTP an administrator would say basically : > 01:01:01:01:01:01:01:01 192.168.0.1 > 01:01:01:01:01:01:01:02 192.168.0.2 > > Etc. You tie a MAC to an IP. If the Bootp server doesn't recognize the > MAC, you don't get an address. It's the same as statically setting all > your IP addresses inside DHCP, and then disallowing DHCP to respond to > foreign NICs. > > BOOTP was easier than manually setting things up, but it didn't clean out > old entries, and you had to associate every new machine with an IP address > in the config table before it would work. > > Kev. > > > > ----- Original Message ----- > From: "Ian Bruseker" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, January 03, 2003 2:15 PM > Subject: RE: (clug-talk) MAC s > > > > There's no advantage with DHCP. There was an advantage before DHCP > > > when people used BOOTP though. > > > > I thought with DHCP, you address the MAC with a given IP address, to make > > sure a certain computer would always get the same IP (sort of a > > dynamically > > > static sort of thing), but giving you the advange of having all the rest > > of > > > the info that travels with DHCP (like name server lists and such) being > > controlled centrally. That's the one use I've ever heard of for them. > > > > > I feel old. > > > > We won't tell. ;-) > > > > > Kev. > > > > Ian
