What I am curious about: Given that code exists that works better than what’s shipping, what keeps the FreeBSD driver team from using it? There has to be a good reason, given how long re(4) has been in this state. Looking at the mailing lists and various discussions showed me people compiling the Realtek code, but I haven’t found anything that explains why that code isn’t or can’t be used in FreeBSD out of the box.
convention most likely, combined with trust issues.
realtek has a rep for not having the most stable NICs, and devs don't wanna waste their (often free) time fixing things that work intermittently, leaving mucking about with non standard configs to people who have sufficient ability to ignore recommendations.
if the freebsd community was as expansive as linux, it might be different, but withous zerg hives worth of devs they will pick and choose hardware they believe is worth their time. it's the same reason these forums highly recomend server grade gear.
this drivers worked for me, I used 12.0, ver 1.96.04, just coppy it to /boot/kernel/if_re.ko, "chmod 555 /boot/kernel/if_re.ko", and then load it under System->Tunables.
this drivers worked for me, I used 12.0, ver 1.96.04, just coppy it to /boot/kernel/if_re.ko, "chmod 555 /boot/kernel/if_re.ko", and then load it under System->Tunables.
Well do not fully know as I only use this for management and sole lightweight back-ups and stuff, I use 10G cards for real trafic, just sent 100G+ back-ups over the interface and trafic looks like this:
this is to a pool running dedup and compression and some vm´s
Main thing is that the interface does not lock up anymore when pushing traffic over it as it was driving me crazy.
The copy was done by Veeam from one pool to another, and pool max sync write is around 140MB/s(due to crappy optane on the SLOG, will replace in the near future) not counting dedup overhead.
Hello @CrimsonMars,
I was facing the same issue with my homemade build. and replaced it with 1.96.04 andit looks like the nic is stable now and not locking up any more.
That's incorrect. You need to do this through tunables, or it won't survive.
Everyone knows there's a crappy re driver included. It's gotten better, I guess, but this thread is really about people trying to mash in drivers that actually work for their particular cards.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.