On Fri, Jun 17, 2016 at 02:17:07PM +0000, Alexander Pisarev wrote:
Hi. Here it is. If need more data or I do something wrong tell me.
Hi, in the log I see: 10:04:50 NM[669]: <info> Auto-activating connection 'prl_nettool-nm-eth0'. ... 10:04:51 dhclient[729]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 10:04:51 dhclient[729]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 10:04:51 dhclient[729]: DHCPOFFER from 10.30.0.25 10:04:51 dhclient[729]: DHCPACK from 10.30.0.24 (xid=0x79722431) ... 10:04:51 NM[669]: <info> (eth0): DHCPv4 state changed unknown -> bound ... 10:04:51 NM[669]: <info> Policy set 'prl_nettool-nm-eth0' (eth0) as default for IPv4 routing and DNS. At this point eth0 has an address, a gateway and the default route. After, the connection becomes active: 10:04:51 NM[669]: <info> (eth0): Activation: successful, device activated. When this message is printed nmcli should return successfully; so from the log it seems that the activation is working as expected and the interface is configured when nmcli returns. Can you please explain the problem you are seeing? Beniamino
Attachment:
signature.asc
Description: PGP signature