On Wed, Nov 14, 2018 at 09:42:17AM +0100, 'Ahmed Al Aqtash' via qubes-users wrote: > Den tir. 13. nov. 2018 kl. 16.05 skrev unman <[email protected]>: > > > > > > > > > Try that with xl console -t pv sys-net > > > > > > > > (Use Ctrl+] to step out from console session onmce you're connected) > > > > > > > > > > Yes, I googled around, and that seems to work. I do have a console in > > > sys-net now. > > > I switched my template for sys-net and sys-firewall out to fedora-28 > > > (sorry for not mentioning). > > > It is vanilla fedora-28 template though. No modifications or anything. > > > > > > I'll try and see if I can get a connection to my network when I get home. > > > >From there it should be smooth sailing. > > > > > > Need to brush up my ip toolchain usage :) > > > > > > Thank you so far for everything! > > > > Keep us posted on progress. > > I'll check back in the morning. > > > > This fixed the issue. > Luckily, as stated earlier in this thread, my VMs started up normally. Only > the GUI was broken. > >From dom0 (with a started sys-net VM) I could then get a TTY by issuing > this command: > sudo xl console -t pv sys-net > > This opens a TTY on sys-net, but it looks like if you used telnet (so > little to no feedback). > Just type "root" to login as root on the sys-net, and then you should get > feedback. > > Now you can use "nmcli", which has luckily been installed in the fedora > image. > You can use > nmcli connection up "name of your network" > to connect to a network you have already been connected to before. > > You should now be connected to the internet through sys-net (and > sys-firewall), and can update your system/install missing packages etc > through dom0. > > Thank you very much for your time unman! > I don't know how to mark a topic as solved, but for future readers > (probably myself), know that this has been completed. > > PS: If you are using nmcli and only have access to networks you have not > been connected to before, then I cannot assist. > I would probably recommend using iwconfig/netctl/or whatever other CLI tool > for networking is available. > Please remember that you can only use 1 tool for networking at a time, so > you need to disable NetworkManager while trying to fix this. > You can then re-enable it after you have solved whatever issues you have. >
Glad you got everything fixed. If you dont already have a connection set up, then use nmcli like this: nmcli con add type ethernet con-name <name> ifname <iface> If you want static address: nmcli con add type ethernet con-name <name> ifname <iface> ip4 <IP address> gw4 <gateway IP> Then: nmcli con up <name> For wireless connections, you use: nmcli radio to check that the radio switch is enabled. nmcli device to identify NICs nmcli device <wifi device> rescan nmcli device <wifi device> list Then something like: nmcli device <wifi device> connect <SSID> password <password> should get you connected. It's well documented, and the advantage is that you dont need to disable NetworkManager, so you will be up and running when you get yoru desktop back. unman -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20181114142538.y4fwmrl5o6vxitxe%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
