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

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

PR for 1.3 https://github.com/vyos/vyos-1x/pull/1813

PR for 1.3 https://github.com/vyos/vyos-1x/pull/1812

okay, so with https://vyos.dev/T4997 in place (tested via my custom build https://github.com/b-/vyos-build-action/releases/tag/v1.4-rolling_bri_add-dhcp-user-hooks ) and the following file in /config/scripts/dhcp-client/post-hooks.d/set-addrgroup

#!/bin/sh
#
# /config/scripts/dhcp-client/post-hooks.d/set-addrgroup

https://github.com/vyos/vyos-1x/pull/1810

Reading more of the fancy internal scripting going on inside VyOS, there's already both a place to put this script (that would cause it to automatically be called by dhclient upon a new address), _and_ it sets a bunch of variables for us so I don't have to hac hac hac parse output that really isn't intended to be parsed. https://github.com/vyos/vyos-1x/tree/current/src/etc/dhcp/dhclient-exit-hooks.d

This is quiet interesting as container memory defaults to 512.

In T2196#125917, @lue30499 wrote:

This feature would be very helpfull for hairpin nat as we can see from the mentions.
Might also be helpfull for ipv6 as well.
I am aware its a different product but edgeos from ubiquiti does something like this (looks to be a managed address group that populates dynamically) for nat and fw:

destination {
    group {
        address-group ADDRv4_eth0
    }
}

I just want to really strongly second this issue — if this feature isn't added and I can't find a good workaround, I won't be able to stick with VyOS :(

Thanks @Viacheslav, that makes sense.

Take a look at this T4165
Maybe the same issue but per rule. Different order of "comment"

Thanks for reporting.
We will take a look at it.

I have the same issue

@zsdc @v.huti this requires your attention

Some adjustments made for command output; re-testing for PR.

Running smoketests; PR's to follow:

eth0 -> PPPoE (Primary link)
eth1 -> DHCP (Backup link)

if I use default-route 'auto' for pppoe then default route via pppoe is not getting configured. That's why I am defining the static default route for pppoe with default-route 'none' option.

I have two wan links as following-

It looks like mine issue with wan load balancing - reply for dnat-ed packets from secondary interfaces was sent by vyos from "primary" https://phabricator.vyos.net/T4587 . Could you dump traffic and check that possibility

@fernandolcx Will be present in the next rolling release, could you test it (after 20230209)?

@c-po Do you have any idea for CLI?

@skoenman Could you write some examples of configuration?

@Usman there is a root task for op-mode rewriting https://phabricator.vyos.net/T4564
https://github.com/vyos/vyos-1x/blob/1042fc32c371a74f048ffaf9a551b5d13c227f45/src/op_mode/bgp.py#L77-L80

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

@Viacheslav Thanks, that works great!

@Usman You have to update to the latest rolling.
https://vyos.net/get/nightly-builds/

Thanks for the reply.

Hi perhaps it is better to get JSON format