#50 Neighbors problem v0.2.10

[mabarcelona]

With the v0.2.10 we can't associate neighbors

- We go to FADA http admin

- We try to join a new neighbor

- If we put the IP, this Exception is shown

nternal server error:

Exception: java.net.MalformedURLException

java.net.URL.(Unknown Source)

java.net.URL.(Unknown Source)

java.net.URL.(Unknown Source)

net.fada.http.FadaProcessor.doAdminCommand(FadaProcessor.java:142)

net.fada.http.FadaProcessor.processPOST(FadaProcessor.java:812)

net.fada.http.DelegatingProcessor.processPOST(DelegatingProcessor.java:92)

net.fada.http.Dispatcher.run(Dispatcher.java:42)

java.lang.Thread.run(Unknown Source)

- If we put a URL like this
http://193.144.228.126:2002, the servENT shows this message

URL: http://localhost:2002/

last message: Connect: Connected neighbor
http://193.144.228.126:2002 to this node

Command executed with success. Go back

but in the neighbors there is no one

[David Sánchez]

Logged In: YES
user_id=1476633

Does the servent autostart Fada or you have done it
manually¿?

In case you have done it manually, please make sure that
on your fada.rc file all the IP's are written explicitely,
I mean, no "localhost" should appear.

As an example I will show the beginning of a correct
fada.rc:

nonSecureURL=http://192.168.100.3:2002
nonSecurePort=2008
secureURL=<my-host>:<my-secure-port>
securePort=<my-secure-port>
secureMode=false

notice that the IP is written "as is".

[mabarcelona]

Logged In: YES
user_id=1300343

Hi, Fada is started manually due to this bug reported
(https://sourceforge.net/tracker/index.php?func=detail&aid=1562176&group_id=138511&atid=740882)

We have changed localhost by the IP and it works.

How can we manage this problem in case of dynamic IPs?

[F.Javier Noguera]

Logged In: YES
user_id=616583

When the servent autostart the FADA node automatically, the
IP can be monitorized and changed on the fly.

This autostart fada option has been disable in version
0.2.10, but will be available again in 0.3.x