awt[asciilifeform]: Is "port hammering" a way for two stations each behind a firewall to connect?
asciilifeform: awt: if both behind nat, will take considerably longer than if only 1. but yes
awt[asciilifeform]: Or is it possibly needed in the case where one station is not behind a NAT (not sure what the direct term for this is)
asciilifeform: orig. thrd re subj
dulapbot: Logged on 2022-09-19 18:23:29 asciilifeform: awt, phf, jonsykkel , et al: proposed 'hammer algo' :
asciilifeform: ( and described in the pre-draft in 'addrcast' sect. )
awt[asciilifeform] just now noticing the address cast packet format has been updated
asciilifeform: http://logs.bitdash.io/pest/2023-06-16#1027075 << ~symmetric~ nat, that is.
bitbot[asciilifeform]: Logged on 2023-06-16 11:33:36 asciilifeform[4]: awt: if both behind nat, will take considerably longer than if only 1. but yes
asciilifeform: awt: it's compat. with the old format (but 'flag' can nao be 1, see 5.4.10.5 )
asciilifeform: awt: but yes, hammer is for the situation where both sides know the other to be live (i.e. recently received broadcasts from one anuther) but each is trapped behind a nat
asciilifeform: addrcast, in such a case, supplies a usable ip but not a usable port
asciilifeform: to connect, they must play 'port roulette' until they simultaneously win.
awt[asciilifeform]: Ok. It seems the dream of lappy to lappy from cafe may soon be realized.
awt[asciilifeform]: asciilifeform: How can a station determine automatically whether or not to set FLAG to 1, or is it a manual configuration?
asciilifeform: awt: see 5.4.10.5 : flag=1 if station believes it is behind a nat
awt[asciilifeform]: Ok, so "originator believes" -> knob
asciilifeform: correct
asciilifeform: 'bolixcoin' has outperformed btc exchrate for last coupla yrs, lol
asciilifeform: pretty strange to see 'ivory' console w/ 36xx keyboard, also. the proper ones evidently finally ran out, snapped up by stamp collectors
signpost[asciilifeform]: !!ticker btc usd
deedbot[asciilifeform]: $26,452