- 18 Feb, 2015 4 commits
-
-
Jeromy authored
-
Jeromy authored
-
Jeromy authored
-
Juan Batiz-Benet authored
-
- 14 Feb, 2015 1 commit
-
-
Brian Tiger Chow authored
-
- 13 Feb, 2015 1 commit
-
-
Jeromy authored
-
- 11 Feb, 2015 1 commit
-
-
Juan Batiz-Benet authored
We were half-way with this. there's no way for net.Dialers to respect contexts, so we have to let the dial finish in the background.
-
- 10 Feb, 2015 1 commit
-
-
Juan Batiz-Benet authored
thanks @whyrusleeping for finding these.
-
- 06 Feb, 2015 1 commit
-
-
Juan Batiz-Benet authored
Use of the ratelimiter should be conscious of the ratelimiter's potential closing. any loops that add work to ratelimiter should (a) only do so if the rate limiter is not closed, or (b) prevent limiter while work is added (i.e. use limiter.Go(addWorkHere))
-
- 05 Feb, 2015 1 commit
-
-
Juan Batiz-Benet authored
- time them out (already was doing that with addrbook) - keep count to counter symmetric nats
-
- 03 Feb, 2015 10 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
Let's save log.Error for things the user can take action on. Moved all our diagnostics to log.Debug. We can ideally reduce them even further.
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
TODOs: - need to consolidate all the versioning stuff into one package - need to do the version check as a handshake, before further communication happens. we used to do this.
-
Juan Batiz-Benet authored
so that we dont get stuck dialing bad addrs first always.
-
Juan Batiz-Benet authored
This will mitigate the fd explosion, but slow down dials majorly as any peer with more addresses than the rate limit will have to wait a whole dial timeout (~15s)
-
Juan Batiz-Benet authored
This addr manager should seriously help with the addrsplosion problem.
-
Juan Batiz-Benet authored
-
- 02 Feb, 2015 4 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
- 01 Feb, 2015 1 commit
-
-
Juan Batiz-Benet authored
-
- 31 Jan, 2015 3 commits
-
-
Juan Batiz-Benet authored
this commit moves management of the nat to its own object. perhaps this can be general enough to work with any host (not just BasicHost), but for now keeping here. the nat manager: - discovers and sets up the nat asynchronously. - adds any port mappings necessary if/after nat has been found. - listens to the network Listen() changes, adding/closing mappings
-
Juan Batiz-Benet authored
After this commit, client can close individual mappings (without closing the whole NAT)
-
Juan Batiz-Benet authored
Network now signals when it successfully listens on some address or when an address shuts down. This will be used to establish and close nat port mappings. It could also be used to notify peers of address changes.
-
- 30 Jan, 2015 4 commits
-
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
p2p/net: network interface Listen func
-
Juan Batiz-Benet authored
network interface now allows setting Listeners after the fact. This is useful to create the network and start listening as separate steps. And to keep the network up to date on new addresses the node might have to listen to.
-
Juan Batiz-Benet authored
network interface now allows setting Listeners after the fact. This is useful to create the network and start listening as separate steps. And to keep the network up to date on new addresses the node might have to listen to.
-
- 29 Jan, 2015 2 commits
-
-
Jeromy authored
-
Juan Batiz-Benet authored
dialing 4000 connections somehow keeps choking both travis and jenkins. dialing this down to 500
-
- 28 Jan, 2015 5 commits
-
-
Juan Batiz-Benet authored
- attempts set to 1 now. - timeouts must account for that.
-
Juan Batiz-Benet authored
p2p/net: dial log -> events
-
Juan Batiz-Benet authored
+ fixed race
-
Juan Batiz-Benet authored
-
Brian Tiger Chow authored
-
- 27 Jan, 2015 1 commit
-
-
Juan Batiz-Benet authored
This commit turns all dial logs into log.Events. Everything's great except for one problem: The LoggableMap I'm using does not print out things correctly. I gave it peer.IDs, and Multiaddrs and both got logged as nothing `{}` (didn't even call their String() methods!) So, for now, this function encodes it when called... This is wrong and should be fixed before being merged in. Otherwise we will be constantly encoding peer.IDs and Multiaddrs without needing to. @briantigerchow how do you suggest doing this? I don't know my way around your Loggable.
-