Yes @syncer . One option is for source and other for destination.

PR https://github.com/vyos/vyos-build/pull/312

PR: https://github.com/vyos/vyos-1x/pull/1840

@Viacheslav can you see what auth modes supported by keepalive
also I think we don't need to configure both

Builds completing. ISO worker on Jenkins should be fixed and pushing new rolling images shortly.

Thanks @Viacheslav https://github.com/vyos/vyos-1x/pull/1838 fixed it for me.

Cherry-pick for 1.3.3 https://github.com/vyos/vyos-1x/pull/1838

PR https://github.com/vyos/vyos-1x/pull/1837

it's fixed already in vyos/vyos-build#293 (although in a different way), just downloaded the newest image and tested it. I'm closing this ticket, apologies for the noise.

The thing is we have default values (for example memory) only for the first container:

##################################################
{'name': {'multitool': {'description': 'Network multitool container',
                        'image': 'wbitt/network-multitool:fedora',
                        'memory': '512',
                        'network': {'cntr-net': {}},
                        'port': {'http': {'destination': '80',
                                          'protocol': 'tcp',
                                          'source': '80'}},
                        'restart': 'on-failure',
                        'shared_memory': '64'},
          'nrpe': {'allow_host_networks': {},
                   'image': 'incitem/almalinux9:nrpe',
                   'protocol': 'tcp'},
          'radius': {'allow_host_networks': {},
                     'image': 'dchidell/radius-web',
                     'protocol': 'tcp',
                     'volume': {'clients': {'destination': '/etc/raddb/clients.conf',
                                            'mode': 'rw',
                                            'source': '/config/containers/radius/clients'},
                                'users': {'destination': '/etc/raddb/users',
                                          'mode': 'rw',
                                          'source': '/config/containers/radius/users'}}}},
 'network': {'cntr-net': {'description': 'VyOS Container Network',
                          'prefix': ['172.253.253.0/24']}},
 'registry': ['docker.io', 'quay.io']}
##################################################

@Viacheslav Its working fine on latest vyos image. Thanks for support.

https://github.com/vyos/vyos-1x/pull/1836

PR https://github.com/vyos/vyos-1x/pull/1835

PR for 1.3 https://github.com/vyos/vyos-1x/pull/1833

A 2nd proposal could be:

PR https://github.com/vyos/vyos-1x/pull/1830

When internal hosts are behind NAT, this is working as expected, because of conntrack.

PR https://github.com/vyos/vyos-1x/pull/1829

Without a hash, it can be useless.
For example, the client initiates a TCP session:

• SYN is forwarded from the client to 10.0.0.7
• 10.0.0.7 responds with SYN/ACK to the client
• client sends ACK, which is forwarded to 10.0.0.2

PR: https://github.com/vyos/vyos-1x/pull/1828

I cannot attach the rest of the artifacts due to size limits.
Publishing them on git instead: https://github.com/volodymyrhuti/QPPB_docs

PR https://github.com/vyos/vyos-1x/pull/1827

set service pppoe-server authentication mode 'noauth'
set service pppoe-server client-ip-pool name foo gateway-address '192.0.2.1'
set service pppoe-server client-ip-pool name foo subnet '192.0.2.0/24'
set service pppoe-server interface eth1

Check

vyos@r14# cat /run/accel-pppd/pppoe.conf | grep "\[auth" -A 2
[auth]
noauth=1

Thanks for clarification @b-

This isn’t specific to WANs at all, no! I am using it for a WAN, so some of my comments reflect that, but really this is just a generic hook for any DHCP interface.

@b- Im not sure 100% sure whats happening, as I am not a developer... I saw your code samples and PR in git...

PRs:
1.3 - https://github.com/vyos/vyos-cloud-init/pull/62
1.4 - https://github.com/vyos/vyos-cloud-init/pull/61

@mas90 Will be present in the next rolling release.
Could you check when it will available? After 20230215

PR https://github.com/vyos/vyos-1x/pull/1825

set system option keyboard-layout uk

Excellent! I'll check it out and report back. Thank you!

@ammmze That PR is merged, so will be in the next rolling. Kindly let me know of any remaining or other issues you see. I'll add autocannon to my common tests; thanks again for that tip.

PR:
https://github.com/vyos/vyos-1x/pull/1823

Fix
PR 1.4 https://github.com/vyos/vyos-1x/pull/1822
PR 1.3 https://github.com/vyos/vyos-1x/pull/1824

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

set protocols bgp address-family l2vpn-evpn vni 100070 route-target both 70:100070

Should return an error, as this is not implemented.

I was wrong. NOT 6 CHILSD_SAs on one tunnel.
6 IKE SAs on one configured tunnel.

I met 2 issues after the last commit.
My config:

Awesome, I am glad to hear the provided info was helpful! Thank you for the quick investigation and explanation.