FRR doesn't delete isis configuration related "interfaces" with

delete protocols isis foo interface eth1

protocol "isisd" in the test was added here https://github.com/vyos/vyos-1x/pull/483/files#diff-060cdf269ea89160caa0deaebe8e323f0559aa6dfd19e5634a33634f3e38e461R72

@kroy What PR?

sounds good - would be good having some other options than just domain-name and email, but that's another story :). I'll follow the other task then!

PR https://github.com/vyos/vyos-1x/pull/584

It already fixed in the master branch.
https://github.com/hiroyuki-sato/vyos-documentation/commit/8587946d16aaae6f5495c1e591220f88005cd276

Resolved in T2985

@SrividyaA Thanks.

I have tested on this rolling release VyOS 1.3-rolling-202010231135 and created a lab setup similar to the reporter's setup.

@craterman it seems bug with your resolution.

set service https certificates certbot

domain-name(s) should contain the desired server-name. A rewrite is in progress in:
https://phabricator.vyos.net/T2289

@jestabro hmmm I don't see that "certbot" in the completion - running on rolling 1.3... ? In fact, nodes "certificates" and "certbot" are not shown here:
set service https
Possible completions:
> api VyOS HTTP API configuration
> api-restrict Restrict api proxy to subset of virtual hosts
> certificates TLS certificates
+> virtual-host Identifier for virtual host

I've been running chronyd for some time in a number of environments without any noticeable issues. I do think the clock on the hosts seems to be a bit more stable, but not something that is overly remarkable one way or the other. I'd have no problem with the change.

It exists:
https://phabricator.vyos.net/T1585

I put a request on this up top. We'll get to it eventually, but I was hoping we could put it like this:

Can you add this commands

This still needs to be integrated into check-qemu-install before PR:
https://github.com/vyos/vyos-1x/compare/current...jestabro:vyos-configtest

PR for crux https://github.com/vyos/vyos-1x/pull/582

Update from VyOS 1.3-rolling-202010210152 to latest rolling vyos-1.3-rolling-202010260327-amd64.iso Failed.

Proposed CLI

set system options disable-spectre

Updated PR with section "parameters"
https://github.com/vyos/vyos-1x/pull/580

Once this task is solved, QoS documentation should include a subsection about NAT, explaining the procedure for both outbound and inbound traffic.

Limit can and should be lifted. I have also some Mellanox or Myricom cards with an MTU up to 16k

All of ours do as far as I know, which includes 10,40, and 100g. I'm pretty sure 2.5g and 5g will as well.

Don't some 10G/40G/100G gear support some megajumbo frame sizes now as well? Not sure about the 2.5/5G stuff though...

Thanks - hopefully T2994 will catch all this stuff! Please be patient, I'm currently in the testing phase.

/usr/lib/python3/dist-packages/vyos/ifconfig/ tunnel.py The corresponding file is in https://github.com/vyos/vyos-1x/blob/current/python/vyos/ifconfig/tunnel.py

Hello,
This is working as "ip link add tun0 type gretap local x.x.x.x remote y.y.y.y ttl z" in linux.

Have you ever tested it?

hello,
Just modify the line 182 of file /usr/lib/python3/dist-packages/vyos/ifconfig/tunnel.py
from

options = ['local', 'remote', ]

to

options = ['local', 'remote', 'ttl', ]

Hi @jingyun, can you share how you added it to your local installation?

Hi @drac, good catch and nice reverse engineering of our code.

Driver will be included in next rolling ISO