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

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

Well.. Actually when only one dhcp-server shared network is defined, service can be disbable with global disable for dhcp-server

So, in a very very simple config like this, user is not able to enable and disable dhcp-server with just a simple command?

To disable shared-network at least one shared network should be working. The second can be disabled without issues.

Error still present in 1.3.0-epa2 version:

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

An interesting thing that I get the error with that configuration:

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

Checked DHCPv6 server on version: VyOS 1.3.0-epa2

vyos@vyos# run show dhcpv6 server leases
Traceback (most recent call last):
  File "/usr/libexec/vyos/op_mode/show_dhcpv6.py", line 209, in <module>
    leases = get_leases(conf, lease_file, args.state, args.pool, args.sort)
  File "/usr/libexec/vyos/op_mode/show_dhcpv6.py", line 142, in get_leases
    leases = sorted(leases, key = lambda k: int(ip_address(k['ip'])))
  File "/usr/libexec/vyos/op_mode/show_dhcpv6.py", line 142, in <lambda>
    leases = sorted(leases, key = lambda k: int(ip_address(k['ip'])))
  File "/usr/lib/python3.7/ipaddress.py", line 54, in ip_address
    address)
ValueError: '2001:cafe:fefe:ffff::/64' does not appear to be an IPv4 or IPv6 address
[edit]

In T1513#108669, @c-po wrote:

Hi @SIN3R6Y,

any idea about an alternative CLI? This is beta functionality in VyOS 1.4 and we can change it arround

any idea about an alternative CLI? This is beta functionality in VyOS 1.4 and we can change it arround

As an option it is possible this workaround:
Install tshark and use this script https://george.mibloving.net/nivex/d6rm/raw/commit/701d49cce3a308aed0c3d89d47be7601178ea4c4/d6rm.py

rVYOSONEX47261d051759: bgp: evpn: T1513: VNI rt and rd are only supported under EVPN VRF.

Other test.
In same lab, pool for LAN subnet was modified:

More tests where done on version 1.3.0-epa1.
First, dhcp_server.py was modified as indicated.

@mickvav You can use &quot. Can you re-check it?
Tested on node VyOS 1.4-rolling-202110130217

Resolved using

Hi Viacheslav,

As I know, iptables works only in UTC time. And any workaround with recalculate Datetime will be affected incorrect behavior.

Tests were done using 1.2.8 and 1.3.0-rc6 version.
Same inconvenient present as described.
Problems is that a default route is added in table 220

As for me we shouldn’t allow to downgrade images. So there are no “downgrade migration scripts”. Each downgrade - good point to get a brick.
At least we should generate a warning.

PR for "crux": https://github.com/vyos/vyos-1x/pull/1029

Can you please retry with the latest 1.4 image as the EUI64 address generation changed and is now "stable/predictive" like on ethernet interfaces

@jestabro I will suggest a move from certbot
to https://github.com/go-acme/lego
This will give us some more flexibility with LE provision

let's do it but not in syslog section