Default EASE API port clashes with a macOS process

[adriangranados]

It appears that in macOS Monterey, a system process already uses port 5000 and conflicts with the default EASE API port, also 5000.

We need to use a different port. 6000?

[gitzone83]

It is just enough to modify the Vargrant file in the ease directory to use different port number, I switched to 25000 with no issues.

cat Vagrantfile 
Vagrant.configure(2) do |config|
  config.vm.box = "intuitibits/ease"
  if Vagrant.has_plugin?("vagrant-vbguest")
    config.vbguest.auto_update = false
  end
  config.vm.provider "virtualbox" do |vb|
    vb.name = "EASE"
    vb.memory = "1024"
    vb.cpus = "2"
    vb.default_nic_type = "virtio"
    vb.customize ["modifyvm", :id, "--usb", "on"]
    vb.customize ["modifyvm", :id, "--usbxhci", "on"]
  end
  config.vm.provision :file, source: "ease.py", destination: "ease.py"
  config.vm.provision :file, source: "ease", destination: "ease"
  config.vm.provision :shell, path: "bootstrap.sh"
  config.vm.network "forwarded_port", guest: 25000, host: 25000
  config.vm.post_up_message = "External Adapter Support Environment (EASE)"
end

[adriangranados]

That resolves the conflict when booting the image, but WiFi Explorer Pro only knows about port 5000. Changes need to be made in WiFi Explorer Pro to use a different port.