Verify check, PR https://github.com/vyos/vyos-1x/pull/1678
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Nov 26 2022
Nov 26 2022
Nov 25 2022
Nov 25 2022
c-po moved T4825: interfaces veth/veth-pairs -standalone used from Need Triage to Finished on the VyOS 1.4 Sagitta board.
Viacheslav changed the status of T4805: PPPoE server does not restart service if pool was changed from Open to In progress.
Viacheslav changed the status of T4804: PPPoE server incorrect unconfigured check from Open to In progress.
It must be RaiseConfigError if we delete one of the peers which related on the other veth interface
set interfaces virtual-ethernet veth0 peer-name 'veth1' set interfaces virtual-ethernet veth1 peer-name 'veth0'
I've made some tested, it seems works as we expected :
@marc_s Would you be able to open a PR against 1.3 ?
The behaviour is quite different depending on what is done. In my case another API key (not the one my application uses) should be deleted and fails, the service restarts afterwards and the config is still the same. Is there something like a hot reload missing? Also, if the API-server dies without restart (had that case several times, would have to find out, which command does that) even a change using cli did not recover the service.
Nov 24 2022
Nov 24 2022
Fixed in T4660
Viacheslav changed the status of T4612: Support arbitrary netmasks in firewall rules from Open to Needs testing.
Viacheslav changed the status of T4825: interfaces veth/veth-pairs -standalone used, a subtask of T4686: Provides support for veth, from Open to Needs testing.
Viacheslav changed the status of T4825: interfaces veth/veth-pairs -standalone used from Open to Needs testing.
nitopt added a comment to T3429: Hyper-V integration services not working on VyOS 1.4 (sagitta/current).
I have the same problem. This is a kernel configuration issue. The following settings must be made:
Nov 23 2022
Nov 23 2022
Issue not present in 1.3.2 image! Thanks
This task can be closed since the PR is merged.
roedie moved T4835: SNMPD configuration incorrect for IPv6 from Need Triage to Finished on the VyOS 1.4 Sagitta board.
roedie changed the status of T4835: SNMPD configuration incorrect for IPv6 from Open to In progress.
Viacheslav closed T4807: Need to fix traceroute help completion, a subtask of T4496: ping vrf help does not list VRFs, as Resolved.
Viacheslav changed the subtype of T4793: Create warning message about disable-route-autoinstall when ipsec vti is used from "Task" to "Feature Request".
a.apostoliuk moved T4704: Allow to set metric (MED) to rtt with rtt,+rtt or -rtt from Finished to Need Triage on the VyOS 1.4 Sagitta board.
a.apostoliuk moved T4704: Allow to set metric (MED) to rtt with rtt,+rtt or -rtt from Need Triage to Finished on the VyOS 1.4 Sagitta board.
a.apostoliuk moved T4807: Need to fix traceroute help completion from Need Triage to Finished on the VyOS 1.4 Sagitta board.
a.apostoliuk moved T4819: Allow printing Warning messages in multiple lines with \n from Need Triage to Finished on the VyOS 1.4 Sagitta board.
Viacheslav moved T4823: swanctl.conf is broken when ipsec site-to-site peer set. from Need Triage to Finished on the VyOS 1.4 Sagitta board.
Nov 22 2022
Nov 22 2022
Viacheslav changed the status of T4793: Create warning message about disable-route-autoinstall when ipsec vti is used, a subtask of T3953: IPSec with vti interfaces by default add default route to table 220, from In progress to Needs testing.
Viacheslav changed the status of T4793: Create warning message about disable-route-autoinstall when ipsec vti is used from In progress to Needs testing.
Thanks sir,
Viacheslav added a project to T4833: Include wireguard peer name in interface summary report: VyOS 1.4 Sagitta.
In T4823#138040, @chesskuo wrote:Hello sir,
In vyos-1.4-rolling-202211220318-amd64.iso, the broken syntax was fixed, but I notice a wired behavior on connection.<conn>.remote.id.
The default value on swanctl.conf will be <name> when I don't set site-to-site -> peer <name> -> authentication -> remote-id.
sarthurdev changed the status of T4834: Limit container network name to 15 characters from In progress to Needs testing.
sarthurdev changed the status of T4834: Limit container network name to 15 characters from Open to In progress.
Hello sir,
@trae32566 My apologies for the inconveniences. You are right. The criteria for triggering this action shall be narrowed down further.
It would be necessary to issue the warning if and only if such colliding peers also specify the exact same remote endpoint addresses (with empty endpoints also being accounted as to be the same).
In other words, we need to identify incoming peers and apply the rule only to them, not the outgoing ones which already have specific remote endpoint addresses statically defined.
Viacheslav changed the status of T4823: swanctl.conf is broken when ipsec site-to-site peer set. from In progress to Needs testing.
This breaks a perfectly valid use case which I utilize regularly: using IPv4 + IPv6 peers with the same public key. Why would I want to create multiple keys for the exact same devices going over IPv4 and IPv6? If you want to include a warning, fine, but don't limit functionality based on someone's interpretation of how something will be used. I understand where this came from, but any time you limit functionality, you limit your users. As Donald Knuth once said:
Unix was not designed to stop you from doing stupid things, because that would also stop you from doing clever things.
@Viacheslav Thank you sir!!!
Nov 21 2022
Nov 21 2022
Viacheslav moved T4812: IPsec ability to show all configured connections from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.3) board.
Viacheslav closed T4812: IPsec ability to show all configured connections, a subtask of T4564: Root task for rewriting [op-mode] to vyos.opmode format, as Resolved.
This is a nice addition but it requires also implementation of RFC 8781 for it to work. It has been merged in latest radvd https://github.com/radvd-project/radvd/commit/a6460662c6ac2b13307a8977ef068825b66fbce0 but it still hasnt been released
jestabro closed T4829: Tunnel argument to 'reset_peer' in ipsec.py should have type hint Optional, a subtask of T4552: Unable to reset IPsec IPv6 peer, as Resolved.
I think the issue is realated to this: https://blog.ipspace.net/2014/09/ipv6-neighbor-discovery-nd-and.html
I add here what I just found and I can reproduce the issue everytime.
You can test with 3-5 servers, the config is basic for each server:
Could you provide config from several items?
How many nodes do we need to reproduce it?
Nov 20 2022
Nov 20 2022
Viacheslav added a project to T4812: IPsec ability to show all configured connections: VyOS 1.3 Equuleus (1.3.3).
Viacheslav changed the status of T4823: swanctl.conf is broken when ipsec site-to-site peer set. from Open to In progress.
Viacheslav changed the status of T4812: IPsec ability to show all configured connections, a subtask of T4564: Root task for rewriting [op-mode] to vyos.opmode format, from In progress to Needs testing.
Viacheslav changed the status of T4812: IPsec ability to show all configured connections from In progress to Needs testing.
1.3 backport https://github.com/vyos/vyos-1x/pull/1670
ipsec site-to-site peer <name> - it is just a connection name and is not related to the IP address
I'll take a look at TS
Viacheslav changed the status of T4830: nat66 - Error in port translation rules from Confirmed to Needs testing.
vyos@r14# set policy route-map FOO rule 100 action permit [edit] vyos@r14# set policy route-map FOO rule 50 action 'deny' [edit] vyos@r14# set policy route-map FOO rule 50 continue '100' [edit] vyos@r14# [edit] vyos@r14# commit [ policy ] rule 50 "continue" cannot be used with action deny!
Viacheslav changed the status of T4831: implement Telegraf build on arm64 / fix hardcoded x86-64 reference from Open to Needs testing.
mcbridematt added a comment to T4831: implement Telegraf build on arm64 / fix hardcoded x86-64 reference.
Pull request: https://github.com/vyos/vyos-build/pull/286