I have a rather complicated net VM I am creating that allows client VMs to access several different networks at once. In addition to the VPNs and routing done in the net vm, I would like to be able to attach some programs to ports in the net vm, such as HAProxy to allow loadbalancing between some upstream servers, and a proxy to route, monitor, and log client vm traffic. I have added some setup in the rc.local config of the net vm to create dummy interfaces with their own 10.x.x.x/32 IPs, and set my HAProxy and other programs to bind to those IPs, and everything works inside the net vm. However, client VMs appear to be able to access the whole network but cannot connect to the dummy interface IPs, although those dummy IPs do respond to ICMP pings from the client VMs. Is anybody able to share how I can allow connectivity to these dummy interface IPs from the client VMs, given that the VM that has the dummy interfaces is set as the net vm for that client?
Edit: I have worked around this by breaking out the services into separate qubes and using the qvm-connect-tcp utility in the client qubes. It’s not ideal, but since all the networking can be automated in the rc.local startup config, it works well enough. I’d still like to know if somebody figures out how to accomplish my original goal though.