#28 closed defect (fixed)
r8169-0.0.3 dows not work with vbox/2's TAP driver
| Reported by: | Michaelhz | Owned by: | |
|---|---|---|---|
| Priority: | minor | Component: | r8169 |
| Version: | Keywords: | ||
| Cc: | multimac@…, ggamba@… |
Description
subject says it's all. VBOX/2 sessions do not have network access when useing the host unterface (TAP driver from willibald PROt.OS2).
Changing boot order does not help also.
No specific error messages from system.
Change History (7)
comment:1 Changed 12 years ago by
| Component: | common → r8169 |
|---|
comment:2 Changed 12 years ago by
comment:3 Changed 12 years ago by
| Cc: | multimac@… added |
|---|
comment:4 Changed 12 years ago by
| Cc: | ggamba@… added |
|---|
comment:5 Changed 12 years ago by
| Priority: | major → Feedback Pending |
|---|
Please try the current version and report back success or not.
comment:6 Changed 12 years ago by
| Priority: | Feedback Pending → minor |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
No response from reporter. Assumed fixed in current version.
comment:7 Changed 12 years ago by
Sorry for very late replay, since I have worked with a workaround. After installing 0.2.1 version of multimac, I've checked again. Works very well now.
thanks for your efforts.
Michael
Note: See
TracTickets for help on using
tickets.
The TAP driver is highly unreliable on most NICs - it usually only works reasonable
with Genmac driver or Intel PRO/100
Even with those NICs, it produces a major CPU overhead for all network traffic,
even if it doesn't go through that driver.
I don't think Multimac can do much here - it is the TAP driver, that needs fixing;
and unfortunately there is not much hope for that.