| Stephen Gran on 30 Oct 2003 08:13:01 -0500 |
|
On Wed, Oct 29, 2003 at 06:18:14PM -0500, David Kaplowitz said: > Why are the clients using this 'repair' function in the first place? It > would seem to me, once assigned, the process of obtaining an IP should > be transparent and the users shouldn't be futzing around with the IP > settings. Anyway... Two of the client machines have flaky PCMCIA NICs. and that's one of the things they're doing to try to restore a connection. > If you go to a WinXP command prompt and type 'ipconfig release', then > 'ipconfig renew', do you get an address? That's usually the very most I > might have to do, and even that is on the rare occasion I didn't pick an > IP up during boot. Sometimes, sometimes not, it seems. That's the odd thing. This morning, after removing any fixed-address lines from dhcp.conf, I see this: Oct 29 20:38:38 NSA-free dhcpd: DHCPREQUEST for 192.168.0.3 from 00:20:18:d8:1f:28 via eth1: unknown lease 192.168.0.3. Oct 29 20:38:49 NSA-free last message repeated 2 times Oct 29 20:39:56 NSA-free dhcpd: DHCPDISCOVER from 00:20:18:d8:1f:28 via eth1 Oct 29 20:39:57 NSA-free dhcpd: DHCPOFFER on 192.168.0.99 to 00:20:18:d8:1f:28 (hppav) via eth1 Oct 29 20:39:57 NSA-free named[652]: client 127.0.0.1#1029: updating zone 'lobefin.net/IN': adding an RR Oct 29 20:39:57 NSA-free named[652]: journal file lobefin.net.db.jnl does not exist, creating it Oct 29 20:39:57 NSA-free named[652]: zone lobefin.net/IN: sending notifies (serial 2003101802) Oct 29 20:39:57 NSA-free named[652]: received notify for zone 'lobefin.net' Oct 29 20:39:57 NSA-free dhcpd: if hppav.lobefin.net IN A rrst doesn't exist add hppav.lobefin.net 43200 IN A 192.168.0.99: success. Oct 29 20:39:57 NSA-free named[652]: client 127.0.0.1#1029: updating zone '0.168.192.in-addr.arpa/IN': deleting an rrset Oct 29 20:39:57 NSA-free named[652]: client 127.0.0.1#1029: updating zone '0.168.192.in-addr.arpa/IN': adding an RR Oct 29 20:39:57 NSA-free named[652]: journal file 192.168.0.db.jnl does not exist, creating it Oct 29 20:39:57 NSA-free named[652]: zone 0.168.192.in-addr.arpa/IN: sending notifies (serial 2) Oct 29 20:39:57 NSA-free dhcpd: delete 99.0.168.192.in-addr.arpa. IN PTR add 99.0.168.192.in-addr.arpa. 43200 IN PTR hppav.lobefin.net: success. Oct 29 20:39:57 NSA-free dhcpd: Wrote 1 leases to leases file. Oct 29 20:39:57 NSA-free dhcpd: DHCPREQUEST for 192.168.0.99 (192.168.0.1) from 00:20:18:d8:1f:28 (hppav) via eth1 Oct 29 20:39:57 NSA-free dhcpd: DHCPACK on 192.168.0.99 to 00:20:18:d8:1f:28 (hppav) via eth1 Oct 29 20:39:57 NSA-free dhcpd: DHCPDISCOVER from 00:20:18:d8:1f:28 via eth1 Oct 29 20:39:57 NSA-free named[652]: received notify for zone '0.168.192.in-addr.arpa' Oct 29 20:39:58 NSA-free dhcpd: DHCPOFFER on 192.168.0.98 to 00:20:18:d8:1f:28 (hppav) via eth1 Oct 29 20:39:58 NSA-free named[652]: client 127.0.0.1#1029: updating zone 'lobefin.net/IN': update failed: 'rrset does not exist' prerequisite not satisfied (YXRRSET) Oct 29 20:39:58 NSA-free dhcpd: if hppav.lobefin.net IN A rrset doesn't exist add hppav.lobefin.net 43200 IN A 192.168.0.98:RRset already exists. Oct 29 20:39:58 NSA-free dhcpd: DHCPREQUEST for 192.168.0.98 (192.168.0.1) from 00:20:18:d8:1f:28 (hppav) via eth1 Oct 29 20:39:58 NSA-free dhcpd: DHCPACK on 192.168.0.98 to 00:20:18:d8:1f:28 (hppav) via eth1 So for some reason, the client machine got two IP's from dhcpd - and there are in fact 2 leases in the dhcpd.leases file. Very odd. Am I just misunderstanding? I thought you had to have two zone files, one fr forward and one for revere dns, but maybe this is what's causing the mess up here. > You might also want to set your dchp lease option to a longer time > interval than a couple days if you are on a small LAN with few machines. I've set it for minimum one day, maximum one week. > Good luck, > > Dave > > > On Wed, 2003-10-29 at 17:19, Stephen Gran wrote: > > Hello all, > > > > I am having a problem with a small LAN. The basic setup is a linux > > (Debian woody) box that connects via pppoe to the isp, and then does > > some basic filtering, NAT, print sharing, dns, and so forth for the LAN. > > The LAN is all WinXP at this point (6 or so boxes). > > > > Recently I switched the LAN to DHCP from static addresses, as some users > > kept complaining that the 'repair' function in WinXP didn't repair > > anything, but in fact made things worse. From what I can gather, the > > 'repair' thing essentially releases any dhcp lease, flushes the arp > > cache, tries to renew a lease, and then sends a bunch of netbios > > discover packets about. > > > > Now that I have installed dhcp3-server, when a users hits 'repair', I > > see this: > > Oct 29 17:08:58 free dhcpd: DHCPRELEASE of 192.168.0.100 from 00:30:ab:1b:52:71 via eth1 (not found) > > Oct 29 17:10:00 free dhcpd: DHCPREQUEST for 192.168.0.100 from 00:30:ab:1b:52:71 via eth1 > > Oct 29 17:10:00 free dhcpd: DHCPACK on 192.168.0.100 to 00:30:ab:1b:52:71 via eth1 > > Oct 29 17:10:07 free dhcpd: DHCPDISCOVER from 00:30:ab:1b:52:71 via eth1 > > Oct 29 17:10:07 free dhcpd: DHCPOFFER on 192.168.0.100 to 00:30:ab:1b:52:71 via eth1 > > Oct 29 17:10:07 free dhcpd: DHCPREQUEST for 192.168.0.100 (192.168.0.1) from 00:30:ab:1b:52:71 via eth1 > > Oct 29 17:10:07 free dhcpd: DHCPACK on 192.168.0.100 to 00:30:ab:1b:52:71 via eth1 > > > > and no lease gets written to /var/lib/dhcp3/dhcpd.leases. On the client > > side, they see 'error flushing the arp cache', but they get a new > > address. The only out of the ordinary thing I did was give a couple of > > addresses fixed-address lines in dhcp.conf - they get the same errors as > > everyone else, though. > > > > The DHCPRELEASE (not found) message is esay enough to guess - there's no > > entry in the leases file to release. Anybody seen anything like this > > before? I would say that it's a client side problem, except that it's > > consistent, and it happens to all of them. I don't know dhcp that well, > > but I thought it was a pretty transparent thing - you shouldn't have to > > do much to get it going. > > > > Is this going to be a situation where I have to allow dhcp to update > > dns? I had hoped to stay away from that. > > ___________________________________________________________________________ > Philadelphia Linux Users Group -- http://www.phillylinux.org > Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce > General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug -- -------------------------------------------------------------------------- | Stephen Gran | Kirkland, Illinois, law forbids bees to | | steve@lobefin.net | fly over the village or through any of | | http://www.lobefin.net/~steve | its streets. | -------------------------------------------------------------------------- Attachment:
signature.asc
|
|