Page MenuHomePhabricator
Feed Advanced Search

Tue, Apr 16

jestabro added a watcher for VyConf: jestabro.
Tue, Apr 16, 4:34 PM

Feb 26 2019

bnjf claimed T1269: GCE build script fixes.

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

Feb 26 2019, 11:41 PM · VyConf
bnjf created T1269: GCE build script fixes.
Feb 26 2019, 11:41 PM · VyConf

Nov 13 2018

nirmal changed Difficulty level from unknown to normal on T1005: Support for multiple SSID in station mode , WPA-EAP.
Nov 13 2018, 5:23 PM · VyOS 1.3 Equuleus
nirmal created T1005: Support for multiple SSID in station mode , WPA-EAP.
Nov 13 2018, 5:23 PM · VyOS 1.3 Equuleus

Sep 6 2018

darkdragon-001 asked Q148: Configuration Reference.
Sep 6 2018, 8:16 PM · Restricted Project, VyConf
darkdragon-001 added a comment to Q147: Automatically delete old logs.

I'm using VyOS 1.2.0-beta1 (lithium) with a 1 GB HDD on ESXi.

Sep 6 2018, 6:50 PM · VyConf
c-po added a comment to Q147: Automatically delete old logs.

I‘m using VyOS 1.2.x wirh a 4GB HDD on ESXi

Sep 6 2018, 5:53 PM · VyConf
darkdragon-001 asked Q147: Automatically delete old logs.
Sep 6 2018, 4:13 PM · VyConf

Aug 4 2018

dmbaturin closed T255: Add curly config renderer as Resolved.

The renderer works now (for a long time already, even), so it's time to close this task finally. ;)

Aug 4 2018, 7:01 PM · VyOS 2.0.x, VyConf

Jun 1 2018

c-po moved T599: Bind NTP service to specific interface from Need Triage to Finished on the VyOS 1.2 Crux board.
Jun 1 2018, 7:17 AM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)

May 31 2018

maugli13 added a comment to T599: Bind NTP service to specific interface.

It looks pretty clear from configuration point of view. Actually this request was made to avoid potential security breach if somebody doesn't have correct acl on wan facing interface.

May 31 2018, 11:23 AM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)
dmbaturin moved T597: Code testing on sonarcloud.com from Need Triage to In Progress on the VyOS 1.2 Crux board.
May 31 2018, 12:13 AM · VyOS 1.3 Equuleus

May 27 2018

c-po added a comment to T599: Bind NTP service to specific interface.

As soon as someone sets set system ntp allow-clients address 172.16.0.0/12 we act as NTP server for this network,too. It's a bit odd that this node is under system but ... it is as it is.

May 27 2018, 6:57 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)
syncer added a comment to T599: Bind NTP service to specific interface.

that is weird,
i was under impression that we have it as client.
So it perfectly make sense have it under service

May 27 2018, 2:47 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)
c-po added a comment to T599: Bind NTP service to specific interface.

@syncer we do offer NTP as service (unfortunately it's unter the system tree instead of service.

May 27 2018, 2:43 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)
syncer triaged T599: Bind NTP service to specific interface as Normal priority.

@c-po i think we not offer ntp service as of now, but i think maybe we should?

May 27 2018, 10:02 AM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)

May 1 2018

c-po updated subscribers of T599: Bind NTP service to specific interface.

We already have set system ntp allow-clients address 172.16.0.0/12 which can become a brother to a new command named set system ntp listen-on.

May 1 2018, 4:35 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)

Apr 12 2018

c-po added a project to T599: Bind NTP service to specific interface: VyOS 1.2 Crux.
Apr 12 2018, 7:45 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)
maugli13 created T599: Bind NTP service to specific interface.
Apr 12 2018, 3:20 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)

Apr 7 2018

syncer triaged T590: openvpn config using openvpn config file as Wishlist priority.
Apr 7 2018, 11:08 AM · VyConf

Apr 6 2018

syncer triaged T597: Code testing on sonarcloud.com as Normal priority.
Apr 6 2018, 8:22 AM · VyOS 1.3 Equuleus

Apr 1 2018

squeeby added a comment to T590: openvpn config using openvpn config file.

I agree with the above, this is actually how I'm dealing with custom options with dhcpd at the moment, however the same can't be done with openvpn as the functionality to include files doesn't exist within openvpn's config format, whereas it does with dhcpd.

Apr 1 2018, 4:41 PM · VyConf
mickvav added a comment to T590: openvpn config using openvpn config file.
Apr 1 2018, 7:09 AM · VyConf
mickvav updated subscribers of T590: openvpn config using openvpn config file.

We have thing like this in dhcpd's config - there you can state something like "subnet-parameters ... include file".
I was thinkking a little bit on it and came to the following idea - may be we should implement general syntax for stanza like "hey, vyos, I have config file for this service, please use it as is, but I still need the service to be operated on by vyos CLI commands". How do you think, would it be a good option to implement @dmbaturin?

Apr 1 2018, 7:09 AM · VyConf

Mar 31 2018

squeeby added a comment to T590: openvpn config using openvpn config file.

Not just for inputting alot of commands, but making it possible to simply specifiy an opevnpn config instead of having to re-implement every possible openvpn setting using the VyOS syntax would be a huge benefit.
Not to mention the automation aspects.. copy config, load it. done.

Mar 31 2018, 8:57 PM · VyConf

Mar 22 2018

wzk created T590: openvpn config using openvpn config file.
Mar 22 2018, 6:04 AM · VyConf

Mar 15 2018

Diffusion added a commit to T210: Use TOML rather than JSON for the vyconfd.conf config: Restricted Diffusion Commit.
Mar 15 2018, 5:21 AM · VyOS 2.0.x, VyConf
Diffusion added a commit to T210: Use TOML rather than JSON for the vyconfd.conf config: Restricted Diffusion Commit.
Mar 15 2018, 5:20 AM · VyOS 2.0.x, VyConf

Mar 3 2018

syncer closed Q4: VyOS CLI startup as resolved.
Mar 3 2018, 11:20 AM · VyOS 2.0.x, VyOS 1.1.x (1.1.8), VyConf
syncer closed Q3: Basic VyConf architecture as resolved.
Mar 3 2018, 11:20 AM · VyConf

Oct 25 2017

Lillecarl added a comment to V3: Tag node syntax for VyOS 2.0.

Considering JSON's a standard that's quite close to the VyOS syntax, i don't see why maintaining another nonstandard format is needed when JSON is available :)

Oct 25 2017, 1:03 PM · VyOS 2.0.x, VyConf

Oct 7 2017

volga629 created T415: Beta ISO VTI Tunnel.
Oct 7 2017, 8:12 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)

Sep 8 2017

dmbaturin created T387: Prevent command injection in VyConf external validator execution.
Sep 8 2017, 6:05 AM · VyConf

Sep 7 2017

dmbaturin added a comment to V3: Tag node syntax for VyOS 2.0.

@sebastianm In VyConf it's going to be fairly easy (ok, possible at least) to implement different input and output formats, so chances are we can add | display json or | display yaml filters if there's demand for it.

Sep 7 2017, 10:23 PM · VyOS 2.0.x, VyConf

Aug 28 2017

JulesT added a comment to V3: Tag node syntax for VyOS 2.0.

To my mind... I'd rather keep a compatible syntax than a new one, even if there are benefits in terms of uniformity and parsing.

Aug 28 2017, 9:36 PM · VyOS 2.0.x, VyConf
sebastianm added a comment to V3: Tag node syntax for VyOS 2.0.

I say don't change it (keep it the same as it's in 1.1.7). I'd consider YAML or JSON (in that order) though. (I am/was lylylyly on IRC).

Aug 28 2017, 8:25 PM · VyOS 2.0.x, VyConf

Jul 24 2017

syncer removed a member for VyConf: kostiantyn.
Jul 24 2017, 6:03 PM
syncer set the image for VyConf to F15957: profile.
Jul 24 2017, 10:58 AM
syncer changed the join policy for VyConf.
Jul 24 2017, 10:55 AM

Feb 26 2017

afics added a watcher for VyConf: afics.
Feb 26 2017, 7:06 PM
creaworlds added a member for VyConf: creaworlds.
Feb 26 2017, 12:06 AM

Feb 8 2017

shon added a comment to T255: Add curly config renderer.
Feb 8 2017, 1:03 PM · VyOS 2.0.x, VyConf

Jan 26 2017

amata added a watcher for VyConf: amata.
Jan 26 2017, 4:13 PM

Jan 18 2017

shon claimed T255: Add curly config renderer.

Following a discussion with @dmbaturin in #vyos, I'm to work on this puppy.

Jan 18 2017, 3:23 AM · VyOS 2.0.x, VyConf

Jan 17 2017

dmbaturin closed T250: Implement intuitive node sorting as Resolved.
Jan 17 2017, 6:42 PM · VyOS 2.0.x, VyConf
dmbaturin added a comment to T250: Implement intuitive node sorting.

I think we can just reference it directly.

Jan 17 2017, 7:05 AM · VyOS 2.0.x, VyConf
shon added a comment to T250: Implement intuitive node sorting.

In that case, BatString can just be added as a dependency, I guess, and we can call upon that function to sort as needed? Or would you still like a specific function for node sorting?

Jan 17 2017, 6:24 AM · VyOS 2.0.x, VyConf
dmbaturin added a comment to T250: Implement intuitive node sorting.

I've just done a quick test of the BatString.numeric_compare, looks perfect.

Jan 17 2017, 6:19 AM · VyOS 2.0.x, VyConf
shon added a comment to T250: Implement intuitive node sorting.

Depending on your feelings toward batteries, we could either use BatString's numeric_compare or just crib the implementation of that function (with all due credit given, of course).

Jan 17 2017, 3:12 AM · VyOS 2.0.x, VyConf
shon added a comment to T250: Implement intuitive node sorting.

I like this kind of problem.

Jan 17 2017, 12:00 AM · VyOS 2.0.x, VyConf

Jan 16 2017

dmbaturin closed T2: Make sure set/delete functions can be used without path validation as Resolved.

Already implemented in Config_tree.

Jan 16 2017, 9:39 AM · VyConf
dmbaturin added a comment to T28: Add auto provisioning.

This has nothing to do with vyconf. Please move it out of the project, and to vyos 1.2.0

Jan 16 2017, 9:39 AM · VyOS 1.3 Equuleus

Jan 15 2017

dmbaturin closed T245: Add support for the old tag node syntax to the curly config parser as Resolved.
Jan 15 2017, 6:38 PM · VyOS 2.0.x, VyConf
dmbaturin closed T249: Add support for "inactive" and "ephemeral" node properties to the parser as Resolved.
Jan 15 2017, 6:36 PM · VyConf, VyOS 2.0.x

Jan 14 2017

dmbaturin closed T216: Decide on the wire protocol for VyConf as Resolved.

Protobuf schema has been written.

Jan 14 2017, 6:46 PM · VyOS 2.0.x, VyConf
dmbaturin updated the task description for T255: Add curly config renderer.
Jan 14 2017, 8:36 AM · VyOS 2.0.x, VyConf
dmbaturin created T255: Add curly config renderer.
Jan 14 2017, 8:31 AM · VyOS 2.0.x, VyConf

Jan 13 2017

jclendenan added a comment to V3: Tag node syntax for VyOS 2.0.

I'm a "NO" as a network engineer with a bunch of different brands already XORP style, or as close to JunOS as you can get it the best. Yet another (Similar) config style would be way too much frustration for most of my peers to even consider.

Jan 13 2017, 9:27 PM · VyOS 2.0.x, VyConf
dmbaturin created T254: Global node name validation in VyConf.
Jan 13 2017, 1:19 PM · VyOS 2.0.x, VyConf
dmbaturin assigned T231: Add a function from loading interface definitions from a directory to the Startup module to shon.
Jan 13 2017, 7:16 AM · VyConf, VyOS 2.0.x
shon added a comment to T231: Add a function from loading interface definitions from a directory to the Startup module.

@dmbaturin, you can probably assign this one to me, if you feel comfortable doing so. I think I'm nearly done. I'd just like to put together some decent test cases before making a PR.

Jan 13 2017, 3:23 AM · VyConf, VyOS 2.0.x

Jan 12 2017

dmbaturin created T251: Implement component dependency sorting.
Jan 12 2017, 2:08 AM · VyOS 2.0.x, VyConf

Jan 11 2017

dmbaturin updated the task description for T250: Implement intuitive node sorting.
Jan 11 2017, 9:39 PM · VyOS 2.0.x, VyConf
dmbaturin created T250: Implement intuitive node sorting.
Jan 11 2017, 9:39 PM · VyOS 2.0.x, VyConf
dmbaturin created T249: Add support for "inactive" and "ephemeral" node properties to the parser.
Jan 11 2017, 4:48 AM · VyConf, VyOS 2.0.x

Jan 9 2017

mickvav added a comment to V3: Tag node syntax for VyOS 2.0.

Well, my vote is "No", because if for small configs it's OK to have just intent-expressed syntax, if you have huge one, e.g. several pages - if you omit prefix before, say, 55, you will have to guess from context, if it is a vlan or preffix list entry, or VRRP group or whatever.

Jan 9 2017, 7:54 AM · VyOS 2.0.x, VyConf
adestis added a comment to V3: Tag node syntax for VyOS 2.0.

The suggestion from @rps (XORP style) seems to be the best way from my point of view:
https://phabricator.vyos.net/V3#51

Jan 9 2017, 7:13 AM · VyOS 2.0.x, VyConf
dmbaturin edited the description of V3: Tag node syntax for VyOS 2.0.
Jan 9 2017, 5:34 AM · VyOS 2.0.x, VyConf
dmbaturin created T245: Add support for the old tag node syntax to the curly config parser.
Jan 9 2017, 4:47 AM · VyOS 2.0.x, VyConf

Jan 8 2017

rps added a comment to V3: Tag node syntax for VyOS 2.0.

With respect to the concerns I mentioned above, I've voted no.

Jan 8 2017, 6:46 PM · VyOS 2.0.x, VyConf
systo added a comment to V3: Tag node syntax for VyOS 2.0.

@dmbaturin, Im with you on the aesthetics, and the readability. In the firewall ruleset example I still feel that the first is easier read than the second. Are we talking hundreds of lines to parse the former vs the latter? It seems like the later, across a whole config would at 10-20 lines if not more depending on the complexity. I for one am interested in seeing as much of the config on one screen, vs needlessly needing to scroll. As for your Q on pfSense, I've had to edit the xml configuration file by hand based on how pfSense sorts VLANs based on their add date vs numerical value.

Jan 8 2017, 6:12 PM · VyOS 2.0.x, VyConf
dmbaturin added a comment to V3: Tag node syntax for VyOS 2.0.

@tmartinson Well, you should change your vote then (votes are not final here, for the better I guess).

Jan 8 2017, 3:43 PM · VyOS 2.0.x, VyConf
rps added a comment to V3: Tag node syntax for VyOS 2.0.

I keep coming back to a sense that dramatic syntax changes are very damaging and disruptive to users. My fear is that we'll be spending years explaining to people that they're looking at old documentation or examples and that they don't have their curly braces in the right place. Or that we'll alienate a segment of our user base that is averse to change.

Jan 8 2017, 3:08 PM · VyOS 2.0.x, VyConf
tmartinson added a comment to V3: Tag node syntax for VyOS 2.0.

In the example above, I vote that the first example where name Foo and rule 10 are on the same line. It is much easier to read, and shortens up the output on the display. Sometimes with long configurations, it is easier when you can see more information on the same screen without scrolling.

Jan 8 2017, 3:04 PM · VyOS 2.0.x, VyConf
dmbaturin added a comment to V3: Tag node syntax for VyOS 2.0.

@systo Just to make sure you are looking at it the right way, in the large it's actually less verbose than old syntax. The vif may not be the best example but firewall would make it apparent:

Jan 8 2017, 12:49 PM · VyOS 2.0.x, VyConf
systo added a comment to V3: Tag node syntax for VyOS 2.0.

As an end user, I just keep coming back to the verbosity of the syntax, and the divergence from all the other established command syntax in this space. VyOS doesn't have the following to do it differently, as it adds another barrier to adoption. Its a subtle change, but it has a long reach, especially when luring former vyatta or EdgeOS converts that want to roll-their-own, vs buy MIPS hardware. While I understand it may save coding time in the end, I'm trying to avoid the verbosity that is pfsense, and awall/shorewall. I bet if you asked a room of non-vyos engineers, they would prefer the first syntax with a much higher percentage, but alas I digress.

Jan 8 2017, 8:57 AM · VyOS 2.0.x, VyConf

Jan 6 2017

whiskeyalpharomeo added a comment to V3: Tag node syntax for VyOS 2.0.

Any change that imparts simplicity for the coding ahead is worthwhile. Time saved in the parser's reduced complexity can be spent in other ways.

Jan 6 2017, 12:35 AM · VyOS 2.0.x, VyConf

Jan 5 2017

dmbaturin added a comment to V3: Tag node syntax for VyOS 2.0.

@rps An serious issue with "interfaces { eth0" is that when there is no parent subtree of all ethernet interfaces specifically, we don't know which script to call when something in "eth0" changes. We'd have to have one big script that handles the whole "interfaces" subtree, which is very problematic when it comes to adding new interface types. If eth* interfaces are children of the "ethernet" node and tun* interfaces are children of the "tunnel" node, it's easy to attach ethernet script to the "ethernet" node and "tunnel" script to the "tunnel" node, if we want to add "openvpn" later, we won't have to modify that large script to accomodate it

Jan 5 2017, 3:43 PM · VyOS 2.0.x, VyConf
rps added a comment to V3: Tag node syntax for VyOS 2.0.

I haven't voted yet because I haven't decided ... It's a big change.

Jan 5 2017, 2:44 PM · VyOS 2.0.x, VyConf
dmbaturin added a comment to V3: Tag node syntax for VyOS 2.0.

@rps No, that's not the biggest challenge. Semicolon at the end of leaf nodes makes them unambiguous enough and easy to tell from tag nodes (this is especially bad with valueless nodes by the way, think "disable", colon wouldn't help there, but semicolon at the end does the job). The biggest challenge is that with "ethernet eth0" the parser must be fully stateful and capable of tracking which parent nodes it's already seen. "eth0", "eth1" etc. are really children of the same node called "ethernet", but in the config they appear separately. Consider this unusual but logically valid config:

Jan 5 2017, 2:02 PM · VyOS 2.0.x, VyConf
Merijn added a comment to V3: Tag node syntax for VyOS 2.0.

@rps this distinction also seems to be easy in the original proposed solution by @dmbaturin because key value pairs are not followed by '{' and the rest is.

Jan 5 2017, 1:57 PM · VyOS 2.0.x, VyConf
rps added a comment to V3: Tag node syntax for VyOS 2.0.

From a parsing perspective the only challenge tag nodes present is that you can't easily distinguish between "key value" and "key tag" without context. "key" and "key tag value" are fine. Using a ":" you get "key: value" vs "key tag" which removes the ambiguity.

Jan 5 2017, 1:45 PM · VyOS 2.0.x, VyConf
kspviswa removed a member for VyConf: kspviswa.
Jan 5 2017, 1:31 PM
kspviswa removed a watcher for VyConf: kspviswa.
Jan 5 2017, 1:30 PM
Merijn added a comment to V3: Tag node syntax for VyOS 2.0.

@dmbaturin I understand that the discussion is "unit 0" vs "unit { 0", what i meant was that i could be an option to keep following the JunOS style as much as possible to maybe enable more interoperability.

Jan 5 2017, 1:29 PM · VyOS 2.0.x, VyConf
Merijn added a comment to V3: Tag node syntax for VyOS 2.0.

Well plain JSON would also be an option then :-)

Jan 5 2017, 1:27 PM · VyOS 2.0.x, VyConf
dmbaturin added a comment to V3: Tag node syntax for VyOS 2.0.

@Merijn I'm still not sure why JunOS has that "unit" thing. To me it looks redundant, redundant ©. Though what we are discussing is "unit 0" vs "unit { 0" grammatic distinction, rather than specific syntax of ethernet interfaces.

Jan 5 2017, 1:27 PM · VyOS 2.0.x, VyConf
rps added a comment to V3: Tag node syntax for VyOS 2.0.

The XORP configuration syntax (which Vyatta initially built upon) solves the parsing issue with the simple introduction of a ":" as a delimiter between keys and values.

Jan 5 2017, 1:21 PM · VyOS 2.0.x, VyConf
Merijn added a comment to V3: Tag node syntax for VyOS 2.0.

In the blog post #7 i liked the address [ 192.168.2.1/24 10.10.10.1/30 ]; part. But since i work most of the time with mixed JunOS and Vyos environments a mostly the same syntax would be very nice :-)
However JunOS would be:

Jan 5 2017, 1:19 PM · VyOS 2.0.x, VyConf
tmartinson added a comment to V3: Tag node syntax for VyOS 2.0.

I was thinking that the variable would actually be "vlan-id 99". That was written simply to make it easier to read. But if it will be the top of a node, then we end up with vif, vlan-id. Which is redundant, redundant. In that case I would drop the "vlan-id" portion all together. It is only there for esthetics.

Jan 5 2017, 1:13 PM · VyOS 2.0.x, VyConf
dmbaturin added a comment to V3: Tag node syntax for VyOS 2.0.

@tmartinson No, "vlan-id 99" is the old style. And, at that stage we don't know if it's ethernet or not.

Jan 5 2017, 12:59 PM · VyOS 2.0.x, VyConf
tmartinson added a comment to V3: Tag node syntax for VyOS 2.0.

Maybe something like this? We already know that it is an ethernet interface by the fact that it is eth0. And by adding the "vlan-id" portion we get a newer style of configuration but keep the read-ability of the configuration stanza.

Jan 5 2017, 12:51 PM · VyOS 2.0.x, VyConf
dmbaturin added a comment to V3: Tag node syntax for VyOS 2.0.

@Merijn Now that you remind me of it, I think "edit interfaces tunnel; copy tun10 to tun11" or similar should be possible regardless of the config syntax. No matter how it looks in the config, internally "tunnel" is a node with children "tun0", "tun1" and so on, and there's no reason why it shouldn't be possible to use it as edit level.

Jan 5 2017, 12:48 PM · VyOS 2.0.x, VyConf
Merijn added a comment to V3: Tag node syntax for VyOS 2.0.

A pro for me would be that i can do 'edit interfaces ethernet eth0 vif' and work with all virtual interfaces.

Jan 5 2017, 12:36 PM · VyOS 2.0.x, VyConf
dmbaturin added a comment to V3: Tag node syntax for VyOS 2.0.

@dsteinkopf Not sure, we'll have to devise some rules regarding line breaks, and past some number of leaf nodes inside we are back to the original aesthetic issue (and then there can be non-leaf nodes inside too!
On a fresh look today, I'm convinced that the old tag node formatting is aesthetically superior, so myself as a user of my own project I'm probably voting no, though as a developer I want to see how many people also think it's worth it.

Jan 5 2017, 12:26 PM · VyOS 2.0.x, VyConf
dsteinkopf added a comment to V3: Tag node syntax for VyOS 2.0.

Maybe it's a good idea to 1. use the new syntax but 2. generate less line breaks. e.g.

interfaces {
  ethernet { eth0 {
      vif {
          99 { address 192.0.2.1/24; }
          101 { address 203.0.113.1/24; }
      }
  } }
}

In this case the new syntax would be fine for me. (Details open for discussion.)

Jan 5 2017, 11:04 AM · VyOS 2.0.x, VyConf
dmbaturin created V3: Tag node syntax for VyOS 2.0.
Jan 5 2017, 9:56 AM · VyOS 2.0.x, VyConf

Jan 1 2017

shon added a watcher for VyConf: shon.
Jan 1 2017, 10:12 AM

Dec 23 2016

dmbaturin reassigned T230: Add missing data access functions to the Reference_tree module, and tests for them from dmbaturin to philsummers.
Dec 23 2016, 1:18 AM · VyConf, VyOS 2.0.x