Hi Greg, (everyone) > On 21 Jan 2025, at 19:26, Greg Troxel <gdt%lexort.com@localhost> wrote: > > Rin Okuyama <rokuyama.rk%gmail.com@localhost> writes: > >> Date: Wed, 4 Oct 2023 17:01:25 +0900 (1 year, 15 weeks, 5 days ago) > > I guess it's been longer than I thought! > >> I've committed igc(4) driver for Intel I225 and I226 series NICs with >> one-week delay ;) >> >> As noted in the commit log, it is still experimental; it lacks some >> logic for minor error >> handling paths, but it works almost fine for both LP64/ILP32 and >> big-/little-endian. > > How is this working, and are these still the caveats? The CVS logs > don't seem to show big changes -- more like some rough edges and bugs > fixed. I did not notice any caveats; on my system: > # ifconfig -v igc0 igc0: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > capabilities=0x3ff00<IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx> > capabilities=0x3ff00<UDP4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Rx,TCP6CSUM_Tx> > capabilities=0x3ff00<UDP6CSUM_Rx,UDP6CSUM_Tx> > enabled=0 > ec_capabilities=0x7<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU> > ec_enabled=0 > address: XX:XX:XX:XX:XX:XX > linkstate: up > media: Ethernet autoselect (2.5GBASE-T full-duplex,flowcontrol,rxpause,txpause) > status: active > input: 9445368 packets, 6693779031 bytes, 29 multicasts > output: 2973235 packets, 207568939 bytes, 12 multicasts There is a second igc interface on this machine, which I am not currently using. This is 80 days since the last reboot, which I performed after an update. Source: $NetBSD: if_igc.c,v 1.3.2.5 2024/06/21 10:54:50 martin Exp $ > Is anyone using this driver in an always-on mode, and is it reliable? So yes, and so far yes. (Thanks for that!) > Is anyone using this on a Protectli box, e.g. > https://protectli.com/product/vp2420/ > > Does this seem like a crazy plan, or ok, for one's home router? Cheers & HTH, -- khorben
Attachment:
signature.asc
Description: Message signed with OpenPGP