Here is patch:
diff --git a/bgpd/bgp_aspath.c b/bgpd/bgp_aspath.c

@beamerblvd no migration was done.

We will not address this in 1.1.x
please retest on 1.2. and reopen ticket or create new one

+1 for removal of telnet

I will advise to try latest rolling release from here
dev.packages.vyos.net/iso/current/amd64/

@UnicronNL please add package
https://packages.debian.org/search?keywords=wakeonlan
This is client tool (to wake up servers/hosts) we will be adding op mode command for it

No version
No config
You have some task to accomplish and it not works as you need.

@UnicronNL @dmbaturin
can we just rebuild fresh from wheeze?

new one, not sure if you can edit T403

Can you submit bug report please

So it looks like vpp progressing a bit.
https://github.com/FRRouting/frr/wiki/Alternate-forwarding-planes:-VPP

@dmbaturin check this out

we actually need clean up grup config a bit
as it have 2 timers for 5 seconds and it's kind of annoying

Please check with latest night build
Not likely that we will spend time on this in 1.1. x series

@UnicronNL applied changes in both 1.1.x and 1.2.x

@UnicronNL please add this when you have time

Yes, let me regain access to this task

Now as @higebu done T373 we can build custom config for waagent that will do provision via cloud-init mechanism

Kim, can you merge this into current
Thanks!

Daniil, can you kindly review and merge
Thanks

Hi Kim, can you merge this
Thanks!

Resolving this and moving to finished

config will be good to see

Just added Finished Board for 1.2.x project
we likely will keep all there before include it in some milestone release

That is not something that we need to choose between,
we keep both, but for environments where users comes from AD, LDAP, Radius, etc.

This one is partially related to T312 but not only
we had some discussions with @dmbaturin in past about keys
and came across idea that it will be great to keep keys outside of config

There is no plans to use this packages in VyOS
This will not be fixed in 1.1.x

No such plans,
but you may want to submit this as feature request to 1.2.x project instead
If you can also add references for this limitations and any additional info
this will helps a lot

maybe we can use something like | not-strip-private
for cases when dump should contain all info

@UnicronNL can we fix and include this in 1.1.8 ?

@dmbaturin can you merge this pull request?

@EwaldvanGeffen confirmed that fix was done for 1.1.x
@dmbaturin can you merge it and introduce in 1.1.8 ?

Can you check this @dmbaturin @UnicronNL

Moved to 1.2 as per discussion with @dmbaturin

reproducible like that

@c-po try to delete upper node

Sorry,
no configs, no version.
Marking this as invalid

@c-po do you want to pick up this?
Basically we need to filter out private info by default
currently it possible to do via

To implement remote auth sources we will need to deal with logins
it seems that we need to handle home folder creation for users that doesn´t exist in config
it´s kind of similar how active directory integration work on linux, where home folder for Active Directory user will be created on first login
Only difference that we not limited to AD and will need same for radius/tacacs+/ad
this will allow us start implement remote auth mechanisms

Hey Christian,
assigning it to you

this task is obsolate

Should be fixed now

@UnicronNL please merge when you have time

Awesome :) So It seems that we waited for @c-po all that time to do that :)

using this opportunity we can replace splash M4
that was original plan that i discussed with @UnicronNL and @dmbaturin
but it's never happened as it's not criticl

that will be half fix
let me check on all lldpctl
i almost sure that we can add some other things (not sure if anything else missing there)

in old version
-L location Enable the transmission of LLDP-MED location TLV for the

given interfaces. Can be repeated to enable the transmission
of the location in several formats.

but in new it´s likely moved to lldpctl
for reference: http://manpages.ubuntu.com/manpages/trusty/man8/lldpctl.8.html

@dmbaturin merged it into
Thanks @c-po

@EwaldvanGeffen pointed another issue in T329
.bash_history content also must be processed (private info must be stripped) before it included

Well is part of show tech-support, output of which must be reviewed,
but i agree

@EwaldvanGeffen see T328

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