Skip to content

Attractor ipv4/ipv6-prefix also accept IP range#322

Open
zolug wants to merge 1 commit intomasterfrom
iprange
Open

Attractor ipv4/ipv6-prefix also accept IP range#322
zolug wants to merge 1 commit intomasterfrom
iprange

Conversation

@zolug
Copy link
Copy Markdown
Collaborator

@zolug zolug commented Nov 17, 2022

Changes allows to limit the pool of IP addresses in a network to allocate IPs from.
IP ranges can be concatenated using a semicolon.

Examples:

    ipv4-prefix: 169.254.100.0-169.254.100.100/24
    ipv6-prefix: 100:100::0-100:100::100/64;100:100::a:0-100:100::a:aaa9/64
    ipv4-prefix: 169.254.100.0/24
    ipv6-prefix: 100:100::0-100:100::100/64;100:100::a:0-100:100::a:aaa9/64

The change are backward compatible. However if a whole network is specified, it is not allowed to specify additional ranges (no concatenation alllowed).

Description

Requires: networkservicemesh/cmd-nse-remote-vlan#110

Issue link

#321

Checklist

  • Purpose
    • Bug fix
    • New functionality
    • Documentation
    • Refactoring
    • CI
  • Test
    • [] Unit test
    • E2E Test
    • Tested manually
  • Introduce a breaking change
    • Yes (description required)
    • No
  • Introduce changes in the Operator
    • Yes (description required)
    • No

@zolug zolug self-assigned this Nov 29, 2022
Allows limiting the pool of IP addresses to allocate IPs from.
-Enables coordination of multiple Attractors when they share
 the same external network.
-Can be also used to exclude reserved IPs of Gateway Routers.

Example:
    ipv4-prefix: 169.254.100.0-169.254.100.100/24
    ipv6-prefix: 100:100::0-100:100::100/64;100:100::2000-100:100::ffff/64
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: 👀 In review

Development

Successfully merging this pull request may close these issues.

2 participants