Weird network access issues

44 views
Skip to first unread message

angelo "angico" costa

unread,
Aug 26, 2016, 5:23:33 PM8/26/16
to qubes-users
Hi, all!

I'm experiencing some weird network access issues. I'm using Qubes 3.1.

After logging in to the system, sys-net, sys-firewall and sys-whonix start as expected, and network access is normally available. I can use apps such as OwnCloud, qBittorrent, Firefox and others to connect to several internet services and they all work fine. But suddenly, and I just cannot specify when, the apps start to fail connecting. One such app that most catches my attention with respect to the problem is OwnCloud, which reports connection failure -- though other devices such as an Android tablet or even another notebook running Debian, tell me Internet access is absolutely normal, including access to my OwnCloud server.

I've already tried restarting the VMs related to network connection -- sys-net and sys-firewall -- but the problem persists, and it's happening with two different notebooks -- an Acer Aspire with Intel Core i7, 10GB RAM, 1TB HD and an unbranded one with equal CPU. 8GB RAM, and 640GB HD.

Does anybody have experienced such issues? Does anybody have any hint on what may be the cause of those issues and on how I can solve them?

TIA and best regards to you all,

Angico.

Andrew David Wong

unread,
Aug 26, 2016, 11:14:40 PM8/26/16
to angelo "angico" costa, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I haven't experienced that (and can't recall any similar reports off the top
of my head). If you're connecting via Tor, then that's probably the reason.
Otherwise, it may be your Wi-Fi connection or network.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXwQWWAAoJENtN07w5UDAwlSkP/1Cixo7axnFILYspLAiFUMK/
icthQD4DBuRLTebPTKki2SMmxLJ4CZpyRO0O6K6sSlQQDvHfKJ8d8QY2DiyPJR5H
5BLWODz6QW0lgAUaQJc0/QV6ExuqtDyNp/YAnpbVUQQoTJMu0NTzz1g67CTCqItj
fwETBcL3etPinMtS9yLJBLBH+vp+c39/oHg4YbiYFUPA8yMsyKmnczvwO1+t8JB2
MFhemt/ljdiRDDol5J3uUrb7NgGMfn+32T4t/kspYx5folIgWDYyN2pITCPXT6nV
EfVv81bG+p5RJwouQc3QZnifojqaLHxxs3IIzMy1jV3W3/4Xmk1XGAl6iRZB5paQ
jumkRdiAnnssj24BwEq0Sk6tbRpCtPtcREM/XB83txvXd3d09vzz4hkWMJxYbqLO
GRMTgMv8x6KKC62EhLAuLzvGOy4m8fcfMsIz9Jfeh3DQLK4ohHGfZuvciiNRuSH6
ZKwKDDZio9dkZ2HlKC5ce2QDUW2dzPH+fjvdYIqqUWqkmV3pdOQNsTgHKllFzFc/
qJu+1DUK/hcbHJHwtU/kpMYNQ4dq/2yuYIyZsLWY+W2K3YyKwWZrK04zk2VTaV7H
WYjGNEx/ZWtcpFKPQDxIIGF48dniDfEVnztxz1mXm1LJaj5MqA5Av35yCclg9Wsv
Mg1pmxR4WMMxWpXy2PRf
=/kpG
-----END PGP SIGNATURE-----

Drew White

unread,
Aug 28, 2016, 8:32:16 PM8/28/16
to qubes-users

According to what you are saying it sounds like it's not an issue with Qubes, but with your connection.

You say you have the issue from Android Tablet, a Notebook running Debian, and your Qubes PC.

If not all 3 are running Qubes, then it isn't a Qubes issue.

bi...@fucked-up.net

unread,
Aug 29, 2016, 10:00:08 AM8/29/16
to qubes...@googlegroups.com
Perhaps I experienced the same issue. It happened to me a few times,
seemingly random. Suddenly my AppVMs are not connecting to anything
outside Qubes anymore. the only VM that was connecting was sys-firewall.
The next time it happens I will write down what exactly I am
experiencing and if the connection between the VMs are working properly.

I also use a skylake i7 cpu, perhaps there is some connection? *shrug*

regards
bisam

Marek Marczykowski-Górecki

unread,
Aug 30, 2016, 11:36:01 AM8/30/16
to bi...@fucked-up.net, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Wasn't that after starting some AppVM by a chance? If so, check status
or qubes-firewall service in sys-firewall:

sudo systemctl status qubes-firewall

You may also try restarting this service.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXxafWAAoJENuP0xzK19csApQH/33HH0IySLPf4GRPkETRWWGM
s6Z0G8+vY1sX+W/mo/Ec6mb0CkKOP/XftCdltLfuEAGJMp3WRRvKuuOkATfZotuc
3KGY1tCsxEIMK5pcsrHkWHGkKvY+LP7O7z8i+KH4/4Dj+UT0u8tvyznD9/noit9m
qApIeZsQn8BNDt3A6WgWBPcc42cy683IsAC5UrX/7W5hEK1CXCJBgRPtCaJwlSR2
GuN4I/0os1IYQCDFnsCJpma7+KuKoAd1Ce4M13UvBDaO4XSrj1DmkzhlnN4wRH+8
87+4HnLABbUJXQpwTMOvzIcitmgCwSMiNR+5BNEVWpXKz/rCQ+E9HEIPGuek5Ss=
=H8NW
-----END PGP SIGNATURE-----

bi...@fucked-up.net

unread,
Aug 30, 2016, 5:47:20 PM8/30/16
to qubes...@googlegroups.com
On 08/30/2016 05:35 PM, Marek Marczykowski-Górecki wrote:
> On Mon, Aug 29, 2016 at 04:00:01PM +0200, bi...@fucked-up.net wrote:
>> On 08/26/2016 11:23 PM, angelo "angico" costa wrote:
>>> Hi, all!
>>>
>>> I'm experiencing some weird network access issues. I'm using Qubes 3.1.
>>>
>>> After logging in to the system, sys-net, sys-firewall and sys-whonix start as expected, and network access is normally available. I can use apps such as OwnCloud, qBittorrent, Firefox and others to connect to several internet services and they all work fine. But suddenly, and I just cannot specify when, the apps start to fail connecting. One such app that most catches my attention with respect to the problem is OwnCloud, which reports connection failure -- though other devices such as an Android tablet or even another notebook running Debian, tell me Internet access is absolutely normal, including access to my OwnCloud server.
>>>
>>> I've already tried restarting the VMs related to network connection -- sys-net and sys-firewall -- but the problem persists, and it's happening with two different notebooks -- an Acer Aspire with Intel Core i7, 10GB RAM, 1TB HD and an unbranded one with equal CPU. 8GB RAM, and 640GB HD.
>>>
>>> Does anybody have experienced such issues? Does anybody have any hint on what may be the cause of those issues and on how I can solve them?
>>>
>>> TIA and best regards to you all,
>>>
>>> Angico.
>>>
>
>> Perhaps I experienced the same issue. It happened to me a few times,
>> seemingly random. Suddenly my AppVMs are not connecting to anything
>> outside Qubes anymore. the only VM that was connecting was sys-firewall.
>> The next time it happens I will write down what exactly I am
>> experiencing and if the connection between the VMs are working properly.
>
> Wasn't that after starting some AppVM by a chance? If so, check status
> or qubes-firewall service in sys-firewall:
>
> sudo systemctl status qubes-firewall
>
> You may also try restarting this service.
>
>

I will note the results the next time it happens. thank you anyway!
Reply all
Reply to author
Forward
0 new messages