Opened 12 years ago
Closed 11 years ago
#34 closed defect (worksforme)
DNS lookups take an extremely long time using R8169 driver
| Reported by: | ataylor | Owned by: | |
|---|---|---|---|
| Priority: | Feedback Pending | Component: | r8169 |
| Version: | 0.2.1 | Keywords: | |
| Cc: |
Description
Using the R8169 multimac driver, DNS lookups on my desktop PC (Athlon X4) take an unusually long time - usually at least four seconds and sometimes considerably longer. (Observed in SeaMonkey? 2.x but presumably affects other applications as well.)
Comparing on the adjacent computer on the same switch, sharing the same connection, using a Broadcom chipset with both the B57 and GenMAC drivers, the exact same DNS lookups there take less than one second.
This has occurred with all versions of the driver, both in my previous residence (in Japan) and my current one (in Canada). It also has occurred with two different r816x NICs (one onboard, one PCI) in this PC.
DNS entries do not seem to be cached for more than a few minutes, meaning that a new lookup is required almost every time the same site is accessed during a single session. With the delay occurring on every lookup, this is a significant headache.
Change History (3)
comment:1 Changed 12 years ago by
comment:2 Changed 11 years ago by
| Priority: | major → Feedback Pending |
|---|
A new driver has been released. You can try it to see if there are any changes to your issue.
comment:3 Changed 11 years ago by
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
No response from reporter. Closing ticket.
The R8169 driver is a low level packet driver and only transfers raw packets of data. It has no knowledge of what is in the packets. The R8169 driver cannot and does not distinguish between "DNS lookups" or any other type of packets, and cannot and does not treat any packet differently from any other packet.
I have never seen this type of behavior on any of my test systems, nor can I reproduce this behavior.
There is insufficient information provided. However, R8169 driver just doesn't have the ability to do what you are describing. It is more likely that you have some kind of setup issue on your system unrelated to the R8169 driver.