It's a bit confusing, I can create a tunnel with 0.0.0.0/0 if I need it. That how it is also done on PaloAlto FW and Fortigate. Anyway, it is just my opinion. Thanks for picking up this request so quickly.

Jun 11 2021, 5:15 PM · VyOS 1.4 Sagitta

sarthurdev added a comment to T3613: Selectors for route-based IPsec tunnel (vti).

I've left vti esp-group to keep backwards compatibility with current behaviour when vti is configured without any tunnels (when it uses 0.0.0.0/0), in that scenario it would still use the group specified.

Jun 11 2021, 5:00 PM · VyOS 1.4 Sagitta

krox2 added a comment to T3613: Selectors for route-based IPsec tunnel (vti).

@sdev That makes sense, you can also get rid of "esp-group" under vti as it will be specified per tunnel.
I like that we can specify multiple prefixes under one tunnel but also can configure multiple tunnels for more complex scenarios.

Jun 11 2021, 4:43 PM · VyOS 1.4 Sagitta

Viacheslav closed T3614: Container network name with hyphen fail as Resolved.

Jun 11 2021, 4:34 PM · VyOS 1.4 Sagitta

sarthurdev added a comment to T3613: Selectors for route-based IPsec tunnel (vti).

I wonder if instead it should just use the existing tunnel node for this. So if VTI is set on a peer, all configured tunnels get marked for the VTI interface. Current VyOS behaviour allows only for tunnels, or VTI - not both.

Jun 11 2021, 4:27 PM · VyOS 1.4 Sagitta

Viacheslav added a comment to T3614: Container network name with hyphen fail.

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

Jun 11 2021, 12:46 PM · VyOS 1.4 Sagitta

Viacheslav claimed T3614: Container network name with hyphen fail.

Jun 11 2021, 12:22 PM · VyOS 1.4 Sagitta

Viacheslav created T3614: Container network name with hyphen fail.

Jun 11 2021, 12:21 PM · VyOS 1.4 Sagitta

krox2 added a comment to T3613: Selectors for route-based IPsec tunnel (vti).

@sdev Yes, this can be done identically as the tunnel definition.

Jun 11 2021, 12:19 PM · VyOS 1.4 Sagitta

sarthurdev added a comment to T3613: Selectors for route-based IPsec tunnel (vti).

@krox2 Oh I think I understand what you mean. You'd want to also be able to create multiple child SAs each with unique left/right subnets?

Jun 11 2021, 11:45 AM · VyOS 1.4 Sagitta

trae32566 reopened T3563: commit-archive breaks with IPv6 source addresses, a subtask of T3356: Script for remote file transfers, as Open.

Jun 11 2021, 9:45 AM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

trae32566 reopened T3563: commit-archive breaks with IPv6 source addresses as "Open".

This does not appear to be fixed; I think it's something specific to 1.4:

trae@cr01a-vyos# commit
Using source address fd52:d62e:8011:fffe:192:168:253:2
Archiving config...
  sftp://stor01z-rh8.int.trae32566.org:/int/cr01a-vyos Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python3/dist-packages/vyos/remote.py", line 287, in upload
    upload_sftp(local_path, url.hostname, url.path, username, password, port, source, progressbar)
  File "/usr/lib/python3/dist-packages/vyos/remote.py", line 166, in upload_sftp
    transfer_sftp('upload', *args, **kwargs)
  File "/usr/lib/python3/dist-packages/vyos/remote.py", line 162, in transfer_sftp
    sock.shutdown()
TypeError: shutdown() takes exactly one argument (0 given)
[edit policy route-map BGP-BACKBONE-OUT]
trae@cr01a-vyos# run show ver

Jun 11 2021, 9:45 AM · VyOS 1.4 Sagitta

trae32566 added a comment to T3378: commit-archive source-address broken for IPv6 addresses.

I have a similar problem, but different, in T3563. I've reopened it and added information, but basically 1.4 still has the issue reported in that bug report.

Jun 11 2021, 9:43 AM · VyOS 1.3 Equuleus (1.3.0)

afics added a comment to T3195: Add support for cisco style GRE keepalives.

See [1] from the previous post:

Note: If you don't want to install anything and don't care about some potential security problems, just enable the following 2 options to get native GRE keepalive support on Linux: […]

I care. Setting these sysctl parameters allows for relaying arbitrary traffic through the router.

Jun 11 2021, 9:43 AM · VyOS Rolling

Jun 10 2021

krox2 added a comment to T3613: Selectors for route-based IPsec tunnel (vti).

@sdev Will it not create a full mesh, for example:
10.10.10.0/24 <--> 192.168.10.0/24
10.10.20.0/24 <--> 192.168.20.0/24
It will also set IPsec for 10.10.10.0/24 <--> 192.168.20.0/24 and 10.10.20.0/24 <--> 192.168.10.0/24 that may not be desired.

Jun 10 2021, 11:09 PM · VyOS 1.4 Sagitta

sarthurdev added a comment to T3613: Selectors for route-based IPsec tunnel (vti).

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

Jun 10 2021, 10:20 PM · VyOS 1.4 Sagitta

krox2 added a comment to T3613: Selectors for route-based IPsec tunnel (vti).

@Viacheslav Can be similar to policy-based ipsec

# set vpn ipsec site-to-site peer 1.1.1.1 tunnel 1 
Possible completions:
   allow-nat-networks
                Option to allow NAT networks
   allow-public-networks
                Option to allow public networks
   disable      Option to disable vpn tunnel
   esp-group    ESP group name
 > local        Local parameters for interesting traffic
   protocol     Protocol to encrypt
 > remote       Remote parameters for interesting traffic

Jun 10 2021, 9:07 PM · VyOS 1.4 Sagitta

Viacheslav added a comment to T3613: Selectors for route-based IPsec tunnel (vti).

@krox2 How should looks like a configuration for many local/remote traffic selectors per one vti interface?

Jun 10 2021, 8:46 PM · VyOS 1.4 Sagitta

Viacheslav added a subtask for T2816: Rewrite IPsec scripts with the new XML/Python approach: T3613: Selectors for route-based IPsec tunnel (vti).

Jun 10 2021, 8:36 PM · VyOS 1.4 Sagitta

Viacheslav added a parent task for T3613: Selectors for route-based IPsec tunnel (vti): T2816: Rewrite IPsec scripts with the new XML/Python approach.

Jun 10 2021, 8:36 PM · VyOS 1.4 Sagitta

krox2 updated the task description for T3613: Selectors for route-based IPsec tunnel (vti).

Jun 10 2021, 8:19 PM · VyOS 1.4 Sagitta

krox2 updated the task description for T3613: Selectors for route-based IPsec tunnel (vti).

Jun 10 2021, 8:18 PM · VyOS 1.4 Sagitta

krox2 created T3613: Selectors for route-based IPsec tunnel (vti).

Jun 10 2021, 8:17 PM · VyOS 1.4 Sagitta

Viacheslav closed T2620: Add ipsec peer-name to log to simplifies grepping and troubleshooting as Resolved.

Jun 10 2021, 8:16 PM · VyOS 1.2 Crux (VyOS 1.2.8)

Viacheslav closed T2620: Add ipsec peer-name to log to simplifies grepping and troubleshooting, a subtask of T2816: Rewrite IPsec scripts with the new XML/Python approach, as Resolved.

Jun 10 2021, 8:16 PM · VyOS 1.4 Sagitta

Viacheslav moved T2620: Add ipsec peer-name to log to simplifies grepping and troubleshooting from Backport Candidates to Finished on the VyOS 1.3 Equuleus board.

Jun 10 2021, 8:16 PM · VyOS 1.2 Crux (VyOS 1.2.8)

c-po changed the status of T3250: PPPoE server: wrong local usernames from Unknown Status to Resolved.

Jun 10 2021, 7:24 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

c-po moved T3250: PPPoE server: wrong local usernames from Open to Finished on the VyOS 1.4 Sagitta board.

Jun 10 2021, 7:24 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

c-po moved T3250: PPPoE server: wrong local usernames from Need Triage to Finished on the VyOS 1.3 Equuleus board.

Jun 10 2021, 7:24 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

jestabro added a comment to T3250: PPPoE server: wrong local usernames.

Already backported: ff7b2b0e62510ef8de28c9c4bfa34badeabec775

Jun 10 2021, 6:59 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

c-po moved T2717: Wrong DHCP server pool size in statistics from Open to Finished on the VyOS 1.4 Sagitta board.

Jun 10 2021, 5:52 PM · VyOS 1.2 Crux (VyOS 1.2.8)

c-po moved T2717: Wrong DHCP server pool size in statistics from Need Triage to Finished on the VyOS 1.3 Equuleus board.

Jun 10 2021, 5:52 PM · VyOS 1.2 Crux (VyOS 1.2.8)

c-po moved T2717: Wrong DHCP server pool size in statistics from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.8) board.

Jun 10 2021, 5:52 PM · VyOS 1.2 Crux (VyOS 1.2.8)

c-po added projects to T2717: Wrong DHCP server pool size in statistics: VyOS 1.4 Sagitta, VyOS 1.3 Equuleus, VyOS 1.2 Crux (VyOS 1.2.8).

Jun 10 2021, 5:51 PM · VyOS 1.2 Crux (VyOS 1.2.8)

c-po closed T3138: ddclient improperly updated when apply rfc2136 config as Resolved.

Jun 10 2021, 5:49 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

c-po moved T3138: ddclient improperly updated when apply rfc2136 config from Backport Candidates to Finished on the VyOS 1.4 Sagitta board.

Jun 10 2021, 5:48 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

c-po moved T3138: ddclient improperly updated when apply rfc2136 config from Need Triage to Finished on the VyOS 1.3 Equuleus board.

Jun 10 2021, 5:48 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

c-po renamed T3318: Update Linux Kernel to v5.4.208 / 5.10.142 from Update Linux Kernel to v5.4.124 / 5.10.42 to Update Linux Kernel to v5.4.125 / 5.10.43.

Jun 10 2021, 5:14 PM · VyOS 1.3 Equuleus (1.3.2), VyOS 1.4 Sagitta

c-po changed the status of T3611: WWAN interface (MC7710) no longer works on Kernel 5.10 from Open to In progress.

Jun 10 2021, 5:10 PM · VyOS 1.4 Sagitta

c-po created T3611: WWAN interface (MC7710) no longer works on Kernel 5.10.

Jun 10 2021, 5:10 PM · VyOS 1.4 Sagitta

c-po added a comment to T3250: PPPoE server: wrong local usernames.

no_tag_node_value_mangle=True does not exist on VyOS 1.3, thus a backport is currently not possible. @jestabro can we backport this?

Jun 10 2021, 5:06 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

trae32566 closed T2645: Editing route-map action requires adding a new rule as Resolved.

Jun 10 2021, 4:48 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

tsantiago.work added a comment to T2645: Editing route-map action requires adding a new rule.

@Viacheslav This is confirmed fixed, I'm guessing it got fixed during the period between reporting it and now.

Jun 10 2021, 4:46 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

Viacheslav added a comment to T2645: Editing route-map action requires adding a new rule.

I can't reproduce it, VyOS 1.3-beta-202106081558

set policy prefix-list FOO rule 10 action 'permit'
set policy prefix-list FOO rule 10 prefix '0.0.0.0/0'
set policy route-map FOO rule 10 action 'permit'
set policy route-map FOO rule 10 match ip address prefix-list 'FOO'
set policy route-map FOO rule 10 set distance '220'
set policy route-map FOO rule 1000 action 'permit'

Jun 10 2021, 11:55 AM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

Jun 9 2021

Viacheslav added a comment to T3610: DHCP-Server creation for not primary IP address fails.

@n.fort You can try to replace True with False there (1.3 and 1.4). But it needs more tests. In some cases, it was some bugs with the DHCP server and not the primary address.
https://github.com/vyos/vyos-1x/blob/5d068442cf7b1863724c83168176ce2940a023fe/src/conf_mode/dhcp_server.py#L237

Jun 9 2021, 6:52 PM · VyOS 1.3 Equuleus (1.3.0-epa3), VyOS 1.2 Crux (VyOS 1.2.9), VyOS 1.4 Sagitta

Viacheslav moved T2620: Add ipsec peer-name to log to simplifies grepping and troubleshooting from Need Triage to Backport Candidates on the VyOS 1.3 Equuleus board.

Jun 9 2021, 5:02 PM · VyOS 1.2 Crux (VyOS 1.2.8)

Viacheslav moved T2620: Add ipsec peer-name to log to simplifies grepping and troubleshooting from Backport Candidates to Finished on the VyOS 1.4 Sagitta board.

Jun 9 2021, 5:02 PM · VyOS 1.2 Crux (VyOS 1.2.8)

Viacheslav added a comment to T2620: Add ipsec peer-name to log to simplifies grepping and troubleshooting.

VyOS 1.3-beta-202106081558
Works as expected.

Jun  9 19:57:38 r4-1 charon: 13[CFG] no IKE_SA named 'peer-192.0.2.2-tunnel-0' found
Jun  9 19:57:38 r4-1 charon: 14[CFG] received stroke: initiate 'peer-192.0.2.2-tunnel-0'
Jun  9 19:57:38 r4-1 charon: 06[IKE] <peer-192.0.2.2-tunnel-0|4> initiating Main Mode IKE_SA peer-192.0.2.2-tunnel-0[4] to 192.0.2.2
Jun  9 19:57:38 r4-1 charon: 06[ENC] <peer-192.0.2.2-tunnel-0|4> generating ID_PROT request 0 [ SA V V V V V ]
Jun  9 19:57:38 r4-1 charon: 06[NET] <peer-192.0.2.2-tunnel-0|4> sending packet: from 192.0.2.1[500] to 192.0.2.2[500] (180 bytes)
Jun  9 19:57:38 r4-1 charon: 07[NET] <peer-192.0.2.2-tunnel-0|4> received packet: from 192.0.2.2[500] to 192.0.2.1[500] (160 bytes)
Jun  9 19:57:38 r4-1 charon: 07[ENC] <peer-192.0.2.2-tunnel-0|4> parsed ID_PROT response 0 [ SA V V V V ]
Jun  9 19:57:38 r4-1 charon: 07[IKE] <peer-192.0.2.2-tunnel-0|4> received XAuth vendor ID
Jun  9 19:57:38 r4-1 charon: 07[IKE] <peer-192.0.2.2-tunnel-0|4> received DPD vendor ID
Jun  9 19:57:38 r4-1 charon: 07[IKE] <peer-192.0.2.2-tunnel-0|4> received FRAGMENTATION vendor ID
Jun  9 19:57:38 r4-1 charon: 07[IKE] <peer-192.0.2.2-tunnel-0|4> received NAT-T (RFC 3947) vendor ID
Jun  9 19:57:38 r4-1 charon: 07[CFG] <peer-192.0.2.2-tunnel-0|4> selected proposal: IKE:AES_CBC_256/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024
Jun  9 19:57:38 r4-1 charon: 07[ENC] <peer-192.0.2.2-tunnel-0|4> generating ID_PROT request 0 [ KE No NAT-D NAT-D ]
Jun  9 19:57:38 r4-1 charon: 07[NET] <peer-192.0.2.2-tunnel-0|4> sending packet: from 192.0.2.1[500] to 192.0.2.2[500] (244 bytes)
Jun  9 19:57:38 r4-1 charon: 05[NET] <peer-192.0.2.2-tunnel-0|4> received packet: from 192.0.2.2[500] to 192.0.2.1[500] (244 bytes)
Jun  9 19:57:38 r4-1 charon: 05[ENC] <peer-192.0.2.2-tunnel-0|4> parsed ID_PROT response 0 [ KE No NAT-D NAT-D ]
Jun  9 19:57:38 r4-1 charon: 05[ENC] <peer-192.0.2.2-tunnel-0|4> generating ID_PROT request 0 [ ID HASH N(INITIAL_CONTACT) ]
Jun  9 19:57:38 r4-1 charon: 05[NET] <peer-192.0.2.2-tunnel-0|4> sending packet: from 192.0.2.1[500] to 192.0.2.2[500] (108 bytes)
Jun  9 19:57:38 r4-1 charon: 08[NET] <peer-192.0.2.2-tunnel-0|4> received packet: from 192.0.2.2[500] to 192.0.2.1[500] (76 bytes)
Jun  9 19:57:38 r4-1 charon: 08[ENC] <peer-192.0.2.2-tunnel-0|4> parsed ID_PROT response 0 [ ID HASH ]
Jun  9 19:57:38 r4-1 charon: 08[IKE] <peer-192.0.2.2-tunnel-0|4> IKE_SA peer-192.0.2.2-tunnel-0[4] established between 192.0.2.1[192.0.2.1]...192.0.2.2[192.0.2.2]
Jun  9 19:57:38 r4-1 charon: 08[IKE] <peer-192.0.2.2-tunnel-0|4> scheduling reauthentication in 2524s
Jun  9 19:57:38 r4-1 charon: 08[IKE] <peer-192.0.2.2-tunnel-0|4> maximum IKE_SA lifetime 3064s
Jun  9 19:57:38 r4-1 charon: 08[ENC] <peer-192.0.2.2-tunnel-0|4> generating QUICK_MODE request 364019988 [ HASH SA No KE ID ID ]
Jun  9 19:57:38 r4-1 charon: 08[NET] <peer-192.0.2.2-tunnel-0|4> sending packet: from 192.0.2.1[500] to 192.0.2.2[500] (316 bytes)
Jun  9 19:57:38 r4-1 charon: 09[NET] <peer-192.0.2.2-tunnel-0|4> received packet: from 192.0.2.2[500] to 192.0.2.1[500] (316 bytes)
Jun  9 19:57:38 r4-1 charon: 09[ENC] <peer-192.0.2.2-tunnel-0|4> parsed QUICK_MODE response 364019988 [ HASH SA No KE ID ID ]
Jun  9 19:57:38 r4-1 charon: 09[CFG] <peer-192.0.2.2-tunnel-0|4> selected proposal: ESP:AES_CBC_256/HMAC_SHA1_96/MODP_1024/NO_EXT_SEQ
Jun  9 19:57:38 r4-1 charon: 09[IKE] <peer-192.0.2.2-tunnel-0|4> CHILD_SA peer-192.0.2.2-tunnel-0{1} established with SPIs cb0aa83a_i c728156c_o and TS 10.1.0.0/24 === 10.2.3.0/24
Jun  9 19:57:38 r4-1 charon: 09[ENC] <peer-192.0.2.2-tunnel-0|4> generating QUICK_MODE request 364019988 [ HASH ]
Jun  9 19:57:38 r4-1 charon: 09[NET] <peer-192.0.2.2-tunnel-0|4> sending packet: from 192.0.2.1[500] to 192.0.2.2[500] (60 bytes)
vyos@r4-1.3:~$

Jun 9 2021, 4:59 PM · VyOS 1.2 Crux (VyOS 1.2.8)

Viacheslav added a comment to T2855: disabled vti interfaces still working.

Ok it already fixed in 1.3 T2916 and can be migrated to crux

Jun 9 2021, 4:27 PM · VyOS 1.2 Crux (VyOS 1.2.8)

n.fort created T3610: DHCP-Server creation for not primary IP address fails.

Jun 9 2021, 3:35 PM · VyOS 1.3 Equuleus (1.3.0-epa3), VyOS 1.2 Crux (VyOS 1.2.9), VyOS 1.4 Sagitta

jestabro added a comment to T3574: Add constraintGroup for combining validators with logical AND.

Draft PRs:
https://github.com/vyos/vyos-utils/pull/1
https://github.com/vyos/vyos-1x/pull/869

Jun 9 2021, 1:08 PM · VyOS 1.4 Sagitta (1.4.0-epa1)

Harliff added a comment to T2855: disabled vti interfaces still working.

In T2855#95665, @Viacheslav wrote:

I can't reproduce it in 1.2.7

Jun 9 2021, 8:48 AM · VyOS 1.2 Crux (VyOS 1.2.8)

Viacheslav closed T3602: Renaming BGP Peer Groups Leaves Router Broken, a subtask of T3182: Main blocker Task for FRR 7.4/7.5 series update, as Resolved.

Jun 9 2021, 7:02 AM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

Jun 8 2021

c-po updated the task description for T2816: Rewrite IPsec scripts with the new XML/Python approach.

Jun 8 2021, 5:53 PM · VyOS 1.4 Sagitta

jestabro updated the task description for T3608: Standardize warnings from configure scripts.

Jun 8 2021, 4:50 PM · VyOS 1.3 Equuleus (1.3.3), VyOS 1.4 Sagitta

jestabro triaged T3608: Standardize warnings from configure scripts as Normal priority.

Jun 8 2021, 4:45 PM · VyOS 1.3 Equuleus (1.3.3), VyOS 1.4 Sagitta

erkin changed the status of T3378: commit-archive source-address broken for IPv6 addresses, a subtask of T3356: Script for remote file transfers, from Open to Needs testing.

Jun 8 2021, 2:31 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

erkin changed the status of T3378: commit-archive source-address broken for IPv6 addresses from Open to Needs testing.

This is resolved for 1.4. Do you still have this problem in 1.3 as of RC4? If so, I'll need to backport the changes.

Jun 8 2021, 2:31 PM · VyOS 1.3 Equuleus (1.3.0)

erkin closed T3563: commit-archive breaks with IPv6 source addresses, a subtask of T3356: Script for remote file transfers, as Resolved.

Jun 8 2021, 2:20 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

erkin closed T3563: commit-archive breaks with IPv6 source addresses as Resolved.

Jun 8 2021, 2:20 PM · VyOS 1.4 Sagitta

Viacheslav moved T2620: Add ipsec peer-name to log to simplifies grepping and troubleshooting from Open to Backport Candidates on the VyOS 1.4 Sagitta board.

Jun 8 2021, 10:53 AM · VyOS 1.2 Crux (VyOS 1.2.8)

Viacheslav added a project to T2620: Add ipsec peer-name to log to simplifies grepping and troubleshooting: VyOS 1.2 Crux (VyOS 1.2.8).

Jun 8 2021, 10:49 AM · VyOS 1.2 Crux (VyOS 1.2.8)

Viacheslav changed the status of T2620: Add ipsec peer-name to log to simplifies grepping and troubleshooting, a subtask of T2816: Rewrite IPsec scripts with the new XML/Python approach, from Open to Needs testing.

Jun 8 2021, 9:14 AM · VyOS 1.4 Sagitta

Viacheslav changed the status of T2620: Add ipsec peer-name to log to simplifies grepping and troubleshooting from Open to Needs testing.

Jun 8 2021, 9:14 AM · VyOS 1.2 Crux (VyOS 1.2.8)

c-po closed T3605: Allow to set prefer-global for ipv6-next-hop as Resolved.

Jun 8 2021, 6:25 AM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

c-po moved T3605: Allow to set prefer-global for ipv6-next-hop from Need Triage to Finished on the VyOS 1.3 Equuleus board.

Jun 8 2021, 6:25 AM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

c-po moved T3605: Allow to set prefer-global for ipv6-next-hop from Open to Finished on the VyOS 1.4 Sagitta board.

Jun 8 2021, 6:25 AM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

c-po added projects to T3605: Allow to set prefer-global for ipv6-next-hop: VyOS 1.3 Equuleus, VyOS 1.4 Sagitta.

Jun 8 2021, 6:25 AM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

c-po closed T3607: [route-map] set ipv6 next-hop prefer-global as Resolved.

Jun 8 2021, 6:24 AM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

c-po moved T3607: [route-map] set ipv6 next-hop prefer-global from Open to Finished on the VyOS 1.4 Sagitta board.

Jun 8 2021, 6:23 AM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

c-po moved T3607: [route-map] set ipv6 next-hop prefer-global from Need Triage to Finished on the VyOS 1.3 Equuleus board.

Jun 8 2021, 6:23 AM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

c-po added a project to T3607: [route-map] set ipv6 next-hop prefer-global: VyOS 1.3 Equuleus.

Jun 8 2021, 6:23 AM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

c-po assigned T3607: [route-map] set ipv6 next-hop prefer-global to fernando.

Jun 8 2021, 6:18 AM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

c-po closed T3289: No description for node "service" conf-mode as Resolved.

Jun 8 2021, 6:17 AM · VyOS 1.2 Crux (VyOS 1.2.7), VyOS 1.4 Sagitta

c-po changed the status of T3289: No description for node "service" conf-mode from Confirmed to In progress.

Jun 8 2021, 5:59 AM · VyOS 1.2 Crux (VyOS 1.2.7), VyOS 1.4 Sagitta

Jun 7 2021

fernando renamed T3607: [route-map] set ipv6 next-hop prefer-global from [route-mapset ipv6 next-hop prefer-global to [route-map] set ipv6 next-hop prefer-global.

Jun 7 2021, 11:59 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

fernando created T3607: [route-map] set ipv6 next-hop prefer-global.

Jun 7 2021, 11:48 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

Viacheslav moved T3289: No description for node "service" conf-mode from Open to Finished on the VyOS 1.4 Sagitta board.

Jun 7 2021, 11:15 PM · VyOS 1.2 Crux (VyOS 1.2.7), VyOS 1.4 Sagitta

Viacheslav closed T3455: system users can not be added in "edit" as Resolved.

Jun 7 2021, 11:12 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

Viacheslav changed the status of T3461: OpenConnect Server redundancy check from Unknown Status to Resolved.

Jun 7 2021, 11:10 PM · VyOS 1.3 Equuleus (1.3.0), VyOS 1.4 Sagitta

Viacheslav created T3606: SNMP unknown notification OID.

Jun 7 2021, 10:37 PM · VyOS 1.4 Sagitta

Viacheslav added a comment to T2620: Add ipsec peer-name to log to simplifies grepping and troubleshooting.

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

Jun  8 00:59:20 r1-roll ipsec_starter[2373]: charon (2374) started after 400 ms
Jun  8 00:59:20 r1-roll charon: 05[CFG] received stroke: add connection 'peer-192.0.2.2-tunnel-0'
Jun  8 00:59:20 r1-roll charon: 05[CFG] added configuration 'peer-192.0.2.2-tunnel-0'
Jun  8 00:59:20 r1-roll charon: 07[CFG] received stroke: initiate 'peer-192.0.2.2-tunnel-0'
Jun  8 00:59:20 r1-roll charon: 07[IKE] <peer-192.0.2.2-tunnel-0|1> initiating Main Mode IKE_SA peer-192.0.2.2-tunnel-0[1] to 192.0.2.2
Jun  8 00:59:20 r1-roll charon: 07[ENC] <peer-192.0.2.2-tunnel-0|1> generating ID_PROT request 0 [ SA V V V V V ]
Jun  8 00:59:20 r1-roll charon: 07[NET] <peer-192.0.2.2-tunnel-0|1> sending packet: from 192.0.2.1[500] to 192.0.2.2[500] (180 bytes)
Jun  8 00:59:20 r1-roll charon: 09[NET] <peer-192.0.2.2-tunnel-0|1> received packet: from 192.0.2.2[500] to 192.0.2.1[500] (160 bytes)
Jun  8 00:59:20 r1-roll charon: 09[ENC] <peer-192.0.2.2-tunnel-0|1> parsed ID_PROT response 0 [ SA V V V V ]
Jun  8 00:59:20 r1-roll charon: 09[IKE] <peer-192.0.2.2-tunnel-0|1> received XAuth vendor ID
Jun  8 00:59:20 r1-roll charon: 09[IKE] <peer-192.0.2.2-tunnel-0|1> received DPD vendor ID
Jun  8 00:59:20 r1-roll charon: 09[IKE] <peer-192.0.2.2-tunnel-0|1> received FRAGMENTATION vendor ID
Jun  8 00:59:20 r1-roll charon: 09[IKE] <peer-192.0.2.2-tunnel-0|1> received NAT-T (RFC 3947) vendor ID
Jun  8 00:59:20 r1-roll charon: 09[CFG] <peer-192.0.2.2-tunnel-0|1> selected proposal: IKE:AES_CBC_256/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024
Jun  8 00:59:20 r1-roll charon: 09[ENC] <peer-192.0.2.2-tunnel-0|1> generating ID_PROT request 0 [ KE No NAT-D NAT-D ]
Jun  8 00:59:20 r1-roll charon: 09[NET] <peer-192.0.2.2-tunnel-0|1> sending packet: from 192.0.2.1[500] to 192.0.2.2[500] (244 bytes)
Jun  8 00:59:20 r1-roll charon: 10[NET] <peer-192.0.2.2-tunnel-0|1> received packet: from 192.0.2.2[500] to 192.0.2.1[500] (244 bytes)
Jun  8 00:59:20 r1-roll charon: 10[ENC] <peer-192.0.2.2-tunnel-0|1> parsed ID_PROT response 0 [ KE No NAT-D NAT-D ]
Jun  8 00:59:20 r1-roll charon: 10[ENC] <peer-192.0.2.2-tunnel-0|1> generating ID_PROT request 0 [ ID HASH N(INITIAL_CONTACT) ]
Jun  8 00:59:20 r1-roll charon: 10[NET] <peer-192.0.2.2-tunnel-0|1> sending packet: from 192.0.2.1[500] to 192.0.2.2[500] (108 bytes)
Jun  8 00:59:20 r1-roll charon: 11[NET] <peer-192.0.2.2-tunnel-0|1> received packet: from 192.0.2.2[500] to 192.0.2.1[500] (76 bytes)
Jun  8 00:59:20 r1-roll charon: 11[ENC] <peer-192.0.2.2-tunnel-0|1> parsed ID_PROT response 0 [ ID HASH ]
Jun  8 00:59:20 r1-roll charon: 11[IKE] <peer-192.0.2.2-tunnel-0|1> IKE_SA peer-192.0.2.2-tunnel-0[1] established between 192.0.2.1[192.0.2.1]...192.0.2.2[192.0.2.2]
Jun  8 00:59:20 r1-roll charon: 11[IKE] <peer-192.0.2.2-tunnel-0|1> scheduling rekeying in 2720s
Jun  8 00:59:20 r1-roll charon: 11[IKE] <peer-192.0.2.2-tunnel-0|1> maximum IKE_SA lifetime 3260s
Jun  8 00:59:20 r1-roll charon: 11[ENC] <peer-192.0.2.2-tunnel-0|1> generating QUICK_MODE request 3783917425 [ HASH SA No KE ID ID ]
Jun  8 00:59:20 r1-roll charon: 11[NET] <peer-192.0.2.2-tunnel-0|1> sending packet: from 192.0.2.1[500] to 192.0.2.2[500] (316 bytes)
Jun  8 00:59:20 r1-roll charon: 12[NET] <peer-192.0.2.2-tunnel-0|1> received packet: from 192.0.2.2[500] to 192.0.2.1[500] (316 bytes)
Jun  8 00:59:20 r1-roll charon: 12[ENC] <peer-192.0.2.2-tunnel-0|1> parsed QUICK_MODE response 3783917425 [ HASH SA No KE ID ID ]
Jun  8 00:59:20 r1-roll charon: 12[CFG] <peer-192.0.2.2-tunnel-0|1> selected proposal: ESP:AES_CBC_256/HMAC_SHA1_96/MODP_1024/NO_EXT_SEQ
Jun  8 00:59:20 r1-roll charon: 12[IKE] <peer-192.0.2.2-tunnel-0|1> CHILD_SA peer-192.0.2.2-tunnel-0{1} established with SPIs c4d940b7_i c9a69e83_o and TS 10.1.0.0/24 === 10.2.3.0/24
Jun  8 00:59:20 r1-roll charon: 12[ENC] <peer-192.0.2.2-tunnel-0|1> generating QUICK_MODE request 3783917425 [ HASH ]
Jun  8 00:59:20 r1-roll charon: 12[NET] <peer-192.0.2.2-tunnel-0|1> sending packet: from 192.0.2.1[500] to 192.0.2.2[500] (60 bytes)

Jun 7 2021, 10:22 PM · VyOS 1.2 Crux (VyOS 1.2.8)

Viacheslav added a project to T2620: Add ipsec peer-name to log to simplifies grepping and troubleshooting: VyOS 1.4 Sagitta.

Jun 7 2021, 8:50 PM · VyOS 1.2 Crux (VyOS 1.2.8)

SearchUse ResultsEdit QueryHide Query

Jun 12 2021

Jun 11 2021

Jun 10 2021

Jun 9 2021

Jun 8 2021

Jun 7 2021

Search
Use Results
Edit Query
Hide Query