Hello
My pc has both LAN and WIFI controller. Both are present under the “SYS-NET” qube. Is i possible to copy the “SYS-NET” qube and dedicate LAN controller to primary “SYS-NET” and put the WIFI controller in the new “SYS_NET-WIFI” qube? I am looking for the possibility to use a few App-Qubes on my WIFI that is on a different network. Thanks in advance
You can do that. I’ve done it, in fact I have sys-net-wifi and sys-net-ether.
At first, though, I’d keep the name sys-net for whichever one is the one that goes onto the internet, and name the other one sys-net-ether or sys-net-wifi, depending. There are numerous system settings that default to “sys-net” and you’ll want sys-net to connect to the internet.
(Eventually you’ll find them and change them to point to the new qube with the more accurate name, but until you do so, if the system can’t find a sys-net, it will actually create one, which will try to seize that device and will lock up.)
Thank you for the reply and big help 
Hello again Steve
Just forgot to ask about the “SYS-FIREWALL” qube? If i want one or two specific qubes to run through the extra soon to be made “SYS-NET-WIFI” and all other qubes are using “SYS-NET” as usual. Then what about the “SYS-FIREWALL” qube? As I understand then I have to make a “SYS-FIREWALL-WIFI” also so the 2 App-qubes I want to run through “SYS-NET-WIFI” goes through “SYS-FIREWALL-WIFI” alongside all other app-qubes that uses the normal “SYS-FIREWALL” and “SYS-NET”? is that correct? Thanks in advance
Correct. Two separate pathways.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
Great and thanks for the quick reply
Unman’s completely correct. I have a sys-firewall-ether and a sys-firewall-wifi as well as the two sys-net-* VMs.
Again, be sure to find all system settings that reference sys-firewall and sys-net and make sure they’re correct for your new setup.
The easiest way to do that is to leave the name of your internet access alone. For example if you get to the internet by wifi, have sys-net (for wifi) and sys-net-ether (or sys-net-lan if you prefer) for your lan. Similarly sys-firewall (for wifi) and sys-firewall-ether or sys-firewall-lan for the firewalls.
Later on you can try renaming sys-net and sys-firewall to sys-net-wifi and sys-firewall-wifi but you’ll definitely have to hunt down all system settings. Fortunately the 4.2 settings tool is pretty comprehensive; it finds things that the tool from 4.1 couldn’t find.