Wrong device name when using dev and dev-type
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 467
- PR merge metrics
- No merged PRs in 30d
Description
When using dev-type in a configuration, dev appears to be ignored. For example, I tried a configuration containing
dev ovpn-stuff
dev-type tun
and the created device is named tun0 instead of ovpn-stuff. If I exclude dev-type, it fails because ovpn-stuff does not start with either tun or tap.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the configuration with dev ovpn-stuff and dev-type tun, then trace how these options are processed when the device is created. Compare the resulting tun0 name with the requested ovpn-stuff; done means valid configurations preserve the requested device name while still supporting device types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100