Already in 1.2.1

I wasn't aware that there was an aws target for the vyos-build scripts.

This can not be backported easily to 1.2 (crux) b/c of jumps in the system@ config version string.

Its already in 1.2.1

@spectre3500 Now that I think of it, did you build it with build-ami or the AWS target of the vyos-build scripts?

...oh, and remove "disable-password-authentication" from the SSH settings of course.

I wonder if this issue will ever stop re-occuring. Every time it happens, it's for some new reason. I think this time it may be related to ongoing work of @Unicron.

Related task: T1334

Here's a commented reference config from Vyatta 6.5 for testing:

I'm also experiencing the same issue with vyos-1.2.0-rolling-201904190439. I was able to create the ami using the build-ami playbooks, but when launched I could not login using the keypair. Is there a fix for this or a workaround?

Thank you most kindly for the information. Adding:-

Unfortunately, current Linux GRE and network stack implementations don't support Cisco-style of GRE keepalives (GRE inside GRE, with spoofed IP addresses). From the Linux point of view, those packets look like martians, and the kernel drop them, information about what you can see inside a log.
Try to disable the keepalive at the Cisco side, after this tunnel must be fully functional.

Since @dmbaturin reverted this, reopen

@c-po please backport this to crux

@c-po can you backport this to crux, please

updated tools to 10.3 that solves the issue