ADTPro v2.0.2 Ethernet "binding" to Local Host ( 127.0.0.1 ) instead of the Ethernet's IP Address

[MarkO-555]

I am trying to get ADTPro v2.0.2 running on Ubuntu 16.04 LTS...

The Ethernet portions starts, but binds to "lo" rather than "enp4so":

administrator@Magor:~/Desktop/Classic Computers/ADTPro-2.0.2$ ifconfig
enp4s0 Link encap:Ethernet HWaddr 08:60:6e:45:02:9c
inet addr:192.168.254.235 Bcast:192.168.254.255 Mask:255.255.255.0
inet6 addr: fe80::fff6:7ce7:2f93:b8c3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29962043 errors:0 dropped:0 overruns:0 frame:0
TX packets:149808509 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7957392248 (7.9 GB) TX bytes:177489822250 (177.4 GB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:3766007 errors:0 dropped:0 overruns:0 frame:0
TX packets:3766007 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:526141251 (526.1 MB) TX bytes:526141251 (526.1 MB)

Is there a Command Line parameter that lets me select the IP Address to bind to??

I have looked in the documentation, and I can get this to work on Mac OS X and Windows 7...

MarkO

[david-schmidt]

ADTPro isn't super concerned about which address it binds to - the kernel actually chooses that, given the architectural combination of UDP sockets and Java:

It's possible to make a similar call that includes the bind IP address, but it adds not-insignificant complexity specifically for "Ubuntu 16.04 LTS," so you might want to help look into why it's different than (every) other *nix implementation.

[rpallred]

Since upgrading from Mojave to Catalina I'm seeing the same issue with both 2.0.2 and 2.0.3.

[MarkO-555]

Since upgrading from Mojave to Catalina I'm seeing the same issue with both 2.0.2 and 2.0.3.

Sorry I didn't Follow Up, when I found a "work around" to this issue...

rpallred:

I found that the HOSTS File on my Linux, ( /etc/hosts ) was what the ADTPro was using for its information. I wanted to make my Internal Network easy to navigate, so I setup Static IP Addresses for my main machines...

( Some Routers, like my TP-Link, let you leave your devices on DHCP and in the Router, "assign" a constant IP address by Mac Address, basically giving your Device a Static IP Address when connected to your router )

Then I added the Static IP Address and Machine name to the /etc/hosts file. When launching ADTPro, it would BIND to the Machine Name IP Address

If the Static Address in the Hosts File is Wrong, then ADTPro will BIND to that IP Address in the HOSTS File, and not your actually assigned IP Address..

My Machine is MAGOR and it's Static IP Address is: 192.168.254.155
My HOSTS File is:
administrator@Magor:~$ cat /etc/hosts
127.0.0.1 localhost
192.168.254.155 Magor

=============================================================

Something for you to try, ( I'm using OSX 10.11.6 "El Capitan" ) :
Use 'ipconfig getpacket en0' from the command line, to locate your assigned IP Address assigned to the Ethernet Port.
Edit the HOSTS File and add that IP Address and Machine Name, and then save the HOSTS File.
Launch ADTPro, and see if it BINDS to the correct IP Address..

MarkO

[rpallred]

That actually seems to have fixed it--even though I didn't have a static IP for my Mac previously. Thanks!