Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upOcasionally, in some rare cases, no MASQUERADE rule created in the NetVM #740
Comments
marmarek
added this to the Release 2 Beta 3 milestone
Mar 8, 2015
marmarek
added
bug
C: core
P: minor
labels
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Modified by joanna on 18 Nov 2013 13:55 UTC |
marmarek
removed this from the Release 2 Beta 3 milestone
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Modified by joanna on 14 Mar 2014 13:05 UTC |
marmarek
added this to the Release 2 milestone
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Modified by joanna on 24 Mar 2014 09:07 UTC |
marmarek
changed the title from
No MASQUERADE rule in NetVM
to
Ocasionally, in some rare cases, no MASQUERADE rule created in the NetVM
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Modified by joanna on 2 Jul 2014 18:05 UTC |
marmarek
modified the milestones:
Release 2.1 (post R2),
Release 2
Mar 8, 2015
marmarek
modified the milestones:
Release 3.1 updates,
Release 2.0 updates
Nov 19, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
@andrewdavidwong We have been unable to reproduce this issue in 3.2 |
andrewdavidwong
closed this
Apr 14, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
marmarek commentedMar 8, 2015
Reported by marmarek on 16 Jun 2013 12:20 UTC
Sometimes iptables in netvm lack of MASQUERADE rule, which result in sending packets with firewallvm source IP to outside world. The packets most likely will be filtered by first router/firewall (so network traffic got lost).
This happen only sometimes, most likely at resume from s3 sleep. Details: https://groups.google.com/d/topic/qubes-users/V5QXOW7Y7zg/discussion
Perhaps related to #42?
Migrated-From: https://wiki.qubes-os.org/ticket/740