I stand corrected. I was not aware 2516 had been updated let alone that the update was ratified.

Sorry but that does not seem a good reason to deny a feature like this.

There really isn't a good reason to do this. The performance difference is minuscule even if you were sending maximum size packets all the time which you won't be. Plus- if it doesn't work- it will likely manifest as an intermittent problem that will be very difficult to track down.

Seems to work fine in 2.x

DPD does not work reliably on 1.1.7 as far as I can tell. I routinely have to restart my sessions to AWS.

Whether or not the MTU is causing the issue- it should obviously be set anyway. MTU issues always seem to cause intermittent and hard to track down problems.

Perhaps only one side is set point-to-point? That would also cause ... interesting behavior.

1 hour is an incredibly short DHCP lease. 8 Hours would be common on something like a guest wifi network- and a day or more would be appropriate for a more static configuration.

@logan.attwood Yeah- I've seen that it's in the source but I'm running a Beta build from a couple of weeks ago and it does not seem to have made it into those builds (unless I'm doing something wrong).

This is an incredibly useful feature specifically because of the AWS transit VPC solution mentioned above (it's a great way to create horrible routing problems if you don't know what you're doing- but there are so many other ways to screw up with BGP that I doubt this a deal breaker).