Skip to content

Add Wireguard support for RouterOS 7#3695

Draft
snuffy22 wants to merge 1 commit into
ipspace:devfrom
snuffy22:routeros7-wg
Draft

Add Wireguard support for RouterOS 7#3695
snuffy22 wants to merge 1 commit into
ipspace:devfrom
snuffy22:routeros7-wg

Conversation

@snuffy22

Copy link
Copy Markdown
Contributor

Provide Wireguard support for RouterOS 7.

Can also provide update to 03/04 tests to have FRR as one side of the test.

03-wireguard.yml
PLAY RECAP ***********************************************************************************************************************************************************************************
dut_r1                     : ok=30   changed=4    unreachable=0    failed=0    skipped=11   rescued=0    ignored=0
dut_r2                     : ok=30   changed=4    unreachable=0    failed=0    skipped=11   rescued=0    ignored=0

Results of configuration script deployments
==============================================================================================================================================================================================
core             Script:  initial
r3               Script:  initial,routing,ospf


[SUCCESS] Lab devices configured


Test dual-stack WireGuard tunnels. The two tested devices have a WireGuard
tunnel carrying both IPv4 and IPv6 and run OSPFv2 and OSPFv3 over it. The
probe should receive the routes advertised from the remote device (DUT_R1)
and be able to ping its loopback over both address families.

[adj]     Check OSPFv2 adjacencies [ node(s): r3 ]
[PASS]    r3: OSPFv2 neighbor 10.0.0.2 is in state Full/-
[PASS]    Test succeeded in 0.1 seconds

[adj6]    Check OSPFv3 adjacencies [ node(s): r3 ]
[PASS]    r3: OSPFv3 neighbor 10.0.0.2 is in state Full
[PASS]    Test succeeded in 0.1 seconds

[pfx]     Check for DUT_R1 IPv4 loopback prefix being propagated to R3 [ node(s): r3 ]
[WAITING] Waiting for SPF to do its magic (retrying for 30 seconds)
[PASS]    r3: The prefix 10.0.0.1/32 is in the OSPF topology
[PASS]    Test succeeded in 12.7 seconds

[pfx6]    Check for DUT_R1 IPv6 loopback prefix being propagated to R3 [ node(s): r3 ]
[PASS]    r3: The prefix 2001:db8:1:1::/64 is in the OSPFv3 topology
[PASS]    Test succeeded in 0.1 seconds

[ping]    Check end-to-end IPv4 connectivity [ node(s): r3 ]
[PASS]    r3: Ping to 10.0.0.1 succeeded
[PASS]    Test succeeded in 0.2 seconds

[ping6]   Check end-to-end IPv6 connectivity [ node(s): r3 ]
[PASS]    r3: Ping to ipv6 2001:db8:1:1::1 succeeded
[PASS]    Test succeeded in 1.1 seconds

[mtu]     Check a full 1500-byte packet traverses the tunnel (underlay MTU 1560) [ node(s): r3 ]
[PASS]    r3: Ping to 10.0.0.1 size 1472 succeeded
[PASS]    Test succeeded in 0.1 seconds

[SUCCESS] Tests passed: 7
04-wireguard-vrf.yml
PLAY RECAP ***********************************************************************************************************************************************************************************
dut_r1                     : ok=30   changed=4    unreachable=0    failed=0    skipped=11   rescued=0    ignored=0
dut_r2                     : ok=30   changed=4    unreachable=0    failed=0    skipped=11   rescued=0    ignored=0

Results of configuration script deployments
==============================================================================================================================================================================================
r3               Script:  initial,ospf


[SUCCESS] Lab devices configured


Test dual-stack WireGuard tunnels in a transport VRF. The two tested devices
have a WireGuard tunnel in the transport VRF carrying both IPv4 and IPv6 and
run (global) OSPFv2 and OSPFv3 over it. The probe should receive the routes
advertised from the remote device (DUT_R1) and be able to ping its loopback
over both address families.

[adj]     Check OSPFv2 adjacencies [ node(s): r3 ]
[PASS]    r3: OSPFv2 neighbor 10.0.0.2 is in state Full/-
[PASS]    Test succeeded in 0.1 seconds

[adj6]    Check OSPFv3 adjacencies [ node(s): r3 ]
[PASS]    r3: OSPFv3 neighbor 10.0.0.2 is in state Full
[PASS]    Test succeeded in 0.1 seconds

[pfx]     Check for DUT_R1 IPv4 loopback prefix being propagated to R3 [ node(s): r3 ]
[WAITING] Waiting for SPF to do its magic (retrying for 30 seconds)
[PASS]    r3: The prefix 10.0.0.1/32 is in the OSPF topology
[PASS]    Test succeeded in 11.6 seconds

[pfx6]    Check for DUT_R1 IPv6 loopback prefix being propagated to R3 [ node(s): r3 ]
[PASS]    r3: The prefix 2001:db8:1:1::/64 is in the OSPFv3 topology
[PASS]    Test succeeded in 0.1 seconds

[ping]    Check end-to-end IPv4 connectivity [ node(s): r3 ]
[PASS]    r3: Ping to 10.0.0.1 succeeded
[PASS]    Test succeeded in 0.1 seconds

[ping6]   Check end-to-end IPv6 connectivity [ node(s): r3 ]
[PASS]    r3: Ping to ipv6 2001:db8:1:1::1 succeeded
[PASS]    Test succeeded in 1.1 seconds

[mtu]     Check a full 1500-byte packet traverses the tunnel (underlay MTU 1580) [ node(s): r3 ]
[PASS]    r3: Ping to 10.0.0.1 size 1472 succeeded
[PASS]    Test succeeded in 0.1 seconds

[SUCCESS] Tests passed: 7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant