Feed All Stories

Yesterday

syncer assigned T523: Forwarder listening on port 53/tcp to c-po.

Want to look into that?

Wed, Jan 17, 6:21 PM · VyOS 1.2.x, VyOS 1.1.x
syncer created T523: Forwarder listening on port 53/tcp.
Wed, Jan 17, 6:20 PM · VyOS 1.2.x, VyOS 1.1.x
afics added a comment to T143: Add support for Large BGP Community.

I am very interested in this, has any work been done?

Wed, Jan 17, 10:13 AM · VyOS 1.2.x, VyOS 2.0.x

Tue, Jan 16

agustafson asked Q124: Slow response from show commands when using Intel g73131 and SNMP.
Tue, Jan 16, 10:43 PM · VyOS 1.1.x
pers.edwin updated the task description for T522: Removing interface from bridge results in error & config / system state mismatch.
Tue, Jan 16, 2:58 PM · VyOS 1.1.x
pers.edwin created T522: Removing interface from bridge results in error & config / system state mismatch.
Tue, Jan 16, 2:35 PM · VyOS 1.1.x
beamerblvd added a comment to Q122: How to properly configure multiple static IPv4 WAN addresses and IPv6 prefix to internal DHCP and static hosts.
In Q122, @aopdal wrote:

With prefix delegation you have a static prefix on your inside, but the "wan" interface on the router is using DHCP.

Tue, Jan 16, 2:17 PM · VyOS 1.1.x
aopdal added a comment to Q122: How to properly configure multiple static IPv4 WAN addresses and IPv6 prefix to internal DHCP and static hosts.

With prefix delegation you have a static prefix on your inside, but the "wan" interface on the router is using DHCP.

Tue, Jan 16, 2:14 PM · VyOS 1.1.x
beamerblvd added a comment to Q122: How to properly configure multiple static IPv4 WAN addresses and IPv6 prefix to internal DHCP and static hosts.
In Q122, @aopdal wrote:

Are your addresses managed from Comcast using prefix delegation?

Tue, Jan 16, 1:53 PM · VyOS 1.1.x
aopdal added a comment to Q122: How to properly configure multiple static IPv4 WAN addresses and IPv6 prefix to internal DHCP and static hosts.

Without routing you probably can't get it to work. Are your addresses managed from Comcast using prefix delegation?

Tue, Jan 16, 1:36 PM · VyOS 1.1.x
beamerblvd added a comment to Q122: How to properly configure multiple static IPv4 WAN addresses and IPv6 prefix to internal DHCP and static hosts.
In Q122, @aopdal wrote:

@beamerblvd have you added routes for your vif 100,200 and 900 in your "COMCAST BUSINESS IP GATEWAY"?

Tue, Jan 16, 1:29 PM · VyOS 1.1.x
aopdal added a comment to Q122: How to properly configure multiple static IPv4 WAN addresses and IPv6 prefix to internal DHCP and static hosts.

@beamerblvd have you added routes for your vif 100,200 and 900 in your "COMCAST BUSINESS IP GATEWAY"?

Tue, Jan 16, 1:23 PM · VyOS 1.1.x
beamerblvd added a comment to Q122: How to properly configure multiple static IPv4 WAN addresses and IPv6 prefix to internal DHCP and static hosts.

So the attempts with /56 and /60 were part of my hundreds of different combinations/attempts to get this to work. I have one /56 assigned to me (2603:xxxx:xxxx:8700::/56) with one gateway assigned to me (2603:xxxx:xxxx:8700:7454:7dff:feb1:d391). Skipping the WAN for just a second because I believe(d) it to need different configuration, I expected to be able to break that /56 up into /64s and use them like so:

Tue, Jan 16, 1:15 PM · VyOS 1.1.x
elico added a comment to Q122: How to properly configure multiple static IPv4 WAN addresses and IPv6 prefix to internal DHCP and static hosts.

I am willing to give some advice but it's an issue to understand your infrastructure based on a very fuzzy set of details.
The basic rule of thumb that I can think of is that you cannot assign ip addresses with the same or overlapping prefix on two interfaces and route between them.
I do not know if the VyOS kernel supports IPV6 NAT feature but this should be a very last resort for specific scenarios.
If you need some examples on how IPv6 prefixes are being used you can try to peek at some IPv6 brokers such as Hurricane Electric.
They give you a very specific IPv6 address and prefix for the WAN side with a specific default route,
Then they give you a different prefix to assign the internal network which is behind the main gateway.
Is your setup different then what HE offers?

Tue, Jan 16, 12:08 PM · VyOS 1.1.x
aopdal added a comment to Q122: How to properly configure multiple static IPv4 WAN addresses and IPv6 prefix to internal DHCP and static hosts.

Perhaps you could make a drawing of what you try to get working? With proper interface naming etc. eth0 - wan, eth1 - dmz, eth2 - lan or whatever you are using. It makes it easier to understand what you try to do. And for the interfaces why do you want to use the /60?

Tue, Jan 16, 7:43 AM · VyOS 1.1.x
beamerblvd added a comment to Q122: How to properly configure multiple static IPv4 WAN addresses and IPv6 prefix to internal DHCP and static hosts.
In Q122, @aopdal wrote:

Maybe this is relevant? https://phabricator.vyos.net/T421

Tue, Jan 16, 7:26 AM · VyOS 1.1.x
aopdal added a comment to Q122: How to properly configure multiple static IPv4 WAN addresses and IPv6 prefix to internal DHCP and static hosts.

Maybe this is relevant? https://phabricator.vyos.net/T421

Tue, Jan 16, 7:17 AM · VyOS 1.1.x
beamerblvd added a comment to Q122: How to properly configure multiple static IPv4 WAN addresses and IPv6 prefix to internal DHCP and static hosts.

So, I ended up handling my IPv4 addresses using 1:1 NAT. It works, and I don't love it, but I think it's the best it's going to get with Comcast's clunky static IP infrastructure. But I'm having no luck with IPv6, and could really use some help with someone who understand's static IPv6 and VyOS a little better. I have a static IPv6 prefix, and I need to statically assign some of those to public-facing servers behind my firewall/router, but it's like pulling teeth from a rhinoceros.

Tue, Jan 16, 5:08 AM · VyOS 1.1.x
genta added a comment to T91: vyosintfwatchd bug.

I've found memory leak bug in Cstore perl binding (perlxs).
This binding is a part of vyatta-cfg.

Tue, Jan 16, 3:24 AM · VyOS 1.2.x

Mon, Jan 15

vovakononov1 asked Q123: ip unnumbered/Super VLAN.
Mon, Jan 15, 11:55 AM · VyOS 2.0.x, VyOS 1.3.x, VyOS 1.2.x

Sun, Jan 14

syncer added a comment to T452: WiFi: Enable support for 5GHz AccesPoints with DFS.

That is fine, maybe with exception for some nasty vulnerabilities, however we also not disappear
just handy to have someone dedicated to wireless (almost separate world)
Thank you!

Sun, Jan 14, 8:44 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar added a comment to T452: WiFi: Enable support for 5GHz AccesPoints with DFS.

@syncer thanks for the offer :)

Sun, Jan 14, 8:01 PM · VyOS 1.2.x, VyOS 1.3.x
syncer triaged T513: Docs for devs: How to use Python, XML et al instead of Bash and Perl for VyOS configuration as Normal priority.
Sun, Jan 14, 5:49 PM · Restricted Project, VyOS 1.2.x
syncer moved T512: New package versions not synced to http://dev.packages.vyos.net from Need Triage to Finished on the VyOS 1.2.x board.
Sun, Jan 14, 5:45 PM · VyOS 1.2.x
syncer closed T512: New package versions not synced to http://dev.packages.vyos.net as Resolved.

@c-po i think this was fixed by @dmbaturin
marking as solved, if not, reopen

Sun, Jan 14, 5:45 PM · VyOS 1.2.x
syncer closed T507: vyatta-cfg-system -> SSH: Failure to correctly alter Ciphers and MACs as Resolved.
Sun, Jan 14, 5:42 PM · VyOS 1.2.x
syncer triaged T506: Support CIDR notation in firewall address-group as Wishlist priority.
Sun, Jan 14, 5:40 PM · VyOS 1.2.x
syncer added a comment to T452: WiFi: Enable support for 5GHz AccesPoints with DFS.

@alainlamar by any chance you want to be maintainer of wireless subsystem ? :)
It looks like you both have knowledge and real life use case and that make it whole easier

Sun, Jan 14, 5:24 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar renamed T521: Network services may fail if vyatta-router.service startup takes longer than a few seconds from Network services may fail if vyatta-router.service startup takes longe rthan a few seconds to Network services may fail if vyatta-router.service startup takes longer than a few seconds.
Sun, Jan 14, 4:49 PM · VyOS 1.2.x
alainlamar renamed T521: Network services may fail if vyatta-router.service startup takes longer than a few seconds from Network Services start before vyatta-router.service is started to Network services may fail if vyatta-router.service startup takes longe rthan a few seconds.
Sun, Jan 14, 4:49 PM · VyOS 1.2.x
alainlamar created T521: Network services may fail if vyatta-router.service startup takes longer than a few seconds.
Sun, Jan 14, 4:47 PM · VyOS 1.2.x
alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sun, Jan 14, 1:52 PM · VyOS 1.2.x, VyOS 1.3.x

Sat, Jan 13

alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sat, Jan 13, 1:10 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sat, Jan 13, 12:57 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sat, Jan 13, 12:54 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sat, Jan 13, 12:47 PM · VyOS 1.2.x, VyOS 1.3.x

Fri, Jan 12

agustafson added a comment to T383: snmpd messages in log with nightly "vyos-999.201709032137-amd64.iso".

I am seeing similar messages in 1.1.8.

Fri, Jan 12, 5:46 PM · VyOS 1.2.x
shamidrasool updated the answer details for Q117: Instructions to build VyOS 1.2 from sources with frr (Answer 169).
Fri, Jan 12, 7:21 AM
dmbaturin created T520: Build scripts should use a load balanced Debian mirror.
Fri, Jan 12, 4:01 AM · VyOS 1.2.x

Thu, Jan 11

dmbaturin closed T519: Make vyos package mirror configurable in build scripts as Resolved.
Thu, Jan 11, 6:51 AM · VyOS 1.2.x
dmbaturin added a comment to T422: Packages server and downloads should be available via HTTPS.

The downloads.vyos.io is now using mandatory HTTPS. On the dev.packages.vyos.net, HTTPS is optional. To declare this closed, we need someone to independently verify that ISO build works with HTTPS for them.

Thu, Jan 11, 6:01 AM · Infrastructure
dmbaturin created T519: Make vyos package mirror configurable in build scripts.
Thu, Jan 11, 5:12 AM · VyOS 1.2.x

Sun, Jan 7

alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sun, Jan 7, 10:12 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sun, Jan 7, 9:05 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sun, Jan 7, 8:50 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar updated subscribers of T513: Docs for devs: How to use Python, XML et al instead of Bash and Perl for VyOS configuration.

@c-po thanks for pointing me to the interface definitions!

Sun, Jan 7, 8:30 PM · Restricted Project, VyOS 1.2.x
alainlamar updated the task description for T513: Docs for devs: How to use Python, XML et al instead of Bash and Perl for VyOS configuration.
Sun, Jan 7, 8:29 PM · Restricted Project, VyOS 1.2.x
c-po added a comment to T518: Move VyOS configuration syntax from Bash and node.def to XML.

@alainlamar nice work digging!

Sun, Jan 7, 8:14 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar added a comment to T517: Port configuration validator and parser to Python.

I found an example file in vyatta-lldp:

Sun, Jan 7, 8:01 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar added a comment to T518: Move VyOS configuration syntax from Bash and node.def to XML.

I found an example XML tag config file in vyatta-lldp:

Sun, Jan 7, 7:58 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar created T518: Move VyOS configuration syntax from Bash and node.def to XML.
Sun, Jan 7, 7:45 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar created T517: Port configuration validator and parser to Python.
Sun, Jan 7, 7:40 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sun, Jan 7, 6:26 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sun, Jan 7, 6:21 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sun, Jan 7, 6:15 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sun, Jan 7, 6:14 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sun, Jan 7, 6:10 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sun, Jan 7, 6:09 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sun, Jan 7, 5:48 PM · VyOS 1.2.x, VyOS 1.3.x
alainlamar updated the task description for T452: WiFi: Enable support for 5GHz AccesPoints with DFS.
Sun, Jan 7, 5:37 PM · VyOS 1.2.x, VyOS 1.3.x
squeeby added a comment to T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown.

I'm using ntop-ng + nprobe.

Sun, Jan 7, 1:28 PM · VyOS 1.2.x
alainlamar changed the visibility for T513: Docs for devs: How to use Python, XML et al instead of Bash and Perl for VyOS configuration.
Sun, Jan 7, 12:52 PM · Restricted Project, VyOS 1.2.x
alainlamar updated the task description for T513: Docs for devs: How to use Python, XML et al instead of Bash and Perl for VyOS configuration.
Sun, Jan 7, 10:57 AM · Restricted Project, VyOS 1.2.x
alainlamar updated the task description for T513: Docs for devs: How to use Python, XML et al instead of Bash and Perl for VyOS configuration.
Sun, Jan 7, 10:53 AM · Restricted Project, VyOS 1.2.x
alainlamar added projects to T513: Docs for devs: How to use Python, XML et al instead of Bash and Perl for VyOS configuration: VyOS 1.2.x, Restricted Project.
Sun, Jan 7, 10:42 AM · Restricted Project, VyOS 1.2.x
alainlamar updated subscribers of T513: Docs for devs: How to use Python, XML et al instead of Bash and Perl for VyOS configuration.
Sun, Jan 7, 10:19 AM · Restricted Project, VyOS 1.2.x
alainlamar created T513: Docs for devs: How to use Python, XML et al instead of Bash and Perl for VyOS configuration.
Sun, Jan 7, 10:16 AM · Restricted Project, VyOS 1.2.x
c-po moved T341: WOL Tools in base image from Backlog to In Progress on the VyOS 1.2.x board.
Sun, Jan 7, 8:26 AM · VyOS 1.2.x
c-po updated subscribers of T341: WOL Tools in base image.

@syncer tools added to base image. This would be perfect for a vyos-1x op mode command. Unfortunately I was not able to build a working template with the relax-ng templates (lack of xml/relax-ng) knowledge. @dmbaturin maybe you can help?

Sun, Jan 7, 8:26 AM · VyOS 1.2.x

Sat, Jan 6

syncer added a project to T508: ISC DHCP incorrect UDP checksum generation: vyatta-dhcp3.
Sat, Jan 6, 11:16 PM · vyatta-dhcp3, VyOS 1.2.x (VyOS 1.2.0 LTS Lithium), VyOS 1.1.x (1.1.9)
syncer triaged T508: ISC DHCP incorrect UDP checksum generation as Normal priority.
Sat, Jan 6, 11:13 PM · vyatta-dhcp3, VyOS 1.2.x (VyOS 1.2.0 LTS Lithium), VyOS 1.1.x (1.1.9)
c-po added a comment to T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown.

@squeeby which sflow collector do you use? Is there one you can recommend?

Sat, Jan 6, 11:02 PM · VyOS 1.2.x
c-po updated the task description for T512: New package versions not synced to http://dev.packages.vyos.net.
Sat, Jan 6, 9:56 PM · VyOS 1.2.x
c-po moved T379: UDP Broadcast Packet Relay from In Progress to Finished on the VyOS 1.2.x board.
Sat, Jan 6, 9:52 PM · VyOS 1.2.x
c-po added a comment to T379: UDP Broadcast Packet Relay.

Rewrote the scripts using vyos-1x and Python. This is now functioning on my routers.

Sat, Jan 6, 9:52 PM · VyOS 1.2.x
c-po created T512: New package versions not synced to http://dev.packages.vyos.net.
Sat, Jan 6, 11:52 AM · VyOS 1.2.x
c-po closed T509: vyos-build: VyOS Images have stopped building as Resolved.
Sat, Jan 6, 8:13 AM · VyOS 1.2.x
c-po added a comment to T509: vyos-build: VyOS Images have stopped building.

Working again

Sat, Jan 6, 8:12 AM · VyOS 1.2.x

Fri, Jan 5

jantman added a comment to V2: Should VyOS-specific shell be the login shell in VyOS 2.0?.

I like the way it works now, but honestly as long as I can get to both the CLI and the OS shell somehow (with a command), I don't really care which is the default.

Fri, Jan 5, 11:11 PM · VyOS 2.0.x
c-po moved T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown from In Progress to Finished on the VyOS 1.2.x board.
Fri, Jan 5, 8:12 PM · VyOS 1.2.x
c-po moved T510: vyos-1x generated crontab nodes missleading from In Progress to Finished on the VyOS 1.2.x board.
Fri, Jan 5, 8:12 PM · VyOS 1.2.x
c-po added a comment to T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown.

Merged into vyatta-netflow package and will be included in tonights build.

Fri, Jan 5, 8:07 PM · VyOS 1.2.x
squeeby added a comment to T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown.

Looks good!

Fri, Jan 5, 3:20 PM · VyOS 1.2.x
c-po added a comment to T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown.

Ok, next try: https://www.mybll.net/vyatta-netflow_ver02_all.deb

Fri, Jan 5, 3:15 PM · VyOS 1.2.x
squeeby added a comment to T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown.

This appears to operate as expected.

Fri, Jan 5, 2:58 PM · VyOS 1.2.x
c-po added a comment to T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown.

Could you alter the file manually to get a working state and pass it to me by e.g. pasting it here or a https://pastebin.com/ link? Then I could regenerate a package for testing. This would help me a lot as I do not have any flow collector.

Fri, Jan 5, 2:43 PM · VyOS 1.2.x
squeeby added a comment to T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown.

So by reverting, the file /opt/vyatta/sbin/vyatta-netflow.pl contains:

328 sub acct_add_nflog_target {
329     my ($intf) = @_;
330
331     my ($table_chain) = acct_get_table_chain();
332     while (my ($chain, $table) = each(%$table_chain)) {
333         my $cmd = "iptables -t $table -I $chain 1 -i $intf -j NFLOG" ." --nflog-group 2";
334         if (defined $nflog_range) {
335             $cmd .= " --nflog-range $nflog_range";
336         }
337         if (defined $nflog_threshold) {
338             $cmd .= " --nflog-threshold $nflog_threshold";
339         }
340         my $ret = system($cmd);
341         if ($ret >> 8) {
342             die "Error: [$cmd] failed - $?\n";
343         }
344     }
345 }
Fri, Jan 5, 2:18 PM · VyOS 1.2.x
c-po added a comment to T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown.

You can revert by switching back to the official VyOS package.

Fri, Jan 5, 2:13 PM · VyOS 1.2.x
squeeby added a comment to T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown.

Do you know how I can restore the previous version so I can see if it was this package that changed it?

Fri, Jan 5, 1:59 PM · VyOS 1.2.x
c-po added a comment to T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown.

Strange. I only changed /opt/vyatta/sbin/vyatta-netflow.pl to your recommendation.

Fri, Jan 5, 9:32 AM · VyOS 1.2.x
squeeby added a comment to T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown.

I applied your patch but now iptables has reverted to using the ULOG target instead of NFLOG:

squeeb@gw1# commit
[ system flow-accounting interface eth2 ]
iptables: No chain/target/match by that name.
Error: [iptables -t raw -I VYATTA_CT_PREROUTING_HOOK 1 -i eth2 -j ULOG --ulog-nlgroup 2 --ulog-cprange 64 --ulog-qthreshold 10] failed - 256
Fri, Jan 5, 7:50 AM · VyOS 1.2.x
c-po moved T510: vyos-1x generated crontab nodes missleading from Need Triage to In Progress on the VyOS 1.2.x board.
Fri, Jan 5, 6:51 AM · VyOS 1.2.x
c-po added a comment to T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown.

@squeeby do you mind verifying the following package containing your fix:

Fri, Jan 5, 6:50 AM · VyOS 1.2.x
squeeby added a comment to T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown.

Changing the following lines to the excerpt below in /opt/vyatta/sbin/vyatta-netflow.pl seems to work:

Fri, Jan 5, 1:51 AM · VyOS 1.2.x
squeeby added a comment to T296: Enabling NetFlow fails, iptables chain VYATTA_CT_PREROUTING_HOOK unknown.
# show system flow-accounting
 interface pppoe0
 interface eth2.2
 interface eth2.3
 sflow {
     agent-address 192.168.64.1
     sampling-rate 10
     server 192.168.64.10 {
         port 2055
     }
 }
Fri, Jan 5, 1:38 AM · VyOS 1.2.x

Thu, Jan 4

c-po triaged T510: vyos-1x generated crontab nodes missleading as Normal priority.
Thu, Jan 4, 11:34 AM · VyOS 1.2.x
c-po created T510: vyos-1x generated crontab nodes missleading.
Thu, Jan 4, 11:33 AM · VyOS 1.2.x
Tanuki added a watcher for vyos-frr: Tanuki.
Thu, Jan 4, 3:15 AM

Wed, Jan 3

netravnen added a watcher for VyOS 2.0.x: netravnen.
Wed, Jan 3, 3:22 PM
netravnen added a watcher for vyos-frr: netravnen.
Wed, Jan 3, 3:18 PM