@gaztel I modified the pm script responsible for the configuration and verified it with iOS 10.3.3 as I do not have a Mac. Windows 10 is now also able to connect.
https://github.com/c-po/vyatta-ravpn/commit/20b85ddf4777ced900da2a56c25922c190823dd5

@syncer thanks!.

We need to change default behaviour and enable strip-private by default
add key not-strip-private for cases when complete dump required

@logan.attwood this isn't included in the beta builds as it isn't in the "current" branch @dmbaturin said that he was merging it to current but it doesn't appear this was done on vyatta-quagga

@hiroyuki-sato maybe 1.2 is not affected with that issue,
i will check with @dmbaturin

@syncer Sorry late reply.

@dmbaturin I agree with adding a configure option. Dependency of VM targets you wrote is correct.

Fix for 1.1.8: https://github.com/vyos/vyos-kernel/commit/ee76a91c5468452a37dda9dd9133acc83014e95b

Fix for 1.1.8: https://github.com/vyos/vyos-kernel/commit/b080c57a1f0f005e0b6c20de67fc0add4d4a3294

@NceAirport Are you connecting two vyos using a gre or vyos to other vendor?
Do these devices have a public ip address on their interfaces or an internal ip with direct routed link(no nat in the middle)?
How can we try to reproduce the issue?

Move this to 1.2
Will need to check
@NceAirport if you run virtualized router on vmware, make sure that you use VMXNET3 adapter as E1000 have issues with GRE

@UnicronNL i recall that you already have build waagent
@higebu was able to convert and upload vhd

qemu-img convert -f qcow2 -o subformat=fixed -O vpc vyos-999.201708201154-qemu-image.qcow2 vyos-999.201708201154-hyperv-image-fixed.vhd

He created os disk and it seems VM boots

Extended IPv6 support will be addressed in 1.2

@UnicronNL can this be added with impact?

Another CVE considered for 1.1.8

Please check when you have time for 1.1.8

@dmbaturin @UnicronNL
any idea why this can happen,
as per report both current and stable affected

Moved this to 1.2.x wish list

Added to 1.1.8 backlog

@UnicronNL can you check patch and advise if that is something that we can include in 1.1.8

That may be considered in 1.2

Moved this to 1.2

Moved this to 1.2

As per my understanding it was fixed, so i mark it as resolved

@dmbaturin i moved this to 1.2 as you partially made changes to repos

Moved this to 1.2 series

Assigned to Kim

Will be basically simple curl wrapper

Agree, @EwaldvanGeffen can you move it to 1.2.x please

It's new feature, but still will need to implement it for support service purpose in 1.1.x

@syncer I think we can remove this task from 1.1.8 backlog, because this is new feature.

@syncer I think we can remove this task from 1.1.8 backlog, because this is new feature.

https://github.com/vyos/vyos-1x/commit/8cc396c20398e01f4af76d386d87a38811cead06
https://github.com/vyos/vyatta-cfg/commit/e55d9affac8159b09b503fca4a364192a24eb52e
https://github.com/vyos/vyatta-cfg/commit/be1dfd64f53776d299651d5347041f17a805aba1

Looks like phabricator hasn't picked up those commits for some reason...

This also may be useful
http://cloudinit.readthedocs.io/en/latest/topics/datasources/azure.html

Please vote in https://phabricator.vyos.net/V4

Still i suggest to do poll on possible syntax and implementation
it could be that is not easy because of many existing problems

@syncer I think the problem is that many fields (eg. within the NAT, WLB, PBR facilities) don't allow to use groups you can use in the firewall stanzas. I think there's no need to poll on this, seems to me like a no-brainer, everyone wants this. Many modern products also add auto variables such as eth0_ipaddresses or eth0_networks. Juniper has an implementation that also allows for hierarchical grouping.

@gaztel can you assign this to me please

@EwaldvanGeffen do poll if so

This required a little voting or some input by a core member on syntax. Once that's established implementation proceeds.

I can confirm this. Above mentioned lines not present in my custom build (Version: VyOS 999.201708011131).

@xrobau and I talked about this on IRC, and agreed on the following points.

Awesome!
@xrobau do you think you can help with this (maybe extend tests)?

I created Jenkins job for vyos-integration-test: https://ci.vyos.net/job/vyos-integration-test/
It works.

Trim is a good point, may be we can but I will emphasize these things here:

1. DO NEVER install vyos or any other linux, intended for running 24x7 on cheap usb flash. I did it. Don't repeat my mistakes.
2. /var/log in tmpfs is generally a very bad idea, as you will have no logs to examine system failures post-mortem.
3. It's a good idea to monitor your ssd's health, and it's a good idea to include smartctl in VyOS default package list, but ssds have different vendor-specific SMART flags for their health indication, so it's up to user to specify the correct ones for his or her equipment.
4. There is a damn dirty and simple solution to address trim issue without any modifications to running image:

tune2fs -o discard /dev/sdXY

but one has to make sure that device supports trim BEFORE doing this :)

@UnicronNL can you review this one?

Lovering priority
we need to retest this

@UnicronNL do you think we can set ntp to start after network?

I think this one is good candidate for backlog

@mrjester is this still actually with latest nightlies?
If so, we need to build list of fixes and push this to backlog

I think we need address this in installer
@dmbaturin your feedback will be very useful

@UnicronNL i think we need review this and move it to backlog if all clear

This is valid request but require elaboration

That is not supported

Please submit feature request and describe use cases