Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1357790 - DHCP package -p option not working
Summary: DHCP package -p option not working
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: dhcp
Version: 6.5
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Pavel Šimerda (pavlix)
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-19 07:48 UTC by Alka
Modified: 2016-07-19 14:27 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 14:27:27 UTC


Attachments (Terms of Use)

Description Alka 2016-07-19 07:48:46 UTC
Description of problem:
Hi,

In the ISC package of DHCP-4.3.4, we have an option of -p with two processes dhclient and dchrelay. But none is working fine. 

Version-Release number of selected component (if applicable):
ISC DHCP-4.3.4 package.

How reproducible:
initiate process with -p option and give any number to be treated as UDP port.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
Instead of using 67 and 68 ports packet should send on the mentioned port.

Additional info:

If any other information is needed free feel to ask.
Its very urgent for our project to understand.

Comment 2 Pavel Šimerda (pavlix) 2016-07-19 14:27:27 UTC
Red Hat Enterprise Linux version 6 is entering the Production 2 phase of its lifetime and this bug doesn't meet the criteria for it, i.e. only high severity issues will be fixed. Please see https://access.redhat.com/support/policy/updates/errata/ for further information.

This issue is fixed in Red Hat Enterprise Linux version 7.


Note You need to log in before you can comment on or make changes to this bug.