disabling it on a per interface basis will still crash the OS if the register read/write is implemented improperly.

Reopened with status "Known issue" due to revert by PR 3177.

To clearify:

Reverted via https://github.com/vyos/vyos-1x/pull/3177

Using igb.EEE=0 or EEE=0 on the kernel commandline has no effect

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

Thanks for your reply.
But I have some questions about this situation.
Because it is something different with I knew "version meaning".

Tags show the code base at the step where the tag was added.
But binary can be changed since this time. For the same reason, you will not be able to build 1.1.8 or 1.2.1, etc. exactly with those binary that were on the step of tagging.
Close it as wonfix.

And remove set protocols static route xxx.xxx.0.0/0 interface pppoe0 unless you use set interfaces pppoe pppoe0 no-default-route.

set interfaces pppoe pppoe0 default-route-distance '255'

https://github.com/vyos/vyos-build/pull/538

Wouldnt PPPoE always assign IP dynamically?

In T6140#180604, @Apachez wrote:

Also since dynamic and not static IP is being used it would be handy if the DHCP exchange can be captured using tcpdump and do this both on the 1.3 where this works and on 1.4/1.5 where this doesnt work.

This way we can find out what the difference is in the request flow (from the client) but also in the response flow (from the server) - in case DHCP would be to be blamed on this behaviour.

Also since dynamic and not static IP is being used it would be handy if the DHCP exchange can be captured using tcpdump and do this both on the 1.3 where this works and on 1.4/1.5 where this doesnt work.

In T6140#180242, @pepe wrote:

Show this commands output if that happens:

show interfaces pppoe pppoe0
show ip route
show log pppoe

Show performance test results from versions 1.3 and 1.4

In T6140#180451, @dongjunbo wrote:

The Root Cause is this 'Static routes not working with PPPoE and VyOS 1.4'
https://forum.vyos.io/t/static-routes-not-working-with-pppoe-and-vyos-1-4/14102

I

Does the problem only appear after your 5am reboot every day?

The Root Cause is this 'Static routes not working with PPPoE and VyOS 1.4'
https://forum.vyos.io/t/static-routes-not-working-with-pppoe-and-vyos-1-4/14102

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

This likely because the global state policy being reintroduced was not accounted for in the firewall check in conf script. I'll check this week.

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

At least tech-support-archive.tgz MUST not copied between updates

yeah I had this problem too, also @Viacheslav I think you are right:

Show this commands output if that happens:

show interfaces pppoe pppoe0
show ip route
show log pppoe

In T6136#180149, @n.fort wrote:

And a simple note for your usage @wenzk
Change
set firewall ipv4 name WAN_IN rule 30 icmp
to this:
set firewall ipv4 name WAN_IN rule 30 protocol icmp

It looks like the local broken build.
At least it is not reproducible.
You can try to set it on some test VM to be sure if is it an issue with the node or the image itself.

In T6126#180142, @Viacheslav wrote:

Can you try the same link as in my example and provide the full output?

And a simple note for your usage @wenzk
Change
set firewall ipv4 name WAN_IN rule 30 icmp
to this:
set firewall ipv4 name WAN_IN rule 30 protocol icmp

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

Can you try the same link as in my example and provide the full output?

In T6126#180130, @Viacheslav wrote:

Could you show show version?

Could you show show version?

Never had this bug with 1.4.0-epa.

vyos@r1-right:~$ show ver
Version:          VyOS 1.4.0-epa1
Release train:    sagitta