I have an email in with @slibert and his Kauai Labs team to look at solutions from the VMXpi side, but it might have gotten lost in the aether and I’ll try again tomorrow…
Somehow I missed the email, but here are some initial thoughts.
I’m assuming on the VMX-pi, networking was configured via the setupWifiAP.sh script. This configures both the RPI’s Wifi and also eth0 ports to issue DHCP addresses to any other device requesting DHCP addresses. You can see the configuration information for this in the /etc/dnsmasq.conf configuration file.
We took this approach as a fallback, so that someone with a PC could directly connect ethernet to the RPI, and as long as the PC had DHCP enabled, the two could communicate easily.
Based upon that, it is likely that whatever DHCP-enabled ethernet devices are connected to the same the ethernet network are having their DHCP addresses assigned by the Raspberry Pi. These will be in the 172.22.11.X subnet.
If that’s not the desired behavior, one option would be to disable the RPI eth0 DHCP by editing the etc/dnsmasq.conf file, and then issuing a restart to the dnsmasq service. We don’t currently include a script that does exactly what I’m describing, so it’d require manual editing of the dnsmasq.conf file.