First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 133905
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Roy Marples (RETIRED) <uberlord@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Jan Spitalnik <jan@spitalnik.net>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 133905 depends on: Show dependency tree
Bug 133905 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-05-20 15:45 0000 
Hi,

after upgrading ISC's dhcp to 3.0.4 (including -r1), dhcp is broken for most of
dhcp clients (works with dhclient), windows,xbox,etc are not able to get IP...

This is what dhclient reports to the dhcp offer:
May 18 16:17:21 spity-nb dhclient: DHCPREQUEST on wifi0 to 255.255.255.255 port
67
May 18 16:17:21 spity-nb dhclient: DHCPACK from 192.168.0.1
May 18 16:17:21 spity-nb dhclient: dhcp-lease-time: 4 extra bytes
May 18 16:17:21 spity-nb dhclient: dhcp-lease-time: 4 extra bytes
May 18 16:17:21 spity-nb dhclient: bound to 192.168.0.15 -- renewal in 19301
seconds

Notice the "dhcp-lease-time: 4 extra bytes" message.
Other clients keeps asking for IP address, presumably because the dhcp packet
being sent is non-standard.

------- Comment #1 From Roy Marples (RETIRED) 2006-05-21 08:32:50 0000 ------- 
http://marc.theaimsgroup.com/?l=dhcp-users&m=114772981510108&w=2

The problem is known upstream - hopefully fixed in dhcp-3.0.5 or if I can get a
patch then sooner. For the time being I've masked 3.0.4

------- Comment #2 From Bjarke Istrup Pedersen 2006-06-27 22:36:21 0000 ------- 
Any reason for package.mask'ing it when it's only broken on amd64? (I use it on
x86 without any problems)
Why not just keyword it -amd64?

Bjarke

------- Comment #3 From Roy Marples (RETIRED) 2006-06-28 02:50:57 0000 ------- 
OK, I've got a patch for this ready.

------- Comment #4 From Roy Marples (RETIRED) 2006-06-28 02:51:53 0000 ------- 
Fixed in dhcp-3.0.4-r2
First Last Prev Next    No search results available      Search page      Enter new bug