Opened 10 years ago
Last modified 4 years ago
#482 assigned Bug / Defect
Win64 client NDIS6 does not shut down TAP interface clearly upon disconnect
| Reported by: | Nfisher | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | tap-windows6 | Version: | OpenVPN 2.3.5 (Community Ed) |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | NDIS6 TAP windows |
| Cc: |
Description
I have openvpn-2.3.5-i602-x64 installed on Win8.1Ent (with latest updates).
I have multiple connection profiles and single TAP interface.
Client is being used in 'dev tap' mode.
When I disconnect from one server and connect to another, the IP settings on TAP interface are not applied properly but look like left intact from previous connection.
The workarounds are:
- Use dedicated TAP adapter for each connection profile
or
- Manually disable and reenable the TAP adapter after disconnection using 'adapter settings' windows snap-in.
Change History (3)
comment:1 Changed 9 years ago by
comment:2 Changed 9 years ago by
| Component: | Generic / unclassified → tap-windows6 |
|---|---|
| Keywords: | windows added |
| Owner: | set to jamesyonan |
comment:3 Changed 4 years ago by
| Owner: | jamesyonan deleted |
|---|---|
| Status: | new → assigned |
We do take care to remove configs at disconnect (*and* overwrite whatever might have been there before).
It is always possible that there is a bug, but without a log, I can not see anything.
Also, 2.3.5 is ancient, so it's very likely that bugs there have long been fixed.
If this can be reproduced with 2.4.9 or 2.5.0 (due in a few weeks), please report again. With a log.
Hi,
can you provide a log file that shows what is happening (using the same tap adapter), and the client config used for that (without key, cert, ca, tls-auth, of course).