- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Dec 1 2020
Nov 30 2020
PR with changed types in docs https://github.com/vyos/vyos-documentation/pull/380
ESP transport mode works properly on Cisco Router and VyOS routers together.
DMVPN Spokes work properly behind a NAT if we use transport mode instead of tunnel. e.g.
set vpn ipsec esp-group ESP-HUB mode transport
So I think we need to add this info to docs.vyos.io and close this Feature Request
Nov 27 2020
Following this issue request https://sourceforge.net/p/opennhrp/support-requests/3/ we need to use transport mode instead of a tunnel. Was tested on AWS node and it looks working even with selector remote_ts = dynamic[gre]
Nov 25 2020
Let's run pimd only if IGMP or PIM configured.
https://github.com/vyos/vyos-1x/pull/618
https://github.com/vyos/vyos-build/pull/134
Nov 13 2020
How about these changes https://github.com/vyos/vyos-1x/blob/current/src/op_mode/powerctrl.py#L37
diff --git a/src/op_mode/powerctrl.py b/src/op_mode/powerctrl.py index 69af427e..c000d7d0 100755 --- a/src/op_mode/powerctrl.py +++ b/src/op_mode/powerctrl.py @@ -34,7 +34,11 @@ def utc2local(datetime): def parse_time(s): try: if re.match(r'^\d{1,2}$', s): - return datetime.strptime(s, "%M").time() + if (int(s) > 59): + s = str(int(s)//60) + ":" + str(int(s)%60) + return datetime.strptime(s, "%H:%M").time() + else: + return datetime.strptime(s, "%M").time() else: return datetime.strptime(s, "%H:%M").time() except ValueError:
It looks like need to do some calculation
vyos@vyos:~$ show version | match Version Version: VyOS 1.3-rolling-202011130217 vyos@vyos:~$ show date Fri 13 Nov 2020 07:18:44 AM UTC vyos@vyos:~$ reboot in 60 Invalid time "60". The valid format is HH:MM vyos@vyos:~$ reboot in 59 Reboot is scheduled 2020-11-13 08:18:04 vyos@vyos:~$ reboot in 61 Invalid time "61". The valid format is HH:MM
Tested on 1.3-rolling-202011130217, all works as expected.
Thanks to @ernstjo
Nov 11 2020
Nov 6 2020
Nov 2 2020
PR https://github.com/vyos/vyos-1x/pull/590
I hope it will be helpful for many people from France. As for me it better solution then glue stickers with QWERTY keys =)
Ok, let's review the situation when you install VyOS on bare metal and you have an only AZERTY keyboard. You press key A but in console, you see Q, you press Z on the console you see W.
Debian way, install console-data from https://packages.debian.org/sid/console-data and run sudo loadkeys fr
Oct 28 2020
Oct 22 2020
Oct 21 2020
@Viacheslav if we set acct-port=0 it should to disable accounting.
[radius] server=x.x.x.x,secret,auth-port=1812,acct-port=0
Oct 20 2020
Oct 19 2020
It looks like this works, but when we don't have any connected user, it listed the current directory file
vyos@RTR1:~$ touch 1.txt vyos@RTR1:~$ reset vpn remote-access user <tab> Possible completions: 1.txt Terminate specified user's current remote access VPN session(s)
After a user connected, all works properly
vyos@RTR1:~$ reset vpn remote-access user <tab> Possible completions: test1 Terminate specified user's current remote access VPN session(s)
Oct 17 2020
Oct 16 2020
Oct 15 2020
Yes, both clients configured as DHCP clients.
Client 1 - eth0 - 50:00:00:06:00:00
Client 2 - eth0 - 50:00:00:07:00:00
Oct 14 2020
Oct 13 2020
PR for CRUX https://github.com/vyos/vyos-1x/pull/568
PR with increasing validator values https://github.com/vyos/vyos-1x/pull/566
Oct 11 2020
@c-po , it looks like the wrong CLI definition, we can increase the limit in XML.
Oct 8 2020
Oct 7 2020
Oct 2 2020
Note: New xl2tpd package does not work with the followings params in options.xl2tpd
crtscts lock
Sep 30 2020
PR https://github.com/vyos/vyos-build/pull/127
Also will be good cherrypick this to crux.
Sep 29 2020
Works properly, tested on 1.3-rolling-202009290117.
One remark, jitter will be applied for all accounting packet except the first packet. The first packet is a flag that the session is started.
Works properly on VyOS 1.3-rolling-202009290117.
When command set service pppoe-server authentication radius preallocate-vif committed, pppoe-server send the next attributes in Access-Request packet on a client authorization:
NAS-Port = 0 NAS-Port-Id = "ppp0" NAS-Port-Type = Virtual
Successfully tested on 1.3-rolling-202009290117
set service pppoe-server authentication radius called-sid-format 'ifname:mac'
Radius recived Called-Station-Id = "eth1:50:00:00:05:00:01"
set service pppoe-server authentication radius called-sid-format 'ifname'
Radius recived Called-Station-Id = "eth1"
By default radius recive Called-Station-Id = "50:00:00:05:00:01"
Sep 28 2020
Sep 24 2020
Sep 23 2020
Sep 18 2020
Marked as resolved
Sep 17 2020
Thanks, let's merge it only after 1.2.6 release
Can we add this implementation for crux in the old style?
https://github.com/DmitriyEshenko/vyatta-cfg-system/commit/0adc41a62b6d532da7c4b47cb5da920d1ed39664
Sep 16 2020
Sep 14 2020
Sep 11 2020
@c-po , the same behavior even with kernel 5.8.8
vyos@R1:~$ uname -a Linux R1 5.8.8-amd64-vyos #1 SMP Thu Sep 10 08:58:42 UTC 2020 x86_64 GNU/Linux
Sep 9 2020
How about migrating this iptables rule from mangle to filter?
New PR for fixing it https://github.com/vyos/vyos-1x/pull/541
As discussed in the maintainer's slack channel will be good to replace CLI commands from set vpn anyconnect to set vpn openconnect. But in our docs we should use anyconnect-compatible server.
Sep 8 2020
PR from @ronie https://github.com/vyos/vyos-documentation/pull/317
Sep 7 2020
Intel QAT works for CRUX brunch. As for rolling with the newest kernel 5.8.5, it seems some issues on the modules building stage.
Sep 6 2020
@c-po I build qat manually but add --enable-qat-lkcf to https://github.com/vyos/vyos-build/blob/crux/packages/linux-kernel/build-intel-qat.sh#L55 and it seems it works
vyos@R2-QAT:~$ show system acceleration qat device qat_dev0 flows +------------------------------------------------+ | FW Statistics for Qat Device | +------------------------------------------------+ | Firmware Requests [AE 0]: 147225 | | Firmware Responses[AE 0]: 147225 | +------------------------------------------------+ | Firmware Requests [AE 1]: 113758 | | Firmware Responses[AE 1]: 113758 | +------------------------------------------------+ | Firmware Requests [AE 2]: 144886 | | Firmware Responses[AE 2]: 144886 | +------------------------------------------------+ | Firmware Requests [AE 3]: 147221 | | Firmware Responses[AE 3]: 147221 | +------------------------------------------------+ | Firmware Requests [AE 4]: 113774 | | Firmware Responses[AE 4]: 113774 | +------------------------------------------------+ | Firmware Requests [AE 5]: 144891 | | Firmware Responses[AE 5]: 144891 | +------------------------------------------------+
Tested on 1.3-rolling-202009060846
Sep 3 2020
Sep 2 2020
Sep 1 2020
@maznu but it seems really odd behavior, I mean message settled in 121 sec. failed!
121 sec - equal to 121 interfaces when the router is first booted. But if in config already present hw-id, it should be faster then 0 sec.
Will be interesting to reproduce this in our lab. Also will be helpful if you provide sudo dmesg output.
Aug 31 2020
Hello @marekm, I think [ppp]unit-cache=n might help in this case, but the main issue in FRR. Do you want a package for the test with these improvements?
unit-cache=n By default is disabled: unit-cache=0
Aug 30 2020
I tested this in LAB and it seems works properly. Changing interface name for eth1 and eth2
vyos@vyos# delete interfaces ethernet eth1 hw-id [edit] vyos@vyos# delete interfaces ethernet eth2 hw-id [edit] vyos@vyos# set interfaces ethernet eth1 hw-id 50:01:00:02:00:02 [edit] vyos@vyos# set interfaces ethernet eth2 hw-id 50:01:00:02:00:01 [edit] vyos@vyos# commit [edit] vyos@vyos# save Saving configuration to '/config/config.boot'... Done [edit] vyos@vyos# run reboot now
After reboot
vyos@vyos:~$ sudo ethtool -P eth1 Permanent address: 50:01:00:02:00:02 vyos@vyos:~$ sudo ethtool -P eth2 Permanent address: 50:01:00:02:00:01
@maznu , can you provide next:
show configuration commands | match hw-id sudo cat /run/udev/log/vyatta-net-name.coldplug
Aug 26 2020
Aug 23 2020
Jenkins output build ID 1015
16:14:06 DEBUG - Running Testcase: /usr/libexec/vyos/tests/smoke/cli/test_vpn_anyconnect.py 16:14:18 DEBUG - . 16:14:18 DEBUG - ---------------------------------------------------------------------- 16:14:18 DEBUG - Ran 1 test in 11.085s 16:14:18 DEBUG - 16:14:18 DEBUG - OK
Works properly, tested on 1.3-rolling-202008231246
Aug 20 2020
Aug 19 2020
This happens only when in config before migration exists nodes system 'ntp' without other params.
Works as expected on VyOS 1.3-rolling-202008190118