On Thursday 09 October 2003 21:44, goteki wrote:
> On Thu, 9 Oct 2003 20:33:54 +0000
>
> Ian Zagorskih <ianzag@megasignal.ru> wrote:
> >  I'm looking for simple AutoIP daemon for NetBSD (v1.6.1/i386).
>
> dhclient can help you here since you can configure it to (if it doesn't
> recieve a dhcp_discover response) staticly assing an ip address. However
> I'm not sure if you can specify a range and let him choose randomly.
> This is only a workaround since there is no AutoIP support in dhclient
> and it won't handle ip addresses colisions.
>

Well, this is what i found too. ATM i use statically assigned IP addresses for 
set of devices but even for 10+ units this looks like a little nightmare. If 
there are hundreds of devices or more this will be a big nightmare.

The problem is that devices must be able to operate in IP LANs without DHCP 
server i.e. for example just several PCs connected together with 100MBit 
Ethernet hub. All/most of them running misc flawours of MS Windows so 
requirement to have running DHCP server looks a bit weird for WinX users :)

On the other hand, i need to assign IP address to devicee some/any way in 
order to access it through LAN. ATM as it seems to me it must be configurable 
and must include as minimum:

1. Statically assigned.
2. DHCP/BOOTP.
3. AutoIP when we do not have DHCP & K.
4. temporay arp mapping ->manual config thriugh web interface
5. maybe RARP if server is available.
6. something else.

ps: this kind of scheme i got looking at implementations of different "LAN 
Ready" devices like access points, LAN printer, web video servers and so on. 
Maybe, folks can suggest me something better ? I believe i'm not alone NetBSD 
user who uses it for smth except Server/Desktop installation.

-- 
JSC Novosibirsk Geophysical Equipment Development Center.
WEB	http://www.megasignal.com