[dhcrelay] Unsupported device type 512 for "pptp-vpn"
Open
Nobody has claimed this yet.
release/19.07
stale
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Maintainer: @<github-user> (find it by checking history of the package Makefile)
Environment: (lantiq, xrx200 (FB7360-SL), 19-07)
Description:
as defined in the config (uci) we cant use ppp0 interfaces as upstream interfaces ex: for wan.
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0.4/9c:c7:a6:e8:63:28
Sending on LPF/eth0.4/9c:c7:a6:e8:63:28
Listening on LPF/eth0.3/9c:c7:a6:e8:63:28
Sending on LPF/eth0.3/9c:c7:a6:e8:63:28
Listening on LPF/eth0.2/9c:c7:a6:e8:63:28
Sending on LPF/eth0.2/9c:c7:a6:e8:63:28
Listening on LPF/eth0.1/9c:c7:a6:e8:63:28
Sending on LPF/eth0.1/9c:c7:a6:e8:63:28
Unsupported device type 512 for "pptp-vpn"
If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug. These pages explain the proper
process and the information we find helpful for debugging.
exiting.
root@fb7360:~#
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
Check the package Makefile history to identify the maintainer and locate the dhcrelay package entry point. Reproduce the configuration with a ppp0 upstream interface on the reported OpenWrt environment, then determine whether the unsupported device type is handled; done means dhcrelay starts and relays traffic through ppp0.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100