User Details
- User Since
- Jan 14 2021, 3:02 AM (296 w, 3 d)
Tue, Sep 1
@Viacheslav / @c-po any thoughts on the above issue? I'd be happy to draft a PR based on whichever path you recommend.
Aug 11 2026
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:
Apr 16 2026
Apr 6 2026
Went with the pN suffix as suggested by @c-po. Port 0 keeps the base name for backward compatibility, ports 1+ get pN appended.
Mar 26 2026
@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
Feb 2 2026
@Viacheslav any preference on which syntax?
Jan 29 2026
*Edited to remove an "option" I don't have a way to code.
Jan 27 2026
Jul 8 2022
Jun 17 2021
@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.
Jun 12 2021
Jan 18 2021
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.