I close this as wontfix
For 1.1.x we will not update quagga as it not make sense
For 1.2.x it's better to focus on FRR instead

I'm using pptp and also IPSEC VPN in combination with VRRP. It works for me, but you must restart the service when a router becomes VRRP master. And you need to create a VRRP sync-group so all interfaces are master on one router. I'm using preempt false to avoid the service to be moved (and restarted) more than necessary.

FYI, as a reference that the esp= line should be formatted as I suggest:
https://wiki.strongswan.org/projects/strongswan/wiki/UsableExamples

Seems to work fine in 2.x

So bad. What about future plans? maybe 1.1.8 or 2.x.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.

We dropping 1.1.x series
not make sense debug this behaviour

It not make sense debug this on 1.1.x
will be addressed in 1.2.x

This require further debugging
we will not spent time on 1.1.x series

This looks like support question and not bug report
please create question instead

@hiroyuki-sato is this applies to 1.2.x series?

This will not be available in 1.1.x
please submit feature request for 1.2 instead

All IPSec stuff goes directly to @dmbaturin

Anyone can confirm this behavior ?

Moved to backlog and assigned to you

@UnicronNL can we fix this for 1.1.8 too?

Gimme the ticket, and I'll take a look at it.

Found my workaround.

could you please confirm if it is working for you in the latest buid (starting from 26 juli) http://dev.packages.vyos.net/iso/current/amd64/

@sepo please assign task to me

@JulesT it's something that con address in 1.2 code base?

There too many possibilities and you not provided any useful info nor configs,
therefore no one will be able to help you

Error mail.

Temporary download site for testing: https://dev.vyos.jp/vyos/images/
Also VMware OVA and Hyper-V image are available.

working job: https://ci.vyos.net/job/vyos-build-vm-images/

@ekim Technically the dhcp lease should not affect on the network traffic at all, the renew should be transparent if the IP stays the same.
I believe that since the issue appears after a minute and the lease is 1 hour then it should be fine and probably not the cause for the issue.

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.

I got a physical server with VT enabled for building qemu image and running integration test.

1 hour is incredibly short, I agree. However, in some cases we are unable to change this parameter as I don't control the device.

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

Hi, for me it's definitely MTU problem, as DBD packets filled fully with prefixes, they require more space,
also you could try to switch "network point-to-point" to broadcast, it could be some limitations of ospfd, but it's probably not the case
anyway Full/DROther for point-to-point looks for me weird, there is should be no elections on link with only two peers...

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.

DHCP lease is 1 hour. Is there a lower/upper bounds that DHCP leases should stay inside of?

Can you verify using tcpdump or other means how long the dhcp lease is?

@UnicronNL can you apply this

I recall @CBRjack started building such list some time ago
see
https://wiki.vyos.net/wiki/CLI-Reference

I added a force-gateway option some time ago. Regardless it's somewhat expected on 1.2, it needs testing and review. I meant 1.1.7 in my previous post (yes, confusion).

been using the VyOS 1.2.0-beta1

save https://github.com/vyos/vyatta-op-dhcp-server/commit/64817db98e485eee75b53caf4b308197d094784c in /opt/vyatta/share/perl5/Vyatta/DHCPServerOpMode.pm

@EwaldvanGeffen not sure how to apply the patch

@tsumaru720 Could you provide feedback?

What version have you been using?