What about the Mac addresses of the laptop itself? Does infecting dom0 reveal
the Mac addresses embedded in the laptop’s hardware?
--
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,
On Sat, Jun 08, 2019 at 03:18:41AM -0700, ljul8...@gmail.com wrote:
> What about the Mac addresses of the laptop itself? Does infecting dom0 reveal
> the Mac addresses embedded in the laptop’s hardware?
>
That depends on what "infecting" means, and what capacities the
infection offers.
The MAC
On 6/8/19 3:20 PM, Chris Laprise wrote:
On 6/8/19 8:22 AM, mmo...@disroot.org wrote:
I saw this issue. But unfortunately the latest-kernel-vm (5.1.2-1)
doesn't contain the modules for wireguard.
So the problem still remains.
When I use the debian-9 template on the sys-vpn the other appvms are
I have a sys-usb that is currently based on fedora but i need to run a
package on debian.
Should it be a problem if i install the package on debian, temporarily
switch the template to debian, use the app when i need, then switch back?
--
You received this message because you are subscribed to
"Try it first with CSM enabled; reason being Qubes will install in GRUB mode
without it so when you re-enable there wouldn't be a UEFI boot entry."
Will it install MBR with CSM enabled? I only need GPT.
Important note: My CSM doesn't completely switch to legacy boot mode, like some
other (bad)
I saw this issue. But unfortunately the latest-kernel-vm (5.1.2-1) doesn't
contain the modules for wireguard.
So the problem still remains.
When I use the debian-9 template on the sys-vpn the other appvms are not able
to resolve any records, only the sys-vpn.
Any ideas?
June 8, 2019 5:48
Stumpy wrote on 6/8/19 1:18 PM:
I have a sys-usb that is currently based on fedora but i need to run a
package on debian.
Should it be a problem if i install the package on debian, temporarily
switch the template to debian, use the app when i need, then switch back?
Shouldn't be a problem,
Hi,
I'm having random issues while on wireguard where request to some sites simply
stalls until it times out. If I reload the pages often enough I will finally
able to get the response, although this happens randomly, currently I'm able to
reproduce this issue in ever few requests. When the
'interested_in_QubesOS' via qubes-users wrote on 6/8/19 3:54 PM:
"Try it first with CSM enabled; reason being Qubes will install in GRUB mode without
it so when you re-enable there wouldn't be a UEFI boot entry."
Will it install MBR with CSM enabled? I only need GPT.
Important note: My CSM
On 6/8/19 8:22 AM, mmo...@disroot.org wrote:
I saw this issue. But unfortunately the latest-kernel-vm (5.1.2-1) doesn't
contain the modules for wireguard.
So the problem still remains.
When I use the debian-9 template on the sys-vpn the other appvms are not able
to resolve any records, only
I assign the PCI trought the setting sys-net but now the terminal say to me
domain sys-net has failed to start :PCI device0:04_00.0
--
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
Seem like I have to reinstall qubes it doesn't start anymore
--
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
Thanks Chris.
I've solved this differently. I'm using the PostUp/PostDown script to set the
DNAT rules through a script that I've made, which also sets the resolv.conf
properly since the resolvconf daemon is not working as it should.
Thank you!
June 8, 2019 9:24 PM, "Chris Laprise"
Well after some more troubleshooting I found the root cause. It seems to be
related with the MTU.
Wireguard by default sets its vif with a MTU of 1420 while the other AppVms are
using a default MTU of 1500 which causes the hanging and stall in the
connection request.
When I set the interfaces
On 6/8/19 6:11 PM, mmo...@disroot.org wrote:
Thanks Chris.
I've solved this differently. I'm using the PostUp/PostDown script to set the
DNAT rules through a script that I've made, which also sets the resolv.conf
properly since the resolvconf daemon is not working as it should.
Just FYI,
On 6/8/19 6:16 PM, mmo...@disroot.org wrote:
Well after some more troubleshooting I found the root cause. It seems to
be related with the MTU.
Wireguard by default sets its vif with a MTU of 1420 while the other
AppVms are using a default MTU of 1500 which causes the hanging and
stall in the
On 6/8/19 6:16 PM, mmo...@disroot.org wrote:
Well after some more troubleshooting I found the root cause. It seems to
be related with the MTU.
Wireguard by default sets its vif with a MTU of 1420 while the other
AppVms are using a default MTU of 1500 which causes the hanging and
stall in the
So I'm following this tutorial online:
https://www.qubes-os.org/doc/vpn/
and proxyVM is not listed. Am I missing something? Under "Type", only AppVM,
and two standalone based options are listed.
Am I missing plugins?
--
You received this message because you are subscribed to the Google
On 6/8/19 7:30 PM, atrainonl...@gmail.com wrote:
So I'm following this tutorial online:
https://www.qubes-os.org/doc/vpn/
and proxyVM is not listed. Am I missing something? Under "Type", only AppVM,
and two standalone based options are listed.
Am I missing plugins?
ProxyVM is the old
I was able to complete everything. Thank you 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
20 matches
Mail list logo
