Bug 448170 - autoip doesn't work
Summary: autoip doesn't work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 9
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-23 21:40 UTC by Roman Kagan
Modified: 2008-11-02 22:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-11-02 22:03:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
do not ignore the return value from nm_device_new_ip4_autoip_config() (664 bytes, patch)
2008-05-23 21:40 UTC, Roman Kagan
no flags Details | Diff

Description Roman Kagan 2008-05-23 21:40:24 UTC
Description of problem:
When a network interface is set up in NM to use link-local address, NM tries to
get one but fails.

According to /var/log/messages, it passess successfully through all
configuration steps, but fails to assign the resulting address:

<info>  Activation (eth0) starting connection 'Auto Ethernet'
<info>  (eth0): device state change: 3 -> 4
<info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
<info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started...
<info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
<info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
<info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting...
<info>  (eth0): device state change: 4 -> 5
<info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful.
<info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
<info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete.
<info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
<info>  (eth0): device state change: 5 -> 7
<info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
<info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
<info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
<info>  autoip: Sending probe #0 for IP address 169.254.15.235.
<info>  autoip: Waiting for reply...
<info>  autoip: Sending probe #1 for IP address 169.254.15.235.
<info>  autoip: Waiting for reply...
<info>  autoip: Sending probe #2 for IP address 169.254.15.235.
<info>  autoip: Waiting for reply...
<info>  autoip: Sending announce #0 for IP address 169.254.15.235.
<info>  autoip: Waiting for reply...
<info>  autoip: Sending announce #1 for IP address 169.254.15.235.
<info>  autoip: Waiting for reply...
<info>  autoip: Sending announce #2 for IP address 169.254.15.235.
<info>  autoip: Waiting for reply...
<info>  (eth0): device state change: 7 -> 9
<info>  Marking connection 'Auto Ethernet' invalid.
<info>  Activation (eth0) failed.
<info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
<info>  (eth0): device state change: 9 -> 3
<info>  (eth0): deactivating device.


Version-Release number of selected component (if applicable):
NetworkManager-0.7.0-0.9.3.svn3623.fc9.x86_64

How reproducible:
Always

Steps to Reproduce:
1. configure an interface to use auto ip configuration
2. connect the computer to a network w/o dhcp service (e.g. cross to another
computer)
  
Actual results:
NM attempts to connect but then reports the network is disconnected

Expected results:
Link-local IP address is configured on the device


The problem appears to be in src/nm-device.c, where the autoip configuration,
once obtained, is dropped on the floor, and NULL is passed down to where the
config is applied.

Comment 1 Roman Kagan 2008-05-23 21:40:24 UTC
Created attachment 306551 [details]
do not ignore the return value from nm_device_new_ip4_autoip_config()

Comment 2 han pingtian 2008-06-28 03:30:40 UTC
hi,

My f9 machines have been blocked by this from connect to network. Please fix it
ASAP! Thanks!

Comment 3 Dan Williams 2008-11-02 22:03:30 UTC
This has been fixed in latest NM updates (svn4022 and later).


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