Hi;
enp0s8 not configured notification popups every few minutes (annoying)
I just installed Fedora Live 64-bit KDE as a VirtualBox Guest OS.
I want to have two VirtualBox ethernet interfaces:
One for the vm to "see" outwards (NAT Network) and
Two for me to ssh into it (Host-only) so that I'm not forced to use the console.
Every few minutes (it seems like every few seconds), I get a notification popup that states that enp0s8 is not configured and then a notification popup that it is being disabled.
How do I configure my outgoing ethernet interface?
I used to edit a file called something like /etc/network*/interface and then I could change the default DHCP setting to be static and the default disabled (off) setting to be enabled (on).
How does one do that kind of stuff now?
Is that a systemd thing?
Thanks, Ken Wolcott
On 04/22/2016 01:32 PM, Kenneth Wolcott wrote:
One for the vm to "see" outwards (NAT Network) and
Two for me to ssh into it (Host-only) so that I'm not forced to use the console.
This one is working? "Not forced to use the console", but you are using it? Can't you just use the KDE network configuration tool? I assume there is one, but I use Gnome so I can't help you with that.
The question is why didn't NetworkManager automatically configure the interface. Did you disable it?
How do I configure my outgoing ethernet interface?
I used to edit a file called something like /etc/network*/interface and then I could change the default DHCP setting to be static and the default disabled (off) setting to be enabled (on).
That sounds like the Debian does network config.
Look in /etc/sysconfig/network-scripts. There should be a file called ifcfg-enp0s8. That contains the configuration. If it doesn't exist, then create one. Hopefully you can find a template with the information to put in it.
On Sat, Apr 23, 2016 at 1:06 AM, Samuel Sieb samuel@sieb.net wrote:
On 04/22/2016 01:32 PM, Kenneth Wolcott wrote:
One for the vm to "see" outwards (NAT Network) and
Two for me to ssh into it (Host-only) so that I'm not forced to use the console.
This one is working? "Not forced to use the console", but you are using it? Can't you just use the KDE network configuration tool? I assume there is one, but I use Gnome so I can't help you with that.
The question is why didn't NetworkManager automatically configure the interface. Did you disable it?
How do I configure my outgoing ethernet interface?
I used to edit a file called something like /etc/network*/interface and then I could change the default DHCP setting to be static and the default disabled (off) setting to be enabled (on).
That sounds like the Debian does network config.
Look in /etc/sysconfig/network-scripts. There should be a file called ifcfg-enp0s8. That contains the configuration. If it doesn't exist, then create one. Hopefully you can find a template with the information to put in it.
Hmmm, one way to solve the notification problem is to disable notifications, another way is to disable this notification, yet another way is change ONBOOT to no.
I give up for now.
On 04/27/2016 01:12 PM, Kenneth Wolcott wrote:
On Sat, Apr 23, 2016 at 1:06 AM, Samuel Sieb samuel@sieb.net wrote:
Look in /etc/sysconfig/network-scripts. There should be a file called ifcfg-enp0s8. That contains the configuration. If it doesn't exist, then create one. Hopefully you can find a template with the information to put in it.
Hmmm, one way to solve the notification problem is to disable notifications, another way is to disable this notification, yet another way is change ONBOOT to no.
I give up for now.
Did you try what I suggested?
On Wed, Apr 27, 2016 at 3:28 PM, Samuel Sieb samuel@sieb.net wrote:
On 04/27/2016 01:12 PM, Kenneth Wolcott wrote:
On Sat, Apr 23, 2016 at 1:06 AM, Samuel Sieb samuel@sieb.net wrote:
Look in /etc/sysconfig/network-scripts. There should be a file called ifcfg-enp0s8. That contains the configuration. If it doesn't exist, then create one. Hopefully you can find a template with the information to put in it.
Hmmm, one way to solve the notification problem is to disable notifications, another way is to disable this notification, yet another way is change ONBOOT to no.
I give up for now.
Did you try what I suggested?
Yes, I initially tried but I got confused when most of what I saw were IPV6 entries.
The /etc/sysconf/network-scripts/ifcfg-enp0s8 files does exist, but the only entries that I recognize now are BOOTPROTO and ONBOOT; everything else looks like IPV6.
I'd rather have IPV4 and I'm pretty sure that is what I want to use from VirtualBox.
I'm not ready to dive into IPV6.
i'd really like to have a compatible and functional set of entries that are based on IPV4, but if I look at a sample from a long time ago, I don't know if those entries will still be understood by the current OS.
I also seem to do much better at home where my VirtualBox host is a Mac; at work the VirtualBox host is WIndows desktop (one instance) and a Windows laptop (second instance).
It seems easier to deal with the networking of VirtualBox from the host (for me) if the host is a Mac.
Anyway, I'd love to be able to ssh into my vm rather than having to use the console exclusively.
Thanks, Ken Wolcott
On 04/27/2016 06:10 PM, Kenneth Wolcott wrote:
The /etc/sysconf/network-scripts/ifcfg-enp0s8 files does exist, but the only entries that I recognize now are BOOTPROTO and ONBOOT; everything else looks like IPV6.
I'd rather have IPV4 and I'm pretty sure that is what I want to use from VirtualBox.
I'm not ready to dive into IPV6.
i'd really like to have a compatible and functional set of entries that are based on IPV4, but if I look at a sample from a long time ago, I don't know if those entries will still be understood by the current OS.
Here's a sample ifcfg-enp0s8 file for you: IPV6INIT=no BOOTPROTO=dhcp DEVICE=enp0s8 ONBOOT=yes UUID=d211cad8-d15d-46a1-b94d-2a42def47212 HWADDR=<put MAC here> TYPE=Ethernet DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=no NAME="System enp0s8"
Put the actual MAC address in the right line or it might work if you completely remove that line. The problem is that I don't know how you've configured the networking in virtualbox. I've never even used virtualbox so I can't help you at all there. I only use KVM. But if virtualbox isn't offering dhcp on that interface (which would make sense, since the other interface is the default one), then this won't work. You will have to setup a manual ip address config in the file. If that's the case, then let me know the ip address you want and I will create a config file for you.
On Thu, Apr 28, 2016 at 1:42 PM, Samuel Sieb samuel@sieb.net wrote:
On 04/27/2016 06:10 PM, Kenneth Wolcott wrote:
The /etc/sysconf/network-scripts/ifcfg-enp0s8 files does exist, but the only entries that I recognize now are BOOTPROTO and ONBOOT; everything else looks like IPV6.
I'd rather have IPV4 and I'm pretty sure that is what I want to use from VirtualBox.
I'm not ready to dive into IPV6.
i'd really like to have a compatible and functional set of entries that are based on IPV4, but if I look at a sample from a long time ago, I don't know if those entries will still be understood by the current OS.
Here's a sample ifcfg-enp0s8 file for you: IPV6INIT=no BOOTPROTO=dhcp DEVICE=enp0s8 ONBOOT=yes UUID=d211cad8-d15d-46a1-b94d-2a42def47212 HWADDR=<put MAC here> TYPE=Ethernet DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=no NAME="System enp0s8"
Put the actual MAC address in the right line or it might work if you completely remove that line. The problem is that I don't know how you've configured the networking in virtualbox. I've never even used virtualbox so I can't help you at all there. I only use KVM. But if virtualbox isn't offering dhcp on that interface (which would make sense, since the other interface is the default one), then this won't work. You will have to setup a manual ip address config in the file. If that's the case, then let me know the ip address you want and I will create a config file for you.
Thanks for the great support! I've finally figured out how to enable the DHCP server on the VirtualBox (Windows) host. I used most of of your suggested entries. I think I have to enable sshd on my vm now. Thanks, Ken
On Thu, Apr 28, 2016 at 6:43 PM, Kenneth Wolcott kennethwolcott@gmail.com wrote:
On Thu, Apr 28, 2016 at 1:42 PM, Samuel Sieb samuel@sieb.net wrote:
On 04/27/2016 06:10 PM, Kenneth Wolcott wrote:
The /etc/sysconf/network-scripts/ifcfg-enp0s8 files does exist, but the only entries that I recognize now are BOOTPROTO and ONBOOT; everything else looks like IPV6.
I'd rather have IPV4 and I'm pretty sure that is what I want to use from VirtualBox.
I'm not ready to dive into IPV6.
i'd really like to have a compatible and functional set of entries that are based on IPV4, but if I look at a sample from a long time ago, I don't know if those entries will still be understood by the current OS.
Here's a sample ifcfg-enp0s8 file for you: IPV6INIT=no BOOTPROTO=dhcp DEVICE=enp0s8 ONBOOT=yes UUID=d211cad8-d15d-46a1-b94d-2a42def47212 HWADDR=<put MAC here> TYPE=Ethernet DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=no NAME="System enp0s8"
Put the actual MAC address in the right line or it might work if you completely remove that line. The problem is that I don't know how you've configured the networking in virtualbox. I've never even used virtualbox so I can't help you at all there. I only use KVM. But if virtualbox isn't offering dhcp on that interface (which would make sense, since the other interface is the default one), then this won't work. You will have to setup a manual ip address config in the file. If that's the case, then let me know the ip address you want and I will create a config file for you.
Thanks for the great support! I've finally figured out how to enable the DHCP server on the VirtualBox (Windows) host. I used most of of your suggested entries. I think I have to enable sshd on my vm now. Thanks, Ken
I can ssh into my vm now!
Thanks, Ken Wolcott
On Thu, Apr 28, 2016 at 1:42 PM, Samuel Sieb samuel@sieb.net wrote:
On 04/27/2016 06:10 PM, Kenneth Wolcott wrote:
The /etc/sysconf/network-scripts/ifcfg-enp0s8 files does exist, but the only entries that I recognize now are BOOTPROTO and ONBOOT; everything else looks like IPV6.
I'd rather have IPV4 and I'm pretty sure that is what I want to use from VirtualBox.
I'm not ready to dive into IPV6.
i'd really like to have a compatible and functional set of entries that are based on IPV4, but if I look at a sample from a long time ago, I don't know if those entries will still be understood by the current OS.
Here's a sample ifcfg-enp0s8 file for you: IPV6INIT=no BOOTPROTO=dhcp DEVICE=enp0s8 ONBOOT=yes UUID=d211cad8-d15d-46a1-b94d-2a42def47212 HWADDR=<put MAC here> TYPE=Ethernet DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=no NAME="System enp0s8"
Put the actual MAC address in the right line or it might work if you completely remove that line. The problem is that I don't know how you've configured the networking in virtualbox. I've never even used virtualbox so I can't help you at all there. I only use KVM. But if virtualbox isn't offering dhcp on that interface (which would make sense, since the other interface is the default one), then this won't work. You will have to setup a manual ip address config in the file. If that's the case, then let me know the ip address you want and I will create a config file for you.
I'm on a different Windows VirtualBox host now and am using a fresh install of Fedora 24 KDE Workstation.
I have implemented the same suggestion you provided here, but it appears to have no effect this time as the notifications keep re-appearing every few seconds.
Thanks, Ken Wolcott
On 07/03/2016 05:37 PM, Kenneth Wolcott wrote:
I'm on a different Windows VirtualBox host now and am using a fresh install of Fedora 24 KDE Workstation.
I have implemented the same suggestion you provided here, but it appears to have no effect this time as the notifications keep re-appearing every few seconds.
Check that the interface names are still the same. What is the output of "ifconfig -a"?
On Sun, Jul 3, 2016 at 10:46 PM, Samuel Sieb samuel@sieb.net wrote:
On 07/03/2016 05:37 PM, Kenneth Wolcott wrote:
I'm on a different Windows VirtualBox host now and am using a fresh install of Fedora 24 KDE Workstation.
I have implemented the same suggestion you provided here, but it appears to have no effect this time as the notifications keep re-appearing every few seconds.
Check that the interface names are still the same. What is the output of "ifconfig -a"?
I forgot to configure and enabled the DHCP server on the VIrtualBox host for host-only on the second host-only VirtualBox network :-)
It's working now.
Thanks, Ken
-
Kenneth Wolcott -
Samuel Sieb