PR https://github.com/vyos/vyos-1x/pull/1825
set system option keyboard-layout uk
PR https://github.com/vyos/vyos-1x/pull/1825
set system option keyboard-layout uk
In T4971#142523, @fernandolcx wrote:service { + pppoe-server { + authentication { + mode radius + radius { + server 172.31.255.2 { + key 123456 + } + } + } + interface eth1 { + } + } }when I commit, throws me:
Traceback (most recent call last): File "/usr/libexec/vyos/conf_mode/service_pppoe-server.py", line 114, in <module> verify(c) File "/usr/libexec/vyos/conf_mode/service_pppoe-server.py", line 60, in verify verify_accel_ppp_base_service(pppoe) File "/usr/lib/python3/dist-packages/vyos/configverify.py", line 424, in verify_accel_ppp_base_service for _, v in config['client_ip_pool']['name'].items(): KeyError: 'client_ip_pool'
Some debugging, the authentication with user vyosunpriv
Don't see any issue with 1.3
vyos@r1:~$ monitor bandwidth-test initiate 192.168.122.14 ------------------------------------------------------------ Client connecting to 192.168.122.14, TCP port 5001 TCP window size: 85.0 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.122.11 port 58042 connected with 192.168.122.14 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 6.37 GBytes 5.47 Gbits/sec vyos@r1:~$ vyos@r1:~$ show version
PR for 1.3 https://github.com/vyos/vyos-1x/pull/1813
PR for 1.3 https://github.com/vyos/vyos-1x/pull/1812
Take a look at this T4165
Maybe the same issue but per rule. Different order of "comment"
Thanks for reporting.
We will take a look at it.
eth0 -> PPPoE (Primary link)
eth1 -> DHCP (Backup link)if I use default-route 'auto' for pppoe then default route via pppoe is not getting configured. That's why I am defining the static default route for pppoe with default-route 'none' option.
@fernandolcx Will be present in the next rolling release, could you test it (after 20230209)?
@c-po Do you have any idea for CLI?
@skoenman Could you write some examples of configuration?
@Usman there is a root task for op-mode rewriting https://phabricator.vyos.net/T4564
https://github.com/vyos/vyos-1x/blob/1042fc32c371a74f048ffaf9a551b5d13c227f45/src/op_mode/bgp.py#L77-L80
@Usman You have to update to the latest rolling.
https://vyos.net/get/nightly-builds/
Hi perhaps it is better to get JSON format
Why did you delete this option and add a static route? Is there any use case?
This option has more priority than others.
Rewritten in 1.4
We are not planning to modify it in 1.3
Got it; it is impossible for now after this migration https://phabricator.vyos.net/T3090
We are working on the re-design firewall CLI
Setting it configurable will be a good solution.
Just like it is done in OpenVPN
vyos@r14# set interfaces openvpn vtun0 tls tls-version-min Possible completions: 1.0 TLS v1.0 1.1 TLS v1.1 1.2 TLS v1.2 1.3 TLS v1.3
@daniil Could you update the PR?
Could you send the full accel-ppp working configuration that you expect?
@Jimz Show please the file cat /config/dhcpd.leases
I cannot reproduce it even if no any leases
vyos@r14:~$ show dhcp server leases IP Address MAC address State Lease start Lease expiration Remaining Pool Hostname ------------ ------------- ------- ------------- ------------------ ----------- ------ ---------- vyos@r14:~$
There are some limitations
In particular, this is a list (may not be complete) of features that are not available when using ovpn-dco:
accel-ppp doesn't support FQDN for RADIUS https://docs.accel-ppp.org/en/latest/configuration/radius.html#radius
So it is impossible until it is available in the accep-ppp