Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#36946 - [netctl] can not restart static wired interface if it is already UP

Attached to Project: Arch Linux
Opened by Daniel YC Lin (dlin) - Monday, 16 September 2013, 00:54 GMT
Last edited by Jouke Witteveen (jouke) - Monday, 21 October 2013, 13:19 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Jouke Witteveen (jouke)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

I found if I try to restart a static wired net. It can not work when the satus of the interface is already 'UP'.
Even I've did the 'restart' command.

$ sudo netctl restart static-wire-net
Job for netctl@2F.service failed. See 'systemctl status netctl@static-wire-net.service' and 'journalctl -xn' for details.

$ ip addr
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
inet 192.168.0.1/24 brd 192.168.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 xxxx::xxxx:xxxx:xxxx:xxxx/64 scope link
valid_lft forever preferred_lft forever

$ sudo ifconfig eth0 down

$ sudo netctl restart static-wire-net
# works

$ ip addr

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
inet 192.168.0.1/24 brd 192.168.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet 192.168.2.160/24 brd 192.168.2.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::xxxx:xxxx:xxxx:xxxx/64 scope link
valid_lft forever preferred_lft forever


Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Jouke Witteveen (jouke)
Monday, 21 October 2013, 13:19 GMT
Reason for closing:  Not a bug
Additional comments about closing:  This is how it should work. Netctl likes to be the only network manager on an interface and this is part of enforcing that.

Loading...