Re: F9 Networkmanager and zeroconf

[hanpingtian gmail com]

Before I am going to active the pppoe interface, I must active the eth0 first.
I use dhcp to give a IP address to eth0. But indeed there is no dhcp server 
in my network. In F8, the NM will get a autoip for eth0 by zeroconf. But in
F9, it wouldn't do the same thing for me. So I cound active the pppoe. 

Could you tell me how to get a "autoIP" connection in the NM? It seems there is
not such a option in the "/usr/bin/nm-connection-editor".

2008/6/24 Dan Williams <dcbw redhat com>:

On Wed, 2008-06-18 at 22:08 +0800, hanpingtian gmail com wrote:
> hi,
>
> It seems that in F8, when nm failed to get a DHCP reply, it will use
> zeroconf to get a IP address for NIC. It's something like this(fedora 8 log):
> ...
> Jun  8 09:27:21 freeopen avahi-daemon[2073]: Registering new address
> record for fe80::216:ecff:fec0:f990 on eth0.*.
> Jun  8 09:27:27 freeopen dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 8
> Jun  8 09:27:35 freeopen dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 18
> Jun  8 09:27:53 freeopen dhclient: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 17
> Jun  8 09:28:05 freeopen NetworkManager: <info>  Device 'eth0' DHCP
> transaction took too long (>45s), stopping it.
> Jun  8 09:28:05 freeopen NetworkManager: <info>  eth0: canceled DHCP
> transaction, dhclient pid 6097
> Jun  8 09:28:05 freeopen NetworkManager: <info>  Activation (eth0)
> Stage 4 of 5 (IP Configure Timeout) scheduled...
> Jun  8 09:28:05 freeopen NetworkManager: <info>  Activation (eth0)
> Stage 4 of 5 (IP Configure Timeout) started...
> Jun  8 09:28:05 freeopen NetworkManager: <info>  No DHCP reply
> received.  Automatically obtaining IP via Zeroconf.
> Jun  8 09:28:05 freeopen NetworkManager: <info>  autoip: Sending probe
> #0 for IP address 169.254.158.8.
> Jun  8 09:28:05 freeopen NetworkManager: <info>  autoip: Waiting for reply...
> Jun  8 09:28:06 freeopen NetworkManager: <info>  autoip: Got some data
> to check for reply packet.
> Jun  8 09:28:06 freeopen NetworkManager: <WARN>  get_autoip(): autoip:
> (eth0) recv arp type=2054, op=1,
> Jun  8 09:28:06 freeopen NetworkManager: <WARN>  get_autoip():  source
> = 199.199.194.2 00:0F:E2:61:F7:8B,
> Jun  8 09:28:06 freeopen NetworkManager: <WARN>  get_autoip():  target
> = 199.199.194.2 0E:2A:65:B5:37:07#012
> Jun  8 09:28:06 freeopen NetworkManager: <info>  autoip: Sending probe
> #1 for IP address 169.254.158.8.
> Jun  8 09:28:06 freeopen NetworkManager: <info>  autoip: Waiting for reply...
> Jun  8 09:28:07 freeopen NetworkManager: <info>  autoip: Got some data
> to check for reply packet.
> Jun  8 09:28:07 freeopen NetworkManager: <WARN>  get_autoip(): autoip:
> (eth0) recv arp type=2054, op=1,
> ...
> BUT, it seems that in F9, nm doesn't use zeroconf anymore. It just
> failed when cannot get a DHCP rely.

Right; if you want zeroconf on the adapter you set specify "AutoIP" mode
in the connection editor.

> This is very bad for me. I am using a pppoe connection. This new
> behavior make the pppoe's NIC failed to
> get a IP address and ppp dial will fail.

I'm not sure I understand how DHCP plays into your network setup.
AFAIK, with PPPoE, NM should be starting PPPoE on your NIC and PPP will
return the IP address that you need to use.  There shouldn't be any DHCP
going on when using PPPoE.

You can set up a real PPPoE connection from the "DSL" tab of the
connection editor (/usr/bin/nm-connection-editor, or right-click the
applet's icon and choose "Edit Connections...").

Dan