Also with 64bit compatibility this means the repo paths have changed.

Yes it can stay as it is.

That's great! So https://github.com/Whonix/whonix-gw-network-conf/blob/master/etc/network/interfaces.d/30_non-qubes-whonix can stay as is?

Great news! This config works without hacks. You can keep 10.0.2.15 unchanged too. Turns out the gateway ip address was just called "ip address"...

No idea. But we should probably stay on the subnet we have.

OK I will try route but I need some help with commands.

Seems like an awful hack. Last resort. If it somehow by some update (by ifupdown) is run after ifupdown, it breaks connectivity.

We're using ConditionVirtualization=kvm elsewhere already.(shared-folder-help systemd unit file) Should be doable to reuse it for the route command also.

We're using ConditionVirtualization=kvm elsewhere already.
(shared-folder-help systemd unit file) Should be doable to reuse it for
the route command also.

Can you redirect these packages using route? (Try in a Debian VM first to exclude Whonix firewall from interfering.)

Can you redirect these packages using route? (Try in a Debian VM first to exclude Whonix firewall from interfering.)

A very ugly hack:

Then we have reached an impasse because nothing I can put in the network configuration can change the gateway IP. Its not KVM's fault as its the norm to have gateway IPs of x.x.x.1 for a given subnet. Because some idiot on the VBox team chose .2 compatibility is impossible.

In T559#10500, @HulaHoop wrote:

address 10.0.2.128
netmask 255.255.255.0

Looks like libvirt supports a gateway= keyword. Does that work?

Looks like libvirt supports a gateway= keyword. Does that work?

In T559#10494, @HulaHoop wrote:

address 10.0.2.15
netmask 255.255.252.0

Various documentation changes:

These steps were not needed at all. Once I selected non-conflicting settings everything worked. Some changes to the netmask and gateway will need to be made to interfaces.d

I doubt it is possible to successfully use a dhcp client with raw sockets disabled. It may be possible to develop such a thing in theory, but I don't think it exists.

What I meant was subnet range using the CIDR calculator:

Same as VirtualBox.

My mistake I was not clear. By network configuration I mean yet another XML to create a new separate network as an alternative to "default" (like how I do it now with whonix internal network for KVM). It has nothing to do with GW files at all. No changes have to be made there.

192... will be a huge generator of FUD "conflicts with my router". Long time ago we moved away from that exactly for that reason.

So can we move to something static in the 192.168.122.2 - 192.168.122.254 range (depends on VBox choking or not) or should I include another network file with the whonix-libvirt package?

By working you mean in multi-GW usecase too?

Can you emulate these changes, use that static IP?

Can you emulate these changes, use that static IP? What will need changes? KVM documentation?

With libvirt a user can create another NAT network besides the default - with the same IP range. So another GW would have its own dedicated NAT without conflicts.

Switched to static network configuration.

no need to replace ip's in /etc/network/interfaces.whonix - https://phabricator.whonix.org/T347:
https://github.com/Whonix/qubes-whonix/commit/b251a4af0a20738446e1cc16bc31d59f52ba7350

use /etc/network/interfaces.d instead of /etc/network/interfaces - https://phabricator.whonix.org/T347:

Currently Qubes configures interfaces manually from udev rule. Actually
I think it would be better to move it to some more standard place, for
example to not conflict with NetworkManager (which is currently handled
as a special case) or other network-related tools.
Or at least move it out of udev rule, which is called in quite
unpredictable time (->race conditions). I think it may somehow related
to:
https://github.com/QubesOS/qubes-issues/issues/1067

I am currently trying to get rid of this hack:
https://github.com/nrgaway/qubes-template-whonix/blob/be0c1f53cc10a3ccb8628d132da35006225bdff6/whonix-gateway/02_install_groups_pre.sh#L122-L130