tonika ip address resolve problem

[hp fk]

my test shows without ip:port configured for both self and the contact
on both side of tonika( total 2x2 ip:port), the 2 peers of tonika
friends can not reach each other.
suppose 2 friends with ADSL connection and with dynamic ip, before
they can reach each other, they must set up the local public ip:port
first every time the ip changed and notify the other side by email, or
they send email to ask for the other's public ip if the other's ip
changed and set it up in tonika.
i hope this is not the way tonika work.

[Petar Maymounkov]

The current version of Tonika requires that at least one of the
endpoints has a static IP that accept connections at a given port
number.

In the future, I hope to integrate STUN/ICE/uPnP-type technology
to allow for firewalled and dynamic IP addresses.

P

[hp fk]

I did more tests, I set up 2 linux, one with 192.168.0.2:44950, the
other 192.168.0.92:39390, and they share an ADSL connection with port
forword incoming TCP/UDP for port 44950 to 192.168.0.2, port 39390 to
192.168.0.92. the ADSL will get a dynamic IP, for example
117.35.228.221, and keep it until connection is dropped. to make
configuration independent, ADSL is dropped and reconnected for
different configurations to get a different external IP address.

configuration 1: on 192.168.0.92, tonika self address left blank, set
friend's address to 117.35.224.160:44950; on 192.168.0.2, both self
address and friend address left blank.
192.168.0.92 can get index.html from 192.168.0.2, 192.168.0.2 can not
get index.html from 192.168.0.92, message showed in browser: ”Could
not fetch data from Tonika“

configuration 2: on 192.168.0.92, tonika self address
117.35.228.221:39390,set friend's address to 117.35.228.221:44950; on
192.168.0.2, both self address and friend address left blank.
both friends can reach and fetch index.html.

configuration 3: on 192.168.0.92, tonika self address
117.35.237.77:39390, friend's address left blank; on 192.168.0.2, to
nika self address 117.35.237.77:44950, friend's address left blank;

friends can not reach each other.

to reach and fetch from a friend, the friend's external IP is needed.
friends know each other's ID, so a subsystem for look up IP from ID is
needed for p2p network, like DNS system for internet. when a node join
the p2p network, it's ID and external IP is automatically revealled to
the p2p network, and the p2p network could have captured the ID and
external IP and stored it in the p2p network for look up.

[Petar Maymounkov]

Thanks for your tests!

I am currently working on NAT and firewall punching.

You can find links to the related projects GoNeedle and GoDCCP
on the Tonika Blog.

Thanks,
--Petar

[hp fk]

2010/8/18 Petar Maymounkov <pet...@gmail.com>:

> Thanks for your tests!
>
> I am currently working on NAT and firewall punching.
>
> You can find links to the related projects GoNeedle and GoDCCP
> on the Tonika Blog.
>
> Thanks,
> --Petar

the HTTP service of tonkia is over TCP,and in the tests, the NAT and
firewall is already punched for tonika in the configuration for the
ADSL box. but even when each tonika node set its own external public
address IP:port for HTTP service, it seems the information does not
available to the friend node through the p2p network.
I do not know how a tonika node joins the p2p network before friends
could accept invitation , suppose tonika nodes form a Kademlia p2p
network, and each tonika node stores its external public address
IP,UDPport-Kademlia,ID on the p2p network, and IP,UDPport-Kademlia can
be looked up by ID,and then through the friend's IP:UDPport-Kademlia
find services available IP:TCPport-http for HTTP service.
anyway, if there's a method for tonika to lookup friend's external
IP:TCPport-http from friend's ID works well, there will be no such
problem concerned with IP:port resolve.