Upgrade from 3.1.0 to 4.1.1

[Abu Abdulla alhanbali]

O.K. i will try to test it. thanks for the tips.

i tried another thing which didn't work. i created a virtual interface
with different IP in the same subnet and it results with this error:
No subnet declaration for nxge0:1 (no IPv4 addresses).

i run the command as:
/export/dhcp-iptv-4.1.1/etc/dhcpd.conf -lf
/export/dhcp-iptv-4.1.1/etc/dhcpd.leases nxge0:1

The network info is:
bash-3.00# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
        inet 127.0.0.1 netmask ff000000
nxge0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
        inet 89.211.240.197 netmask fffffff8 broadcast 89.211.240.199
        ether 0:14:4f:e4:6a:60
nxge0:1: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu
1500 index 2
        inet 89.211.240.196 netmask fffffff8 broadcast 89.211.240.255

i tried to use server-identifier without success as well.

my config is:
# more dhcpd.conf
ddns-update-style none;
authoritative;
log-facility local3;
server-identifier 89.211.240.196;

subnet 89.211.240.192 netmask 255.255.255.248 { }

i'm running solaris 10 and have already another DHCP running on interface nxge0


On Tue, Feb 23, 2010 at 11:42 PM,  <sthaug at nethelp.no> wrote:
>> >> where can i found info on how to compile with USE_SOCKETS and how can
>> >> i use this feature. i only need to run multiple DHCP instances on
>> >> different ports using the same IP
>> >
>> > Here:
>> >
>> > https://lists.isc.org/pipermail/dhcp-users/2009-August/009667.html
>> >
>> > is the recipe I used to compile with USE_SOCKETS on FreeBSD. Note:
>> >
>> > - Step 3 in that recipe is no longer needed with 4.1.1 release version.
>> >
>> > - If your environment doesn't use BPF (e.g. Linux, Solaris) then you
>> > don't need the USE_BPF_HWADDR define.
>> >
>> Thanks. but it includes patching the code which I'm afraid to do it
>> especially with other versions. I'm not familiar with coding but it
>> might be better to have it in the main code. running multiple
>> instances on different ports is a common feature for many servers. it
>> will add a value to have it by default without patching.
>
> Absolutely agreed. However, I have asked for this before, and it sounds
> like ISC would *like* to make this more easily usable (no patching) but
> it hasn't gotten to the top of the list yet. So - if you need this now
> your only option is patching the code.
>
> Steinar Haug, Nethelp consulting, sthaug at nethelp.no
>