Bug 613159 - dhcp client can not obtain address
Summary: dhcp client can not obtain address
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-09 20:41 UTC by Ferry Huberts
Modified: 2010-07-11 14:27 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-11 14:27:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ferry Huberts 2010-07-09 20:41:43 UTC
Description of problem:
with the new kernel the new dhcp client can not obtain an address


Version-Release number of selected component (if applicable):
new kernel (non working): 2.6.33.6-147.fc13.x86_64
old kernel (working): 2.6.33.5-124.fc13.x86_64
dhclient: 12:4.1.1-23.P1.fc13.x86_64


How reproducible:
always

Steps to Reproduce:
1. boot
2.
3.
  
Actual results:
no networking address, interface does not come up

Expected results:
normal networking

Additional info:


setup:
I have a bridge setup in which eth0 is connected to br0, and br0 is connected to a lot of VMs


ifcfg-eth0
==========
DEVICE=eth0
HWADDR=xxxxxxxxxxxxx
ONBOOT=no
TYPE=Ethernet
#BOOTPROTO=dhcp
BRIDGE=br0
DEFROUTE=yes
NAME="System eth0"
UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03
IPV6INIT=yes
IPV6_AUTOCONF=no
IPV6_DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
DHCP_CLIENT_ID=storage

ifcfg-br0
=========
DEVICE=br0
BOOTPROTO=dhcp
ONBOOT=yes
TYPE=Bridge
DELAY=0
STP=on

Comment 1 Ferry Huberts 2010-07-11 14:27:54 UTC
Sorry for this report.

I forgot that I was running a custom e1000 driver because of report
https://bugzilla.redhat.com/show_bug.cgi?id=528234

I recompiled the driver for the new kernel and it worked again

can close. but please DO work on report
https://bugzilla.redhat.com/show_bug.cgi?id=528234


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