dhcp issueshttps://gitlab.isc.org/isc-projects/dhcp/-/issues2019-09-17T18:57:52Zhttps://gitlab.isc.org/isc-projects/dhcp/-/issues/46ISC DHCP Relay: Vlan based DHCP Packets are not relayed.2019-09-17T18:57:52ZGhost UserISC DHCP Relay: Vlan based DHCP Packets are not relayed.---
name: Bug report
about: Create a report to help us improve
---
If you believe your bug report is a security issue (e.g. a packet that can kill the server), DO NOT
REPORT IT HERE. Please use https://www.isc.org/community/report-bug/...---
name: Bug report
about: Create a report to help us improve
---
If you believe your bug report is a security issue (e.g. a packet that can kill the server), DO NOT
REPORT IT HERE. Please use https://www.isc.org/community/report-bug/ instead or send mail to
security-office(at)isc(dot)org. If you really need to report it here, please set the confidential
field to true.
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Run dhcrelay with the following single server and client. Client shall use tagged vlan Interface for sending discover packet.
2. Client packet is not received by DHCP Relay as BPF is configured in such a way that only IP packets(0x0800 ethertype) are passed to DCHP Relay and VLAN ethertype(0x8100) is not handled by BPF and those packets are dropped.
**Expected behavior**
A clear and concise description of what you expected to happen:
DHCP Relay shall support VLAN based Discover also.
**Environment:**
- ISC DHCP version: 4.3.6
- OS: [Any Linux]
- Which features were compiled in
**Additional Information**
Add any other context about the problem here. In particular, feel free to share your config file and
logs from around the time error occurred. Don't be shy to send more logs than you think are
relevant. It is easy to grep large log files. It is tricky to guess what may have happened without
any information.
Make sure you anonymize your config files (at the very lease make sure you obfuscate your database
credentials, but you may also replace your actual IP addresses and host names with example.com
and 10.0.0.0/8 or 2001:db8::/32).
**Some initial questions**
- Are you sure your feature is not already implemented in the latest ISC DHCP version?
- Are you sure your requrested feature is not already impemented in Kea? Perhaps it's a good time
to consider migration?
- Are you sure what you would like to do is not possible using some other mechanisms?
- Have you discussed your idea on dhcp-users and/or dhcp-workers mailing lists?
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
It is very important to describe what you would like to do and why?
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context about the feature request here.
**Funding its development**
ISC DHCP is run by ISC, which is a small non-profit organization without any government funding or
any permanent sponsorship organizations. Are you able and willing to participate financially in the
development costs?
**Participating in development**
Are you willing to participate in the feature development? ISC team always tries to make a feature
as generic as possible, so it can be used in wide variety of situations. That means the proposed
solution may be a bit different that you initially thought. Are you willing to take part in the
design discussions? Are you willing to test an unreleased engineering code?
**Contacting you**
How can ISC reach you to discuss this matter further? If you do not specify any means such as
e-mail, jabber id or a telephone, we may send you a message on github with questions when we have
them.Outstandinghttps://gitlab.isc.org/isc-projects/dhcp/-/issues/36ISC DHCPv6 server not receving incoming DHCPv6 client info request message2019-07-25T13:03:16ZGhost UserISC DHCPv6 server not receving incoming DHCPv6 client info request messageI am running ISC DHCPv6 server and odhcp6c client is sending DHCPv6 info request message. Using tcpdump, I am able to see the client messages in the server ethernet port. But server is not responding/receiving incoming info request (not ...I am running ISC DHCPv6 server and odhcp6c client is sending DHCPv6 info request message. Using tcpdump, I am able to see the client messages in the server ethernet port. But server is not responding/receiving incoming info request (not seeing any log messages for the incoming DHCPv6 info req message). The ISC DHCPv6 version is 4.4.1 in centos7. Looks like that I am seeing following bug reported here in the below URL. can you please confirm ?? if it is related to this below bug, how to resolve it in my ISC DHCP server 4.4.1 version ??
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882250
Thanks,
Rajaram.Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/dhcp/-/issues/25unable to send option 66 in offer message2019-07-16T19:40:23ZGhost Userunable to send option 66 in offer messagei have included the following 2 lines in the dhcp.conf, but DHCP server is not sending option 66 in the offer for a received DISCOVER. my requirement is to must send the option 66 in OFFER, irrespective of the requested option list from ...i have included the following 2 lines in the dhcp.conf, but DHCP server is not sending option 66 in the offer for a received DISCOVER. my requirement is to must send the option 66 in OFFER, irrespective of the requested option list from client DISCOVER.
option boot-server code 66 = string;
option tftp-server-name "192.168.50.11";Thomas MarkwalderThomas Markwalder