PR https://github.com/vyos/vyos-user-utils/pull/7
vyos@r4# echo '{"system": "VyOS", "rate": 100}' | jq '.system'
"VyOS"
[edit]
vyos@r4#PR https://github.com/vyos/vyos-user-utils/pull/7
vyos@r4# echo '{"system": "VyOS", "rate": 100}' | jq '.system'
"VyOS"
[edit]
vyos@r4#PR for VyOS 1.5 https://github.com/vyos/vyos-1x/pull/2335
PR for 1.3.5 https://github.com/vyos/vyos-1x/pull/2333
The easiest way is to add a Patch for FRR 7.5.1 if possible.
We can't migrate to FRR 9.1 for 1.3.x
PR for 1.3 https://github.com/vyos/vyos-1x/pull/2310
In T5586#160073, @Apachez wrote:How does FRR/vrrpd work regarding SNMP compatability?
Im thinking if the keepalived could be replaced in favour of FRR/vrrpd?
And for now keep keepalived around only for virtual-server (unless that too can be dealt with by FRR/vrrpd)?
Ok, I was thinking if that then waited for some password or such.
I haven't tried anything else since I rebooted back into 1.4, but I did try sudo su - which gave the same error.
How does a simple "sudo bash" work?
I think this broke a whole lot of things for RADIUS users (these work fine in 1.4-rolling-202308040317, but are broken in 1.5-rolling-202309170024):
How does FRR/vrrpd work regarding SNMP compatability?
PR created: https://github.com/vyos/vyos-1x/pull/2264
Should probably add "-M rpki" permanently to FRR/bgp.
Could the error from latest nightly be due to that rpki module isnt loaded for FRR/bgp?
Could https://vyos.dev/T2044 be related to the failed nightly build from last night?
PR for 1.3.x https://github.com/vyos/vyatta-cfg-quagga/pull/102
PR for the current https://github.com/vyos/vyos-1x/pull/2252
PR for 1.3.x https://github.com/vyos/vyos-1x/pull/2225
For 1.4 add session [default=ignore success=2] pam_succeed_if.so service = sudo to /etc/pam.d/common-session-noninteractive fixes the issue
# here are the per-package modules (the "Primary" block) session [default=1] pam_permit.so # here's the fallback if no module succeeds session requisite pam_deny.so # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around session required pam_permit.so # and here are more per-package modules (the "Additional" block) session required pam_mkhomedir.so umask=0022 skel=/etc/skel session [default=ignore success=2] pam_succeed_if.so service = sudo session [default=ignore success=ignore] pam_succeed_if.so user ingroup aaa quiet session [authinfo_unavail=ignore success=ok default=ignore] pam_radius_auth.so session required pam_unix.so # end of pam-auth-update config
A workaround was provided in T5428 for the specific issue.
Should be executed there, for future debugs https://github.com/vyos/vyatta-wanloadbalance/blob/c7708bc6ef689f5744272a15a601a56a03890afa/src/lbdecision.cc#L429
Just waiting for upstream updates
Any updates to this?
At the moment of applying vrrp configuration eth1 IPv6 address
inet6 2001:db8::3/125 scope global tentative
Then
inet6 2001:db8::3/125 scope global
PR for 1.3 https://github.com/vyos/vyos-1x/pull/2191
Thanks for the follow-up @eyanulis!
Just use /usr/bin/accel-cmd -p 2001 pppoe interface add "xxx"
Still bug
vyos@r1# set service webproxy
Possible completions:
append-domain
Default domain name
> authentication
Proxy Authentication Settings
+> cache-peer Specify other caches in a hierarchy
cache-size Disk cache size in MB (default: 100)
default-port Default Proxy Port (default: 3128)
disable-access-log
Disable logging of HTTP accesses
+ domain-block Domain name to block
+ domain-noncache
Domain name to access without caching
+> listen-address
IPv4 listen-address for WebProxy [REQUIRED]
maximum-object-size
Maximum size of object to be stored in cache in kilobytes
mem-cache-size
Memory cache size in MB
minimum-object-size
Maximum size of object to be stored in cache in kilobytes
outgoing-address
Outgoing IP address for webproxy
+ reply-block-mime
MIME type to block
reply-body-max-size
Maximum reply body size in KB
> url-filtering
URL filtering settingsCherry-pick for 1.3.4 https://github.com/vyos/vyos-1x/pull/2187
It cannot reproduce in the current 1.3 VyOS 1.3-stable-202308240442
vyos@r1:~$ sudo sysctl -a | grep send_redire net.ipv4.conf.all.send_redirects = 1 net.ipv4.conf.default.send_redirects = 0 net.ipv4.conf.dum0.send_redirects = 0 net.ipv4.conf.eth0.send_redirects = 0 net.ipv4.conf.eth1.send_redirects = 0 net.ipv4.conf.eth2.send_redirects = 0 net.ipv4.conf.eth3.send_redirects = 0 net.ipv4.conf.eth4.send_redirects = 0 net.ipv4.conf.eth5.send_redirects = 0 net.ipv4.conf.eth6.send_redirects = 0 net.ipv4.conf.lo.send_redirects = 1 vyos@r1:~$ vyos@r1:~$ vyos@r1:~$ reboot now
It could be added the same way https://github.com/vyos/vyatta-cfg-quagga/commit/db2f0bbeb375e0d568ef4740bad2b50690cd8644 (if required)
If not, just close it. Already have in 1.4
We won't extend the old Perl code anymore (for 1.3.x) https://github.com/vyos/vyatta-cfg-qos/pull/19
Implemented for 1.4
Provide some logs and examples of configuration.
Do you use SNMP?
PR for 1.3.4 https://github.com/vyos/vyatta-cfg-quagga/pull/101
@dsummers Could you re-check? Should be fixed in https://github.com/PowerDNS/pdns/pull/12203
We didn't get the requested information.
Reopen it if it is required with steps to reproduce and some output.