[qubes-users] Re: Thinkpad T440s i7 and Qubes 4.0 compatibility
maybe, I am missing something, did you try installing 4.0 in legacy mode? it seems with the older thinkpads this is the way to avoid the dreaded black screen EFI thing. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0243fee9-9cff-8919-629a-5ba035fdd234%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] screen sharing
Hello The Flakes, schrieb am So., 29. Apr. 2018, 02:34: > What's the best way to allow app/screen sharing in WebEx / GotoMeeting / > Hangouts etc. ? > I had to ask the same question when moving to Qubes OS as part of my job is heavily based on Collaboration and Screen sharing. Working for an IT company/Cisco Partner I had the benefit that we can use some tools for free. While I like WebEx it is a shame that there is no real solution for Linux and companies who are not providing cross platform solution should be "punished" by not using their products ;-) As such I have looked at other alternatives like TeamViewer and AnyDesk as both solution can be run for free as an individual user and can be used for business when paid. I prefer AnyDesk over TeamViewer as it is super easy to setup and doesn't cost much when used for business. Please consider that most screen sharing apps are closed source and as such can't be trusted. Another option is to create a screen sharing "Proxy VM". You could then run your Screensharing App there and use VNC to make a connection from there to your AppVM. This includes to set firewall rules between both VMs to allow VNC. But you could easily write a script which does all the necessary steps: Idea: qvm-screenshare start The Script will start the Screensharing AppVM, then launch the Screensharing Application in this VM. Additionally it will setup the required firewall rules between both AppVMs qvm-screenshare stop This will remove the firewall rules between both VMs. [799] -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAJ3yz2tLc7E1YDoEfJaskyrD10pNk_Um8XmBjJ5KzS0ZjTU80A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: debian-9 template
Thanks for comments but still no success. Does anyone know how to access files or a terminal for deb-9. Have tried qvm-run -a debian-9 gnome-terminal AND prompt box says "Running gnome-terminal on debian-9. PROBLEM is - it still doesn't appear anywhere. NOTHING AVAILABLE - files,terminal, anything. (Think I might need to give up and try and use FEDORA) -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/29fbf715-7e07-4b20-8949-c6aa405541b6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: QUBES 4.0 | Installation issue: [Dom0] Qubes OS Setup, Configuring TemplateVM fedora-26 freezed
I have been unable to install due to the same error. Installing on USB 500gb hard drive. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1509cc43-3647-48c5-8c13-51d3caa36085%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Installing the boot loader to /dev/sda6 instead of /dev/sda
Is there a way to specify that the boot loader will be installed to a partition, i.e. /dev/sda6 instead of to /dev/sda during Qubes 4.0 install? I couldn't figure it out in the install menu, the only thing I can select is not to install the boot loader to /dev/sda—which would be fine, if I can then do it later. The reason I want to do this is I want to just experiment with Qubes, so want to keep my MBR as is, boot to other GNU systems, and when I want to play with Qubes, I'll chainload its boot partition from the regular GRUB I use—for this the boot loader needs to be installed to Qubes's partition. The only way of achieving it now—that I can think of is: — install Qubes to sda6 without the boot loader — install it again to a USB — boot from the USB — run grub-install to the /dev/sda6 — I'm assuming Qubes uses GRUB — I've never used Qubes before — then Qubes should be bootable from sda6 via chainloading Any easier way to do this? -- 白い熊 -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b188ce27-4918-45f2-a9ab-6ab760b928a6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: debian-9 template
tried --- sudo qubes-dom0-update --enablerepo=qubes-templates-community --action=reinstall qubes-template-debian-9 Again it appears to reinstall - message appears saying successfully installed. Then try to start DEBIAN-9 VM and get "ERROR:VM directory does not exist: /var/lib/qubes/vm-templates/debian-9". Help! -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/69ea12a6-e96e-4078-b10d-dd8822668f0f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Thinkpad T440s i7 and Qubes 4.0 compatibility
On Sat, 28 Apr 2018, john wrote: maybe, I am missing something, did you try installing 4.0 in legacy mode? it seems with the older thinkpads this is the way to avoid the dreaded black screen EFI thing. I tried installing Qubes 4.0 in legacy mode at first. I was presented with the legacy-installer, and after hitting "Return" the screen went black. UEFI-installer worked like charm, but booting after install did not (stuck in boot-loop, no grub-menu). Eivind -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0243fee9-9cff-8919-629a-5ba035fdd234%40riseup.net. For more options, visit https://groups.google.com/d/optout. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/alpine.LFD.2.20.1804291524300.1734%40localhost. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4 on USB Not Rebooting
On Monday, April 23, 2018 at 8:21:01 AM UTC-4, myblackc...@gmail.com wrote: > Hey, > > i have the same problems and Qubes 4.0 not want boot from the USB Device. > > For this probleme i install Fedora on Virtualbox and copy the Image with the > command "dd if=Qubes-R4.0-x86_64.iso of=/dev/sdb bs=1M && sync" successfully > on my device. > > The probleme by this the Stick boot and i can see some Linux commands. After > this, the screen is only black and nothing happened. > > This are my Bios settings: > > https://picload.org/view/dorgorpl/img_2 ... 4.jpg.html > > https://picload.org/view/dorgorpi/img_2 ... 9.jpg.html > > Hope, that someone can help. > > regards I finally found a resolution for this. There is a doc in Qubes that discusses how some firmware will not recognize the default Qubes EFI configuration. Here is what makes the computer boot the drive after installing qubes to a USB: Rename the qubes EFI folder: sudo mv /boot/efi/EFI/qubes/ /boot/efi/EFI/BOOT Rename the two files: sudo mv /boot/efi/EFI/BOOT/xen.efi /boot/efi/EFI/BOOT/BOOTX64.efi sudo mv /boot/efi/EFI/BOOT/xen.cfg /boot/efi/EFI/BOOT/BOOTX64.cfg Now when you restart the computer and choose the USB drive in the BIOS, it will boot the USB drive into Qubes. FYI, there is a warning in the document that this may need to be done again after every kernel and Xen update. I sure hope Qubes developers fix this. If an update occurs and you restart before making these changes you won't be able to boot back up onto the USB again to make the changes! A reinstall is in you near future! -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/825b65d1-6cb5-41ef-8fcf-b67da22f0737%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Remote Control Question
On 04/28/2018 08:50 PM, Stuart Perkins wrote: Hi list. I'm considering setting up Qubes capable server at my home. What I need, however, is to be able to remotely control it. Updates...reboot/stop/start system and app vm's etc. Is this even possible with Qubes? I currently run a Ubuntu powered old laptop as a "server" and have it hosting a couple of VM's with virtualbox. I can ssh into it and even have an sshuttle setup for VPN over SSH functionality for when I need to do something "gui" remotely. One of my VM's is an old XP system which monitors my solar electric. One is a ubuntu install hosting a Drupal website. One is also installed which is a full blow VPN server for when I need to do more than just simple things...I rarely use this one. I will be upgrading my "server" hardware to a real server class platform one of these days, and I would like something specific to running independent VM's, but the remote maintenance might be a Qubes eliminating need... Anybody here attacked a remote console to dom0 before, or does it so completely violate the philosophy of Qubes that it is an absolute no-way-in-hell thing? Stuart Hi Stuart, Philosophies aside, you can do whatever you want :) Adding networking to dom0 is certainly defeating a lot of the hardwork/security that went into qubes. If you wanted to go this route you might consider just running Xen directly? Especially if you are putting this in your closet/basement? There is another issue however, aside from just giving dom0 network access, and that's the LUKS password. If you needed to reboot the machine entirely from remote, you'd be stuck if you had LUKS encryption on the disk with no way to enter it remotely. Unless you do what I did, and hook up a Raspberry Pi to the serial console of my machine, and update the kernel boot line in grub to use the serial console (Note: This REQUIRES you to use the serial console to enter the LUKS password, you lose the ability to enter it from your keyboard locally). Stating the obvious, if someone gets access to the Raspberry Pi I'd be in a bit of trouble, though as long as I remember to log out of the shell at the serial console on the Pi, someone compromising that machine does not immediately give them access to the Qubes box, they would have to guess my password or wait for me to log back in and enter it if I didn't know they were there and they could capture it. I run OSSEC on this PI to help combat that issue. Also considering defense in depth, I can only access that Raspberry Pi via VPN, I do NOT expose it directly to the internet, it also sits on it's own VLAN which I leave isolated, so when I do have to do remote administration I first have to grant access to that VLAN from my router console. So at the end of the day, less secure? Yes. Added convenience? Yes. Added complexity? Yes... You can draw the line wherever you want :) Ed -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/pc4lao%24llv%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 4.0 - ACPI Errors during boot
Hi Everyone! During the boot and before unlock the LuKS volume I'm getting a lot of ACPI errors regarding Namespace lookup failure: [ 1.726445] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) [ 1.726525] ACPI Error: Method parse/execution failed _PR.CPU1._CST, AE_NOT_FOUND (20170728/psparse-550) [ 1.726609] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) [ 1.726739] ACPI Error: Method parse/execution failed _PR.CPU2._CST, AE_NOT_FOUND (20170728/psparse-550) [ 1.726932] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) [ 1.727136] ACPI Error: Method parse/execution failed _PR.CPU3._CST, AE_NOT_FOUND (20170728/psparse-550) [ 1.727332] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) [ 1.727517] ACPI Error: Method parse/execution failed _PR.CPU4._CST, AE_NOT_FOUND (20170728/psparse-550) [ 1.727709] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) [ 1.727896] ACPI Error: Method parse/execution failed _PR.CPU5._CST, AE_NOT_FOUND (20170728/psparse-550) [ 1.728105] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) [ 1.728290] ACPI Error: Method parse/execution failed _PR.CPU6._CST, AE_NOT_FOUND (20170728/psparse-550) [ 1.728483] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) [ 1.728667] ACPI Error: Method parse/execution failed _PR.CPU7._CST, AE_NOT_FOUND (20170728/psparse-550) How can I solve this? Thank you -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2ff8aa16d3ee91c3806be4e5a01096e5%40disroot.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: debian-9 template
On Sun, April 29, 2018 12:20 pm, higginsonj...@gmail.com wrote: > > tried --- > > > sudo qubes-dom0-update --enablerepo=qubes-templates-community > --action=reinstall qubes-template-debian-9 > > > Again it appears to reinstall - message appears saying successfully > installed. > > Then try to start DEBIAN-9 VM and get > "ERROR:VM directory does not exist: /var/lib/qubes/vm-templates/debian-9". There was a recent bug fix pushed to testing that addresses this. You can either upgrade dom0 to the testing repo (but be aware some updates in there may have other bugs) or manually reinstall with a dnf remove then regular install of qubes-template-debian-9. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d67d19baa785bfaf9c6e4edc4f9ee4a6.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Issues with Qubes 4.0 on Lenovo T450s
On Sat, April 28, 2018 8:15 pm, maur...@disroot.org wrote: > Hi Everyone. > > Whenever I try to get to private more in FF by pressing ctrl+shift+p all > my VMs get paused. Is there a reason for this? Is it possible to disable > it? Whenever that happen I have to manually select each VM and resume it, > which is kind of annoying. There is a way to customize the XFCE keyboard shortcuts, but I can't remember how exactly. Think it involves editing a file. Try searching this mailing list- I like to use https://www.mail-archive.com/qubes-users@googlegroups.com/. > Qube manager is no longer started by default like in version 3.2, instead > I got now an icon on the top right corner that allows to invoke > operations on the running VMs. But some of the VMs in there are show an > inconsistent state (I'm only allow to check the logs, set the preferences > or kill it and not shut them down as with some of the displayed VMs) > there's a cursor looping for the inconsistent VMs. Is there a way to fix > this? https://github.com/QubesOS/qubes-issues/issues/3660 > Also Qube manager shows all VMs and not only the running ones, is > there an option to show only the VMs that are running? Qube Manager > doesn't refresh the state of the VMs as it happened in Qubes 3.2. Instead > I have to manually hit refresh whenever I want to check when a VM has > stopped or started. Is there a way one could have check the state of the > VMs on Qube manager as it happened on version 3.2? Qube Manager was originally not going to be included in 4.0 and got re-added relatively late so it still has some display issues. To refresh a single VM, you can click on a different one then back on that VM. It's a little faster than refreshing them all. > During the boot and before unlock the LuKS volume I'm getting a lot of > ACPI errors regarding Namespace lookup failure: I get these too but they don't seem to hurt anything. Try searching https://github.com/QubesOS/qubes-issues/issues to see if there's more info in there. > Shutdown is also taking an huge amount of time to complete spending lots > of time waiting for the disk to be ready. Try manually shutting down any AppVMs you have running first, before shutting down Qubes. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2e289dd237bffe9bea9b0573aa20e2fd.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Assigning USB to VM fails
lørdag den 28. april 2018 kl. 18.03.33 UTC+2 skrev awokd: > And qubes-usb-proxy installed in the template used for lokal-belkin? If > so, I'm not sure what else it could be... Yes it is. I don't know either. It seems that RedHat should just get exFat fs support and everything would have been fine :) I guess I need to have 1 sys-usb for offloading images from my camera and 1 sys-usb for local networking via usb. Weird, but I will maybe try from scratch with sys-usb on debian. Sincerely Max -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e78d3114-0aa7-4056-8158-30a085a9674e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Issues with Qubes 4.0 on Lenovo T450s
On 04/29/2018 08:38 PM, 'awokd' via qubes-users wrote: > On Sat, April 28, 2018 8:15 pm, maur...@disroot.org wrote: >> Hi Everyone. >> > > >> Whenever I try to get to private more in FF by pressing ctrl+shift+p all >> my VMs get paused. Is there a reason for this? Is it possible to disable >> it? Whenever that happen I have to manually select each VM and resume it, >> which is kind of annoying. > > There is a way to customize the XFCE keyboard shortcuts, but I can't > remember how exactly. Think it involves editing a file. Try searching this > mailing list- I like to use For XFCE: Qubes menu -> System Tools -> Keyboard -> Application Shortcuts Alternatively, edit the following file but the gui above is more straightforward: $HOME/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml > https://www.mail-archive.com/qubes-users@googlegroups.com/. > >> Qube manager is no longer started by default like in version 3.2, instead >> I got now an icon on the top right corner that allows to invoke >> operations on the running VMs. But some of the VMs in there are show an >> inconsistent state (I'm only allow to check the logs, set the preferences >> or kill it and not shut them down as with some of the displayed VMs) >> there's a cursor looping for the inconsistent VMs. Is there a way to fix >> this? > > https://github.com/QubesOS/qubes-issues/issues/3660 > >> Also Qube manager shows all VMs and not only the running ones, is >> there an option to show only the VMs that are running? Qube Manager >> doesn't refresh the state of the VMs as it happened in Qubes 3.2. Instead >> I have to manually hit refresh whenever I want to check when a VM has >> stopped or started. Is there a way one could have check the state of the >> VMs on Qube manager as it happened on version 3.2? > > Qube Manager was originally not going to be included in 4.0 and got > re-added relatively late so it still has some display issues. To refresh a > single VM, you can click on a different one then back on that VM. It's a > little faster than refreshing them all. > >> During the boot and before unlock the LuKS volume I'm getting a lot of >> ACPI errors regarding Namespace lookup failure: > > I get these too but they don't seem to hurt anything. Try searching > https://github.com/QubesOS/qubes-issues/issues to see if there's more info > in there. > >> Shutdown is also taking an huge amount of time to complete spending lots >> of time waiting for the disk to be ready. > > Try manually shutting down any AppVMs you have running first, before > shutting down Qubes. > > -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6f4d0850-7909-2e74-d3a7-e7f8a853c5b2%40maa.bz. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Issues with Qubes 4.0 on Lenovo T450s
Thank you all! I've managed to disable the shortcut on xfce! Now I can finally use FF in private more :) Didn't find anything related with the ACPI errors though. I think its best if I can raise an issue in github? April 29, 2018 7:38 PM, "awokd" wrote: > On Sat, April 28, 2018 8:15 pm, maur...@disroot.org wrote: > >> Hi Everyone. >> >> Whenever I try to get to private more in FF by pressing ctrl+shift+p all >> my VMs get paused. Is there a reason for this? Is it possible to disable >> it? Whenever that happen I have to manually select each VM and resume it, >> which is kind of annoying. > > There is a way to customize the XFCE keyboard shortcuts, but I can't > remember how exactly. Think it involves editing a file. Try searching this > mailing list- I like to use > https://www.mail-archive.com/qubes-users@googlegroups.com. > >> Qube manager is no longer started by default like in version 3.2, instead >> I got now an icon on the top right corner that allows to invoke >> operations on the running VMs. But some of the VMs in there are show an >> inconsistent state (I'm only allow to check the logs, set the preferences >> or kill it and not shut them down as with some of the displayed VMs) >> there's a cursor looping for the inconsistent VMs. Is there a way to fix >> this? > > https://github.com/QubesOS/qubes-issues/issues/3660 > >> Also Qube manager shows all VMs and not only the running ones, is >> there an option to show only the VMs that are running? Qube Manager >> doesn't refresh the state of the VMs as it happened in Qubes 3.2. Instead >> I have to manually hit refresh whenever I want to check when a VM has >> stopped or started. Is there a way one could have check the state of the >> VMs on Qube manager as it happened on version 3.2? > > Qube Manager was originally not going to be included in 4.0 and got > re-added relatively late so it still has some display issues. To refresh a > single VM, you can click on a different one then back on that VM. It's a > little faster than refreshing them all. > >> During the boot and before unlock the LuKS volume I'm getting a lot of >> ACPI errors regarding Namespace lookup failure: > > I get these too but they don't seem to hurt anything. Try searching > https://github.com/QubesOS/qubes-issues/issues to see if there's more info > in there. > >> Shutdown is also taking an huge amount of time to complete spending lots >> of time waiting for the disk to be ready. > > Try manually shutting down any AppVMs you have running first, before > shutting down Qubes. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1effa0f9bc9c27512c995277f3f9ac15%40disroot.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
Chris/Tasket, I am currently using this version: https://github.com/tasket/Qubes-vpn-support "Master version" I have this running in a proxy AppVM (Not in a template) Using PIA VPN service OpenDNS checks out OK I just tried this version in 4.0 in the template. Some notes feedback: 1) When I tried changing the DNS to OpenDNS in my config file: setenv vpn_dns '208.67.222.222 208.67.220.220' I then went to: http://welcome.opendns.com/ It failed and informed me I was not using OpenDNS. 2) The step 3. in the abbreviated instructions say to run: /usr/lib/qubes/qtunnel-setup --config However I had to run: sudo /usr/lib/qubes/qtunnel-setup --config I was able to get to the internetI didn't do any further testing. If you want me to try some things more then happy to help... Thanks again for the work. V -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b86bb2c7-91db-4c6f-aa4d-a9de218eea88%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4 boot ISO
On Sunday, 29 April 2018 01:50:22 UTC+10, awokd wrote: > On Sat, April 28, 2018 2:24 am, Drew White wrote: > > On Saturday, 28 April 2018 02:07:21 UTC+10, awokd wrote: > > > >> On Fri, April 27, 2018 6:40 am, Drew White wrote: > >> > >>> Still not working no matter what I do. > >>> > >>> > >>> > >>> Does anyone have any possible resolution to resolve this please? > >>> > >> > >> How are you making the boot device? If USB from Linux, a standard "cp > >> qubes.iso /dev/xvdj" (where xvdj is your USB device) should work. You > >> can also try switching to legacy boot mode. > > > > I burn it to DVD. It is an ISO after all. > > I always use Legacy Boot mode. > > I had trouble burning to DVD at first because the image is large enough to > require dual-layer burner support. Ended up using Debian Stretch with > default software and a newer drive before I got a good burn. If you're > using some other tool, try Debian instead. The Qubes 4 ISO fits on a normal DVD. So it's fine. The thing is it worked and booted in a Guest once. But wouldn't boot on the PC or using external HDD. This is why I am unsure. I have all the requirements filled, but it won't boot to it because of that issue. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/835f7ea9-a9af-4245-b7b9-b84dd1431bfc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4 boot ISO
On Saturday, 28 April 2018 15:49:23 UTC+10, @LeeteqXV wrote: > > > How are you making the boot device? > > 1. Whenever there is a problem getting for example a USB stick to boot/behave > as a Read-Only boot device from an ISO file, I use either Unetbootin or the > Linux dd command line tool to make the USB stick into a bootable Read-Only > ISO device. That normally works. > > 2. Sometimes the safest bet is also to use BIOS Legacy Mode (disable the BIOS > secure boot function + enable the BIOS CSM legacy mode). > > 3. If an otherwise properly made USB stick still does not boot, there are > also some BIOS systems that oddly places the recognised USB stick "inside" > the list of bootable Hard Drives. Read: AS a Hard Drive, as if you now have > more than your normal 1+ HDDs... > In those cases, you need to enter into the hard drive menu option, change the > order so that the USB stick is the first, and then go back and also place it > before the hard drive in the main Boot order menu (in these cases there are 2 > places to do this, and you must place it first in both those lists...) > > 4. Then there is the not-too-rare situation where a particular > system/computer is incompatible with a particular USB stick, so it does not > boot it even if another computer does. Change to another USB stick model/make > and try that one. > > 5. And in some cases, it still fails even if all has been done properly, and > all pieces are technically ready, IF you exit the BIOS when saving the last > changes with the normal direct "exit-and-save-and-reboot" option. Sometimes > you actually have to then power off completely right after it has rebooted > (as long as the BIOS changes are actually saved), remove and re-insert the > USB stick and then power the computer back on. Strange, but that also happens. > > (And add to any possible confusion that yet again some systems seems to alter > the boot order (or have forgotten your saved changes) when you get back into > the BIOS after having physically removed the USB key, or tried to > boot/replace it with another USB key. Sometimes that is only an unsaved > suggestion that happens when you re-enter the BIOS. Your saved order might > still actually be in place as long as you boot from that particular USB stick > you used when saving the BIOS changes the last time.) > > -- > Regards, > Teqleez Thanks for the details, good to know for using USB. But it's an ISO, not a USB Image that I am using. As I stated I am using Legacy. You should put the information you posted here somewhere that it relates to though. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/48e90694-ecb9-477f-856b-a56977de1d39%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
Using debian 9, link indicates "Link is up", I get internet connection, https://www.dnsleaktest.com/ indicates my VPNs IP(despite "setenv vpn_dns '208.67.222.222 208.67.220.220'" in my vpn configuration) when I use this configuration... V -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/71b39261-7ea0-4259-a639-05a007c1cfa0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4 boot ISO
On Mon, Apr 30, 2018, at 02:13, Drew White wrote: > Thanks for the details, good to know for using USB. But it's an ISO, not > a USB Image that I am using. As I stated I am using Legacy. You can burn ISO images to USB sticks, which effectively makes them behave like a CD/DVD. Not sure If I get your meaning in your last comment, unless you did not know you can use ISO files with USB sticks? About not booting the external USB: Ref. #3 in my list about some USBs (sticks, or external drives, no difference here) which sometimes gets listed by the BIOS as Hard Drives, and always then gets listed AFTER the current hard drive. In those cases one need to re-order that list, so that the external USB is tried before the internal HDD. + Also make sure that the USB partition in question actually has the Boot flag after installation. (BIOS can not fix that, AFAIK, need to use a tool like fdisk, gparted, gnome disks or the like.) -- Regards, Teqleez -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1525065533.3298263.1355142464.365AA4B1%40webmail.messagingengine.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4 boot ISO
On Monday, 30 April 2018 15:18:57 UTC+10, @LeeteqXV wrote: > On Mon, Apr 30, 2018, at 02:13, Drew White wrote: > > Thanks for the details, good to know for using USB. But it's an ISO, not > > a USB Image that I am using. As I stated I am using Legacy. > > You can burn ISO images to USB sticks, which effectively makes them behave > like a CD/DVD. > Not sure If I get your meaning in your last comment, unless you did not know > you can use ISO files with USB sticks? > You can, but I'm using a DVD, not a USB that takes the ISO and writes it to USB. Even if I did that I would still have the same issue if it isn't even booting from an ISO OR a DVD. There is a lot more than just burning it that is causing any issue. It's the ISO/DVD itself from Qubes that has an issue. Nothing my end, just the Qubes ISO from Qubes. > About not booting the external USB: > > Ref. #3 in my list about some USBs (sticks, or external drives, no difference > here) which sometimes gets listed by the BIOS as Hard Drives, and always then > gets listed AFTER the current hard drive. In those cases one need to re-order > that list, so that the external USB is tried before the internal HDD. > > + Also make sure that the USB partition in question actually has the Boot > flag after installation. > (BIOS can not fix that, AFAIK, need to use a tool like fdisk, gparted, gnome > disks or the like.) > > -- > Regards, > Teqleez -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1eccf641-3270-46da-9262-aba2b9063c07%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Help understanding qubes networking
Hello, I'm trying to understand where I can tweak my network configuration in a fedora-26-min based AppVM. As far as I understand networking for eth0 is currently configured by DHCP from the sys-firewall AppVM. I am trying to understand how networking is configured. Nomally I would expect to find the IP-configuration for eth0 in /etc/sysconfig/network-scripts but there is only an ifcfg-lo not an ifcfg-eth0. Nameservers are set as usual in /etc/resolv.conf. I assume that there are qubes specific script involved? Can someone explain? I would like to know how networking is setup and how I can change my configuration (likely on sys-firewall) so that I can decide which AppVM gets which IP-address. I looked at the Qubes OS networking doc located at https://www.qubes-os.org/doc/networking/ but it seems that the side is gone. -> 404 not found [799] -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20180430064807.mkb2sy7ruos4nell%40my-privmail. For more options, visit https://groups.google.com/d/optout.
