Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

network internet connectivity issues with Qubes VM kernel #5667

Closed
adrelanos opened this issue Feb 18, 2020 · 1 comment
Closed

network internet connectivity issues with Qubes VM kernel #5667

adrelanos opened this issue Feb 18, 2020 · 1 comment
Labels
C: kernel eol-4.0 Closed because Qubes 4.0 has reached end-of-life (EOL) P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@adrelanos
Copy link
Member

Qubes OS version
R4

Affected component(s) or functionality
Networking.

Brief summary
When using Qubes VM kernel in Debian VMs after a while no new connections are possible. After waiting a few minutes, new connections are possible.

To Reproduce
Steps to reproduce the behavior:
_1. setup Qubes VM kernel in debian-10 TemplateVM
_2. shut down debian-10 based AppVM
_3. do regular internet browsing or other network activity
_4. existing network connections still functional but often no new connections can be opened for minutes

Expected behavior
No connectivity issues.

Actual behavior
Connectivity issues where no causal connection to reproducible steps could be made.

Solutions you've tried
Keeping ping to some destinations running after boot of the VM. Ping will never show any issues and keep going. However, new websites opened in the browser might stop to function. nslookup might also still be available.

No network issues when reverting to Qubes dom0 kernel. (Due to #5212 this is a non-solution long term.)

Related, non-duplicate issues
There was a similar issue maybe 1-2 years ago where a kernel upgrade has lead to sporadic networking issues. Does anyone remember?

//cc @HW42 (iirc was analyzing the previous bug.)

@adrelanos adrelanos added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. labels Feb 18, 2020
@andrewdavidwong andrewdavidwong added this to the Release 4.0 updates milestone Feb 19, 2020
@andrewdavidwong andrewdavidwong added the needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. label Feb 17, 2022
@andrewdavidwong andrewdavidwong added the eol-4.0 Closed because Qubes 4.0 has reached end-of-life (EOL) label Aug 5, 2023
@github-actions
Copy link

github-actions bot commented Aug 6, 2023

This issue is being closed because:

If anyone believes that this issue should be reopened and reassigned to an active milestone, please leave a brief comment.
(For example, if a bug still affects Qubes OS 4.1, then the comment "Affects 4.1" will suffice.)

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 6, 2023
@andrewdavidwong andrewdavidwong removed the needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. label Aug 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: kernel eol-4.0 Closed because Qubes 4.0 has reached end-of-life (EOL) P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

No branches or pull requests

2 participants