Author Topic: gnunet-transport-check does not work for me  (Read 10911 times)

0 Members and 1 Guest are viewing this topic.

Offline artwine

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
gnunet-transport-check does not work for me
« on: May 29, 2006, 09:39:51 PM »
Hi,
I have installed gnunet0.7.0d on my gentoo box
and configured it (hopefuly properly) thru gnunet-setup and gnunet-setup -d
and set forwarding for tcp+udp 2086 and 1080 on my router,
but command gnunet-transport-check gives only this output:

Testing transport(s) udp tcp http nat

and waits forever. Similarly: "gnunet-transport-check -p" gives only this:

Available transport(s): udp tcp http nat

and waits forever too (I have been wait for 15 minutes for both).
What I am doing wrong?

Offline artwine

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
gnunet-transport-check does not work for me
« Reply #1 on: May 29, 2006, 09:44:40 PM »
note: I did both gnunet-setup and gnunet-transport-check
under non-root user which was add to gnunet group
(I do not know if it is gentoo specific or not)

Offline ndurner

  • Advanced
  • ***
  • Posts: 176
  • Karma: +5/-1
  • Planet Peer Community
    • View Profile
    • Nils Durner
Re: gnunet-transport-check does not work for me
« Reply #2 on: May 30, 2006, 04:53:37 AM »
Code: [Select]
Hi,

please try
[code]
gnunet-transport-check -L DEBUG
This should give a little more output about what the transport-check is doing.

Note that earlier versions of the Gentoo package were completely broken and a proficient member of the GNUnet community wasn't able to get GNUnet running on Gentoo. That's why the package isn't listed on gnunet.org.

If you have the same difficulties installing GNUnet, please get the source and compile as described on: http://www.gnunet.org/user_gnunet.php3. After the "make" step, you might want to do "make check" first (it'll run some tests to ensure the most vital parts are working as they should).

Hope this helps,

Nils[/code]
« Last Edit: May 31, 2006, 03:43:44 PM by ndurner »

Offline artwine

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: gnunet-transport-check does not work for me
« Reply #3 on: May 31, 2006, 07:45:14 AM »
Thans, now I see it was createing a key for more than 7 hours :-)
(It is an old pentium-mmx so no wonder) :

$ gnunet-transport-check -L DEBUG
Testing transport(s) udp tcp http nat
May 30 23:03:33 DEBUG: Loading service `identity'
May 30 23:03:33 MESSAGE: Creating new hostkey (this may take a while).
May 31 06:23:58 MESSAGE: Done creating hostkey.
....

Offline artwine

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: gnunet-transport-check does not work for me
« Reply #4 on: May 31, 2006, 07:47:51 AM »
but I have another problem, there are some error messages:

$ gnunet-transport-check
Testing transport(s) udp tcp http nat
`tcp': Did not receive message within 5000 ms.
`http': Could not send.
`udp': Did not receive message within 5000 ms.

... or from first run with DEBUG output enabled:

$ gnunet-transport-check -L DEBUG
Testing transport(s) udp tcp http nat
May 30 23:03:33 DEBUG: Loading service `identity'
May 30 23:03:33 MESSAGE: Creating new hostkey (this may take a while).
May 31 06:23:58 MESSAGE: Done creating hostkey.
May 31 06:23:58 DEBUG: Loading service `transport'
May 31 06:23:58 DEBUG: Loading transports `udp tcp http nat'
May 31 06:23:58 DEBUG: Loading service `stats'
May 31 06:23:58 DEBUG: Loaded transport `udp'
May 31 06:23:58 DEBUG: Loaded transport `tcp'
May 31 06:23:58 DEBUG: Loaded transport `http'
May 31 06:23:58 DEBUG: Loaded transport `nat'
May 31 06:23:58 DEBUG: I am peer `0EI2RUO28SCLSKO1CD62NER27MADBFOPQ94S153CETCMBV8OAKCRV9K0VFSI7KUEPM74NUT64COJV0UR8QKRHP3HUEI6QEK6AE4O570'.
May 31 06:23:58 DEBUG: connection goal is 28 peers (3000000 BPS bandwidth downstream)
May 31 06:23:58 DEBUG: Loading service `session'
May 31 06:23:58 DEBUG: Loading service `pingpong'
May 31 06:23:58 DEBUG: `pingpong' registering handlers 2 3 (plaintext and ciphertext)
May 31 06:23:58 DEBUG: Loading service `topology_default'
May 31 06:23:58 DEBUG: `session' registering handler 1 (plaintext and ciphertext)
May 31 06:23:58 DEBUG: Loading service `fragmentation'
May 31 06:23:58 DEBUG: `fragmentation' registering handler 5
May 31 06:23:58 DEBUG: TCP uses IP address 83.147.6.208.
May 31 06:23:59 DEBUG: TCP uses IP address 83.147.6.208.
`tcp': Did not receive message within 5000 ms.
`http': Could not send.
`udp': Did not receive message within 5000 ms.
May 31 06:24:08 DEBUG: Unloading service `module_session'.
May 31 06:24:08 DEBUG: Unloading service `module_fragmentation'.
May 31 06:24:08 DEBUG: Unloading service `module_topology_default'.
May 31 06:24:08 DEBUG: Unloading service `module_pingpong'.
May 31 06:24:08 DEBUG: Unloading service `module_transport'.
May 31 06:24:08 DEBUG: Unloading service `module_stats'.
May 31 06:24:08 DEBUG: Unloading service `module_identity'.
May 31 06:24:08 MESSAGE: Shutdown complete.
« Last Edit: May 31, 2006, 08:00:26 AM by artwine »

Offline artwine

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: gnunet-transport-check does not work for me
« Reply #5 on: May 31, 2006, 07:57:04 AM »
note: in my iptables rules there is "-A INPUT -i lo -j ACCEPT" as the first rule,
so firewall is probably not the problem, as I understand that gnunet-transport-check
use loopback interface...

Offline ndurner

  • Advanced
  • ***
  • Posts: 176
  • Karma: +5/-1
  • Planet Peer Community
    • View Profile
    • Nils Durner
Re: gnunet-transport-check does not work for me
« Reply #6 on: May 31, 2006, 03:52:07 PM »
May 30 23:03:33 MESSAGE: Creating new hostkey (this may take a while).
May 31 06:23:58 MESSAGE: Done creating hostkey.
Was your system very busy during key generation?
From my Pentium Classic-100:
Code: [Select]
May 31 18:47:44 MESSAGE: Creating new hostkey (this may take a while).
May 31 18:48:21 MESSAGE: Done creating hostkey.

Quote
so firewall is probably not the problem, as I understand that gnunet-transport-check
use loopback interface...

No, you have to allow incoming connections on your external interface (83.147.6.208). The loopback interface (lo, 127.0.0.1) is used for client connections only.

Regards,

 Nils

Offline artwine

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: gnunet-transport-check does not work for me
« Reply #7 on: May 31, 2006, 05:57:20 PM »
No, it was not bussy, gnunet-transport-check was the only active process..

Yes, outer connection has needed ports allowed and forwared correctly I hope.

I have not found in available docs, what do these messages mean:
`tcp': Did not receive message within 5000 ms.
`http': Could not send.
`udp': Did not receive message within 5000 ms.

Offline ndurner

  • Advanced
  • ***
  • Posts: 176
  • Karma: +5/-1
  • Planet Peer Community
    • View Profile
    • Nils Durner
Re: gnunet-transport-check does not work for me
« Reply #8 on: May 31, 2006, 07:00:25 PM »
`tcp': Did not receive message within 5000 ms.
A message that was sent to itself wasn't received within 5 seconds, so there's something wrong with your network.
Note that this isn't too bad. It's just that other peers are not able to connect to you. But you're able to connect to them yourself, resulting just in fewer connected peers.

Quote
`http': Could not send.
The HTTP transport failed for some reason. Did you run with "-L DEBUG"?

Regards,

  Nils

Offline artwine

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: gnunet-transport-check does not work for me
« Reply #9 on: June 01, 2006, 09:56:05 AM »
Yes, please see -L DEBUG output in this thread...

Ad "there's something wrong with your network":
but *what* is wrong? it works for all other apps, and this was check using localhost loopback,
so what could be wrong?

Offline ndurner

  • Advanced
  • ***
  • Posts: 176
  • Karma: +5/-1
  • Planet Peer Community
    • View Profile
    • Nils Durner
Re: gnunet-transport-check does not work for me
« Reply #10 on: June 01, 2006, 07:25:10 PM »
There are infinite possibilities to mess up your packet filter/NAT, I'm afraid.
Maybe you should ask someone you trust to nmap your port 2086. If it is open, fine. If not, post your configuration, maybe the error is obvious.

HTH,

Nils