On 13 May 2016 07:37, "Alexander Todorov" <atodorov@xxxxxxxxxx> wrote:
>
> На 12.05.2016 в 15:32, Phil Sutter написа:
>>
>> Hi,
>>
>> On Thu, May 12, 2016 at 02:47:19PM +0300, Alexander Todorov wrote:
>>>
>>> # cat /etc/sysconfig/network-scripts/ifcfg-enp1s0f0
>>> Generated by dracut initrd
>>
>>
>> The line above is supposed to be a comment.
>>
>
> OK, fixed that then I got:
>
> # systemctl status network.service
>
> ● network.service - LSB: Bring up/down networking
> Loaded: loaded (/etc/rc.d/init.d/network)
> Active: failed (Result: exit-code) since пт 2016-05-13 02:33:54 EDT; 36s ago
> Docs: man:systemd-sysv-generator(8)
> Process: 2189 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
>
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: [ OK ]
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Bringing up interface enp1s0f0: [ OK ]
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Bringing up interface enp1s0f1: Error: Connection activation f...tion.
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: [FAILED]
> май 13 02:33:53 amd-dinar-02.lab.bos.redhat.com network[2189]: Bringing up interface br0: [ OK ]
> май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]: network.service: Control process exited, code=exited status=1
> май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]: Failed to start LSB: Bring up/down networking.
> май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]: network.service: Unit entered failed state.
> май 13 02:33:54 amd-dinar-02.lab.bos.redhat.com systemd[1]: network.service: Failed with result 'exit-code'.
> Hint: Some lines were ellipsized, use -l to show in full.
>
>
>
> And
>
>
> # ip a s
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
> link/ether 00:00:1a:1a:94:70 brd ff:ff:ff:ff:ff:ff
> inet 10.16.42.33/21 brd 10.16.47.255 scope global dynamic enp1s0f0
> valid_lft 77820sec preferred_lft 77820sec
>
> inet6 2620:52:0:102f:200:1aff:fe1a:9470/64 scope global noprefixroute dynamic
> valid_lft 2591924sec preferred_lft 604724sec
>
> inet6 fe80::200:1aff:fe1a:9470/64 scope link
> valid_lft forever preferred_lft forever
> 3: enp1s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
> link/ether 00:00:1a:1a:94:71 brd ff:ff:ff:ff:ff:ff
> 4: br0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
> link/ether 42:61:9f:68:1d:85 brd ff:ff:ff:ff:ff:ff
>
Please note that you have mailed the development and test Fedora lists, not the users list.
This looks like it would better apply there.
Is there a reason you aren't using NetworkManager in your systemctl attempts above?
If scripting networking you may well find a cleaner solution utilising nmcli:
https://www.hogarthuk.com/?q=node/8
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@xxxxxxxxxxxxxxxxxxxxxxx
