I was able to figure out that on Fedora CoreOS, nmcli  is the way to
A related question with this Fedora CoreOS release is that have there been
any improvements to do namespace based networking in CoreOS? An example is
- being able to run Open vSwitch as a container on the CoreOS and ability
to connect other containers to the OVS bridge on a container.
On Wed, Sep 18, 2019 at 12:00 PM Andrew Jeddeloh <andrew.jeddeloh(a)redhat.com>
I don't know off the top of my head, maybe someone else on this
does. However, Fedora CoreOS's NetworkManager isn't special; it's just
regular NM*, you might try asking on #nm on freenode or on their
mailing list as well.
*We don't ship the legacy ifcfg script plugin
On Tue, Sep 17, 2019 at 10:04 PM Shivaram Mysore
> I have a box with multiple network interfaces. I am running:
> # uname -a
> Linux rhino 5.2.11-200.fc30.x86_64 #1 SMP Thu Aug 29 12:43:20 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
> # cat /etc/*release
> Fedora release 30 (Thirty)
> VERSION="30.20190905.0 (CoreOS preview)"
> PRETTY_NAME="Fedora 30.20190905.0 (CoreOS preview)"
> I am happy with eth0 as it uses DHCP.
> What is the best way to configure on the system the below command:
> $ sudo ifconfig eth1 0
> I have a container in which I have an interface - call it a OVS bridge
which will be linked to eth1 and that interface will get the IP address. I
also need to force the container to use eth1 as the default route interface
and not eth0.
> I understand that Network Manager (/var/run/NetworkManager/) is the
method to configure networking on this CoreOS. Is this model supported?
Any references to how this can be accomplished?
> I have another similar use case for a VPN tunnel.
> Appreciate pointers.
> Thanks & Regards
> CoreOS mailing list -- coreos(a)lists.fedoraproject.org
> To unsubscribe send an email to coreos-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: