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

Update network configuration for the Qubes staging environment #18

Open
lsd-cat opened this issue Oct 3, 2022 · 0 comments
Open

Update network configuration for the Qubes staging environment #18

lsd-cat opened this issue Oct 3, 2022 · 0 comments

Comments

@lsd-cat
Copy link
Member

lsd-cat commented Oct 3, 2022

Expected behavior

The network configuration described in https://github.com/freedomofpress/securedrop-dev-docs/blob/main/docs/qubes_staging.rst should work out of the box. However, when setting up the staging environment in a 4.1 Qubes (with also the Workstation installed), I had problems connecting the focal VM to the internet.

Actual behavior

When using the IP Addresses provided by Qubes as static addresses and following the guide, the VM does not properly connect to the internet.

Steps to reproduce the problem

  1. Follow the guide up until "Initial VM configuration"
  2. Log in and test internet connectivity

Additional information

I think that Qubes updated their networking settings. All my domains have their static IP Addresses in the 10.137.0.0/24 range. However the gateway is in the 10.138.0.0/24 subnet. When configuring the network like this, without a static route for the gateway first, the gateway cannot be set properly.

As an example, my personal domain currently has this output from ip route:

default via 10.138.2.138 dev eth0 onlink 
10.138.2.138 dev eth0 scope host onlink 

Thus, to address this issue on Ubuntu, we need to add a static route in netplan after installation.

In /etc/netplan/00-installer-config.yml add after the addresses section:

routes:
- to: 10.138.0.138/32
  scope: link

Where 10.138.0.138 is the gateway IP.

Before opening an actual pull request, I'd like to double-check if it is reproducible for anyone else or if it is due to some Qubes or other misconfiguration on my side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant