@Viacheslav can you see what auth modes supported by keepalive
also I think we don't need to configure both
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Feb 22 2023
Feb 21 2023
Builds completing. ISO worker on Jenkins should be fixed and pushing new rolling images shortly.
Also bug with ifb interface
vyos@r14# set interfaces input ifb0 [edit] vyos@r14# set interfaces ethernet eth0 redirect 'ifb0'
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
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.
Feb 20 2023
Same problem here, on 1.3:
PR for 1.3 https://github.com/vyos/vyos-1x/pull/1833
Feb 19 2023
@c-po confirmed fixed, thank you.
Feb 18 2023
A 2nd proposal could be:
When internal hosts are behind NAT, this is working as expected, because of conntrack.
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
Feb 17 2023
I cannot attach the rest of the artifacts due to size limits.
Publishing them on git instead: https://github.com/volodymyrhuti/QPPB_docs
========================================================================================================= The QoS Policy Propagation via BGP feature allows you to classify packets by IP precedence based on the Border Gateway Protocol (BGP) community lists, BGP autonomous system paths, access lists, thus helping to classify based on the destination instead of source address.
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...