WCH's official forum confirmed on Sep 20 that the CH32H417 can run lwIP, though no official example ships yet. Here is what the in-house WCHNET stack gives you today, and the practical path to bring lwIP up on the H417's RGMII-based Ethernet.
The CH32H417 is WCH's dual-core RISC-V flagship around USB 3.0 SuperSpeed, and its Ethernet side is equally relevant for industrial designs: the MAC exposes an RGMII interface for an external PHY, and WCH has published an official RGMII reference design with example code (forum thread 161112) that covers the hardware bring-up side - PHY choice, reference clocking, magnetics and the matching MAC initialization.
WCHNET, the stack inside the EVT examples, is the friction-free option: it is maintained by WCH, matches the EVT code line by line, and covers the common TCP/UDP server-client workload out of the box. lwIP is the industry standard: richer protocol coverage, an active upstream, and - the argument that usually decides it - one networking API across your entire MCU fleet instead of one stack per vendor.
A pragmatic split we see working: keep WCHNET where an EVT-derived product ships fast, and bring up lwIP when you need a common networking layer across several families, for example CH32V307 (Gigabit MAC), CH32V317 (integrated 10M PHY) and CH32H417 in the same product line.If the product is a single-family design with standard TCP/UDP traffic, WCHNET still delivers example parity and vendor support for free. Porting lwIP costs engineering weeks; make sure you are buying something with that price.
For gateway-class designs that need more than one Ethernet port, the pattern we use on our own open-riscv.com reference designs pairs two RGMII interfaces with external PHYs to expose physically isolated port groups - the same approach works on K1-based Linux gateways and WCH MCU-class devices, depending on where the line between OS-managed and firmware-managed networking sits in your architecture. Sources: