-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TAP & wintun adapters are "unknown" #197
Comments
Hi,
On Sun, Oct 11, 2020 at 08:42:46AM -0700, TinCanTech wrote:
Using 2.5-rc2-I601-2-x86.msi, the install all works for me (I know there are some things going on under the hood but I have not investigated those).
But just for the record, the network adapters are "unknown".
Do I understand you correctly, if you do a fresh install of RC1, this
does not happen, but with RC2 it does?
There have been a few changes in the tap and msm and openvpnmsica
side of things, but I had assumed that nothing would affect "what
windows thinks the resulting adapter is like" (and, if I read the
commit log right, only the "MAC address" stuff is in RC1 -> RC2).
@selvanair: could this be related to the (new) absence of "MAC"?
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany gert@greenie.muc.de
|
I think this must have started when we tagged the adapter as virtual (not ethernet) around release 2.4.8. It used to show up as an "Ethernet adapter" before then. The device manager will list it a "Tap-Windows Adapter v9" device. |
@cron2 - I rolled back to 2.4.9 - status 2.4.7
@selvanair probably 👍 |
Hi,
On Sun, Oct 11, 2020 at 01:36:20PM -0700, TinCanTech wrote:
2.4.9 - status `unknown`
So, what Selva said - we changed the adapter type from "Ethernet" to
"virtual" quite a while back (2.4.8).
I can't seem to find the relevant PR, but here's the commit
OpenVPN/tap-windows6@c869bc9
gert
…--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany gert@greenie.muc.de
|
2.4.8 may have been neglected ... |
I just built |
@TinCanTech is this issue still relevant or has it been fixed in the mean time? |
@flichtenheld With 2.6_beta1, still
Note: DCO in topology NET30 .. |
As discussed earlier, this appears to have started since we changed IfType in the tap driver from ETHERNET to IF_TYPE_PROP_VIRTUAL (== Proprietary Virtual/Internal). In retrospect, not surprising as it used to show up as an Ethernet adapter but is now "Proprietary" which is arguably same as "Unknown". We have not touched it since, so no change is expected in 2.6. I would say just read "Unknown" to mean "Proprietary", and let it be. The description says what it is. |
|
@selvanair did you have a chance to try dco-win driver? have you noticed any difference? difference in performance? As dco is the default now, my connection(s) have been using it, but my usage of VPN on Windows is only for some routine remote access, nothing performance critical. I heard some good feedback from others though. As for this "Unknown adapter" thingie, dco-win could probably set the IfType as IF_TYPE_TUNNEL (131) instead of IF_TYPE_PROP_VIRTUAL (53)? |
Using 2.5-rc2-I601-2-x86.msi, the install all works for me (I know there are some things going on under the hood but I have not investigated those).
But just for the record, the network adapters are "unknown".
The text was updated successfully, but these errors were encountered: