qvm-ls -n output: display meanigful networking info

[marmarek]

Reported by joanna on 16 May 2012 13:32 UTC
The IP that is displayed as 'gateway' makes no sense. It should rather be displayed as the netvm's IP address (although then it makes problematic to what display in this field for proxy vms). So, it would be better, perhaps to display two IP addresses for each VM:

1. IP (front)
2. IP (back)

Any AppVM will have only IP (front), while any NetVM will have only IP (back -- this would be the 10.137.x.1 pseudo address through which other VMs see this netvm. Proxy VMs, however, will have both of them.

The gateway field of any AppVM/HVM or ProxyVM, should match the IP (back) of the corresponding Proxy/NetVM to which it is connected.

NetVMs should have nothing displayed in the gateway field.

Qubes Manager should be adjust adjusted accordingly.

Migrated-From: https://wiki.qubes-os.org/ticket/573

[marmarek]

Comment by marmarek on 20 May 2012 00:02 UTC
The IP in 'gateway' field isn't real IP at all (isn't assigned to any interface) - only used to DNAT DNS traffic. It is used as default gateway only to not fill ARP cache (but really there can be used ANY address) - see #355.
Also introducing some "back" and "front" names will only confuse not-so-advanced user.
IMHO the 'gateway' field can be renamed to 'DNS', but no other change.

[marmarek]

Comment by marmarek on 20 May 2012 00:02 UTC
The IP in 'gateway' field isn't real IP at all (isn't assigned to any interface) - only used to DNAT DNS traffic. It is used as default gateway only to not fill ARP cache (but really there can be used ANY address) - see #355.
Also introducing some "back" and "front" names will only confuse not-so-advanced user.
IMHO the 'gateway' field can be renamed to 'DNS', but no other change.

[marmarek]

Comment by joanna on 21 May 2012 08:27 UTC
That's I wrote 'pseudo' address. Anyway, it isn't important whether it is real or pseudo IP -- what is important is to let the (advanced) user to easily figure out how VM's are interconnected in terms of IP routing. Hence, the idea of using ip front and back. I don't see how this could be confusing -- on the contrary, the current display model is really confusing.

[marmarek]

Comment by joanna on 21 May 2012 08:27 UTC
That's I wrote 'pseudo' address. Anyway, it isn't important whether it is real or pseudo IP -- what is important is to let the (advanced) user to easily figure out how VM's are interconnected in terms of IP routing. Hence, the idea of using ip front and back. I don't see how this could be confusing -- on the contrary, the current display model is really confusing.

[marmarek]

Comment by marmarek on 21 May 2012 12:22 UTC
Current display model show configuration for VM - eg when the user want to configure it manually (eg when using Windows PV network driver). Still doesn't understand why you want to introduce some IP needed for one VM in row describing other VM.

BTW You propose to add additional column to already wide table (currently about 120 chars), not everyone use fullscreen terminal

[marmarek]

Comment by marmarek on 21 May 2012 12:22 UTC
Current display model show configuration for VM - eg when the user want to configure it manually (eg when using Windows PV network driver). Still doesn't understand why you want to introduce some IP needed for one VM in row describing other VM.

BTW You propose to add additional column to already wide table (currently about 120 chars), not everyone use fullscreen terminal

[marmarek]

Comment by marmarek on 5 Jun 2012 18:00 UTC
Finally agreed on replacing 'netmask' column with 'ip back'.

[marmarek]

Comment by marmarek on 5 Jun 2012 18:00 UTC
Finally agreed on replacing 'netmask' column with 'ip back'.

[marmarek]

Comment by marmarek on 5 Jun 2012 19:28 UTC
http://git.qubes-os.org/gitweb/?p=marmarek/core.git;a=commit;h=3b8272c1b671accede56bc78ce4420cc1eb2ebfe

[marmarek]

Comment by marmarek on 5 Jun 2012 19:28 UTC
http://git.qubes-os.org/gitweb/?p=marmarek/core.git;a=commit;h=3b8272c1b671accede56bc78ce4420cc1eb2ebfe