Yes, thanks, c-po; the revised settings (above) are consistent with defaults and behaviour for both crux and equuleus.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jan 16 2020
As I recently rewrote this part in XML/Python please also check the default values in the Python script
Jan 15 2020
I will backport this, unless objections ...
For consistency with the relative sizes set by CLI in the conf_mode script (system-ip.py), the default params should be:
The size of an ARP cache entry is 384 bytes (x86-64), so the change will add ~720k -- ~3 MiB, which seems reasonable. I will add the suggested settings to sysctl defaults.
Jan 13 2020
In FRR 7.0.1 (VyOS 1.2.3) was some bug, due to which static routes were not updated (maybe, not in all cases or environments) after the next-hop state change. In VyOS 1.2.4 we use stable FRR 7.2, which processes this situation without problems. An example (key point from FRR debug log):
FRR 7.0.1:
Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.0/30: Adding route rn 0x5612ea69d1f0, re 0x5612ea69d370 (type 2) Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.0/30: Redist update re 0x5612ea69d370 (type 2), old (nil) (type -1) Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.0/30: Adding route rn 0x5612ea69d490, re 0x5612ea69e110 (type 2) Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.0/30: Redist update re 0x5612ea69e110 (type 2), old (nil) (type -1) Jan 13 15:29:51 vyos zebra[1041]: NHT processing check for zvrf default Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.1/32: Evaluate RNH, type 0 Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.1/32: NH resolved over route 10.230.230.0/30 Jan 13 15:29:51 vyos zebra[1041]: 0:10.230.230.1/32: Notifying client static about NH Jan 13 15:29:51 vyos zebra[1041]: 0:192.168.20.1/32: Evaluate RNH, type 0
FRR 7.2:
Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.0/30: Adding route rn 0x5574620a18b0, re 0x5574620a1930 (connected) Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.0/30: Adding route rn 0x5574620a29b0, re 0x5574620a1850 (connected) Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.0/30 update_from_ctx(): no fib nhg Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.0/30 update_from_ctx(): rib nhg matched, changed 'true' Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.0/30: Redist update re 0x5574620a1930 (connected), old 0x0 (None) Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.1/32: Evaluate RNH, type Nexthop Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.1/32: NH resolved over route 10.230.230.0/30 Jan 13 15:33:23 vyos zebra[1042]: 0:10.230.230.1/32: Notifying client static about NH Jan 13 15:33:23 vyos zebra[1042]: rib_add_multipath: 0:10.0.0.0/8: Inserting route rn 0x5574620a1b10, re 0x5574620a1a30 (static) existing (nil) Jan 13 15:33:23 vyos zebra[1042]: 0:10.0.0.0/8: Adding route rn 0x5574620a1b10, re 0x5574620a1a30 (static) Jan 13 15:33:23 vyos zebra[1042]: netlink_route_multipath(): RTM_NEWROUTE 10.0.0.0/8 vrf 0(254) Jan 13 15:33:23 vyos zebra[1042]: netlink_route_multipath() (single-path): nexthop via 10.230.230.1 if 3(0) Jan 13 15:33:23 vyos zebra[1042]: netlink_talk: netlink-dp (NS 0) type RTM_NEWROUTE(24), len=60 seq=10 flags 0x501 Jan 13 15:33:23 vyos zebra[1042]: 0:10.0.0.0/8 update_from_ctx(): no fib nhg Jan 13 15:33:23 vyos zebra[1042]: 0:10.0.0.0/8 update_from_ctx(): rib nhg matched, changed 'true' Jan 13 15:33:23 vyos zebra[1042]: 0:10.0.0.0/8: Redist update re 0x5574620a1a30 (static), old 0x0 (None)
So, configured static routes updating properly.
Jan 9 2020
Created new Azure image
Jan 8 2020
Jan 7 2020
Seems to be a simple fix so i've submitted a PR: https://github.com/vyos/vyos-1x/pull/199
Jan 6 2020
In 1.3 default-route 'force' works as expected, for 1.2.x (crux) we need merge patch which was proposed by @hagbard
Hi @rherold , I can't create this behaviour in LAB.
I have clear vyos-1.2.3 installed and do next steps:
- sudo nano /config/scripts/vyos-postconfig-bootup.script
#!/bin/sh # This script is executed at boot time after VyOS configuration is fully applie$ # Any modifications required to work around unfixed bugs # or use services not available through the VyOS CLI system can be placed here. /config/scripts/rcs/rcs-mgnt-vlan.sh 2>/dev/null 1>/dev/null
- sudo mkdir /config/scripts/rcs/
- Create file sudo nano /config/scripts/rcs/rcs-mgnt-vlan.sh with following commands
#!/bin/bashTested successfully on VyOS 1.3-rolling-202001060217
Jan 5 2020
Jan 4 2020
Jan 3 2020
Jan 2 2020
Jan 1 2020
As this is on the new XML Python interface this is not a problem in crux
We have this feature on our documentation, but not in stable release 1.2.3/1.2.4
https://docs.vyos.io/en/crux/services/pppoe-server.html#radius-based-shaper-setup
Dec 31 2019
With this patch we have binded IRQ for each core
vyos@vyos:~$ cat /proc/interrupts | grep vif0 31: 4 31761 0 0 xen-dyn -event vif0-q0-tx 32: 30389 0 0 0 xen-dyn -event vif0-q0-rx 33: 1 0 0 20496 xen-dyn -event vif0-q1-tx 34: 1 0 18741 0 xen-dyn -event vif0-q1-rx 35: 3 21115 0 0 xen-dyn -event vif0-q2-tx 36: 45095 0 0 0 xen-dyn -event vif0-q2-rx 37: 2 0 0 32254 xen-dyn -event vif0-q3-tx 38: 2 0 19594 0 xen-dyn -event vif0-q3-rx
Dec 30 2019
Tested successfully
Dec 29 2019
For rolling we need add small fix to opennhtp.init
https://github.com/vyos/vyos-nhrp/pull/3
Dec 28 2019
set system ipv6 disable can be used to globally disable IPv6 address assignment
I agree this should be killed.