harry newton wrote:

Bear in mind that there is *no router* involved in this setup.

Well 10.50.0.1 *is* you default gateway, if that wasn't acting as a
router you wouldn't have internet connectivity.

This is a *great* command to see the *relationship* between the IP
address and the interface adapter!

This powershell command will show you all IP addresses to do with all
interfaces and their status, paste it into a powershell window

get-netIpAddress | format-table -property *

My own script based on that command filters the list down to IPv4
addresses, excludes interfaces that windows won't make use of, and uses
CIDR notation. It shouldn't mind being pasted into a powershell window
with the line-breaks as they are below

get-netIpAddress -addressState preferred -addressFamily ipv4 |
format-table -property interfaceAlias, prefixOrigin,
@{
label="ipAddress";
expression={ $_.ipAddress + "/" + $_.prefixLength}
}

You could save that as a handy .ps1 script, but to run it you'll need to
jigger about with your powershell execution policy.

https://blog.netspi.com/15-ways-to-bypass-the-powershell-execution-policy