In T9197#281816, @c-po wrote:

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

In T9197#281380, @c-po wrote:

@srnoth I will pick the task so I can track it on my stack.

@Viacheslav / @c-po any thoughts on the above issue? I'd be happy to draft a PR based on whichever path you recommend.

Test results: rebuilt vyos-linux-firmware against the IWLMLD-enabled kernel (rolling @ 6.18.44) with the missing files included, rebuilt the ISO, and the BE200 now works end-to-end on the same hardware from the original report:

Follow-up: I test-built an ISO from rolling with the merged fix (e14a489) to validate on the same BE200 hardware. The initial PR works... the card is now properly detected:

In T9197#274465, @Viacheslav wrote:

@srnoth Would you like to claim the task and submit a PR?

Went with the pN suffix as suggested by @c-po. Port 0 keeps the base name for backward compatibility, ports 1+ get pN appended.

@c-po fair enough. That would end up looking like this though:
usb0b1.4.1p1.0
usb0b1.4.1p1.0p1
usb0b1.4.1p1.0p2
usb0b1.4.1p1.0p3

@Viacheslav any preference on which syntax?

*Edited to remove an "option" I don't have a way to code.

In T8211#248553, @Viacheslav wrote:

Hey @srnoth would you like to create a PR?

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.

@Viacheslav per your suggest in the discussion thread I ran the following:

@c-po for simplicity I created a barebones vyos VM to route between two subnets.

Still present in the 1.2.6-S1 release. Makes vyos unusable in environment with DHCP WAN IPs and using the DNS forwarder for specific domains. Those domain forwarders are lost every time the ISP renews the public IP.