I put a request on this up top. We'll get to it eventually, but I was hoping we could put it like this:
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Oct 26 2020
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...
Oct 25 2020
Thanks - hopefully T2994 will catch all this stuff! Please be patient, I'm currently in the testing phase.
Oct 24 2020
/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
Oct 23 2020
The latest driver also includes a fix for link flapping, which is the issue we are experiencing.
Oct 22 2020
Besides the command proposal there is a common issue with how we build op-mode commands. The best example is the ping op-mode command where and artifical node.tag folder is created which links (ln -s) back to itself.
The current NTP config always binds to localhost and localhost is not a part of the mgmt VRF thus this error message.
It looks good, I want to ask how other people in the community think about this?
- If the user configures his cluster as a "pool" or a bunch of "server" they should work fine, he can also "allow" them to connect to him if he wishes. I would recommend connecting to a good pool myself, or a low stratum device hosted locally, instead of making some kind of cluster.
- https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-users/2016/03/msg00001.html
Does anyone understand the meaning of these performance data? I don’t know the unit of these data
- 1. When the user's data source uses NTP cluster, whether switching to the new service may lead to the compatibility problem of NTP cluster network
Yes, absolutely, and if you visit the link in the post you'll see a comparison of them, and at the bottom is some explanation.
Can chronyd completely replace NTP?
Вячеслав @Viacheslav, я не понял вопроса...
В шапке таска лежит рабочий патч
Tested creation on both server and client.
OpenVPN conf file is contains the key-direction
Server and client can connect correctly.