Fedora 32
ifup/ifdown warns me it is about to be depreciated and to use NetworkManager instead.
Question:
Why does # /usr/sbin/NetworkManager down eno2
not disconnect me, but # nmcli dev disconnect eno2
does?
Many thanks, -T
On 2020-04-26 14:07, ToddAndMargo via test wrote:
Fedora 32
ifup/ifdown warns me it is about to be depreciated and to use NetworkManager instead.
Question:
Why does # /usr/sbin/NetworkManager down eno2
not disconnect me, but # nmcli dev disconnect eno2
does?
Many thanks, -T
/usr/libexec/nm-ifdown eno2 /usr/libexec/nm-ifup eno2
also works.
Which one should I use to avoid being depreciated?
On 4/26/20 2:07 PM, ToddAndMargo via test wrote:
Fedora 32
ifup/ifdown warns me it is about to be depreciated and to use NetworkManager instead.
Question:
Why does # /usr/sbin/NetworkManager down eno2
not disconnect me, but # nmcli dev disconnect eno2
You don't call "NetworkManager" directly, that's what "nmcli" is for.
Also, if you remove the "network-scripts" package you will get "ifup/down" commands from NetworkManager which work and won't give you that warning.
On 2020-04-26 14:22, Samuel Sieb wrote:
On 4/26/20 2:07 PM, ToddAndMargo via test wrote:
Fedora 32
ifup/ifdown warns me it is about to be depreciated and to use NetworkManager instead.
Question:
Why does # /usr/sbin/NetworkManager down eno2
not disconnect me, but # nmcli dev disconnect eno2
You don't call "NetworkManager" directly, that's what "nmcli" is for.
Also, if you remove the "network-scripts" package you will get "ifup/down" commands from NetworkManager which work and won't give you that warning.
No joy
# dnf remove NetworkManager Dependencies resolved. ... Complete!
# which ifup /usr/sbin/ifup
# ifup eno2 WARN : [ifup] You are using 'ifup' script provided by 'network-scripts', which are now deprecated. WARN : [ifup] 'network-scripts' will be removed from distribution in near future. WARN : [ifup] It is advised to switch to 'NetworkManager' instead - it provides 'ifup/ifdown' scripts as well.
Determining IP information for eno2... done.
On 4/26/20 2:28 PM, ToddAndMargo via test wrote:
On 2020-04-26 14:22, Samuel Sieb wrote:
On 4/26/20 2:07 PM, ToddAndMargo via test wrote:
Fedora 32
ifup/ifdown warns me it is about to be depreciated and to use NetworkManager instead.
Question:
Why does # /usr/sbin/NetworkManager down eno2
not disconnect me, but # nmcli dev disconnect eno2
You don't call "NetworkManager" directly, that's what "nmcli" is for.
Also, if you remove the "network-scripts" package you will get "ifup/down" commands from NetworkManager which work and won't give you that warning.
No joy
# dnf remove NetworkManager Dependencies resolved. ... Complete!
You removed "NetworkManager" which is the complete opposite of what I said. Do you have any networking now?
On 2020-04-26 14:31, Samuel Sieb wrote:
On 4/26/20 2:28 PM, ToddAndMargo via test wrote:
On 2020-04-26 14:22, Samuel Sieb wrote:
On 4/26/20 2:07 PM, ToddAndMargo via test wrote:
Fedora 32
ifup/ifdown warns me it is about to be depreciated and to use NetworkManager instead.
Question:
Why does # /usr/sbin/NetworkManager down eno2
not disconnect me, but # nmcli dev disconnect eno2
You don't call "NetworkManager" directly, that's what "nmcli" is for.
Also, if you remove the "network-scripts" package you will get "ifup/down" commands from NetworkManager which work and won't give you that warning.
No joy
# dnf remove NetworkManager Dependencies resolved. ... Complete!
You removed "NetworkManager" which is the complete opposite of what I said. Do you have any networking now?
Yes. Lucky me. I put it back.
What is the dnf command to get rid of the right stuff?
On 4/26/20 2:38 PM, ToddAndMargo via test wrote:
On 2020-04-26 14:31, Samuel Sieb wrote:
On 4/26/20 2:28 PM, ToddAndMargo via test wrote:
On 2020-04-26 14:22, Samuel Sieb wrote:
On 4/26/20 2:07 PM, ToddAndMargo via test wrote:
Fedora 32
ifup/ifdown warns me it is about to be depreciated and to use NetworkManager instead.
Question:
Why does # /usr/sbin/NetworkManager down eno2
not disconnect me, but # nmcli dev disconnect eno2
You don't call "NetworkManager" directly, that's what "nmcli" is for.
Also, if you remove the "network-scripts" package you will get "ifup/down" commands from NetworkManager which work and won't give you that warning.
No joy
# dnf remove NetworkManager Dependencies resolved. ... Complete!
You removed "NetworkManager" which is the complete opposite of what I said. Do you have any networking now?
Yes. Lucky me. I put it back.
What is the dnf command to get rid of the right stuff?
"dnf remove network-scripts"
On 2020-04-26 14:39, Samuel Sieb wrote:
On 4/26/20 2:38 PM, ToddAndMargo via test wrote:
On 2020-04-26 14:31, Samuel Sieb wrote:
On 4/26/20 2:28 PM, ToddAndMargo via test wrote:
On 2020-04-26 14:22, Samuel Sieb wrote:
On 4/26/20 2:07 PM, ToddAndMargo via test wrote:
Fedora 32
ifup/ifdown warns me it is about to be depreciated and to use NetworkManager instead.
Question:
Why does # /usr/sbin/NetworkManager down eno2
not disconnect me, but # nmcli dev disconnect eno2
You don't call "NetworkManager" directly, that's what "nmcli" is for.
Also, if you remove the "network-scripts" package you will get "ifup/down" commands from NetworkManager which work and won't give you that warning.
No joy
# dnf remove NetworkManager Dependencies resolved. ... Complete!
You removed "NetworkManager" which is the complete opposite of what I said. Do you have any networking now?
Yes. Lucky me. I put it back.
What is the dnf command to get rid of the right stuff?
"dnf remove network-scripts"
Joy. Thank you!
now to get my network icon back in my task bar (Xfce)
Why does /usr/sbin/NetworkManager down eno2 not work?
On 2020-04-26 14:44, ToddAndMargo via test wrote:
On 2020-04-26 14:39, Samuel Sieb wrote:
On 4/26/20 2:38 PM, ToddAndMargo via test wrote:
On 2020-04-26 14:31, Samuel Sieb wrote:
On 4/26/20 2:28 PM, ToddAndMargo via test wrote:
On 2020-04-26 14:22, Samuel Sieb wrote:
On 4/26/20 2:07 PM, ToddAndMargo via test wrote: > Fedora 32 > > ifup/ifdown warns me it is about to be depreciated and > to use NetworkManager instead. > > Question: > > Why does > # /usr/sbin/NetworkManager down eno2 > > not disconnect me, but > # nmcli dev disconnect eno2
You don't call "NetworkManager" directly, that's what "nmcli" is for.
Also, if you remove the "network-scripts" package you will get "ifup/down" commands from NetworkManager which work and won't give you that warning.
No joy
# dnf remove NetworkManager Dependencies resolved. ... Complete!
You removed "NetworkManager" which is the complete opposite of what I said. Do you have any networking now?
Yes. Lucky me. I put it back.
What is the dnf command to get rid of the right stuff?
"dnf remove network-scripts"
Joy. Thank you!
now to get my network icon back in my task bar (Xfce)
# dnf install network-manager-applet
Why does /usr/sbin/NetworkManager down eno2 not work?
On 2020-04-26 18:22, ToddAndMargo via test wrote:
On 2020-04-26 14:48, ToddAndMargo via test wrote:
"dnf remove network-scripts"
And I just put it back in as qemu-kvm requires it to do bridge networking (br0)
Error starting domain: Cannot get interface MTU on 'br0': No such device
Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 66, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/object/domain.py", line 1279, in startup self._backend.create() File "/usr/lib64/python3.8/site-packages/libvirt.py", line 1234, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirt.libvirtError: Cannot get interface MTU on 'br0': No such device
On 4/26/20 6:22 PM, ToddAndMargo via test wrote:
On 2020-04-26 14:48, ToddAndMargo via test wrote:
"dnf remove network-scripts"
And I just put it back in as qemu-kvm requires it to do bridge networking (br0)
I use kvm with bridge networking and I don't have network-scripts installed.
On 2020-04-27 09:43, Samuel Sieb wrote:
On 4/26/20 6:22 PM, ToddAndMargo via test wrote:
On 2020-04-26 14:48, ToddAndMargo via test wrote:
"dnf remove network-scripts"
And I just put it back in as qemu-kvm requires it to do bridge networking (br0)
I use kvm with bridge networking and I don't have network-scripts installed.
Same here....
virsh # iface-dumpxml virbr0 <interface type='bridge' name='virbr0'> <protocol family='ipv4'> <ip address='192.168.122.1' prefix='24'/> </protocol> <protocol family='ipv6'> <ip address='2001:b030:112f:2::2' prefix='64'/> <ip address='fe80::5054:ff:fe9a:e849' prefix='64'/> </protocol> <bridge> <interface type='ethernet' name='virbr0-nic'> <link state='down'/> <mac address='52:54:00:9a:e8:49'/> </interface> <interface type='ethernet' name='vnet0'> <link state='unknown'/> <mac address='fe:54:00:9b:21:c1'/> </interface> </bridge> </interface>
On 2020-04-26 18:47, Ed Greshko wrote:
On 2020-04-27 09:43, Samuel Sieb wrote:
On 4/26/20 6:22 PM, ToddAndMargo via test wrote:
On 2020-04-26 14:48, ToddAndMargo via test wrote:
"dnf remove network-scripts"
And I just put it back in as qemu-kvm requires it to do bridge networking (br0)
I use kvm with bridge networking and I don't have network-scripts installed.
Same here....
virsh # iface-dumpxml virbr0
<interface type='bridge' name='virbr0'> <protocol family='ipv4'> <ip address='192.168.122.1' prefix='24'/> </protocol> <protocol family='ipv6'> <ip address='2001:b030:112f:2::2' prefix='64'/> <ip address='fe80::5054:ff:fe9a:e849' prefix='64'/> </protocol> <bridge> <interface type='ethernet' name='virbr0-nic'> <link state='down'/> <mac address='52:54:00:9a:e8:49'/> </interface> <interface type='ethernet' name='vnet0'> <link state='unknown'/> <mac address='fe:54:00:9b:21:c1'/> </interface> </bridge> </interface>
It has to do with how I handle iptables and two Ethernet ports and how I pass through to the Internet
On 2020-04-28 11:07, ToddAndMargo via test wrote:
On 2020-04-26 18:47, Ed Greshko wrote:
On 2020-04-27 09:43, Samuel Sieb wrote:
On 4/26/20 6:22 PM, ToddAndMargo via test wrote:
On 2020-04-26 14:48, ToddAndMargo via test wrote:
> > "dnf remove network-scripts"
And I just put it back in as qemu-kvm requires it to do bridge networking (br0)
I use kvm with bridge networking and I don't have network-scripts installed.
Same here....
virsh # iface-dumpxml virbr0
<interface type='bridge' name='virbr0'> <protocol family='ipv4'> <ip address='192.168.122.1' prefix='24'/> </protocol> <protocol family='ipv6'> <ip address='2001:b030:112f:2::2' prefix='64'/> <ip address='fe80::5054:ff:fe9a:e849' prefix='64'/> </protocol> <bridge> <interface type='ethernet' name='virbr0-nic'> <link state='down'/> <mac address='52:54:00:9a:e8:49'/> </interface> <interface type='ethernet' name='vnet0'> <link state='unknown'/> <mac address='fe:54:00:9b:21:c1'/> </interface> </bridge> </interface>
It has to do with how I handle iptables and two Ethernet ports and how I pass through to the Internet
virsh # iface-dumpxml "br0" <interface type='bridge' name='br0'> <protocol family='ipv4'> <ip address='192.168.255.10' prefix='24'/> <ip address='192.168.255.116' prefix='24'/> </protocol> <protocol family='ipv6'> <ip address='fe80::fc62:7fff:fefe:1fdf' prefix='64'/> </protocol> <bridge> <interface type='ethernet' name='eno1'> <link state='down'/> <mac address='ac:1f:6b:62:10:06'/> </interface> <interface type='ethernet' name='vnet0'> <link state='unknown'/> <mac address='fe:54:00:eb:37:2b'/> </interface> </bridge> </interface>
On 2020-04-26 15:41, Samuel Sieb wrote:
On 4/26/20 2:44 PM, ToddAndMargo via test wrote:
Why does /usr/sbin/NetworkManager down eno2 not work?
NetworkManager is the server, you never run it directly. You talk to it over dbus using either an applet or the nmcli command.
Then the man page need some work. Thank you for the explanation.
On 4/26/20 4:03 PM, ToddAndMargo via test wrote:
On 2020-04-26 15:41, Samuel Sieb wrote:
On 4/26/20 2:44 PM, ToddAndMargo via test wrote:
Why does /usr/sbin/NetworkManager down eno2 not work?
NetworkManager is the server, you never run it directly. You talk to it over dbus using either an applet or the nmcli command.
Then the man page need some work. Thank you for the explanation.
I'm not sure what you're referring to. There's nothing in there about running it. The list of "actions" are in the section explaining about how it runs the scripts stored in /etc/NetworkManager/dispatcher.d.
-
Ed Greshko -
Samuel Sieb -
ToddAndMargo