@raphielscape Could you re-test it?

vyos@r14# set interfaces ethernet eth0 ip adjust-mss 
Possible completions:
   clamp-mss-to-pmtu    Automatically sets the MSS to the proper value
   <500-65535>          TCP Maximum segment size in bytes

Fixed

S>* 0.0.0.0/0 [210/0] via 192.0.2.1, eth1, weight 1, 00:02:31
C>* 192.0.2.0/24 is directly connected, eth1, 00:02:31
C>* 192.168.122.0/24 is directly connected, eth0, 00:04:09

@Viacheslav, thanks.
Already fixed in roling

vyos@vyos# set service pppoe-server interface eth0 vlan-range 
Possible completions:
   start-end            VLAN monitor range for the automatic creation of vlans (e.g. 1-4094)

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

Any chance you can test this on 1.4 rolling image?

Package and CI available https://dev.packages.vyos.net/?dir=repositories/current/pool/main/t/telegraf && https://ci.vyos.net/job/vyos-build-telegraf/job/current/

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

You can get duid data from python
https://github.com/vyos/vyos-1x/blob/44b1bdd3273dce4e74a5474c401ac7107950635b/src/op_mode/show_dhcpv6.py#L95-L97
Replace format_hex_string(lease.host_identifier_string) to `lease.duid
and lease_display_fields['iaid_duid'] = 'IAID_DUID'
https://github.com/vyos/vyos-1x/blob/44b1bdd3273dce4e74a5474c401ac7107950635b/src/op_mode/show_dhcpv6.py#L44

I've been running TAYGA inside VyOS with absolutely no problems for the last several years.

I would suggest going with tayga if this feature is planned to be implemented.

In T2664#126031, @Viacheslav wrote:

As we have the 1.3 LTS release (where it is fixed) I propose to close it.
It is a big change for 1.2 that we should avoid.

As we have the 1.3 LTS release (where it is fixed) I propose to close it.
It is a big change for 1.2 that we should avoid.

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

I downloaded

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

Output plugins that we use in 1.4

"github.com/influxdata/telegraf/plugins/outputs/azure_data_explorer"
"github.com/influxdata/telegraf/plugins/outputs/influxdb_v2"
"github.com/influxdata/telegraf/plugins/outputs/prometheus_client"
"github.com/influxdata/telegraf/plugins/outputs/http"

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

@c-po I opened https://github.com/vyos/vyos-documentation/pull/805

Feature backport: https://github.com/vyos/vyos-1x/pull/1400

@dsummers I strongly believe we should not publish bleeding edge HEAD revisions and stick bleeding edge releases only.

After doing some research, it appears this is a known bug in PowerDNS Recursor 4.7 (amazing to me).

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:

Confirmed working on "current" branch.

Is anyone else seeing this same problem? It is keeping me from being able to use VyOS in an IPv6-only environment.

OK, I just noticed the merge to "current" branch.