Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #83486 > unrolled thread

Bug#1078607: Feature Request: Add `auto` option for VRF table id management

Started byMike Waterman <mwaterman@vultr.com>
First post2024-08-13 19:50 +0200
Last post2024-08-14 15:30 +0200
Articles 5 — 4 participants

Back to article view | Back to linux.debian.kernel


Contents

  Bug#1078607: Feature Request: Add `auto` option for VRF table id management Mike Waterman <mwaterman@vultr.com> - 2024-08-13 19:50 +0200
    Bug#1078607: Feature Request: Add `auto` option for VRF table id management Luca Boccassi <bluca@debian.org> - 2024-08-14 10:20 +0200
    Processed: Re: Feature Request: Add `auto` option for VRF table  id management "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-08-14 10:20 +0200
    Bug#1078607: Feature Request: Add `auto` option for VRF table id management Daniel Gröber <dxld@darkboxed.org> - 2024-08-14 10:50 +0200
      Bug#1078607: Feature Request: Add `auto` option for VRF table id management Mike Waterman <mwaterman@vultr.com> - 2024-08-14 15:30 +0200

#83486 — Bug#1078607: Feature Request: Add `auto` option for VRF table id management

FromMike Waterman <mwaterman@vultr.com>
Date2024-08-13 19:50 +0200
SubjectBug#1078607: Feature Request: Add `auto` option for VRF table id management
Message-ID<Jb3OF-4MfT-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Package: iproute2
Version: 5.10.0-4
Severity: wishlist

I'm requesting the addition of an `auto` option for VRF table ID management
in the iproute2 package on Debian. (Apologies if the package is incorrect.)
Currently, managing VRF table IDs manually can be cumbersome and
error-prone. In Cumulus Linux, the `auto` option allows the OS to handle
allocating and releasing VRF table IDs automatically, which greatly
simplifies network configuration and management. Having a similar feature
in Debian would be highly beneficial for users who manage complex
networking setups.

For example, instead of this:

```
auto vrfexample
iface vrfexample
    vrf-table 1001

auto vrfexample2
iface vrfexample2
    vrf-table 1002
```

Or this:

```
ip link add vrfexample type vrf table 1001
ip link add vrfexample2 type vrf table 1002
```

It'd be great to do this:

```
auto vrfexample
iface vrfexample
    vrf-table auto

auto vrfexample2
iface vrfexample2
    vrf-table auto
```

Or this:

```
ip link add vrfexample type vrf table auto
ip link add vrfexample2 type vrf table auto
```

We’d like to request this be backported to Bullseye for compatibility
reasons.

Best,
Mike Waterman

[toc] | [next] | [standalone]


#83489

FromLuca Boccassi <bluca@debian.org>
Date2024-08-14 10:20 +0200
Message-ID<JbhoB-4UKQ-1@gated-at.bofh.it>
In reply to#83486

[Multipart message — attachments visible in raw view] — view raw

Control: tags -1 upstream
Control: close -1

On Tue, 13 Aug 2024 13:41:32 -0400 Mike Waterman <mwaterman@vultr.com>
wrote:
> Package: iproute2
> Version: 5.10.0-4
> Severity: wishlist
> 
> I'm requesting the addition of an `auto` option for VRF table ID
management
> in the iproute2 package on Debian. (Apologies if the package is
incorrect.)
> Currently, managing VRF table IDs manually can be cumbersome and
> error-prone. In Cumulus Linux, the `auto` option allows the OS to
handle
> allocating and releasing VRF table IDs automatically, which greatly
> simplifies network configuration and management. Having a similar
feature
> in Debian would be highly beneficial for users who manage complex
> networking setups.
> 
> For example, instead of this:
> 
> ```
> auto vrfexample
> iface vrfexample
>     vrf-table 1001
> 
> auto vrfexample2
> iface vrfexample2
>     vrf-table 1002
> ```
> 
> Or this:
> 
> ```
> ip link add vrfexample type vrf table 1001
> ip link add vrfexample2 type vrf table 1002
> ```
> 
> It'd be great to do this:
> 
> ```
> auto vrfexample
> iface vrfexample
>     vrf-table auto
> 
> auto vrfexample2
> iface vrfexample2
>     vrf-table auto
> ```
> 
> Or this:
> 
> ```
> ip link add vrfexample type vrf table auto
> ip link add vrfexample2 type vrf table auto
> ```
> 
> We’d like to request this be backported to Bullseye for compatibility
> reasons.

Please submit such feature requests upstream.

-- 
Kind regards,
Luca Boccassi

[toc] | [prev] | [next] | [standalone]


#83490 — Processed: Re: Feature Request: Add `auto` option for VRF table id management

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2024-08-14 10:20 +0200
SubjectProcessed: Re: Feature Request: Add `auto` option for VRF table id management
Message-ID<JbhoB-4UKQ-3@gated-at.bofh.it>
In reply to#83486
Processing control commands:

> tags -1 upstream
Bug #1078607 [iproute2] Feature Request: Add `auto` option for VRF table id management
Added tag(s) upstream.
> close -1
Bug #1078607 [iproute2] Feature Request: Add `auto` option for VRF table id management
Marked Bug as done

-- 
1078607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078607
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]


#83491

FromDaniel Gröber <dxld@darkboxed.org>
Date2024-08-14 10:50 +0200
Message-ID<JbhRD-4UV2-3@gated-at.bofh.it>
In reply to#83486

[Multipart message — attachments visible in raw view] — view raw

Hi Mike,

On Tue, Aug 13, 2024 at 01:41:32PM -0400, Mike Waterman wrote:

> It'd be great to do this:
> 
> ```
> auto vrfexample
> iface vrfexample
>     vrf-table auto
> 
> auto vrfexample2
> iface vrfexample2
>     vrf-table auto
> ```
> 
> Or this:
> 
> ```
> ip link add vrfexample type vrf table auto
> ip link add vrfexample2 type vrf table auto
> ```

If the ability to specify 'auto' in iproute2 isn't an absolute requirement
and iproute2 upstream rejects the idea then implementing this in ifupdown*
would also be possible.

I maintain ifupdown-ng in Debian (and am involved upstream) which already
has rudimentary [VRF support] I'd be happy to help you work on this, but
the first step really is to ask the iproute2 maintainer,
Stephen Hemminger <stephen@networkplumber.org>, to consider this feature.

[VRF support]: https://github.com/ifupdown-ng/ifupdown-ng/blob/main/executor-scripts/linux/vrf

Please CC me and the netdev mailinglist: netdev@vger.kernel.org and be sure
to include "iproute2" in the mail subject. That list serves many projects :)

I'd also recommend trimming your feature request down to the essentials of
what affects iproute2, kernel maintainers are busy people. Don't waste
their attention. I can help you draft something if you want.

--Daniel

[toc] | [prev] | [next] | [standalone]


#83493

FromMike Waterman <mwaterman@vultr.com>
Date2024-08-14 15:30 +0200
Message-ID<JbmeB-4XOz-7@gated-at.bofh.it>
In reply to#83491

[Multipart message — attachments visible in raw view] — view raw

Thanks, Daniel! I'm setting up to submit to netdev now. I shortened the
request as you suggested.


On Wed, Aug 14, 2024 at 4:44 AM Daniel Gröber <dxld@darkboxed.org> wrote:

> Hi Mike,
>
> On Tue, Aug 13, 2024 at 01:41:32PM -0400, Mike Waterman wrote:
>
> > It'd be great to do this:
> >
> > ```
> > auto vrfexample
> > iface vrfexample
> >     vrf-table auto
> >
> > auto vrfexample2
> > iface vrfexample2
> >     vrf-table auto
> > ```
> >
> > Or this:
> >
> > ```
> > ip link add vrfexample type vrf table auto
> > ip link add vrfexample2 type vrf table auto
> > ```
>
> If the ability to specify 'auto' in iproute2 isn't an absolute requirement
> and iproute2 upstream rejects the idea then implementing this in ifupdown*
> would also be possible.
>
> I maintain ifupdown-ng in Debian (and am involved upstream) which already
> has rudimentary [VRF support] I'd be happy to help you work on this, but
> the first step really is to ask the iproute2 maintainer,
> Stephen Hemminger <stephen@networkplumber.org>, to consider this feature.
>
> [VRF support]:
> https://github.com/ifupdown-ng/ifupdown-ng/blob/main/executor-scripts/linux/vrf
>
> Please CC me and the netdev mailinglist: netdev@vger.kernel.org and be
> sure
> to include "iproute2" in the mail subject. That list serves many projects
> :)
>
> I'd also recommend trimming your feature request down to the essentials of
> what affects iproute2, kernel maintainers are busy people. Don't waste
> their attention. I can help you draft something if you want.
>
> --Daniel
>

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web