dhcpd 4.2.4 vs 4.3.5

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

dhcpd 4.2.4 vs 4.3.5

Gregory Sloop
dhcpd 4.2.4 vs 4.3.5 This is mostly for ISC dev staff, [or anyone else who might know]

Should failover peers running 4.2.4 talk to another peer running 4.3.5 properly?
Or are there differences large enough between the two versions to prevent them from working as a pair?

[Reason - I'm upgrading a pair of 4.2.4's to 4.3.5 - and moving one of the pair to 4.3.5 and then the other also to 4.3.5 seems like a very nice way to manage the upgrade. But they'll have to work together well to do it this way.]

-Greg
[hidden email]
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: dhcpd 4.2.4 vs 4.3.5

Gregory Sloop
Re: dhcpd 4.2.4 vs 4.3.5 I should have added - I've read the release notes [mainly searching for "peer"], and there's not much mentioned about changes in peer communications or the peer underpinnings - so I'd *guess* they'll talk fine - but having someone with some real knowledge weigh in would be a lot more helpful in making me feel fairly confident it will.

[I just don't want to turn off a 4.2.4 and bring up a 4.3.5 and have it make a hash of things, so it's quite difficult to go back to 4.2.4, and suddenly I don't have any working DHCP servers!]

Again, thanks for any light someone might shed on this!

-Greg



This is mostly for ISC dev staff, [or anyone else who might know]

Should failover peers running 4.2.4 talk to another peer running 4.3.5 properly?
Or are there differences large enough between the two versions to prevent them from working as a pair?

[Reason - I'm upgrading a pair of 4.2.4's to 4.3.5 - and moving one of the pair to 4.3.5 and then the other also to 4.3.5 seems like a very nice way to manage the upgrade. But they'll have to work together well to do it this way.]

-Greg


_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: dhcpd 4.2.4 vs 4.3.5

Bill Shirley-2

I have:
dhcp-4.2.5-23.fc19.x86_64
dhcp-server-4.3.6-9.fc27.x86_64
running in a pair.  Also:
dhcp-4.2.5-23.fc19.x86_64
dhcp-4.3.1-12.fc21.x86_64
in a pair.

Bill

On 4/12/2019 4:28 PM, Gregory Sloop wrote:
Re: dhcpd 4.2.4 vs 4.3.5 I should have added - I've read the release notes [mainly searching for "peer"], and there's not much mentioned about changes in peer communications or the peer underpinnings - so I'd *guess* they'll talk fine - but having someone with some real knowledge weigh in would be a lot more helpful in making me feel fairly confident it will.

[I just don't want to turn off a 4.2.4 and bring up a 4.3.5 and have it make a hash of things, so it's quite difficult to go back to 4.2.4, and suddenly I don't have any working DHCP servers!]

Again, thanks for any light someone might shed on this!

-Greg



This is mostly for ISC dev staff, [or anyone else who might know]

Should failover peers running 4.2.4 talk to another peer running 4.3.5 properly?
Or are there differences large enough between the two versions to prevent them from working as a pair?

[Reason - I'm upgrading a pair of 4.2.4's to 4.3.5 - and moving one of the pair to 4.3.5 and then the other also to 4.3.5 seems like a very nice way to manage the upgrade. But they'll have to work together well to do it this way.]

-Greg


_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users