Vort

How IP addresses for your nodes look like? Also it worth checking for connections as I said before. There may be bugs in simulation tool of course, but first of...

Try using "real" addresses like 1.1.1.1 - 1.1.1.254 for example. I think simulation environment should allow it. Not sure if errors will go away, there may be more problems, but...

> It does not work :( Maybe it worth to try something simpler than i2pd first - web server (nginx) and web client (curl) for example. Or custom made tcp...

> However, i'm still having issues with the peer connection Do you see `Connecting` messages like I mentioned eariler? > and now i am facing a new issue: I don't...

Also I suggest to look at routerinfos inside of netdb directory for your nodes. Do they have `host` and `port` specified? What `caps` they have? 

`PfG` caps are not right. Why transit is disabled? It should not be like that. Also where this RI was located? In netdb of node with other IP (like 100.0.0.2)?...

> this is the router.info found in the data directory for that specific i2pd router It should appear in netdb directory of other routers, in some way, either manually (which...

Router Ident is calculated with hashing. I was saying it because if you have RI file of "unknown" router, you can calculate such ID without additional information. > i added...

I made test by myself, with two virtual machines. First machine, 100.0.0.1, hosted floodfill with such config: ``` bandwidth = P floodfill = true loglevel = debug host = 100.0.0.1...

You may also check for time related problems. If simulation have zero timestamps at the start, it may cause problems. I don't know for sure if that's the case, but...