Re: [qubes-users] TemplateVM updates almost instantly fail when target is VPN qube but dom0 updates run just fine
@unman The dom0 updates setting is set correctly and working as intended through the VPN qube, I haven't tried browsing from the VPN qube itself but I can definitely browse from an AppVM connected to it and I can confirm that all the browsing being done there is tunneled through the VPN. I'm using a fedora minimal and I don't see any sort of package requirement for a qube to install to provide TemplateVM updates as I read through the Fedora Minimal documentation. Only thing that has a requirement from the looks of it is a qube for dom0 updates. Thanks for the suggestion about updateProxy service. I suppose I should set it to provide qubes-yum-proxy, is that right? @Chris Thank you for telling me that as I too am using fedora-30, specifically fedora-30-minimal Templates I am trying to do a setup where a qube is dedicated for the purpose of updating, something similar to yours I believe. I'll try to work on this tomorrow and report results back to this topic. -- 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/7623ccd5-9a7d-4bed-b331-b54a6008aa5c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes: Encrypted LVM
By all means hold your horses on asking if Qubes is vulnerable to every single one of those lol I used to be paranoid about Computer Security but if you ain't even gonna bother to delve deep down from how computers work up to the way computer applications/programs work then you should just focus on what you can actually do as a user to strengthen your privacy. If your biggest concern is trusting your hardware then the best thing you can do is to buy Hardware that respects your privacy and install hardened linux/bsd into it and never use Windows 10 ever again. https://www.bleepingcomputer.com/news/hardware/there-are-only-25-devices-that-respect-your-privacy/ Or if you want an easy life just do away with this: https://puri.sm/products/librem-15/ Only thing left to do with that is to harden it and install your privacy goodies -- 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/e80c2e06-1904-483b-8247-b74c3df40413%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Unable to get network adapter working
Hi all! It's my first time installing Qubes and I need some help with my network adapters. I am using Qubes 4.0.1 The hardware is Fitlet2 with Intel Celeron J3455 (supports both VT-x and VT-d). It comes with 4 Gigabit Ethernet ports using Intel i211. Installation was successful but EFI boot entry could not be added. Editing EFI entries using tty2 (Ctrl-Alt-F2) or 'Rescue a Qubes' mode both throw errors. Eventually solved by booting into Live Ubuntu and editing EFI entries from there. Successfully booted into Qubes but couldn't get network working. 1. Physically, port LEDs go off and start blinking after awhile. Keeps repeating. 2. Network icon on top right is red and shows 'loading animation' 3. Network adapter can negotiate speed and duplex but cannot get IP address from DHCP server 4. Changing of network cable and connecting to another switch gives the same results 5. dmesg shows adapter in reset cycle 6. Network adapter works perfect when boot into Live Ubuntu using same hardware dmesg from Qubes [user@sys-net ~]$ sudo dmesg | grep igb [ 4.296718] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k [ 4.296783] igb: Copyright (c) 2007-2014 Intel Corporation. [ 4.7426971 igb :00:06.0: added PHC on eth0 [ 4.742724] igb :00:06.0: Intel(R) Gigabit Ethernet Network Connection [ 4.742758] igb :00:06.0: eth0: (PCIe:2.5Gb/s:Width xl) 00:01:c0:15:66:d2 [ 4.742798] igb :00:06.0: eth0: PBA No: FF-0FF [ 4.742826] igb :00:06.0: Using MSI interrupts. 1 rx queue(s), 1 tx queue(s) [ 5.034919] igb :00:07.0: added PHC on eth1 [ 5.634921] igb :00:07.0: Intel(R) Gigabit Ethernet Network Connection [ 5.034924] igb :00:07.0: eth1: (PCIe:2.5Gb/s:Width xl) 00:01:c0:15:46:54 [ 5.034927] igb :00:07.0: eth1: PBA No: FF-0FF [ 5.034929] igb :00:07.0: Using MSI interrupts. 1 rx queue(s), 1 tx queue(s) [ 5.281971] igb :00:08.0: added PHC on eth2 [ 5.281973] igb :00:08.0: Intel(R) Gigabit Ethernet Network Connection [ 5.281976] igb :00:08.0: eth2: (PCIe:2.5Gb/s:Width xl) 00:01:c0:15:46:55 [ 5.281979] igb :00:08.0: eth2: PBA No: FF-0FF [ 5.281981] igb :00:08.0: Using MSI interrupts. 1 rx queue(s), 1 tx queue(s) [ 5.564667] igb :00:09.0: added PHC on eth3 [ 5.564697] igb :00:09.0: Intel(R) Gigabit Ethernet Network Connection [ 5.564735] igb :00:09.0: eth3: (PCIe:2.5Gb/s:Width xl) 00:01:c0:15:66:d1 [ 5.564780] igb :00:09.0: eth3: PBA No: FF-0FF [ 5.564810] igb :00:09.0: Using MSI interrupts. 1 rx queue(s), 1 tx queue(s) [ 5.614700] igb :00:08.0: ens8: renamed from eth2 [ 5.639207] igb :00:07.0: ens7: renamed from eth1 [ 5.949373] igb :00:09.0: ens9: renamed from eth3 [ 5.962094] igb :00:06.0: ens6: renamed from eth0 [11.744508] igb :00:06.0: igb: ens6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [13.728120] igb :00:06.0: Reset adapter [17.761975] igb :00:06.0: igb: ens6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [23.007124] NETDEV WATCHDOG: ens6 (igb): transmit queue 0 timed out [23.067303] Modules linked in: ip6table_raw iptable_raw nft_reject_ipv4 nft_reject xen_netback nf_conntrack_ipv6 nf_tables_ipv6 nf_tables_ipv4 nf_tables nfnetlink xt_REDIRECT nf_nat_redirect ip6table_filter ip6_tables xt_conntrack ipt_v4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nt_nat_ipv4 nf_conntrack libcrc32c joydev intel_rapl crctl0dif_p ghash_clmulni_intel intel_rapl_perf ttm drm_kms_helper igb ptp pps_core serio_raw drm i2c_algo_bit ehci_pci pcspkr dca i2c_piix4 floppy u2mfn(0) xen_gntdev xen_gntalloc xen_blkback xenfs xen_privcmd xen_evtchn xen_blkfront [23.009259] igb :00:06.0: Reset adapter [27.72] igb :00:06.0: igb: ens6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX dmesg from Ubuntu ubuntu@ubuntu:~$ sudo dmesg | grep igb [13.454671] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k [13.454673] igb: Copyright (c) 2007-2014 Intel Corporation. [13.454862] igb :01:00.0: enabling device ( -> 0002) [13.700328] igb :01:00.0: added PHC on eth0 [13.700330] igb :01:00.0: Intel(R) Gigabit Ethernet Network Connection [13.700332] igb :01:00.0: eth0: (PCIe:2.5Gb/s:Width xl) 00:01:c0:15:46:54 [13.700335] igb :01:00.0: eth0: PBA No: FF-0FF [13.700337] igb :01:00.0: Using MSI interrupts. 2 rx queue(s), 2 tx queue(s) [13.700418] igb :02:00.0: enabling device ( -> 0002) [13.944973] igb :02:00.0: added PHC on eth1 [13.944974] igb :02:00.0: Intel(R) Gigabit Ethernet Network Connection [13.944977] igb :02:00.0: eth1: (PCIe:2.5Gb/s:Width xl) 00:01:c0:15:66:d1 [I3.944979] igb :02:00.0: eth1: PBA No: FF-0FF [13.944981] igb :02:00.0: Using MSI interrupts. 2 rx queue(s), 2 tx queue(s) [13.945065] igb :03:00.0: enabling device ( -> 0002) [14.186215] igb :03:00.0: added PHC on eth2 [14.186217] igb :03:00.0: Intel(R) Gigabit Ethernet Network Connection [14.186219] igb :0
Re: [qubes-users] Unable to get network adapter working
Chris: Hi all! Welcome! Successfully booted into Qubes but couldn't get network working. 1. Physically, port LEDs go off and start blinking after awhile. Keeps repeating. 2. Network icon on top right is red and shows 'loading animation' 3. Network adapter can negotiate speed and duplex but cannot get IP address from DHCP server 4. Changing of network cable and connecting to another switch gives the same results 5. dmesg shows adapter in reset cycle 6. Network adapter works perfect when boot into Live Ubuntu using same hardware Quickest thing to try is to switch sys-net's template to Debian. Also, experiment with https://www.qubes-os.org/doc/pci-devices/#pci-passthrough-issues attach options. -- 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/d8c9c33b-e84b-1b3a-e5cd-349c269ef579%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] TemplateVM updates almost instantly fail when target is VPN qube but dom0 updates run just fine
On Wed, Jun 26, 2019 at 02:54:04AM -0700, Sphere wrote: > @unman The dom0 updates setting is set correctly and working as intended > through the VPN qube, I haven't tried browsing from the VPN qube itself but I > can definitely browse from an AppVM connected to it and I can confirm that > all the browsing being done there is tunneled through the VPN. > > I'm using a fedora minimal and I don't see any sort of package requirement > for a qube to install to provide TemplateVM updates as I read through the > Fedora Minimal documentation. Only thing that has a requirement from the > looks of it is a qube for dom0 updates. > > Thanks for the suggestion about updateProxy service. I suppose I should set > it to provide qubes-yum-proxy, is that right? > The new name is qubes-updates-proxy service: enable that. I think the other is a red herring. > @Chris Thank you for telling me that as I too am using fedora-30, > specifically fedora-30-minimal Templates > > I am trying to do a setup where a qube is dedicated for the purpose of > updating, something similar to yours I believe. > > I'll try to work on this tomorrow and report results back to this topic. > -- 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/20190626130646.uv3xto37idiffq6u%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Unable to get network adapter working
On 6/26/19 7:56 AM, 'awokd' via qubes-users wrote: Chris: Hi all! Welcome! Successfully booted into Qubes but couldn't get network working. 1. Physically, port LEDs go off and start blinking after awhile. Keeps repeating. 2. Network icon on top right is red and shows 'loading animation' 3. Network adapter can negotiate speed and duplex but cannot get IP address from DHCP server 4. Changing of network cable and connecting to another switch gives the same results 5. dmesg shows adapter in reset cycle 6. Network adapter works perfect when boot into Live Ubuntu using same hardware Quickest thing to try is to switch sys-net's template to Debian. Also, experiment with https://www.qubes-os.org/doc/pci-devices/#pci-passthrough-issues attach options. Debian can be a good sys-net distro, but unfortunately the template doesn't have all the wifi drivers pre-installed... I have to manually install 'firmware-iwlwifi' to get Intel cards working. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/99f50700-cd46-c103-f51a-d858b7f24bd6%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [Dom0] error when trying to setup
It worked, Thanks a lot! -- 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/859942d4-7c97-4ace-a243-f4af551f56a6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] TemplateVM updates almost instantly fail when target is VPN qube but dom0 updates run just fine
On 6/26/19 9:06 AM, unman wrote: On Wed, Jun 26, 2019 at 02:54:04AM -0700, Sphere wrote: @unman The dom0 updates setting is set correctly and working as intended through the VPN qube, I haven't tried browsing from the VPN qube itself but I can definitely browse from an AppVM connected to it and I can confirm that all the browsing being done there is tunneled through the VPN. I'm using a fedora minimal and I don't see any sort of package requirement for a qube to install to provide TemplateVM updates as I read through the Fedora Minimal documentation. Only thing that has a requirement from the looks of it is a qube for dom0 updates. Thanks for the suggestion about updateProxy service. I suppose I should set it to provide qubes-yum-proxy, is that right? The new name is qubes-updates-proxy service: enable that. I think the other is a red herring. In my case qubes-updates-proxy was already enabled and working with debian and earlier versions of fedora. Also would like to clarify that my updatevm is a dedicated fedora-30 VM 'sys-update' that is downstream from the VPN VM; sys-update is often in stopped state and has to start when updates are performed, but not sure if that matters. I don't see anything obvious in the fedora-30 log except for a very large number of 'success' messages like: Jun 26 09:47:18 fedora-30 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=qubes-updates-proxy-forwarder@13-127.0.0.1:8082-127.0.0.1:45048 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jun 26 09:47:18 fedora-30 systemd[1]: qubes-updates-proxy-forwarder@13-127.0.0.1:8082-127.0.0.1:45048.service: Succeeded. I wonder if its restarting over and over. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/d8b0b945-6282-2bf4-03af-785350583ec3%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Trouble setting up network
After I Add network controller to sys-net I go to applications to add network shortcut but no applications appear but when I try to refresh I get the following error: ‘Domain sys-net has failed to start: internal error: libxenlight failed to create new domain sys-net’ I can’t edit anything under network connections Also I set up my network as: says-net(with Realtek network device added)-> none sys-firewall-> says-net is this a secure setup? If someone could help me connect to the internet it would be greatly appreciated. -- 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/9502f7fe-f728-4476-9d0d-d5866aeb5489%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: How to creat a new vm with Tor configurating trough whonix
thanks awokd. works perfectly -- 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/e7bfeeeb-6217-46c8-9448-ae0b8580%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Trouble setting up network and connecting to the internet
After I Add network controller to sys-net I go to applications to add network shortcut but no applications appear but when I try to refresh I get the following error: ‘Domain sys-net has failed to start: internal error: libxenlight failed to create new domain sys-net’ I can’t edit anything under network connections . When I go to says-firewall I get the error: sys-firewall is connected to sys-net which does not support firewall. But I get a loop error when I try to add the firewall I get a loop error. Also I set up my network as: sys-net(with Realtek network device added)-> none sys-firewall-> says-net is this a secure setup? If someone could help me give me a full explanation on how to connect to the internet it would be greatly appreciated. -- 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/b3f0fced-c3d5-4b29-b88e-7941617696fa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] TemplateVM updates almost instantly fail when target is VPN qube but dom0 updates run just fine
Now I see this affects Debian templates also. Its just that Debian is a little more persistent and may succeed sometimes. I believe the culprit is with the fedora-30 version of the updates proxy – it seems to be un-blocking the update procedure before it is ready to handle traffic. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/7995ab54-248f-9d07-97fe-643e217a8759%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] wasabi in qubes
I wouild like to use wasbi in a whonix VM. Can any one tell me how to make it work step by step_ Thansk for youre time and suport -- 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/d6342f04-2d14-44bf-b759-825a7190e034%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [Dom0] error when trying to setup
shamaarmarti...@gmail.com: It worked, Thanks a lot! I saw you started a couple other threads. Are you still having trouble with sys-net? Looks like you have one of those buggy Realtek adapters. Try also adding the Realtek Cardbus device to sys-net the same way you added the wifi adapter, then seeing if it starts. -- 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/44bb1e5c-d362-f2aa-84e0-61306ca07a7e%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] wasabi in qubes
ehag...@gmail.com: I wouild like to use wasbi in a whonix VM. Can any one tell me how to make it work step by step_ Assuming Wasabi is a cloud provider and assuming it has some Linux client (would be good if you provided more detail so people don't have to guess), the direct answer to your question as stated would be to install their client software into the whonix-ws-14 template. However, unless you've audited their software this could be a bad idea from an anonymity perspective as it may link your identity across all Whonix client sessions. Safer option would be to clone whonix-ws-14 to a new template just for Wasabi use, install their software in it, then create an AppVM based on it networked to sys-whonix. -- 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/4f723f52-0bd5-8dad-587c-bd0698f15142%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] no DNS resolving being passed to sys-firewall or other appVMs after updates?
I am not sure if this is related to recent updates but after updating today and doing a reboot, my sys-firewall and other appVMs are not getting DNS resolving working. - sys-net (fedora30) starts up with out an issue, can resolve and connect to the internet - sys-firewall starts up and gets an IP address, it can ping sys-net and hosts on the internet by IP but can not by name. - appVMs are the same as sys-firewall on sys-firewall and appVMs I have two entries in /etc/resolv.conf 10.139.1.1 and .2 I am not sure what these IPs are as they do not show up in qubes manager and I can not ping them. IPs all start at 10.139.0.5 which is sys-net The only way I can get to the internet is to use Tor or VPN which don't rely on the system DNS. Is anyone else experiencing this, does anyone know what 1.1 and 1.2 hosts are or how I can get DNS up and running again? cubit -- 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/LiJcm7V--B-1%40tutanota.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [Dom0] error when trying to setup
Now I get the error: Unable to reset PCI device :00:1f.4 no FLR PM reset or bus reset available. I also get a failed to start kernel module when booting but I log in fine. I also forgot to mention that I created a couple installation partitions during my earlier failed attempts( stupid on my part I just thought qubes was just as easy as setting up any other os) would formatting my SSD get rid of the partitions and the bugs without destroying my card? I know how to through windows but qubes whipped it off of my drive. Is there a way to do this through a qubes terminal? You’ve Been a great help btw. -- 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/73e251b7-a664-48ee-9e9a-42a6d1d34d76%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [Dom0] error when trying to setup
shamaarmarti...@gmail.com: Now I get the error: Unable to reset PCI device :00:1f.4 no FLR PM reset or bus reset available. Set that device to not require strict reset, either by clicking the large button at the bottom of the Devices tab, or https://www.qubes-os.org/doc/pci-devices/#no-strict-reset. I also get a failed to start kernel module when booting but I log in fine. Ignore it. I also forgot to mention that I created a couple installation partitions during my earlier failed attempts( stupid on my part I just thought qubes was just as easy as setting up any other os) would formatting my SSD get rid of the partitions Yes and the bugs No without destroying my card? I know how to through windows but qubes whipped it off of my drive. Is there a way to do this through a qubes terminal? You’ve Been a great help btw. Not sure how formatting could destroy your card. If you're sure you want to erase everything on the disk, when you install Qubes and are configuring the drive choose the option to make additional space available and select everything so it deletes it all. -- 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/561c009a-8d91-4f67-80d4-23c1063540e0%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: bluetooth support in dom0
So I've gone through all the trouble installing blueman and exposing my hypervisor to all the building. I have found out that bluetooth headphones operate at 2.4ghz which happens to be the same frequency as my Dell's wireless card. So if you attempt to listen to music via youtube, evntually the internet connection will become unusable, as the latency of the sound reaching your head. I would suggest everyone wanting to use wireless mouses to stick to those with an usb dongle. I don't recommend using wireless keyboards at all, but if you do, use one with an usb dongle and don't use the internal laptop bluetooth card. As for bluetooth headphones, those things are only good for listening to your smartphone's music when you're in the bus. Or listening to music while you're walking, which will probably lead to you getting run over by a car. Just stick to wired headphones. If you want to move more freely, use a p2 extension for the audio cable. Conclusion: there's still no good reason at all to activate bluetooth on dom0. -- 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/c7faa99c-b420-4aab-9b18-bd7036af868b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: bluetooth support in dom0
PS: And since what I said is not specific to Qubes, there doesn't seem to be a good reason to use the internal laptop bluetooth in any operational system at all. -- 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/025a30c4-0147-4e6f-9b15-66a4244804d3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Unable to get network adapter working
On 6/26/19 1:33 PM, Chris Laprise wrote: On 6/26/19 7:56 AM, 'awokd' via qubes-users wrote: Chris: Hi all! Welcome! Successfully booted into Qubes but couldn't get network working. 1. Physically, port LEDs go off and start blinking after awhile. Keeps repeating. 2. Network icon on top right is red and shows 'loading animation' 3. Network adapter can negotiate speed and duplex but cannot get IP address from DHCP server 4. Changing of network cable and connecting to another switch gives the same results 5. dmesg shows adapter in reset cycle 6. Network adapter works perfect when boot into Live Ubuntu using same hardware Quickest thing to try is to switch sys-net's template to Debian. Also, experiment with https://www.qubes-os.org/doc/pci-devices/#pci-passthrough-issues attach options. Debian can be a good sys-net distro, but unfortunately the template doesn't have all the wifi drivers pre-installed... I have to manually install 'firmware-iwlwifi' to get Intel cards working. I don't think you said which template you are using for sys-net did you? IMO use Fedora-30 as last I checked using Debian-9 is likely to mess up your dom0 clock , which matters for updates -- 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/59829b75-3f4d-e297-338c-ad4b0f069d8f%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [Dom0] error when trying to setup
Now the error is: fedora-29 has failed to start after I try to import applications. Based off of what you helped me with so far, I’m going to assume the remaining systems just need to be assigned a PCI device? I’m just not sure which goes where. -- 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/69047f9c-d859-44ad-9922-127c991da5fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [Dom0] error when trying to setup
And I get the same libxenlight error for sys-whonix and disp7764 but I can’t add Bus because of the dynamic memory balance -- 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/be4de489-4fdf-4a63-99d2-155013cae0af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [Dom0] error when trying to setup
shamaarmarti...@gmail.com: And I get the same libxenlight error for sys-whonix and disp7764 but I can’t add Bus because of the dynamic memory balance Don't add devices to other VMs. If you've made changes to VMs besides sys-net, undo them. Does sys-net start now and your networking work? -- 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/aaedbf60-d46e-2301-169b-82e340449052%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Video-screen
On 6/25/19 2:13 AM, 'awokd' via qubes-users wrote: danotty via qubes-users: Hello Does exist a software to capture video-screen in Qubes? Check under Productivity on https://github.com/Qubes-Community/Contents/tree/master/code. you would install a debian or fedora package that does a "screen-grab" if that is what you mean by capture screen or youtube-dl is another package for capturing streaming data but maybe you know this already -- 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/9a8144ea-bf45-712a-33d2-577d3063e15e%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Quick question please, need help!
On 6/21/19 10:37 PM, ljul8047-re5jqeeqqe8avxtiumw...@public.gmane.org wrote: So I’m still learning about Qubes but I have a question please. I was told that if dom0 gets infected, everything in the laptop can be found and read. The ip is not a problem but I’m not sure about the MAC address? If they found out the latter by infecting dom0, what are the possibilities to trace that MAC address to the laptop owner? https://www.qubes-os.org/intro/ I would guess no different than any other operating system / probably your question is not specific to Qubes or this forum the selling point for Qubes seems to be tied to Xen Hypervisor being "bare metal" vs. other efforts at virtualization safety, which I hear even windows is using to some extent now -- 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/e9ca3a6d-cf0a-b278-c84e-a67c9e2a4d32%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] wasabi in qubes
'awokd' via qubes-users: > ehag...@gmail.com: >> I wouild like to use wasbi in a whonix VM. >> >> Can any one tell me how to make it work step by step_ There's some discussion here: https://forums.whonix.org/t/wasabi-wallet-in-whonix/7597. Basically just download it, verify signature, run it, and change config settings to use your gateway's ip for your tor host. > > Assuming Wasabi is a cloud provider and assuming it has some Linux Wasabi is a Bitcoin wallet that facilitates CoinJoins for users: https://www.wasabiwallet.io/. It's a centralized, easy to use solution for people that want to protect against some blockchain analysis. > client (would be good if you provided more detail so people don't have > to guess), the direct answer to your question as stated would be to > install their client software into the whonix-ws-14 template. However, > unless you've audited their software this could be a bad idea from an > anonymity perspective as it may link your identity across all Whonix > client sessions. > > Safer option would be to clone whonix-ws-14 to a new template just for > Wasabi use, install their software in it, then create an AppVM based on > it networked to sys-whonix. > Don't need to install in a template. Just run a release in an AppVM. -- qubenix CODE PGP: FE7454228594B4DDD034CE73A95D4D197E922B20 EMAIL PGP: 96096E4CA0870F1C5BAF7DD909D159E1241F9C54 IRC OTR: DFD1DA35 D74E775B 3E3DADB1 226282EE FB711765 -- 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/170dd2d4-9569-6aba-ec04-08688f68f60f%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4.0.1 Installation To Emergency
'[NOTIFICATION]' via qubes-users: Attachment: Qubes 401 Emergency.jpg Can't seem to install Qubes 4.0.1 on the RAZER BLADE GTX and even on the RTX models. Keeps sending to emergency mode. Using the USB SOFTARE in the link. It is known as ETCHER. What causing this installation being sent to emergency mode at every start of install? Instead of Etcher, try using dd or cp to copy the install ISO directly to your USB on /dev/sdwhatever. See https://www.qubes-os.org/doc/installation-guide/#copying-the-iso-onto-the-installation-medium. -- 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/1e5b9b59-5a15-a471-127d-4f220dc30e0c%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [Dom0] error when trying to setup
Seems like security risk so I didn’t. Sys-net comes to a hault but no error code when starting. -- 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/4bd1716c-da88-4ec5-8749-1b872b3ae730%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Unable to get network adapter working
> Quickest thing to try is to switch sys-net's template to Debian. Also, > experiment with I tried the Debian template but it still doesn't work. Same symptoms > https://www.qubes-os.org/doc/pci-devices/#pci-passthrough-issues attach > options. I need some help here. Couldn't find the configuration file mentioned (/var/lib/qubes/servicevms/ is empty) to insert pci_permissive=1. I am not very good with Linux. -- 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/badbebe5-7a18-4a52-8b81-101e579eeaf0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Unable to get network adapter working
> I don't think you said which template you are using for sys-net did you? The default was Fedora-29. And some observations.. When I shutdown sys-net, the physical LED of the network adapter is still going through the blinking and off cycle. This probably means that it has nothing to do with the vm but with xen itself. -- 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/79f13cca-c707-4437-82f6-23344126c5e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Unable to get network adapter working
On 6/27/19 1:10 AM, Chris wrote: Quickest thing to try is to switch sys-net's template to Debian. Also, experiment with I tried the Debian template but it still doesn't work. Same symptoms https://www.qubes-os.org/doc/pci-devices/#pci-passthrough-issues attach options. I need some help here. Couldn't find the configuration file mentioned (/var/lib/qubes/servicevms/ is empty) to insert pci_permissive=1. I am not very good with Linux. fedora-30 is the newer qubes template , maybe it will have some support for your device, that older OS doesn't , seems logical to me in dom0: $ sudo qubes-dom0-update qubes-template-fedora-30 IMO: you shouldn't have to get into the config files, I'd find new hardware if it was me. -- 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/d8bf8265-9fe7-ee69-a3db-7c7c6da38894%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] TemplateVM updates almost instantly fail when target is VPN qube but dom0 updates run just fine
@unman: thanks for that I also noticed that qubes-updates-proxy.service fails by default on startup and I'm unsure if that is a minimal template-only problem but I was able to fix it thanks to it indicating that the problem is a missing folder: /var/run/qubes-service/qubes-updates-proxy Pretty much the same problem that I get with clocksync service thankfully so I was able to confirm that this service was running as intended systemctl status qubes-updates-proxy: qubes-updates-proxy.service - Qubes updates proxy (tinyproxy) Loaded: loaded (/usr/lib/systemd/system/qubes-updates-proxy.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-06-27 12:06:14 +08; 2s ago Process: 1603 ExecStartPre=/usr/lib/qubes/iptables-updates-proxy start (code=e xited, status=0/SUCCESS) Main PID: 1608 (tinyproxy) Tasks: 3 (limit: 414) Memory: 4.1M CGroup: /system.slice/qubes-updates-proxy.service ├─1608 /usr/bin/tinyproxy -d -c /etc/tinyproxy/tinyproxy-updates.conf ├─1609 /usr/bin/tinyproxy -d -c /etc/tinyproxy/tinyproxy-updates.conf └─1610 /usr/bin/tinyproxy -d -c /etc/tinyproxy/tinyproxy-updates.conf Jun 27 12:06:14 redacted systemd[1]: Starting Qubes updates proxy (tinyproxy)... Jun 27 12:06:14 redacted systemd[1]: Started Qubes updates proxy (tinyproxy). Jun 27 12:06:14 redacted tinyproxy-wrapper[1608]: Found tinyproxy at /usr/bin/tinyproxy Despite this however, the problem still persists and still behaves the same even after trying dnf update for 5 times I think is right about the fact that there is a bug about this @Chris I think you may be right about the fact that this is a bug and I guess it's time to escalate it into an issue in github. I'm willing to lend a helping hand in making the issue as needed. My setup is all fully dependent on variations of fedora-30-minimal template that I have tailored depending on use-case of the AppVM that would be using it. -- 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/56db9edd-8442-4a7c-a46b-30b9ca97c1cf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.