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 upMake Qubes IP addressing somehow uniqe #73
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Mar 8, 2015
Member
Comment by joanna on 4 Oct 2010 17:46 UTC
At least two other tools need to be updated, as they use hardcoded IP of Dom0 (10.0.0.1):
- qvm-dom0-network-via-netvm
- dom0/init.d/qubes_netvm
|
Comment by joanna on 4 Oct 2010 17:46 UTC
|
marmarek
assigned
rootkovska
Mar 8, 2015
marmarek
added this to the Release 1 Alpha 3 milestone
Mar 8, 2015
marmarek
added
bug
C: core
P: major
labels
Mar 8, 2015
marmarek
modified the milestones:
Release 1 Beta 1,
Release 1 Alpha 3
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 15 Mar 2011 00:50 UTC |
marmarek
assigned
marmarek
and unassigned
rootkovska
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Mar 8, 2015
Member
Comment by marmarek on 27 Mar 2011 11:02 UTC
Changed addresses to 10.137.x.0/24
|
Comment by marmarek on 27 Mar 2011 11:02 UTC |
marmarek
closed this
Mar 8, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
marmarek commentedMar 8, 2015
Reported by joanna on 28 Sep 2010 18:10 UTC
Clearly, the use of 10.x.0.0/16 addressing make it prone to IP conflicts when the user connects to network that itself uses same addressing scheme. There doesn't seem to be any good generic solution for this problem (?), but perhaps we could use some less likely addressing for our network? Like e.g. 10.199+x.0.0/16? Or 10.137.x.0/24? (who needs more than 254 AppVMs anyway?).
Migrated-From: https://wiki.qubes-os.org/ticket/73