On 12/2/21 8:35 AM, 'Rune Philosof' via qubes-users wrote:
I have installed 4.1rc2 and chose a disposable sys-net, because I could
think of a reason not to.
But now that I have to type in the wifi password again and again, I know a
reason to not choose dispVM for sys-net.
Use a dedicated templa
I have installed 4.1rc2 and chose a disposable sys-net, because I could
think of a reason not to.
But now that I have to type in the wifi password again and again, I know a
reason to not choose dispVM for sys-net.
Maybe it should be mentioned in the installation process what consequences
it wil
On 5/26/21 5:45 PM, Ulrich Windl wrote:
Do you have some hints how I could try to improve that? Best, Bernhard
See what "journalctl -f" outputs in net-vm.
that gave an error message that helped to understand that seemingly
mac-randomization-while-scanning and OpenWRT are a bad mixture ...
On 5/24/21 9:09 PM, haaber wrote:
I have an build-in Intel 8265 / 8275 wireless controller, and my
(debian-10-minimal based) sys-net has more and more problems to connect.
It starts to connect and then hangs. That is strange since it used to
run perfectly 2 years ago. But now it takes 1-5 minutes
I have an build-in Intel 8265 / 8275 wireless controller, and my
(debian-10-minimal based) sys-net has more and more problems to connect.
It starts to connect and then hangs. That is strange since it used to
run perfectly 2 years ago. But now it takes 1-5 minutes, sometime a
qvm-kill forced reboot
Hi,
I'm wondering about many "odd" messages seen in syslog; maybe someone can
explain what they really mean and whether they are intended to appear.
First in sys-net when booting:
Mar 06 22:58:10 localhost kernel: Run /init as init process
Mar 06 22:58:10 localhost kernel: Invalid max_queues (4
dubstepcombust...@gmail.com:
> Qubes OS version: R4:0
>
> Hey everyone, bear with me as I am somewhat of a noob to Qubes, and haven't
> been on in awhile due to this issue which I have held on the backburner. So
> one day, everything on Qubes was running fine and smoothly, until I
> (stupidly)
Qubes OS version: R4:0
Hey everyone, bear with me as I am somewhat of a noob to Qubes, and haven't
been on in awhile due to this issue which I have held on the backburner. So
one day, everything on Qubes was running fine and smoothly, until I
(stupidly) decided to hard-shutdown my computer wit
On Tue, Jan 07, 2020 at 10:42:22AM -0800, paulos elias wrote:
> sys-firewall starts just fine. It just doesn't have internet access.
you mentioned using a very nonstandard network setup earlier.
have you tried just using a plain qubes default network setup?
does that work?
if you "customized" yo
And for default thing you said, I have been using sys-firewall as netvm for
other appvms this whole time as you would expect. It was all normal until today.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
sys-firewall starts just fine. It just doesn't have internet access.
--
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
On Tue, 7 Jan 2020 07:10:53 -0800 (PST)
paulos elias wrote:
> I have been using qubes for over a month and everything was working fine
> and in good shape until today. Today I opened up my PC and found out that
> sys-net has internet access but not other appvms whose netvm is sys-net. I
> can do
I have been using qubes for over a month and everything was working fine and in
good shape until today. Today I opened up my PC and found out that sys-net has
internet access but not other appvms whose netvm is sys-net. I can do pinging
and all from sys-net but I always get "host unreachable" e
On Fri, Dec 27, 2019 at 08:46:35AM +, 'awokd' via qubes-users wrote:
What responsibilties does sys-net have in terms of forwarding DNS? The
documentation specifies how things work for AppVMs, and it says there is
no DNS server in the "network driver domain" (sys-net), but it does not
say what
tetrahedra via qubes-users:
> On Thu, Dec 26, 2019 at 11:47:37AM +, 'awokd' via qubes-users wrote:
>> There's a brief discussion at https://www.qubes-os.org/doc/networking/,
>> but there may be more detailed notes in the source code for Qubes' VM
>> networking components. Qubes uses Xen's netwo
On Thu, Dec 26, 2019 at 11:47:37AM +, 'awokd' via qubes-users wrote:
There's a brief discussion at https://www.qubes-os.org/doc/networking/,
but there may be more detailed notes in the source code for Qubes' VM
networking components. Qubes uses Xen's networking, so that might be the
best plac
On Thu, Dec 26, 2019 at 11:47:37AM +, 'awokd' via qubes-users wrote:
tetrahedra via qubes-users:
I haven't been able to find any documentation for what network
interfaces sys-net is expected to expose internally. If I want to create
my own sys-net from scratch, how does Xen/Qubes send networ
tetrahedra via qubes-users:
> I haven't been able to find any documentation for what network
> interfaces sys-net is expected to expose internally. If I want to create
> my own sys-net from scratch, how does Xen/Qubes send network traffic to
> sys-net, to be sent onwards to my NIC?
>
There's a bri
I haven't been able to find any documentation for what network
interfaces sys-net is expected to expose internally. If I want to create
my own sys-net from scratch, how does Xen/Qubes send network traffic to
sys-net, to be sent onwards to my NIC?
--
You received this message because you are subsc
On Wed, Dec 11, 2019 at 11:46:04AM +, 'awokd' via qubes-users wrote:
This should work, but make sure sys-firewall is shutdown before
attempting to change. If it still isn't, try changing with qvm-prefs
sys-firewall.
Ok, I didn't realize sys-firewall had to be shutdown. Most of the time
you
tetrahedra via qubes-users:
> However, when I try to configure sys-firewall to use sys-net2 instead of
> sys-net for networking, I get the error:
> ERROR Basic tab: Failed to access 'netvm' property
This should work, but make sure sys-firewall is shutdown before
attempting to change. If it still
On Thu, Dec 05, 2019 at 03:05:42PM +, Claudia wrote:
I am wondering if it would make sense to re-create sys-net from scratch.
Could it be that this is something from fedora-29 that is not working
well with fedora-30?
Did you keep the fedora 29 template installed? If so, I think you
could j
tetrahedra via qubes-users:
see the corresponding issue:
https://github.com/QubesOS/qubes-issues/issues/5508
The tldr is that ever since I upgraded to fedora-30, sys-net has started
dying intermittently (or less intermittently, nearly every time) I put
my laptop to sleep.
This is really problem
see the corresponding issue:
https://github.com/QubesOS/qubes-issues/issues/5508
The tldr is that ever since I upgraded to fedora-30, sys-net has started
dying intermittently (or less intermittently, nearly every time) I put
my laptop to sleep.
This is really problematic.
I am wondering if it w
> On 9/18/19 2:43 PM, unman wrote:
> >> today I had a look in logs of my router, and discovered that it logs my
> >> qubes machine as "sys-net". I did not change anything in my
> >> "out-of-the-box" sys-net, so I presume that the observed behaviour is
> >> common to all standard qubes installs.
> >
On 9/18/19 2:43 PM, unman wrote:
today I had a look in logs of my router, and discovered that it logs my
qubes machine as "sys-net". I did not change anything in my
"out-of-the-box" sys-net, so I presume that the observed behaviour is
common to all standard qubes installs.
Q: is it a wanted featu
On 2019-09-18 08:43, unman wrote:
On Wed, Sep 18, 2019 at 02:04:53PM +0200, haaber wrote:
today I had a look in logs of my router, and discovered that it logs my
qubes machine as "sys-net". I did not change anything in my
"out-of-the-box" sys-net, so I presume that the observed behaviour is
comm
On Wed, Sep 18, 2019 at 02:04:53PM +0200, haaber wrote:
> today I had a look in logs of my router, and discovered that it logs my
> qubes machine as "sys-net". I did not change anything in my
> "out-of-the-box" sys-net, so I presume that the observed behaviour is
> common to all standard qubes inst
today I had a look in logs of my router, and discovered that it logs my
qubes machine as "sys-net". I did not change anything in my
"out-of-the-box" sys-net, so I presume that the observed behaviour is
common to all standard qubes installs.
Q: is it a wanted feature that all wireless networks imme
--
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 vie
techpu...@tutanota.com:
On startup, sys-net, sys-firewall, sys-usb, and sys-whonix start.
I want to be able to connect to the internet (I haven't been able to yet). So
I change the applications to add Settings in sys-net qube preferences. The
sys-net preferences are the only thing I can acce
On startup, sys-net, sys-firewall, sys-usb, and sys-whonix start.
I want to be able to connect to the internet (I haven't been able to yet). So
I change the applications to add Settings in sys-net qube preferences. The
sys-net preferences are the only thing I can access.
However I cannot star
Em segunda-feira, 24 de junho de 2019 22:51:39 UTC-3, awokd escreveu:
> Brendan Hoar:
> > I think it was the kernel-latest-qubes-vm package from the -testing repo.
> >
> If upgrading the kernel doesn't help, try changing your sys-net to use
> the Debian template.
Following the Kernel Upgrade se
Brendan Hoar:
I think it was the kernel-latest-qubes-vm package from the -testing repo.
If upgrading the kernel doesn't help, try changing your sys-net to use
the Debian template.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe
I think it was the kernel-latest-qubes-vm package from the -testing repo.
--
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
Em segunda-feira, 18 de março de 2019 12:33:03 UTC-3, seaclue escreveu:
> I switched to kernel-latest and now it's working.
Sorry, but how you did that?
On dom0 I did sudo qubes-dom0-update kernel-latest and installed the kernel
5.1.2-1 as explained on (https://www.qubes-os.org/doc/managing-vm-
On Wednesday, April 10, 2019 at 9:49:03 PM UTC-4, haaber wrote:
> > Qubes OS version: R4:0
> >
> > Hey everyone, bear with me as I am somewhat of a noob to Qubes, and haven't
> > been on in awhile due to this issue which I have held on the backburner. So
> > one day, everything on Qubes was runn
On Wednesday, April 10, 2019 at 10:03:20 PM UTC-4, awokd wrote:
> sykers...@gmail.com:
> > Qubes OS version: R4:0
> >
> > but sys-net would not start, and somehow, the debian-9 template private vm
> > file was gone.
>
> Have you tried changing AppVMs like sys-net to use the fedora template
> in
sykers...@gmail.com:
Qubes OS version: R4:0
but sys-net would not start, and somehow, the debian-9 template private vm file
was gone.
Have you tried changing AppVMs like sys-net to use the fedora template
instead of debian-9?
--
You received this message because you are subscribed to the G
Qubes OS version: R4:0
Hey everyone, bear with me as I am somewhat of a noob to Qubes, and haven't been on in awhile due to this
issue which I have held on the backburner. So one day, everything on Qubes was running fine and smoothly,
until I (stupidly) decided to hard-shutdown my computer with
Qubes OS version: R4:0
Hey everyone, bear with me as I am somewhat of a noob to Qubes, and haven't
been on in awhile due to this issue which I have held on the backburner. So one
day, everything on Qubes was running fine and smoothly, until I (stupidly)
decided to hard-shutdown my computer with
On Monday, March 18, 2019 at 11:33:03 AM UTC-4, seaclue wrote:
> I switched to kernel-latest and now it's working.
Can confirm: same wifi chipset and my fedora-29 networking was broken for
me...as my system default VM kernel was rather old (being a 4.0 install from
last year, upgraded regularly)
> Interesting- in the template or dom0?
both.
--
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, sen
'seaclue' via qubes-users wrote on 3/18/19 3:32 PM:
I switched to kernel-latest and now it's working.
Interesting- in the template or dom0?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving email
I switched to kernel-latest and now it's working.
--
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,
'awokd' wrote:
> Try Debian too. Maybe Fedora broke one of their packages.
Tried it, didn't 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+un
'seaclue' via qubes-users:
After a fresh Qubes os install (4.0.1), wifi works fine, after fedora-29
update, sysnet can't load the firmware,
[user@sys-net ~]$ sudo dmesg | grep ath10k
[ 12.294827] ath10k_pci :00:06.0: pci irq msi oper_irq_mode 2 irq_mode 0
reset_mode 0
[ 13.386937] ath1
After a fresh Qubes os install (4.0.1), wifi works fine, after fedora-29
update, sysnet can't load the firmware,
[user@sys-net ~]$ sudo dmesg | grep ath10k
[ 12.294827] ath10k_pci :00:06.0: pci irq msi oper_irq_mode 2 irq_mode 0
reset_mode 0
[ 13.386937] ath10k_pci :00:06.0: Direct f
On Wednesday, January 23, 2019 at 6:29:04 AM UTC-5, Mike Keehan wrote:
>
> Hi Bryce,
>
> Glad you got something working for you :)
>
> This is a good description of the changes in Qubes 4.0 :-
>https://www.qubes-os.org/doc/releases/4.0/release-notes/
>
> Mike.
Thanks Mike
--
You received
On Tue, 22 Jan 2019 12:26:00 -0800 (PST)
Bryce wrote:
> On Saturday, January 19, 2019 at 6:37:47 AM UTC-5, Mike Keehan wrote:
> >
> > Ah, what a shame. It does seem as if your iommu is a problem.
> >
> > Without any other ideas, the only thing I can suggest is that you
> > try the latest Qubes
On Saturday, January 19, 2019 at 6:37:47 AM UTC-5, Mike Keehan wrote:
>
> Ah, what a shame. It does seem as if your iommu is a problem.
>
> Without any other ideas, the only thing I can suggest is that you try
> the latest Qubes 3.2 just to allow you to try out Qubes. It doesn't
> require the v
On Fri, 18 Jan 2019 11:55:14 -0800 (PST)
Bryce wrote:
> On Friday, January 18, 2019 at 11:42:32 AM UTC-5, Bryce wrote:
> > > That's odd. You say you are installing 4.01, yet the qubes
> > > manager shows that fedora is only release 26. I thought that
> > > Qubes 4.01 had Fedora 29 in it.
> > >
On Friday, January 18, 2019 at 10:31:33 AM UTC-5, Mike Keehan wrote:
> On Fri, 18 Jan 2019 07:17:00 -0800 (PST)
> scott wrote:
>
> > On Friday, January 18, 2019 at 9:16:59 AM UTC-5, unman wrote:
> > > On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott wrote:
> > > > Thanks but unfortunately I don't
> That's odd. You say you are installing 4.01, yet the qubes manager
> shows that fedora is only release 26. I thought that Qubes 4.01 had
> Fedora 29 in it.
>
> Mike.
Well Mike that could be it; you made me check when you said that, the image I
used was "Qubes-R4.0-x86_64.iso" from 11/27/18.
On Fri, 18 Jan 2019 08:14:43 -0800 (PST)
Bryce wrote:
> On Friday, January 18, 2019 at 11:11:00 AM UTC-5, Mike Keehan wrote:
> > Ah, afraid I've run out of ideas now.
> >
> > I was hoping it was just the iommu not being enabled, but not
> > starting any vm at all is not something I've seen befor
Ah, afraid I've run out of ideas now.
I was hoping it was just the iommu not being enabled, but not starting
any vm at all is not something I've seen before, as long as there is
enough memory. 16Gb is fine.
Sorry, out of inspiration now,
Mike.
--
You received this message because you are
On Friday, January 18, 2019 at 10:31:33 AM UTC-5, Mike Keehan wrote:
> On Fri, 18 Jan 2019 07:17:00 -0800 (PST)
> scott wrote:
>
> > On Friday, January 18, 2019 at 9:16:59 AM UTC-5, unman wrote:
> > > On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott wrote:
> > > > Thanks but unfortunately I don't
On Fri, 18 Jan 2019 07:17:00 -0800 (PST)
scott.lewis.engin...@gmail.com wrote:
> On Friday, January 18, 2019 at 9:16:59 AM UTC-5, unman wrote:
> > On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott wrote:
> > > Thanks but unfortunately I don't know that issue helps, as those
> > > who were able to
On Friday, January 18, 2019 at 10:17:01 AM UTC-5, scott.lewi...@gmail.com wrote:
> On Friday, January 18, 2019 at 9:16:59 AM UTC-5, unman wrote:
> > On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott wrote:
> > > Thanks but unfortunately I don't know that issue helps, as those who were
> > > able to r
On Friday, January 18, 2019 at 9:16:59 AM UTC-5, unman wrote:
> On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott wrote:
> > Thanks but unfortunately I don't know that issue helps, as those who were
> > able to resolve it did so by updating which I cannot do since sys-net fails
> > to start.
> >
> >
On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott Lewis wrote:
> Thanks but unfortunately I don't know that issue helps, as those who were
> able to resolve it did so by updating which I cannot do since sys-net fails
> to start.
>
> This issue, https://github.com/QubesOS/qubes-issues/issues/3349 , s
Thanks but unfortunately I don't know that issue helps, as those who were
able to resolve it did so by updating which I cannot do since sys-net fails
to start.
This issue, https://github.com/QubesOS/qubes-issues/issues/3349 , seems to
cover that problem but nothing's mentioned about net & firewall
On Thu, 17 Jan 2019 16:42:28 -0800 (PST)
scott.lewis.engin...@gmail.com wrote:
> Hello, I apologize in advance if this has already been addressed but
> searching for "sys-net" & "libxl" give many confusing results, I
> don't see any that match both not working, and I'm completely new to
> Qubes. M
Hello, I apologize in advance if this has already been addressed but searching
for "sys-net" & "libxl" give many confusing results, I don't see any that match
both not working, and I'm completely new to Qubes.
My problem is that after 2 different installs of the same version, 4.01, I keep
gettin
ultimatev...@gmail.com:
Qubes OS version:
R4.0
Affected component(s):
Intel Wireless N 1000
Steps to reproduce the behavior:
I installed QubesOS R4.0 and made it to the installation configuration page
(where the system finishes installing, reboots, and then you are prompted with
the config f
Qubes OS version:
R4.0
Affected component(s):
Intel Wireless N 1000
Steps to reproduce the behavior:
I installed QubesOS R4.0 and made it to the installation configuration page
(where the system finishes installing, reboots, and then you are prompted with
the config finishing installer) and I
Den lør. 17. nov. 2018 kl. 13.54 skrev Chris Laprise :
> On 11/17/2018 04:44 AM, aaq via qubes-users wrote:
> > Hello!
> >
> > So, I switched to KDE as you can see in some other threads, and honestly
> I like it way better than XFCE.
> >
> > My biggest issue right now however is, that the network
On 11/17/2018 04:44 AM, aaq via qubes-users wrote:
Hello!
So, I switched to KDE as you can see in some other threads, and honestly I like
it way better than XFCE.
My biggest issue right now however is, that the network manager applet does not
show in KDE. I get notification when I start my se
Hello!
So, I switched to KDE as you can see in some other threads, and honestly I like
it way better than XFCE.
My biggest issue right now however is, that the network manager applet does not
show in KDE. I get notification when I start my session that I am connected to
my network, and I do ha
On Mon, September 3, 2018 8:29 pm, odindva0...@gmail.com wrote:
> Hey guys currently running Qubes R 4.0 .
> And my sys-net as failing to connect to the internet + when I switch on
> mozila is lagging pretty bad. Please check the pic to see what exactly
> the configuration shows me . https://imgur.
Hey guys currently running Qubes R 4.0 .
And my sys-net as failing to connect to the internet + when I switch on mozila
is lagging pretty bad. Please check the pic to see what exactly the
configuration shows me .
https://imgur.com/a/6fgXaAq
Thanks in advance
--
You received this message because
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Daniil Travnikov:
> I turned off auto-start of sys-net when laptop starting, and all is
> ok with this moment.
>
> But if my laptop will be turned on some while and I will be just in
> Qubes Manager with turned off all of the VM's, after some time I
I turned off auto-start of sys-net when laptop starting, and all is ok with
this moment.
But if my laptop will be turned on some while and I will be just in Qubes
Manager with turned off all of the VM's, after some time I will see like how
sys-net turning on itself.
How could it possible? Wher
On 05/01/2018 08:50 AM, trueriver wrote:
I do not want my laptop to boot up and immediately look for a network
connection.
Therefore I set sys-net and sys-firewall NOT to start at boot.
The only domain that is currently set to start at boot time is one that has not
network connection. And dom
On 05/01/2018 03:50 PM, trueriver wrote:
> I do not want my laptop to boot up and immediately look for a network
> connection.
>
> Therefore I set sys-net and sys-firewall NOT to start at boot.
>
> The only domain that is currently set to start at boot time is one that has
> not network conn
I do not want my laptop to boot up and immediately look for a network
connection.
Therefore I set sys-net and sys-firewall NOT to start at boot.
The only domain that is currently set to start at boot time is one that has not
network connection. And dom0 of course ;)
At boot time those indeed
Hello,
After a normal reboot I had a working dom0 without any ServiceVM started.
Found that `sys-net` could not start because the 'vm-sys-net-private' LVM
volume was missing.
Looking around I found that the '-tmp' version of it was available, and after
mounting it I could see the contents of th
I have a desktop with intel ethernet. I found out sleep actually works if
using uefi bios mode. But when I resume I have to restart sys-net to get
networking.
Any solution to this problem?
Thanks,
Rich.
--
You received this message because you are subscribed to the Google Groups
"qubes-
I've upgraded a laptop from 3.2 to 4.0rc4. I didn't have the problem described
here in 3.2...
When I sleep the laptop (by closing lid), I find that every time I wake it,
sys-net is unresponsive.
I cannot bring up a terminal in sys-net. Terminals already open are
unresponsive to input.
Cal
Hello,
I am running Qubes 3.2 on a Lenovo Yoga 720. The wireless hardware for this is
Qualcomm Atheros QCA6174. This card has given me a few headaches.
Anytime I go to shutdown sys-net (typically to restart it) I get the following
errors (in dom0) in /var/log/libvirt/libxl/libxl-driver.log:
question. Those two ip addresses would be the
> actual ip of the qubes. (sorry I have to be sure : )
> Essax
> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>
> > Original Message
> > Subject: Re: [qubes-users] Sys-net with a 2 port NIC, ho
https://protonmail.com) Secure Email.
> Original Message --------
> Subject: Re: [qubes-users] Sys-net with a 2 port NIC, how to allow/block
> interfaces?
> Local Time: July 5, 2017 9:24 PM
> UTC Time: July 6, 2017 1:24 AM
> From: un...@thirdeyesecurity.org
> To: Essax
> Google gr
On Wed, Jul 05, 2017 at 08:08:02PM -0400, 'Essax' via qubes-users wrote:
> I have laptop with a 2 port NIC. I would like to have 1 subset of appVMs that
> are connected to sys-net to use the eth0 interface and the other subset to
> use the eth1 interface. It is not possible to assign 1 port into
I have laptop with a 2 port NIC. I would like to have 1 subset of appVMs that
are connected to sys-net to use the eth0 interface and the other subset to use
the eth1 interface. It is not possible to assign 1 port into seperate sys-nets.
I have tried that and only eth0 will function. Its also my
Trying to configure Qubes 3.2 and having an issue getting my network up and
going.'
sys-net does not see either of my network devices (ethernet or wifi). The only
device that it can see is the loopback (lo) device. The devices are listed in
the Devices tab for the VM and I can see both devices
Hello,
I have a problem when working with Qubes OS 3.2 using my built-in
LTE-Card (Sierra Wireless EM7345 4G LTE) - after a while the sys-net VM
freezes and when killing the sys-net Net-VM and trying to restart I get
an error message.
The LTE-card is internally connected as an USB device and
I am using Qubes 3.2 with Fedora 24 netVM.
I have just noticed after changing the WPA2 password on one of the Access
points I use that Qubes no longer remembers the Wifi password for any new
access point that I add.
It will remember the password as long as I do not restart the sys-net AppVM or
you can create a debian-based sys-net and assign network cards to that. hope
you can get Qubes working for 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 q
Hello Qubes-users,
I have installed Qubes and had no problems but the internet access
only works for a few minutes.
If I open a terminal in sys-net and start a ping (to 4.2.2.1 for
example) it stops working after a while and then the only way to get
it back it to reboot.
I know the
I ran into this and found my issue was the fedora-24-minimal did not
have tinyproxy installed.
On 02/28/2017 04:27 PM, Ray Brainer wrote:
It starts. But there is no ip resolution.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscri
It starts. But there is no ip resolution.
--
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 em
On 02/28/2017 03:08 PM, Ray Brainer wrote:
I successfully installed fedora-24 template and removed fedora-23 template.
Sys-net was assigned to fedora-23.
I reassigned it to fedora-24-minimal.
No luck.
Any advice?
Did sys-net fail to start? Did it start, but network-manager won't connect?
Chri
I successfully installed fedora-24 template and removed fedora-23 template.
Sys-net was assigned to fedora-23.
I reassigned it to fedora-24-minimal.
No luck.
Any advice?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this gr
On Sat, Feb 25, 2017 at 07:35:15PM +, Unman wrote:
> On Fri, Feb 24, 2017 at 06:11:56PM -0500, Oleg Artemiev wrote:
> > How do I disable autostart of sys-net, sys-firewall? Qubes manager
> > setting seem to be ignored.
> > Qubes r3.2
> >
> > --
> > Bye.Olli.
>
>
> This same question was ask
On Fri, Feb 24, 2017 at 06:11:56PM -0500, Oleg Artemiev wrote:
> How do I disable autostart of sys-net, sys-firewall? Qubes manager
> setting seem to be ignored.
> Qubes r3.2
>
> --
> Bye.Olli.
This same question was asked yesterday and has been asked before.
There are open issues, but there's
How do I disable autostart of sys-net, sys-firewall? Qubes manager
setting seem to be ignored.
Qubes r3.2
--
Bye.Olli.
gpg --search-keys grey_olli , use key w/ fingerprint below:
Key fingerprint = 9901 6808 768C 8B89 544C 9BE0 49F9 5A46 2B98 147E
Blog keys (the blog is mostly in Russian): http:/
On Wednesday, November 30, 2016 at 3:47:01 PM UTC-6, Marek Marczykowski-Górecki
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Wed, Nov 30, 2016 at 01:44:41PM -0800, steve wrote:
> > sys-net and sys-firewall were both running fine before I installed Win 7
> > x64. qvm-start sy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, Nov 30, 2016 at 01:44:41PM -0800, stevemichaelph...@gmail.com wrote:
> sys-net and sys-firewall were both running fine before I installed Win 7 x64.
> qvm-start sys-net fails with the message:
> ERROR: PCI device 01:00.0 does not exist (doma
sys-net and sys-firewall were both running fine before I installed Win 7 x64.
qvm-start sys-net fails with the message:
ERROR: PCI device 01:00.0 does not exist (domain sys-net)
lspci confirms the device 01:00.0 does not in fact exist
--
You received this message because you are subscribed to th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-10-17 08:24, katerim...@sigaint.org wrote:
> Sorry, maybe it is a bug
> There is network manager applet but it is invisible
>
Yes, this is a known issue:
https://github.com/QubesOS/qubes-issues/issues/2242
- --
Andrew David Wong (Axon)
C
1 - 100 of 102 matches
Mail list logo
