OK. Minor tweaks - actually wired 'show vpn ipsec sa' to use the pretty-print code, rather than just calling swanctl to get half a page of ugliness.

Ok, sorry about that.

Looks to me that you are mixing up two things. 6rd (Radpid Deployment) is used for ISPs to connect the customers to the IPv6 world (https://en.wikipedia.org/wiki/IPv6_rapid_deployment).

@UnicronNL https://github.com/vyos/vyos-build/pull/11

@c-po https://github.com/vyos/vyos-cfg-avahi.git is created, and ci integration is also done.

Yeah, C-po. That doesn't surprise me.

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

@syncer @dmbaturin Pull request ready: https://github.com/vyos/vyos-build/pull/10

@syncer @dmbaturin Please pull https://github.com/vyos/vyatta-cfg-system/pull/60 and https://github.com/vyos/vyos-build/pull/9

Tag VyOS 1.2.x should be removed as CVE is already fixed.

Verified using iOS 10.3.3 accross VLANs. mDNS services like Airplay working.

@UnicronNL could you please mirror https://github.com/c-po/vyos-bcast-relay.git to https://github.com/vyos/vyos-bcast-relay.git and set up a CI job? After this I can submit the appropriate merge requests for vyos-world abd vyos-build.

@UnicronNL could you please mirror https://github.com/c-po/vyos-cfg-avahi.git to https://github.com/vyos/vyos-cfg-avahi.git and set up a CI job? After this I can submit the appropriate merge requests for vyos-world abd vyos-build.

Status can be seen here: https://github.com/c-po/vyos-cfg-avahi

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

Actually I like the fact to have the users SSH pub key inside the config. This makes it super handy to just copy/paste a users config entry arround VyOS instances.

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

https://github.com/vyos/vyatta-cfg-system/commit/2f3ec2cd1f5ec543abb8fc46c5ab606ebe8edcdc
https://github.com/vyos/vyos-build/commit/53bd0ad27836eee5be5caee0f34d15205800a510

https://github.com/vyos/vyos-build/commit/51e4718ed2d77fcad6448fd09814e8e3272f10b4

same problem:
https://forum.vyos.net/showthread.php?tid=18134

@syncer This one is fixed/merged and already working in the nightly builds.

Just to give some more information.

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

strip-private is a bash-pipe function (/etc/bash_completion.d/vyatta-op).

Good objection. This should be avoided!

Can you check this @dmbaturin @UnicronNL

Moved to 1.2 as per discussion with @dmbaturin

note: careful when overruling vtysh commands (tt == save?)

@syncer could this change be approved or is anything else missing?

Hi @c-po. Unfortunately I have no access to EdgeOS to offer guidance on this. I will however ask on the VyOS boards since a lot of folks seem to be using them, perhaps one of those folks can offer feedback.

I'll start an investigation after T345.

@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

Should be fixed now

During restructuring my IPsec HUB/SPOKES I would have liked this possibility, too.

@babak do you happen to know if this is workong on EdgeOS devices? Then I could extract their implementation.

@UnicronNL please merge when you have time

https://github.com/vyos/vyos-build/pull/8

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

@syncer, I integrated your referenced splash.png

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

This is how it would look like:

Right. Pull request merged. I'll make sure that it's all working once it's made it to the nightlies, and then close this one.

Well, I have to ask everybody to double think about the very decision to drop the support for "install system" option.
The point is - when you do "install image" - you just drop known-working OS image file to some directory, and if you want to update the OS, you just drop another one (am I correct here?).
But, If you've installed some custom .deb's on the host, you should re-install them after the OS image is updated, even if you had to install new image because of one-line security fix.
Isn't it the scenario for which all those people in debian have used package manager for decades? Isn't it better to just update one package in installed system?

+1 for removal.

Yup. Definately not reproducible.

Removed and sent pull request:
https://github.com/vyos/vyatta-cfg-system/pull/59
https://github.com/vyos/vyatta-op/pull/10

Fixed in Kernel 4.4.26. VyOS 1.2.x (development) uses 4.4.47.

I just have verified that " LLDP-MED fast start mechanism: yes" is the default after my mentioned commit.

@syncer As this is an option to lldpcli I suggest fixing the above (1) and create a new command (2) for LLDP-MED enable/disable and interval. My current knowledge ov VyOS build/configure currently only allows me to fix (1).

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)

I can remove -L so it's working again. Should I?

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

Please see: https://github.com/vyos/vyatta-wireless/pull/6 this should fix the wrong path issue!

@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

@syncer not in the config dump, in the bash-history that's included.

@EwaldvanGeffen see T328

I just noticed your pastes. We need to filter out the set password commands as they will contain plaintext passwords. This could be solved by making the command interactive (it asks for the password to be typed in) similarly to other platforms. There might be other stuff that requires filtering-out history or refactoring.