By default we don't need delay, I think it must be configurable feature.
set service pppoe-server pado-delay delay 100 sessions 100 set service pppoe-server pado-delay delay 200 sessions 300 set service pppoe-server pado-delay delay 300 sessions 1000
and configuration for this
If it possible, please explain me in private message how I can reach this behaviour. In my LAB this does not reproduced.
This patch tested successful on VyOS 1.2.4 VM with 25 network interfaces.
Also works as expected on VyOS 1.3-rolling-202001230217
Thx @runar !
PR https://github.com/vyos/vyatta-cfg-quagga/pull/40 also need add script migration
set protocols bgp 65535 neighbor 192.168.255.10 enforce-first-as
Look like FRR changes commands for this feature, now this option per neighbour.
I propose in this case use set vpn l2tp remote-access outside-address 0.0.0.0. It works in current rolling.
Works in 1.3-rolling-202001150217, propose cherry-pick in to crux.
Resolved in 1.3-rolling-202001150217
All works, but seems we need works with timezone for correct converting USEC to "date time" format
In this case we can use /run/systemd/shutdown/scheduled file for detecting powertrl scheduler
PR for this task https://github.com/vyos/vyos-1x/pull/201
https://github.com/vyos/vyos-1x/pull/200
adding CLI commands
Successfully tested on latest rolling 1.3-rolling-202001080217
PR for this task https://github.com/vyos/vyos-1x/pull/198
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:
#!/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
#!/bin/bashTested successfully on VyOS 1.3-rolling-202001060217
PR for this task https://github.com/vyos/vyatta-cfg-system/pull/116 which rename (masked) VF interface to vf_ethX
@c-po, it not possible to reproduce in 1.2.4 and 1.3 latest rolling.
I tried also delete system console on deployed 1.2.3, and it also works without issues, syslog clear.
Already in 1.2.4
@Merijn, which exactly version are you using? Provide please show version output.
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
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
Tested successfully
@kroy , Great. Thank you.
Yes, already in latest rolling. @kroy, can you check migration again?
For rolling we need add small fix to opennhtp.init
https://github.com/vyos/vyos-nhrp/pull/3
PR for this task https://github.com/vyos/vyos-1x/pull/193
@jjakob for equuleus too, wait for merge PR. We have also some ideas how we can improve net naming, and fix issues with renameX interfaces after boot.
Successfully tested on 1.3. PR for current branch https://github.com/vyos/vyatta-cfg-system/pull/113
Note: If we have interfaces with description on device panel, like WAN, DMZ, etc, we can use predefined alias in this case.
vyos@QAT-R1:~$ sudo cat /lib/udev/rules.d/64-vyos-SAF51003I-net.rules
ATTR{[dmi/id]board_name}!="SAF51003I", GOTO="end_ec_nic"PR for CRUX branch https://github.com/vyos/vyatta-cfg-system/pull/112
Works correct on 1.3-rolling-201912190503
@c-po I can't find any usable from vyatta-ravpn now, seem we can archived it and drop from build process.
Also fixed additional issue with multiple snmp script-extensions entry (jinja2 sort)
In latest rolling 1.2-rolling-201912180217 permission problem solved, but exist one more problem with script path.
CLI allow us to choice script, which stored on '/config/user-data'
@sento own build 1.2.4 this is 1.2-rolling (branch current), in crux branch all works as expected.
patch will be proposed after keepalived.service modification
https://github.com/DmitriyEshenko/vyos-1x/commit/807864242773f482aa1894ca968a4396a3507187
@c-po this is IKEv2?
can you increase log level?
Hello @trae32566 , with 1.2-rolling the same installing result?
I can't reproduce this issue on 1.2.3 and 1.2/1.3 rolling. @hagbard can you test again too?
Works as expected in VyOS 1.2-rolling and 1.3-rolling.
Hello @primoz , seems you right. left|rightnexthop deprecated in strongswan.
This parameter is usually not needed any more because the NETKEY IPsec stack does not require explicit routing entries for the traffic to be tunneled. If left|sourceip is used with IKEv1 then left|rightnexthop must still be set in order for the source routes to work properly.
And in CLI rolling l2tp implementation we need replace outside-nexthop to gw-ip-address.
In rolling this was fixed T1204, we need add this to crux.
tested successfully
@ekim seems this issue with kernel and your device. If I build custom stable kernel for VyOS installed on same device without CONFIG_PINCTRL_CHERRYVIE all works properly.
Can you show cat /pro/interrupt output for confirm this?
You can also change /boot/grub/grub.cfg add noapic and reboot device.
menuentry "VyOS 1.2.3 linux (Serial console)" {
linux /boot/1.2.3/vmlinuz boot=live noapic quiet rootdelay=5 vyos-union=/boot/1.2.3 console=tty0 console=ttyS0,9600
initrd /boot/1.2.3/initrd.img
}Can you confirm that with grub modification after reboot all works correct?
This patch successfully tested on VyOS 1.2.3
vyos@vyos# run show snmp mib ifmib
lo: ifIndex = 1
ifAlias = lo
ifDescr = lo
eth0: ifIndex = 2
ifAlias = eth0
ifDescr =
eth1: ifIndex = 3
ifAlias = eth1
ifDescr =
eth2: ifIndex = 4
ifAlias = eth2
ifDescr =
eth3: ifIndex = 5
ifAlias = eth3
ifDescr =