103 lines
7.6 KiB
HTML
103 lines
7.6 KiB
HTML
{% extends "_layout.html" %}
|
|
{% block title %}I2P Development Meeting 148{% endblock %}
|
|
{% block content %}<h3>I2P dev meeting, September 20 @ 20:00 GMT</h3>
|
|
<div class="irclog">
|
|
<p>16:18 < jrandom> 0) hi</p>
|
|
<p>16:18 < jrandom> 1) 0.6.0.6</p>
|
|
<p>16:18 < jrandom> 2) I2Phex 0.1.1.27</p>
|
|
<p>16:18 < jrandom> 3) migration</p>
|
|
<p>16:18 < jrandom> 4) ???</p>
|
|
<p>16:18 < jrandom> 0) hi</p>
|
|
<p>16:18 * jrandom waves</p>
|
|
<p>16:18 < jrandom> weekly status notes posted up @ http://dev.i2p.net/pipermail/i2p/2005-September/000929.html</p>
|
|
<p>16:18 <+postman> hello</p>
|
|
<p>16:18 < forest> hi</p>
|
|
<p>16:18 < jrandom> lets jump on in to 1) 0.6.0.6</p>
|
|
<p>16:19 < jrandom> the status notes cover pretty much what i've got on my mind for 0.6.0.6. anyone have any questions/concerns/comments to bring up?</p>
|
|
<p>16:19 <+postman> jrandom: observation:</p>
|
|
<p>16:19 <+postman> jrandom: much higher bandwidth consumption</p>
|
|
<p>16:20 <+postman> jrandom: all within the limits and running fine - but my routers really getting warm now</p>
|
|
<p>16:20 * nickless_head makes similar observation</p>
|
|
<p>16:20 < jrandom> aye, me too, i think its likely due to an increase in bt and i2phex traffic</p>
|
|
<p>16:20 <+postman> what increase, with just 80 active torrents on the tracker? :)</p>
|
|
<p>16:20 < jrandom> heh</p>
|
|
<p>16:21 <+postman> but its good to see, that the network does not crumble</p>
|
|
<p>16:21 <+postman> irc is pretty stable altho the router does 50k/s atm</p>
|
|
<p>16:21 < jrandom> mos' def'. i'm not even logged into freenode anymore, as irc here is stable enough</p>
|
|
<p>16:22 * postman hands the mike back</p>
|
|
<p>16:22 < jrandom> cool, thanks. i think there's definitely still room to go for bandwidth efficiency, but it seems reasonable atm</p>
|
|
<p>16:22 < jrandom> (hopefully the thing i'm working on will help, but more on that when its ready)</p>
|
|
<p>16:22 < fox> <mihi> you should definitely distinguish between OK (Nat) and Err (Nat)...</p>
|
|
<p>16:23 < fox> <mihi> or is your hole punching almighty?</p>
|
|
<p>16:23 < jrandom> heh</p>
|
|
<p>16:23 < jrandom> well, ERR-SymmetricNAT is and will continue to be an ERR</p>
|
|
<p>16:23 < fox> <mihi> or is it impossible to check whether it was successful?</p>
|
|
<p>16:24 < fox> <mihi> ok</p>
|
|
<p>16:24 < jrandom> but ERR-Reject is due to restricted cone, while full cone nats work fine</p>
|
|
<p>16:24 < jrandom> (since i2p uses only one source port for everyone, as long as you're on i2p you'll have a hole punched for the full cone)</p>
|
|
<p>16:25 < jrandom> still, it is better when people forward their ports so they don't need introducers, as that lets them also become introducers themselves</p>
|
|
<p>16:25 < fox> <mihi> as long as there are no nasty iptables rules (like drop UDP to 8887 from IP addresses divisable by 7 :) )</p>
|
|
<p>16:25 < jrandom> heh</p>
|
|
<p>16:26 < jrandom> and unfortunately, some people do have b0rked configurations like that (*cough*peerguardian*cough*)</p>
|
|
<p>16:26 < jrandom> someone the other day was wondering why i2p didn't work, even though they had their firewall dropping packets from all .edu peers</p>
|
|
<p>16:27 <+Ragnarok> .edu? That's pretty random</p>
|
|
<p>16:27 < jrandom> yeah, made no sense to me, in so many ways</p>
|
|
<p>16:27 < jrandom> but, c'est la vie</p>
|
|
<p>16:27 * nickless_head sings: We don't need no education...</p>
|
|
<p>16:28 < jrandom> heh</p>
|
|
<p>16:28 < jrandom> ok, anyone else have anything on 1) 0.6.0.6?</p>
|
|
<p>16:29 < jrandom> if not, moving on to 2) i2phex 0.1.1.27</p>
|
|
<p>16:29 < jrandom> not much to say here beyond whats in the mail either...</p>
|
|
<p>16:30 <+postman> jrandom: there was no positive response in the mentioned forums either :(</p>
|
|
<p>16:31 <+postman> jrandom: i will forward your statusnotes and links - maybe the readers get the point</p>
|
|
<p>16:31 < jrandom> postman: people are of course able to use whatever they want, but I don't recommend the binary release from legion as the source doesn't match the binary, and the launcher is entirely closed source</p>
|
|
<p>16:32 < jrandom> now that we've got i2phex on a web accessible location, built from cvs, hopefully that will reduce people's reliance on that</p>
|
|
<p>16:33 < jrandom> (perhaps if you want to post the irc log from #i2p-chat an hour or two ago between legion and i, that might help explain the situation to people more completely)</p>
|
|
<p>16:34 < jrandom> ok, anyone else have anyhing on 2) i2phex, or shall we move on to 3) migration</p>
|
|
<p>16:34 * postman has a look</p>
|
|
<p>16:34 < jrandom> there's not much really to add for 3), its more of an fyi</p>
|
|
<p>16:34 < jrandom> so, perhaps we can jump quickly to 4) ???</p>
|
|
<p>16:34 < jrandom> anyone have anything else they want to bring up for the meeting?</p>
|
|
<p>16:35 <+Complication> Migration?</p>
|
|
<p>16:36 < jrandom> if you didn't notice, great :)</p>
|
|
<p>16:36 < jrandom> we moved from one colo to another</p>
|
|
<p>16:36 < jrandom> (cvs.i2p.net, dev.i2p.net, www.i2p.net, mail.i2p.net)</p>
|
|
<p>16:36 <+Complication> Oh, that migration. :)</p>
|
|
<p>16:36 * Complication is simply a bit slow today</p>
|
|
<p>16:39 <+Complication> By the way, 0.6.0.6 seems very nice... in the regard that my router didn't touch 0 participating tunnels in 54 hours.</p>
|
|
<p>16:39 <+Complication> Not even once.</p>
|
|
<p>16:39 < jrandom> nice</p>
|
|
<p>16:40 < jrandom> ok, if there's nothing else people want to bring up for the meeting...</p>
|
|
<p>16:40 * jrandom winds up</p>
|
|
<p>16:40 <+postman> jrandom: one thing</p>
|
|
<p>16:40 * jrandom stops winding</p>
|
|
<p>16:40 <+postman> jrandom: you just incremented the i2phex version - what if sirup plans another release?</p>
|
|
<p>16:40 < jrandom> postman: sirup uses the cvs</p>
|
|
<p>16:41 <+postman> jrandom: how about giving it a an additional tag</p>
|
|
<p>16:41 <+postman> ok, that's fine then</p>
|
|
<p>16:41 <+postman> :)</p>
|
|
<p>16:41 * postman is back in his cave</p>
|
|
<p>16:41 < jrandom> (developing code outside a source control system == crazy)</p>
|
|
<p>16:41 * Kefoo remembers how crazy it was developing inside a source control system, too</p>
|
|
<p>16:41 <+postman> jrandom: (it did not need to be YOUR's)</p>
|
|
<p>16:42 < jrandom> heh true enough Kefoo ;)</p>
|
|
<p>16:42 < jrandom> heh well, yeah... his just happens to be though ;)</p>
|
|
<p>16:43 * bar just set a new personal record of 156 concurrent udp connections (old record was 152)</p>
|
|
<p>16:43 < jrandom> cool, yeah, i saw 173 earlier today</p>
|
|
<p>16:44 <+bar> oh :) yeah the indtroducing is doing its thing fo' sure</p>
|
|
<p>16:44 < Kefoo> Not to backtrack, but is i2phex supossed to try connecting on startup? I've heard both yes and no.</p>
|
|
<p>16:44 <+bar> -d</p>
|
|
<p>16:44 < jrandom> wikked bar</p>
|
|
<p>16:44 < jrandom> Kefoo: afaik, no.</p>
|
|
<p>16:44 < jrandom> but, i'm no phex dev</p>
|
|
<p>16:45 < Kefoo> The only way I've found is to copy and paste the host keys into the program and connect to them manually</p>
|
|
<p>16:45 < jrandom> thats what i've done Kefoo</p>
|
|
<p>16:45 <+postman> wind ye up now, jrandom :)</p>
|
|
<p>16:45 < Kefoo> Ok, so I'm not making it harder than it should be</p>
|
|
<p>16:45 < Kefoo> I do that sometimes</p>
|
|
<p>16:46 < jrandom> Kefoo: if there's something easier, i'd like to hear about it :)</p>
|
|
<p>16:46 < jrandom> ok ok postman, you can go get your beer ;)</p>
|
|
<p>16:46 * jrandom winds up</p>
|
|
<p>16:46 * jrandom *baf*s the meeting closed</p>
|
|
</div>
|
|
{% endblock %} |