Yeah, what actually happened to me, is that Ethernet DOES work just fine.
But WiFi doesn't.
So this is actually I think related to this issue:
Wifi no longer recognised in Debian-based sys-net VM after 3.0 -> 3.1 upgrade
I have an Intel 3165
On Thu, Sep 22, 2016 at 9:56 PM, wrote:
> OK, now, I had real problems trying to switch to debian8.
> I shut down sys-net and sys-firewall
> Switched them both over to debian8
> First thing, it said "Internet disconnected" in network manager, and
> simply wouldn't
OK, now, I had real problems trying to switch to debian8.
I shut down sys-net and sys-firewall
Switched them both over to debian8
First thing, it said "Internet disconnected" in network manager, and simply
wouldn't show any WiFi networks at all.
Second thing, it wouldn't even open the
Those interface names come from systemd, which renames interfaces during boot
based on their bus and location on that bus (which USB port, for example) from
"eth0" to what you're seeing. You can think of them as effectively equivalent.
You received this message because you are
Can I also ask
Is it true to say
"enp0s1" is the sys-net equivalent of "eth0"
and "wlp0s0" is the sys-net equivalent of "wlan0"
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails
On 09/22/2016 01:32 PM, neilhard...@gmail.com wrote:
I may need to change "sys-net" from the Fedora template VM, to the Debian
If I did this, would it break anything..? Or does it simply have to be Fedora..?
A number of us have been doing this for a while and it works