@FlinchX
Thanks for the clarifications, it looks like the r8169 driver is not really functional in this 2 cards scenario and the r8168 should be used instead ATM. Your English is good, don't worry about it, I'm also not a native speaker. Regarding your privacy concerns, you're not the only one and paranoia is just heightened awareness, remember that
I was suggesting to get in touch with the developers yourself just because they might ask some HW details that I couldn't provide as I don't own any r816x NICs. Anyways, I just sent an E-mail to the two developers (originators) found in the header of the source file and asked them politely to take a look at this thread and the other one related that I referenced above.
https://github.com/torvalds/linux/bl...ealtek/r8169.c
@bassmadrigal
EDIT>
The r8168 driver you referred to looks to be maintained by a single contributor that takes it from Realtek. I was under the impression that Realtek stopped the development on it and that the r8169 took it's place:
https://git.slackbuilds.org/slackbui...b2110e283e9d4a
https://github.com/mtorromeo/r8168/
Related to the r8169 kernel supported driver, it is actively maintained but it's a little difficult to go through all the changes and try to relate them with the issues observed.
https://github.com/torvalds/linux/co...ealtek/r8169.c
I'm concerned about this driver because it looks like the Realtek chips that require this driver are getting used more often in Motherboards / NICs.