Technically according to IEEE autoneg is mandatory when doing 1Gbps and above using RJ45.

Hi, Yes I get the same if I try that but mine is already 2500 full.

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

The fix is still work in progress, I need to dig deeper into accel-ppp history that predates the github repo. Not sure why some code was commented out over 10 years ago, IPV6CP restart timer is not stopped and disconnects in 3 seconds. Looking at older history in sourceforge but not sure if the answer is even there, sourceforge seems to have lost old history before 2011 (broken links).

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

reproduced on:
Version: VyOS 1.5-rolling-202409160007
Version: VyOS 1.4-stable-202409170309

I can not immediately recreate the issue:

SteveP - Even when using 2.18.1 - when I try to force the speed of the USB interface to 2500 (and duplex to full, as then required), I see error messages on the commit. See below. This happens with multiple 2.5G capable interfaces.

i retested this issue
actual for:
Version: VyOS 1.3-stable-202409270542 (DHCP Relay Agent 4.4.1)

This PR https://github.com/vyos/vyos-1x/pull/3311 has fixed the issue.
Tested in 1.4.0 and latest rolling release. 1.5-rolling-202409250007

Yes I am overloaded (who isn't), and yes I plan to make a PR but want to test it a bit more first, to be reasonably sure it causes no regression (potential resource leak if something allocated by the incomplete IPv6 configuration is not freed - not sure enough about accel-ppp internals). I'm working to rebuild replacement accel-ppp package (based on the same commit as in equuleus with just my patch applied, no other changes) and run it for a week or two while watching memory usage. Testing a fairly complex config in production environment, so not brave enough to try rolling or even sagitta just yet.

@jmaslak It's been a while since you reported this bug and we've been through multiple FRR updates since then. Could you check if the issue is fixed in the latest nightly build, or attach a config that triggers that behavior if it still exists?

I've merged this into the feature request because the real issue is that we don't have dynamic hairpin NAT yet, while this behavior for "static" NAT is not wrong. We'll get to it.

@marekm Do you plan to make a PR?
If you are overloaded, we can import a patch ourselves, but a PR would be nice.

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

I am currently using 2.18.1 with kernel 6.6.51-vyos

I am currently using 2.18.1 with kernel

we've added this new feature called Server bridge , it's available in 1.5 and backported 1.4: