On 21/06/05, Steve Holdoway wrote: > Sad to say, I lay in bed last night thinking about this. Something along > the lines of 'why isn't your dhcp server working just because there > isn't an ethernet connection?' My original thoughts were of poor > analysis and programming of the unit. But then it dawned on me that the > dhcp server can't start until it has all the information that it needs > to impart on to it's clients - like dns servers - which, of course will > be available when the dhcp client side of the router is set up from the > upstream dhcp server. > > Because, of course, its primary function is as a router, not a dhcp > server. Only when it's configured can it provide its secondary services.
My IPCop box does not suffer from this problem, which is just as well because the laser printer (on jetdirect) and laptop need a DHCP server to talk to each other (with my current set-up. The LAN is small enough to make do with host files, so the DHCP server may be overkill. The LAN's gonna grow though). Yuri -- ** WARNING to mailing list repliers ** Gmail over-rides "Reply-To:" field. Check your "To:" address before sending reply to this post.
