Hey Macedo, the port 2097 is used for local clients to communicate with the messenger service.
Cheers t3sserakt On 27.06.21 12:58, t3sserakt wrote: > You are right with 2097. I was not aware of this port. The messenger > subsystem is using it. It is quite new. We have to add this to the > documentation! > > thx > > - t3sserakt > > On 27.06.21 11:23, Guilherme Macedo via Mailinglist for GNUnet > developers wrote: >> Hi t3sserakt. >> >> Thanks for pointing to the doc. I saw that too. Just asked to be sure, >> because I also have port 2097 opened. >> >> Proto Recv-Q Send-Q Local Address Foreign Address State >> PID/Program name >> tcp 0 0 0.0.0.0:2086 0.0.0.0:* LISTEN >> 503/gnunet-service-transport >> tcp 0 0 0.0.0.0:2097 0.0.0.0:* LISTEN >> 473/gnunet-service-arm >> tcp6 0 0 :::2086 :::* LISTEN >> 503/gnunet-service-transport >> tcp6 0 0 :::2097 :::* LISTEN >> 473/gnunet-service-arm >> >> Do you know if 2097 is just for gnunet-arm internal/local control and can be >> closed? >> Otherwise, no worries, now with GNUnet fully working I can finally start >> playing :) >> Best regards. >> >> Guilherme Macedo >> >> >> >> 27 Jun 2021, 10:51 by [email protected]: >> >>> Hey Guilherme, >>> >>> as you can read here >>> >>> https://docs.gnunet.org/handbook/gnunet.html#Configuring-NAT >>> >>> the default port for external communication is 2086 (and maybe 1080). >>> >>> Cheers >>> >>> t3sserakt >>> >>> On 26.06.21 23:45, Guilherme Macedo via Mailinglist for GNUnet >>> developers wrote: >>> >>>> Hi Christian. >>>> >>>> I tried to install in Debian stable, as according to the instructions in >>>> the doc, but it failed while trying to download the dependencies. >>>> >>>> # apt install -f -t sid gnunet >>>> Reading package lists... Done >>>> Building dependency tree >>>> Reading state information... Done >>>> Some packages could not be installed. This may mean that you have >>>> requested an impossible situation or if you are using the unstable >>>> distribution that some required packages have not yet been created >>>> or been moved out of Incoming. >>>> The following information may help to resolve the situation: >>>> >>>> The following packages have unmet dependencies: >>>> gnunet : Depends: libgnunet (= 0.14.1-1) but it is not going to be >>>> installed >>>> Depends: libc6 (>= 2.29) but 2.28-10 is to be installed >>>> Depends: libgnutls-dane0 (>= 3.7.0) but it is not going to be >>>> installed >>>> Depends: libgnutls30 (>= 3.7.0) but 3.6.7-4+deb10u7 is to be >>>> installed >>>> Depends: libsodium23 (>= 1.0.18) but 1.0.17-1 is to be >>>> installed >>>> E: Unable to correct problems, you have held broken packages. >>>> >>>> I tried to force the install, but I failed. Certainly it's trivial to fix, >>>> but I must admit that my Linux skills are a bit rusty. I've been using Mac >>>> for too long. Maybe it's time to switch back :) >>>> >>>> So I opted for the easy way, installed Ubuntu and used the package >>>> provided by Taler (v0.14.1 git-2a1a812f3). It worked like a charm! >>>> >>>> The only issue that I had, is that it complained that it could not create >>>> /var/log/gnunet.log. I just had to create it manually for GNUnet to >>>> finally work. Not sure if it's related to Taler's package or if I should >>>> open a bug report. >>>> >>>> I'll try another time to compile it again from source. Now it's time to >>>> play a bit with GNS and re:claimID :) >>>> >>>> Quick question, is there a doc about which ports are needed and used by >>>> GNUnet? >>>> I'm asking in order to harden the server and only open the needed ones in >>>> the firewall. >>>> >>>> Best regards. >>>> >>>> Guilherme Macedo >>>> >>>> >>>> >>>> 25 Jun 2021, 08:12 by [email protected]: >>>> >>>>> I recommend installing a way more recent package, i.e. by following: >>>>> >>>>> https://docs.taler.net/taler-exchange-manual.html#installing-the-gnu-taler-binary-packages-on-debian >>>>> >>>>> And then running >>>>> >>>>> # apt install -t sid gnunet >>>>> >>>>> instead of >>>>> >>>>> # apt install -t sid taler-exchange >>>>> >>>>> ;-) >>>>> >>>>> Happy hacking! >>>>> >>>>> Christian >>>>> >>>>> On 6/25/21 12:05 AM, Guilherme Macedo via Mailinglist for GNUnet >>>>> developers wrote: >>>>> >>>>>> Hey! >>>>>> >>>>>> I installed GNUnet v0.10.1 in Debian 10.10 from the package provided by >>>>>> the distro. However, for some reason I can't connect to the peer network >>>>>> since it can't download the hostlist. The returned error is: >>>>>> >>>>>> hostlist-645 WARNING Download of hostlist from >>>>>> `http://v10.gnunet.org/hostlist' failed: `Couldn't resolve host name' >>>>>> >>>>>> If I try to download it manually, I receive the same error. >>>>>> >>>>>> % curl http://v10.gnunet.org/hostlist >>>>>> curl: (6) Could not resolve host: v10.gnunet.org >>>>>> >>>>>> I've read the documentation, but I couldn't find a solution. Maybe the >>>>>> solution is trivial, so apologies in advance. >>>>>> >>>>>> Best regards. >>>>>> >>>>>> Guilherme Macedo >>>>>>
pEpkey.asc
Description: application/pgp-keys
