I think its a bit odd to completely disable EEE where the solution would be to disable EEE by default but having the config option to adjust for EEE if wanted.

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

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

Maintainers agreed that we will disable EEE by default - we are a router pushing packets.

PR for 1.5 https://github.com/vyos/vyos-1x/pull/2687

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

In T5721#168743, @giuavo wrote:

I have followed your suggestion: a fresh VyOS install in a VM and tried to load the current configuration. Here are the errors I get:

[ service dns dynamic name service-ovh-eth1-11-web web-options url checkip.dyndns.com ]
"checkip.dyndns.com" is not a valid URL


[ service dns dynamic name service-ovh-eth1-11-web web-options url checkip.dyndns.com ]
Invalid HTTP(S) URL format

[[]] failed

@indrajitr Could you take a look? As I remember you are working on it.

PR for 1.5 https://github.com/vyos/vyos-1x/pull/2683

PR for VyOS 1.5 https://github.com/vyos/vyos-1x/pull/2682 which will also be backported to 1.4

I have followed your suggestion: a fresh VyOS install in a VM and tried to load the current configuration. Here are the errors I get:

Sometimes container is not cleaned properly, see also https://github.com/containers/podman/issues/15708

That means I should create a new VyOS instance and then load my current configuration in order to spot any migration error. I can try that.

On the newest system you can use load /path/to/config

The same task T5712

In T160#168646, @danielpo wrote:

That's great!
I tried running make interface_definitions in vyos-1x and copy in the changed files into my vyos install, but the files kept disappearing when rebooting, and couldn't figure out how to build an iso with your vyos 1-x repo.

So I wil try it when there is a vyos rolling iso available.

In T3316#167494, @indrajitr wrote:

set service dhcp-server dynamic-dns-update
set service dhcp-server hostfile-update
set service dhcp-server shared-network-name LAN authoritative
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 default-router '192.168.1.1'
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 domain-name 'home'
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 name-server '192.168.1.1'
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 range 0 start '192.168.1.120'
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 range 0 stop '192.168.1.230'
set service dhcp-server shared-network-name LAN subnet 192.168.1.0/24 static-mapping ...
...

I also notice that ddclient has a similar problem.

ddclient[1710]: FAILED:   Unable to obtain information for 'pppoe0' -- missing ip or ifconfig command

This might be a problem that's specific to me. I don't know why every systemd start too early.

This was fixed recently for dynamic interfaces like pppoe. @Zen3515 can you please try with 1.5-rolling-202312171632?

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

I have tried to move to the rolling version vyos-1.5-rolling-202312231415-amd64.

Actually, it doesn't! :(
{F4050258}

Latest 1.5 rolling ISO has it

That's great!
I tried running make interface_definitions in vyos-1x and copy in the changed files into my vyos install, but the files kept disappearing when rebooting, and couldn't figure out how to build an iso with your vyos 1-x repo.

I have moved on. The description here is vague and probably doesn't make any sense.

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

set interfaces ethernet eth0 address '192.168.122.14/24'
set interfaces ethernet eth0 address '192.168.122.10/24'
set interfaces ethernet eth2 address '2001:db8::1/64'

This can be reproduced by:

In T5851#168608, @Viacheslav wrote:

Has the interface index changed?

Has the interface index changed?

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

Also I found this log

It binds port 647

set interfaces dummy dum8765 address '192.0.2.1/24'

After update it cannot pass the smoketest

vyos@r4:~$ /usr/libexec/vyos/tests/smoke/cli/test_service_dhcp-server.py
test_dhcp_exclude_in_range (__main__.TestServiceDHCPServer.test_dhcp_exclude_in_range) ... ok
test_dhcp_exclude_not_in_range (__main__.TestServiceDHCPServer.test_dhcp_exclude_not_in_range) ... ok
test_dhcp_failover (__main__.TestServiceDHCPServer.test_dhcp_failover) ... FAIL
test_dhcp_multiple_pools (__main__.TestServiceDHCPServer.test_dhcp_multiple_pools) ... ok
test_dhcp_relay_server (__main__.TestServiceDHCPServer.test_dhcp_relay_server) ... ok
test_dhcp_single_pool_options (__main__.TestServiceDHCPServer.test_dhcp_single_pool_options) ... ok
test_dhcp_single_pool_range (__main__.TestServiceDHCPServer.test_dhcp_single_pool_range) ... ok
test_dhcp_single_pool_static_mapping (__main__.TestServiceDHCPServer.test_dhcp_single_pool_static_mapping) ... ok

Cannot pass smoketest

vyos@r4:~$ /usr/libexec/vyos/tests/smoke/cli/test_service_dhcp-server.py
test_dhcp_exclude_in_range (__main__.TestServiceDHCPServer.test_dhcp_exclude_in_range) ... ok
test_dhcp_exclude_not_in_range (__main__.TestServiceDHCPServer.test_dhcp_exclude_not_in_range) ... ok
test_dhcp_failover (__main__.TestServiceDHCPServer.test_dhcp_failover) ... FAIL
test_dhcp_multiple_pools (__main__.TestServiceDHCPServer.test_dhcp_multiple_pools) ... ok
test_dhcp_relay_server (__main__.TestServiceDHCPServer.test_dhcp_relay_server) ... ok
test_dhcp_single_pool_options (__main__.TestServiceDHCPServer.test_dhcp_single_pool_options) ... ok
test_dhcp_single_pool_range (__main__.TestServiceDHCPServer.test_dhcp_single_pool_range) ... ok
test_dhcp_single_pool_static_mapping (__main__.TestServiceDHCPServer.test_dhcp_single_pool_static_mapping) ... ok

if you are running the netfilter implementation, I think the iptables mangle is handled automatically.(I verified this by changing my Jool to netfilter and removed these lines below:

ip6tables -t mangle -A PREROUTING --destination 64:ff9b::/96 -j JOOL --instance default
iptables  -t mangle -A PREROUTING --destination 172.21.8.202 -p tcp --dport 1:65535 -j JOOL --instance default
iptables  -t mangle -A PREROUTING --destination 172.21.8.202 -p udp --dport 1:65535 -j JOOL --instance default
iptables  -t mangle -A PREROUTING --destination 172.21.8.202 -p icmp -j JOOL --instance default

I stil haven't tried nat64, but quick config example, for nat64 for single ipv6 address is not allowed by our cli:

Sure, I will do that and report here the outcome.

@danielpo marking IPv6 packet is possible

set policy route6 PBR6 interface 'eth1'
set policy route6 PBR6 rule 100 set mark '4'
set policy route6 PBR6 rule 100 source address '2001:db8::/64'

Some users have issues https://forum.vyos.io/t/grub-menu-fails-to-load-on-serial-only-devices-with-no-kvm/

@giuavo , can you please test in latest rolling release

All good from my side! Just did quick test and it seems to work as expected. Thanks @n.fort

Is it possible to add support for policy routing?

Configuration shared seems to work correctly on latest version: