#14: Investigate systemd-networkd
------------------------------+--------------------------------
Reporter: mattdm | Owner: janeznemanic
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Alpha)
Component: Cloud Base Image | Resolution:
Keywords: |
------------------------------+--------------------------------
Comment (by janeznemanic):
Replying to [comment:6 gospo]:
> Replying to [comment:3 janeznemanic]:
> > But if I tried to use for example ifup or ifdown script then that
script failed. Because it couldn't source ifcfg-*. I think so, I might be
wrong. Since ifup and ifdown are links to /usr/sbin/{ifup,ifdown} it might
be possible to remove /usr/sbin/{ifup,ifdown}. But I haven't tested that
so I'm not sure. I think we also don't need to use
/etc/rc.d/init.d/network. I removed that file and networking worked fine
with systemd-networkd.
> >
> Sorry, I forgot to address this in my last post. As was mentioned above
there are some who will want to preserve some of the ability to use
ifup/ifdown in some manner. I know that controlling the network
interfaces is a current TODO for networkd, but it would seem reasonable
that the networkd unit can be stopped/started or restarted if one wanted
to reset the network config, correct?
You can do ''systemctl {start,stop,restart} systemd-networkd.service'' to
control networking.
I'm not fedora networking expert, but I think it is possible to use ip
command instead of ifup/ifdown to bring interface up or down.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/14#comment:11>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
