- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Today
It is impossible to set several addresses, but it is possible 0.0.0.0
Limits of the accel-ppp
looks good for VyOS 1.5-rolling-202404260019 and VyOS 1.4-stable-202404120309
vyos@r4# set system config-management commit-archive location scp://vyos:[email protected]/tmp/ vyos@r4# [edit] vyos@r4# commit Archiving config... scp://192.168.255.11/tmp/ Unable to upload "scp://vyos:[email protected]/tmp//config.boot-r4.vyos.local.20240426_153518": [Errno 101] Network is unreachable run-parts: /etc/commit/post-hooks.d/02vyos-commit-archive exited with return code 1 [edit] vyos@r4#
It looks working on VyOS 1.5-rolling-202404260019
set system domain-name 'vyos.local' set system host-name 'r4' set system static-host-mapping host-name r4.vyos.local inet '100.64.0.14'
In T6258#185013, @Apachez wrote:Im thinking since sysctl can be changed after the system have completed its boot shouldnt the "system sysctl" be runned among the last tasks according to "/usr/libexec/vyos/priority.py", which would also fix this issue ?
Yesterday
@Apachez, there is no easy way to fix anything related to sysctl, until one component depends on another.
Especially, for example, if we have to deal with "dynamic" interfaces.
Globally, this task is still open and could contain subtasks.
Thanks!
In T6266#184977, @sarthurdev wrote:Possibly would make sense for CLI to fall under firewall global-options?
Stay tuned; check our blog post.
Allowing only ethernet interface task https://vyos.dev/T6265
After adding check, this task can be closed
Will be available in the next rolling release.
The group is reserved
r4(config)# interface eth2 r4(config-if)# ip igmp join 224.0.0.0 224.0.0.10 % Configuration failed.
PR https://github.com/vyos/vyos-1x/pull/3361
vyos@r4# set interfaces ethernet eth2 ipv6 base-reachable-time 28 [edit] vyos@r4# commit [edit] vyos@r4# [edit] vyos@r4# sudo sysctl net.ipv6.neigh.eth2.base_reachable_time_ms net.ipv6.neigh.eth2.base_reachable_time_ms = 28000 [edit] vyos@r4# vyos@r4# cat /proc/sys/net/ipv6/neigh/eth2/base_reachable_time_ms 28000 [edit] vyos@r4#
In T6258#184876, @canoziia wrote:
This sysctl option is deprecated
DEPRECATED PARAMETERS top
Wed, Apr 24
Close it as wontfix due to legacy backend.
In some cases, we can't predict the interface name (if the interface name is over 15 characters) https://vyos.dev/T6222
@sempervictus Any updates or additional context?
Fixed, VyOS 1.5-rolling-202404240023
vyos@r4# run show conf com | match "bri|tun0" set interfaces bridge br0 member interface tun0 set interfaces tunnel tun0 encapsulation 'gretap' set interfaces tunnel tun0 remote '192.168.122.111' set interfaces tunnel tun0 source-address '192.168.122.14' [edit] vyos@r4# delete interfaces tunnel [edit] vyos@r4# commit [ interfaces tunnel tun0 ] Interface "tun0" cannot be deleted as it is a member of bridge "br0"!
Tue, Apr 23
Not actual for 1.5/1.4
@mrlocke Can you re-check the 1.3?
@doctorpangloss Any updates?
@modzilla99 Could you provide an example of set commands to reproduce?
What happens if another value occupies the index?
For example, PPPoE-server and PPP interface can generate thousands of interfaces
It was filtered in https://vyos.dev/T2086 to avoid pam_unix mess
Can't reproduce it, close the task
Most likely needs to change priority to 319 for the sysctl
vyos@r4:~$ /usr/libexec/vyos/priority.py | match "ethernet|sysctl"
300 interfaces_virtual-ethernet.py ['interfaces', 'virtual-ethernet']
318 interfaces_ethernet.py ['interfaces', 'ethernet']
318 system_sysctl.py ['system', 'sysctl']
321 interfaces_pseudo-ethernet.py ['interfaces', 'pseudo-ethernet']
vyos@r4:~$Extend to <1-65535>
PR https://github.com/vyos/vyos-1x/pull/3353
What do I need to do to get these values?
root@r1-right:/home/vyos# sysctl net.ipv6.neigh.eth3/2.base_reachable_time_ms sysctl: cannot stat /proc/sys/net/ipv6/neigh/eth3.2/base_reachable_time_ms: No such file or directory
Mon, Apr 22
Could you provide the full set of commands to reproduce?
I tried to extend the range, and seems it also relies on nftables conntrack zones
vyos@r4# compare
+ vrf {
+ name blue {
+ table "4294967295"
+ }
+ name red {
+ table "1"
+ }
+ }Sun, Apr 21
The flowtable has to be set on ethernet interfaces only!
It does not need to set it to PPP/BOND/VLAN/etc, as it will work anyway.
We need to hardcode it only for ethX interfaces, because people use it incorrect.
Sat, Apr 20
Fri, Apr 19
Thu, Apr 18
Test addresses have to be different
Provide the set of the commands to reproduce