http://blog.gmane.org/gmane.network.peer-to-peer.netsukuku hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2311 <pre>Hi all! What do you think about this article? "Netsukuku unsuitable for wireless networks" https://we.riseup.net/mbxxii/netsukuk-unsuitable-for-wireless-networks Bye, Ilario Gelmetti _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku </pre> Ilario Gelmetti 2013-06-02T16:19:13 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2305 <pre>As far as I understand, all current implementations of Netsukuku uses IPv4 and 10.0.0.0/8, which does not mix well with private networks, VPNs and so on. But at the same time in the IPv6 world there is such thing as "Unique Local IPv6 Unicast Addresses" which seems to be Just Right for Netsukuku or similar networks: http://tools.ietf.org/html/rfc4193 Maybe Netsukuku should use choose a Global ID and aim primarily for IPv6, allowing to use Netsukuku together with existing IPv4, IPv6 and with other private IPv6 networks (that use other Global ID). Here is example of such prefix: fdf4:0a5c:11c8::/48 fd00::/8 is "Unique Local IPv6 Unicast" area, f40a5c11c8 is Netsukuku's Global ID, the rest 80 bits can be chosen by Netsukuku. _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku </pre> _vi-cmBhpYW9OiY< at >public.gmane.org 2013-05-28T22:42:28 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2299 <pre>The Netsukuku site has been updated! nice one :) _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku </pre> Yussi 2013-05-26T14:17:24 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2286 <pre>I think we need some starting node to make this network, I don't have a domain, or even a static IP, but it would be very nice for new installers to have some network to connect to. Will it be possible to set one up with some sort of public VPN on dyne or freaknet? _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku </pre> Yussi 2013-05-24T13:25:50 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2273 <pre>This guy is starting to convince me that to all intents and purposes ntk and cjdns are the same thing, and ntk has not major advantages over cjdns http://www.reddit.com/r/darknetplan/comments/1emjof/new_netsukuku_subreddit/ca1suwk Is he right? can anyone find a silver bullet that will give a reason not to just drop ntk and go with cjdns? _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku </pre> Yussi 2013-05-20T16:40:05 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2268 <pre>I just made reddit.com/r/netsukuku Not sure why, but why not. Feel free to join, I'll make you a mod if I can figure out how to. _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku </pre> Yussi 2013-05-19T09:10:28 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2253 <pre>Hi! How does one connect two netsukuku nodes without a direct connection? Such as, Through the internet? I saw this on the story of netsukuku deployment blog http://www.tinc-vpn.org/_______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku </pre> Valeska Grim 2013-05-18T07:19:30 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2224 <pre>Hi, I cannot register to edit the https://lab.dyne.org/NewNetsukukuOrg page. It requests a password to register, that must be wrong. _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku </pre> Yussi 2013-05-17T06:39:16 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2204 <pre>To install a virtual machine: you need qemu/kvm (Or any other VM, this is the one i know) create a large file (like at least 2 Gigs), this will be your fake harddrive. $dd if=/dev/zero of=./deb-hda bs=1M count=2000 this will create a file named deb-hda of 2000M (if: input file, of: output file, bs: block size, count: # of blocks) Download any install image, if you know how to build an image yourself even better, you only need a minimal install, X is a unnecessary for our needs. you can get it here: http://cdimage.debian.org/debian-cd/7.0.0/i386/iso-cd/debian-7.0.0-i386-CD-1.iso $kvm --hda deb-hda --cdrom debian-7.0.0-i386-CD-1.iso I used expert install, with pretty much default options, no window manager. this should install it, when done, run $kvm --hda deb-hda When you've done this, i'll show you how to setup the tunnels and bridges. Even though this isn't a qemu list, any problems you have post them here so we can get some sort of testing environment running for a few people. _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku </pre> Yussi 2013-05-16T07:38:59 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2195 <pre>For netsukuku vala: deps: valac &gt;=0.14 libgee-dev libpth-dev libgcrypt11-dev recommended: bzr #see https://savannah.nongnu.org/bzr/?group=netsukuku howto: #clone vala ntk repository bzr branch bzr://bzr.savannah.nongnu.org/netsukuku/vala netsukuku-vala cd netsukuku-vala ./configure make #got a lot of warnings here make install usage: ntkd -i tunnel1 -i wireless -i eth0 -i whatever-interface For messing around apt-get install openvpn bridge-utils #make a tunnel interface sudo openvpn --mktun --dev tap0 --user `id -un` #check it's there ifconfig tap0 #make a bridge interface brctl addbr br0 #check it's there ifconfig br0 #add tunnel if to bridge brctl addif br0 tap0 #start ntkd on the bridge (won't work on tap0 ?!?) ntkd -i br0 #watch it tcpdump -i br0 more or less... _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/netsukuku </pre> Yussi 2013-05-15T15:59:50 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2175 <pre>Spam detection software, running on the system "assata.dyne.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see &lt; at &gt;&lt; at &gt;CONTACT_ADDRESS&lt; at &gt;&lt; at &gt; for details. Content preview: U kunt uw vrije tijd in geld omzetten. Verdien vanaf 100 euro per uur, door per week 1 uur of meer te werken. U krijgt de benodigde scholing kosteloos. Uw werk levert niet alleen geld op. Dankzij u krijgen jonge pati&amp;#235;nten een behandeling van hoge kwaliteit en ook nog op tijd. Voor nadere informatie stuur een bericht naar Charley-QjgbLm7CqLDjTS2pbBBVFw&lt; at &gt;public.gmane.org [...] Content analysis details: (12.3 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 3.6 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL [2.190.3.129 listed in zen.spamhaus.org] 1.6 RCVD_IN_BRBL_LASTEXT RBL: RCVD_IN_BRBL_LASTEXT [2.190.3.129 listed in bb.barracudacentral.org] 1.7 URIBL_DBL_SPAM Contains an URL listed in the DBL blocklist [URIs: hollandsjob.com] 1.8 URIBL_BLACK Contains an URL listed in the URIBL blacklist [URIs: hollandsjob.com] 1.7 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist [URIs: hollandsjob.com] 0.6 URIBL_SBL Contains an URL listed in the SBL blocklist [URIs: hollandsjob.com] 1.3 RDNS_NONE Delivered to internal network by a host with no rDNS _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org http://lists.dyne.org/mailman/listinfo/netsukuku </pre> netsukuku-6BmP915+9Ldg9hUCZPvPmw< at >public.gmane.org 2013-02-04T16:40:46 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2174 <pre> re all, as some might have noticed or read, Dyne.org has been hacked and lulled a few weeks ago by the crewz at Everyone Gets Owned http://pastebin.com/NnJ19iPz (beware the above is better read while playing your fav tunes of Autechre, Clock DVA, Ozric Tentacles, Chemical Broz or even NIN) In the E.G.O. release there is an interesting range of informations about the happy mess running in one of our public servers: you can even use some of it to figure out some passwords and stuff. Damn. While the l33t sp33ch in the zine sounds quite l4m3 (c'mon guys, its 2013, and happy new year!) the reader should be careful before judging this as a scriptkid gig, because to our analysis it seems to be an interesting hack. EGO crewz have used a 0-day vulnerability in the wiki Moin Moin to gain shell access as www-data, something that affected at that time a lot of more websites like the Debian wiki or the Python wiki. Here are the details as released by the Moin Moin crews: http://moinmo.in/SecurityFixes As of now this is a rather serious vuln, patches are almost all out, everyone should update. Our reaction to the discovery was simply to inform Debian and MoinMoin privately, nothing else. We were anyway honoured to see a 0-day burned like that on us. Wow :^) The tech they used to gain the shell is quite serious, there is some smart tunneling via Tor involved and cute moinexec.py shell, in general a rather neat way to cut through our butter with a style that looks better in code than in their z1n3 l33t sp33ch. And they were also right in guessing that almost noone used Jaro Mail. Ultimately the E.G.O. hackers have been kind on us and have not bothered to damage or deface anything. Some people reported outage of the dyne:bolic webpage on reddit http://www.reddit.com/r/pwned/comments/15ay04/dynebolic_r00ted/ but that was pure coincidence since the dynebolic.org website is hosted on another machine that had an harddisk failure right during those days. In their release they speak about having rooted kernel, vendor and bugged our software with backdoors, but frankly that's not true. We have crypto hashes and signatures of all the software we distribute and controlling those everything matches. The server "Munir" which was hacked had a lax security policy anyway because nothing really critical was in there.... it also seems that E.G.O. crews haven't bothered to do root escalation either, but then we might be just wrong on that :^) and while our software users will still be safe, we'll leave those hackers keep a shell on our server, why not. After all, they seem to be able to get one anyway if they want. In fact, just in case they like to step forward with us privately, we are keen to have some exchange and even include part of their interested members in our network (yes, we do have some private mailinglists, you might have seen then by now). At last, since as we mentioned the hack was done with proper tools and as of now a 0-day was burned for the lulz, we offer a reward of 10.1337 Bitcoins to the E.G.O. hackers for releasing some of their neat tools as free software, like the stuff they have used with us... if you do, just publish a Bitcoin address on the next zine, we'll pimp it up for your next golden teeth implant. that's almost all folks! now lets talk politics :^) we leave you with two quotes, the last one is a rather long text from the 5th issue of the Zero For Owned zine titled "Summer of Ham" where some known r0ckst4rs were hacked. Immediately below another short quote. All this because we agree with the rant of the often marginalized, so called "black hats": there are serious problems in the security industry, that the hacker community at large should address, maybe is the time to bash the hell out of the manager cast and their fck'd up hierarchy. As Michael Abrash once wrote, quoting his colleague Gabe Newell: When he (Gabe Newell) looked into the history of the organization, he found that hierarchical management had been invented for military purposes, where it was perfectly suited to getting 1,000 men to march over a hill to get shot at. When the Industrial Revolution came along, hierarchical management was again a good fit, since the objective was to treat each person as a component, doing exactly the same thing over and over. [...] Hierarchical management ... bottlenecks innovation through the people at the top of the hierarchy, and there's no reason to expect that those people would be particularly creative about coming up with new products that are dramatically different from existing ones - quite the opposite, in fact. | \ / _\/_ Industry check .-'-. //o\ _\/_ -- / \ -- | /o\\ ^^~^~^~^~^~^~^~^~~^~^~^~^~^~^~^~^~^~^-=======-~^~~^^~~^~^~^~|~~^~^|^~` We don't talk to police | We don't make a peace bond The security scene is fucked. You have Dan Kaminsky lecturing you on how DNS poisoning will destroy life as we know it. You have Matasano harvesting talent and critiquing everyone, and then Ptacek can only announce the release of....a graphical firewall management client. There's kingcope killing bugs and dropping weaponized exploits while making no other contribution except putting a smile on the face of kiddies. There's iDefense and their competitors selling exploits and only doing research in how to make more exploits. There's Jeff Moss running a conference under the hideous misnomer "Blackhat Briefings" where the same researchers search for glory and present the same shit year after year. There are people who just live press release by press release. And on top of it all, somehow you STILL have not got rid of Kevin Mitnick. The industry cares about virtualization one year and iPhones the next, every year forgetting the lessons it should have picked up in the last. If you are just someone looking to pay a fair price to not get owned, you find out quickly that none of these people exist to help you. Very few people in this industry have their income model based around actually making you more secure. At best, some of them have it based around convincing you that you are better off. The very concept of "penetration testing" is fundamentally flawed. The problem with it is that the penetration tester has a limited set of targets they're allowed to attack, while a real attacker can attack anything in order to gain access to the site/box. So if a site on a shared host is being tested, just because site1.com is "secure" that does NOT in anyway mean that the server is secure, because site2.com could easily be vulnerable to all sorts of simple attacks. The time constraint is another problem. A professional pentester with a week or two to spend on a client's network may or may not get into everything. A real dedicated hacker making the slog who spends a month of eight hour days WILL get into anything they target. You're lucky if it even takes him that long, really. Those things should all be very obvious, but whitehats still make the mistake of discounting them. Look at Mitnick. Every time he gets owned he blames his host or his DNS provider. If he's getting owned through them, that's still his fault. Choosing a host is a security decision, it's just like choosing a password. If you choose a weak one you expose yourself. It's still your fault. It's the same with outsourcing the development of your security-critical code. Mitnick could get someone else to make him a flashy website, and then blame them when it is full of file include vulnerabilities. People do this all the time, indirectly, by using ridiculous CMS or blog software. As an easy example, look at Wordpress. Even easier, look at Wordpress in 2007. Horrid. When considering Wordpress, a blackhat starts reading the PHP, shudders and giggles, and then laughs at the idea of ever using it on one of their servers. A whitehat never gets that far apparently, they just install it and get owned. I simply fail to see how leading security researchers run all kinds of code that is blatantly dangerous. Are they really that bad at reading code? Or do they just not care much if their passwords end up on Full Disclosure? If it's the second option, why is that? Why can these people make a living selling security when they make such bad choices? How do they maintain legitimacy? They take less responsibility for getting owned than do the people who they sell services to. There's a popular term for people who don't read code. We call them script kiddies. You cannot outsource blame. You HAVE to take responsibility for your mistakes, whether they are mistakes in your code, mistakes in code you are using, mistakes by your host, or mistakes in who you trust. These are all security choices. Learn to control this shit. Learn how to read code. A lot of the time it only takes a very shallow audit to realise that the code is crap and is bound to have bugs. In a smarter world, security professionals get paid to stop people from getting owned. End of. These is no limit to the scope of an audit. Are you professional types really this out of touch? I see all these papers about how to protect yourself from these super-fucking-advanced techniques and exploits that very few people can actually develop, and most hackers will NEVER USE. It's the simple stuff that works now, and will continue to work years into the future. Not only is it way easier to dev for simple mistakes, but they are easier to find and are more plentiful. The whole concept of full-disclosure has backfired. It will never work. It's some slashdot hippie pipe dream. Even you dumbass corporate types should recognize this. If you're constantly giving away all the vulnerabilites you find, for *FREE* mind you (and what other industry does that?), and the vulnerabilites get harder and harder to find and exploit, it will get harder and harder for you all to do your "job". Frankly, I'm surprised that the non-disclosure movement didn't start in the security industry in the first place. In a way it did, by default. With full-disclosure, the security industry is all about show and gloat, it is not about fixing anything. A lot of bugs have been fixed from it, but it comes with the price of an industry that likes to cripple itself. Projects run by teams of trained monkeys are always eager to add more bugs to replace those that have been fixed. We hate the industry because it is full of shit. There are so many trolls like Kaminsky who just desperately search for anything new, to get attention. So many talentless buffoons trying to scam the planet. A lot of the actual talent out there is severely misapplied. It's an industry tied to news and not results, because very few of you can even attain results. When you can't, who's the wiser? Your customers can hardly tell if you have really made them more secure or not. Sometimes there are superficial benefits, sometimes there aren't. How do you convince the customer that they are more ZF0-safe than before, if they were never targetted and probably never will be? And you all lack the legitimacy to really do the job you should anyways. We can only expose so many frauds, the rest of you can pretend you have changed something. Very few whitehats actually go out there and provide a service where they make people more secure. Not just for a day or a month. Are you genuinely fixing the underlying design and logic flaws that generate security problems for your clients or customers? If you actually clean up every exposed security flaw they have, will they still be "secure" in six months or a year? We could go on. Just in general, the industry is failing. Flat out failing. You cannot even protect yourselves. ---------------------------------------------------------------------- </pre> Jaromil 2013-01-15T10:22:07 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2172 <pre>Spam detection software, running on the system "assata.dyne.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see &lt; at &gt;&lt; at &gt;CONTACT_ADDRESS&lt; at &gt;&lt; at &gt; for details. Content preview: Goedemiddag, U kunt in uw vrije tijd 6 tot 12 euro per uur verdienen door ons te helpen. Ons bedrijf is gespecialiseerd in medisch toerisme. Wij helpen mensen een medische behandeling bij de beste doktoren te krijgen en dat tegen een redelijke prijs. Wij zijn op zoek naar vertegenwoordigers in uw stad. Het werk bestaat uit de controle van betalingen en het versturen van documenten per post. [...] Content analysis details: (16.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 3.6 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL [188.76.148.178 listed in zen.spamhaus.org] 0.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address [188.76.148.178 listed in dnsbl.sorbs.net] 1.7 URIBL_DBL_SPAM Contains an URL listed in the DBL blocklist [URIs: hollandjobnl.com] 1.7 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist [URIs: hollandjobnl.com] 0.3 URIBL_RHS_DOB Contains an URI of a new domain (Day Old Bread) [URIs: hollandjobnl.com] 1.8 URIBL_BLACK Contains an URL listed in the URIBL blacklist [URIs: hollandjobnl.com] 3.9 HELO_DYNAMIC_IPADDR2 Relay HELO'd using suspicious hostname (IP addr 2) 2.9 HELO_DYNAMIC_SPLIT_IP Relay HELO'd using suspicious hostname (Split IP) 0.1 TVD_RCVD_IP TVD_RCVD_IP 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines 0.6 URIBL_SBL Contains an URL listed in the SBL blocklist [URIs: hollandjobnl.com] 0.4 RDNS_DYNAMIC Delivered to internal network by host with dynamic-looking rDNS _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org http://lists.dyne.org/mailman/listinfo/netsukuku </pre> alpt-6BmP915+9Ldg9hUCZPvPmw< at >public.gmane.org 2012-12-25T19:26:17 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2171 <pre>Spam detection software, running on the system "assata.dyne.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see &lt; at &gt;&lt; at &gt;CONTACT_ADDRESS&lt; at &gt;&lt; at &gt; for details. Content preview: Geachte dames en heren, Wij bieden u de mogelijkheid in uw vrije tijd 12 tot 59 euro per dag te verdienen. Wat moet u doen? U moet de betaling van onze klant via Internet controleren en de ontvangen documenten per post opsturen. Dat kost u 2 a 3 uur tijd. Dat hebben wij nodig om de bestellingen sneller te verwerken. Wij zijn gespecialiseerd in medisch toerisme en verkopen reizen vouchers voor medische behandeling in andere landen. De betaling wordt dagelijks uitbetaald, na de uitvoering van het werk. Wij organiseren voor u een kostenloze opleiding op maat en instructies. Ik verzoek u uw aanvraag naar mijn e-mailadres Wendell-JNQ2O8C66cYwPvpn7j8cfQ&lt; at &gt;public.gmane.org te sturen. Vermeld hierin de volgende gegevens: 1. Uw achternaam 2. Uw woonplaats 3. Het gewenste aantal werkuren per week. In de antwoordbrief stuur ik u uitgebreide informatie over ons bedrijf en dit werk. Ik hoop, dat wij straks zullen beginnen met samenwerken. Met hartelijke groet, [...] Content analysis details: (10.6 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 1.7 URIBL_DBL_SPAM Contains an URL listed in the DBL blocklist [URIs: euroworknl.com] 3.2 HELO_DYNAMIC_DIALIN Relay HELO'd using suspicious hostname (T-Dialin) 3.6 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL [80.134.149.185 listed in zen.spamhaus.org] 1.8 URIBL_BLACK Contains an URL listed in the URIBL blacklist [URIs: euroworknl.com] 0.4 RDNS_DYNAMIC Delivered to internal network by host with dynamic-looking rDNS _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org http://lists.dyne.org/mailman/listinfo/netsukuku </pre> netsukuku-6BmP915+9Ldg9hUCZPvPmw< at >public.gmane.org 2012-12-19T09:13:48 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2165 <pre>Venu Gopal wants you to try Dropbox! Dropbox lets you bring all your photos, docs and videos with you anywhere and share them easily. Accept invitation here: http://www.dropbox.com/el/?r=/referrals/NjI2NTU1ODMyNzc%3Fsrc%3Dreferrals_email9%26eh%3DAAAjAdMO3zFawFGj3u-UD5v_j6BFsEyl8xs6VbdJ8LTEEQ&amp;b=clk:None:9244356694636434056:789:462&amp;z=AAC4kZ3_Jz9M6rVadUYCLwW47VQE-s3EySis5xBtZ_kZtw - The Dropbox Team ____________________________________________________ To stop receiving invites from Dropbox, please go to http://www.dropbox.com/bl/AACt6pyfMUHiDhPMTXjyw4UVmMT96D3BUVvCm7L7FnjCVA/netsukuku%40lists.dyne.org_______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org http://lists.dyne.org/mailman/listinfo/netsukuku </pre> Dropbox 2012-10-01T12:55:11 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2162 <pre>I just found out about netsukuku and caught my attention. If there can be found more information about setup and necessary libs I would need to compile I would like to start to deploy in and around Budapest. I'm running Backtrack and have linux certification so shouldn't be to difficult. Perhaps one of the programmers can start to make a windows version of it and also make it available for apt under Linux. Also, the freaknet website would be nice to see in English :) _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org http://lists.dyne.org/mailman/listinfo/netsukuku </pre> Attilafx 2012-09-09T06:57:38 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2157 <pre>Hi, I've been meaning to start rolling this for years now, and now this seems like a good time. I wrote this "pitch", and i intend to distribute this or something similar around London circles. I figured i'll pass it through you to get your input, especially Luka's. I am hoping that this will get things starting. have a look and let me know If I should change anything. Also, if you are in London and want to help out, please contact me. Thanks, Yussi. _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org http://lists.dyne.org/mailman/listinfo/netsukuku </pre> Yussi 2012-06-20T11:54:57 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2152 <pre>Recently I have had very little free time to spend on netsukuku. During this time I explored and worked my way through the use of Anjuta (IDE) and Autotools-based configuration of projects in order to improve my netsukuku-coding workflow (at the moment I code with gedit, the makefiles are hand-written, and I debug occasionally with nemiver on the generated C source files) Further, I am writing down some notes for presenting to the public what we are trying to achieve with netsukuku network and what is the current status of the software tools. These notes will form the content and structure of the new website. Writing something updated in the website is extremely important. First, because many people looking at the website get the impression that the project is dead. Second, the website has to convey the points that we want to address. We must expose, in a non technicalese language, what are the limits that the current architecture of the Internet impose on us. Which are not fixed enough by other projects that are actively developed: OLSR, CJDNS, ... These points are too hard to find and understand in the website right now. Finally, the website has to make very easy for the user to experiment with the currently available prototypes of the software tools on their own hardware. My notes are available here at the moment: http://lab.dyne.org/NewNetsukukuOrg Contributions are welcome --Luca _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org http://lists.dyne.org/mailman/listinfo/netsukuku </pre> Luca Dionisi 2012-06-15T12:02:23 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2151 <pre> _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org http://lists.dyne.org/mailman/listinfo/netsukuku </pre> Margherita Goldire 2012-06-05T13:58:45 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2150 <pre>I made another attempt at preparing a OpenWRT firmware and SDK for my router (TP-LINK 1043ND) which is suited for building and running the netsukuku daemon. This time I used a more recent revision of OpenWRT, 31835. The remarkable point in that revision is the use of a 3.3 linux kernel with patches from the amazing work from bufferbloat.net team at CeroWRT (CoDel AQM, Fair queue, BQL and the likes) [0] Further I used the versions of glib2 and pthsem libraries which are included in the OpenWRT. The version for glib2 is much older (2.26 vs 2.32), but it seems that it works ok. So that the process for building is much shorter. I took notes while producing that here: [1] The code of netsukuku in the repository now builds with Vala 0.14.2 --Luca [0] http://gettys.wordpress.com/2012/05/08/fundamental-progress-solving-bufferbloat/ [1] http://lab.dyne.org/Netsukuku_Dev/vala/flashing_notes3 _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org http://lists.dyne.org/mailman/listinfo/netsukuku </pre> Luca Dionisi 2012-05-28T07:22:48 http://comments.gmane.org/gmane.network.peer-to-peer.netsukuku/2149 <pre>A new revision is in the repository. The main point of it, is that I used a fresh installation of a recent O.S. (Ubuntu 12.04) So it builds with - valac 0.14.2 - glib2 2.32.1 In other news, I tried and built a new firmware with a more recent revision of OpenWRT: rev31710. It is worth to note that recently OpenWRT passed from glibc to eglibc. I flashed my tp-link with - OpenWRT rev 31710 - eglibc 2.13 and it is able to run netsukuku. I have put on the wiki more detailed instructions: http://lab.dyne.org/Netsukuku_Dev/vala/flashing_notes2 --Luca _______________________________________________ Netsukuku mailing list Netsukuku-pma9X3FYtpzZ+VzJOa5vwg&lt; at &gt;public.gmane.org http://lists.dyne.org/mailman/listinfo/netsukuku </pre> Luca Dionisi 2012-05-20T21:14:07 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.network.peer-to-peer.netsukuku