Bug 202371 - Error message after the second DHCP request
Summary: Error message after the second DHCP request
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libdhcp
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Cantrell
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-13 19:26 UTC by Felix Schwarz
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-20 14:36:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Felix Schwarz 2006-08-13 19:26:12 UTC
Description of problem:
If one selects the back button after the dhcp request was answered (got an ip),
pump always fails and displays the error message "There was an error configuring
your network interface". Therefore one can not progress to the next screens, a
successful installation is only possible after a reboot.

How reproducible:
Always

Steps to Reproduce:
1. select an installation method which needs TCP/IP (e.g. http)
2. TCP/IP dialog: accept the standard selection, click ok
pump needs some time to time out for ipv6, gets an ipv4 ip.
3. HTTP configuration dialog: select "back"
4. you are in the TCP/IP dialog again - click next
"requesting ip" ...
=> Error message. 

Additional info:
In the console I see the following error message: 
add: failed - 17: Netlink Error (errno = File exists)
nic_configure: failed to add routes
DHCPv4 interface configuration failed
result of pumpSetupInterface is DHCP configuration failed - 1 Operation not
permitted

Comment 1 Jeremy Katz 2006-08-15 00:37:53 UTC
Note that pump is no longer being used by anaconda (hooray!)

I think David fixed this in libdhcp today, but assigning to him to make sure

Comment 2 Felix Schwarz 2006-09-20 07:21:44 UTC
verified fixed in FC6T3, requesting close.

Comment 3 David Cantrell 2006-09-20 14:36:08 UTC
Great, thanks.


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