A few of these sprout up organically in locales and it would be like the BBS days of yore - ultimately it could lead to a larger geographical footprint of a "side-net".
mesh is in preparation.
There is already a mesh implementation done for the sister-project "LibraryBox. The code is contributed back to PirateBox. It still needs some tine addons to work nicely.
Bridging could be done with some configuration, I think. IMHO the 2nd device don't need to be a PirateBox.
FreedomBox perhaps? WunderWurfel? Anything seems better than Pirate-something.
"I know patentees are much troubled with piracies upon
their inventions" (Irwin v. McRoberts 1879)
"he has a just defence, and is not a willful pirate
of the plaintiff’s invention" (Goodyear v. Dunbar 1860)
and so on...
PirateBox is a self-contained mobile communication and file sharing device. Simply turn it on to transform any space into a free and open communications and file sharing network. Inspired by pirate radio and the free culture movements, PirateBox utilizes Free, Libre and Open Source software (FLOSS) to create mobile wireless communications and file sharing networks where users can anonymously chat and share images, video, audio, documents, and other digital content.
How does it work?
Simply turn PirateBox on to transform any space into an offline communication and wireless file sharing network. When users join the PirateBox wireless network and open a web browser, they are automatically redirected to the PirateBox welcome page. Users can then immediately begin to chat anonymously, post images or comments on the bulletin board, watch or listen to streaming media, or upload and download files.
PirateBox runs on multiple devices, including wireless routers, Android-based phones, single-board computers like the Raspberry Pi, and even laptops.
Is it safe?
PirateBox is designed to be private and secure. No logins are required and no user data is logged. Users remain anonymous – the system is purposely not connected to the Internet in order to subvert tracking and preserve user privacy.
Can I make my own PirateBox?
Absolutely! The PirateBox is is free (as in freedom) because it is registered under the GNU GPLv3. This license grants the right to freely copy, distribute, and transform creative works according to the principles of copyleft.
PirateBox can be built for as little as US$35. For detailed instructions, visit the PirateBox OpenWrt DIY page.
Where can I read more about the PirateBox?
Visit the PirateBox Press page for a listing of and links to more than 175 stories about the PirateBox.
Where can I find more photos of the PirateBox?
Check out the PirateBox Gallery.
Where can I find more videos of the PirateBox?
Check out these PirateBox Videos.
Why did you build the PirateBox?
The PirateBox solves a technical/social problem by providing people in the same physical space with an easy way to anonymously communicate and exchange files. This obviously has larger cultural and political implications and thus the PirateBox also serves as an artistic provocation. See this ars technica article and this New Scientist article for more info.
Why is it called the PirateBox?
The PirateBox is inspired by the free culture and pirate radio movements. The name is a playful remixing of the title of the world’s most resilient BitTorrent site, The Pirate Bay.
Does the PirateBox promote stealing?
No. The PirateBox is designed to facilitate communication and sharing between friends and local community members.
Who helps build the PirateBox?
The PirateBox was created by David Darts and the lead developer is Matthias Strubel. Aaron Williamson from the Software Freedom Law Center provided advice on the project and Christiane Ruetten originally ported PirateBox to OpenWrt. The project is actively supported by developers and testers all over the world.
Do you know of any other projects similar to PirateBox?
Yes, check out Aram Bartholl's fantastic Dead Drops. There are also several forks of the project, including Jason Griffey’s LibraryBox, the Bibliobox, the LibroBox and the CoWBox (CoWorking Box).
Where can I discuss the PirateBox?
Visit the PirateBox Forum to discuss the PirateBox, share your builds, and receive support.
> PirateBox runs on multiple devices, including wireless routers, Android-based phones, single-board computers like the Raspberry Pi, and even laptops.
That's a little confusing. So it is a device or an app? Or is it just saying that you can connect to it from all of those devices?
it is just a open wifi LAN with a single AP node?
what am i missing here? this seems utter pointless if i understood that correctly.
Crazy? Actually, I have it on good report that the chairman of pathology at the Mayo Clinic just bought all the pathologists Magnifi adapters to do exactly that (the exact words were "Hey, Mayo's chairman just bought all the pathologists adapters, just like yours, to facetime consults to each other).
Presumably, the chairman at Mayo has more clout than a resident at a military hospital though. If I want to introduce innovation, it's going to have to be on my own, provably separate from the institution. So this is perfect for my use case.
B) Even if you used some sort of video app that worked on the Piratebox, discussing PHI/PII over an open unencrypted WIFI network would violate all kinds of HIPAA regulations.
C) The IT Department is there for a reason, stop trying to break security protocols. Especially when you are Department of Defense.
D) This thing isn't actually secure/private like it says it is. They said there are no logins. And your MAC address is still associated to a device. Even if you spoofed it, you still have to be 30 ft near the thing. Not hard to hide.
unless this evolves to a mesh it is just a hyped AP
Where did another floor come in?
my router already does all that. and it was before i flashed openwrt on it.
That said, with a unique 'box' identifier and a simple store and forward protocol you could have them link together into a simple network, where you could pass messages or files with addresses like box1!box2!box3!userhandle :-)
I've heard of people doing this to scare the crap out of their low-key criminal neighbours.
That's called Source Routing, and is what cjdns  does, although in a more federated and private manner. There's an OpenWRT firmware called meshbox  that works on the same devices as PirateBox (and more).
There's no apps shipped with it, but instead you get a secure, adhoc, near-zeroconf mesh network.
Even ISPs (those who care) have issues ensuring that there would be enough bandwidth for peers to watch their videos and low enough latency to play their games. Especially it's tricky to balance ingress trafic when there are multiple paths to you (your ISP has many peers), but one pipe's clogged and one's nearly unused (and situation changes all the time, so next day - or sometimes even hour - it could be the opposite).
and each city would be disconnected from the next big city, as there is no realistic way to span that amount of space in between for hobbyists.
but it would be great, despite these limitations. governments would no longer be able to kill all communication... until they adapted anyway. nothing easier than spamming these networks with useless entries to hide the actually worthwhile ones
> What is the PirateBox?
> PirateBox is a self-contained mobile communication and file sharing device. Simply turn it on to transform any space into a free and open communications and file sharing network. Inspired by pirate radio and the free culture movements, PirateBox utilizes Free, Libre and Open Source software (FLOSS) to create mobile wireless communications and file sharing networks where users can anonymously chat and share images, video, audio, documents, and other digital content.
> How does it work?
> Simply turn PirateBox on to transform any space into an offline communication and wireless file sharing network. When users join the PirateBox wireless network and open a web browser, they are automatically redirected to the PirateBox welcome page. Users can then immediately begin to chat anonymously, post images or comments on the bulletin board, watch or listen to streaming media, or upload and download files.
My main feedback is that the page does nothing to tell new users what the heck is PirateBox. The landing page should contain an explanation of what it is and why do you want it.
I built a piratebox using a cheapo tplink router about 2 1/2 years ago. I'm somewhat surprised nothing has been built using commodity Android phones since then. They'd be better suited to the task as far as having a battery built in, better antennas, etc.
Can it actually run this way? Do they actually have a portable way of powering this device?
Before you downvote me: from a legal POV, this is the same as leaving your WiFi open or protected with WEP. In front of a court you will be either held liable for just aiding distribution of child porn/warez (if you're lucky), or worse, for possession. In Germany this definitely means time behind bars, in the US it means federal court for child porn/aiding a drug business. Good luck getting out of this.
You would not even remotely consider leaving your WiFi open, right? Then, why do you consider putting up a PirateBox or whatever it is named for public use?
A car battery is fast and easy to charge. I would guess a car battery would last 20 to 80 hours, depending on the the battery, the router, and the usage.
Alternatively most cigarette-lighter USB chargers can take under-voltage so you can easily hook up a LiIon laptop battery (nominally 10.8 Volts). Laptop batteries are great because they come with a laptop that can charge them very quickly.
A car battery gives you the option to use many other routers (maybe you have a suitable one lying around!). Routers often use a 12 Volt DC input, and although a direct connection between the battery and the device is theoretically the wrong voltage, in practice I myself would just connect it straight through without any qualms (unless it was an expensive or rare router!). The WR703N probably uses less power so would run longer, but maybe compromises on range?!
I linked and described my observed runtime here: http://piratebox.aod-rpg.de/dokuwiki/doku.php/about/matthias
We summarized all the sources here: https://github.com/orgs/PirateBox-Dev
When the page is working in normal parameters again, we'll put a link the sourcecode to the page.
We are sorry about the inconvenience.
1. First download a copy of install_piratebox.zip and a customized
copy of OpenWrt for the MR3020, WR702N or MR3040 to your computer
from: http://stable.openwrt.piratebox.de/auto (be sure to download
the “*squashfs-factory.bin” file that corresponds with your specific
Using OpenWrt and off-the-shelf hardware, you can build a PirateBox
1.0 for as little as US$35. Check out the OpenWrt DIY page for more
info and visit the OpenWrt Discussion Board for support.
They should take a look at mod_pagespeed (https://developers.google.com/speed/pagespeed/module) and start using a CDN.
The issue was the cpu power. The VPS hadn't got enough cpu time for fullfilling all these requests. The machine reportet 8 cores, but load didn't cross the 4 - mark.
Memory is 4GB, but that was more then enough.
On the top list you were able to clearly verify the php processes running and trying to fullfill the request.
We swapped to my provider http://net-build.net , which has a good performance.
thanks for the hint anyway. I think David already exchanged it.
~$ ping -c1 piratebox.cc
PING piratebox.cc (220.127.116.11): 56 data bytes
64 bytes from 18.104.22.168: icmp_seq=0 ttl=49 time=96.722 ms
--- piratebox.cc ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 96.722/96.722/96.722/0.000 ms
~$ nslookup 22.214.171.124
127.103.111.64.in-addr.arpa name = ps43705.dreamhost.com.
Authoritative answers can be found from:
103.111.64.in-addr.arpa nameserver = ns3.dreamhost.com.
103.111.64.in-addr.arpa nameserver = ns1.dreamhost.com.
103.111.64.in-addr.arpa nameserver = ns2.dreamhost.com.
ns1.dreamhost.com internet address = 126.96.36.199
ns2.dreamhost.com internet address = 188.8.131.52
ns3.dreamhost.com internet address = 184.108.40.206
$ whois 220.127.116.11 # Note: IP!=same, similar is ok
NetRange: 18.104.22.168 - 22.214.171.124
NetType: Direct Allocation
The above shows us that the IP address range has been owned by Dreamhost since 2005.
$ traceroute -M16 126.96.36.199 # Note: Hides first 15 hops
traceroute to 188.8.131.52 (184.108.40.206), 64 hops max, 52 byte packets
16 te0-0-2-0.nr11.b037327-0.iad02.atlas.cogentco.com (220.127.116.11) 150.006 ms 112.416 ms 111.521 ms
17 18.104.22.168 (22.214.171.124) 110.817 ms 111.131 ms 113.563 ms
18 ip-208-113-156-8.dreamhost.com (126.96.36.199) 122.604 ms 119.393 ms 120.720 ms
19 ip-208-113-156-14.dreamhost.com (188.8.131.52) 118.675 ms 116.344 ms 116.236 ms
20 ps43497.dreamhost.com (184.108.40.206) 165.690 ms 111.885 ms 119.339 ms
This shows you the carrier in use leading to the facility (cogentco).
Often facilities without reverse DNS (apparently in the final hop) or without own IP ranges (as we discovered above Dreamhost has) can still be determined without actually passing traffic by reading the reverse DNS information on the closest border hop on their carrier. In this case we don't get lucky with that technique, since #17 is not showing any reverse DNS.
Beyond the above you can start looking at AS-driven routing records, physical network layouts, internet historical information, etc. before resorting to more active probes.
HARD MODE: Is is actually 'hiding' those hops, or does it not even look for them?
Using Apple's `traceroute.c`:
case 'M': /* FreeBSD compat. */
first_ttl = str2val(optarg, "first ttl", 1, 255);
Note: For those not in the know, traceroute works by adjusting the TTL (time-to-live) value on the packet it sends out. The TTL is basically the max number of hops that the packet can take. Each 'hop' decrements the TTL value, until it reaches the destination or TTL == 0. If the TTL == 0 before it gets to the destination, then the packet it sent back as rejected.
In terms of comprehension for the record I would recommend instead of the source the explanation at Wikipedia: https://en.wikipedia.org/wiki/Traceroute
For awhile it used to be that people would write their own traceroute implementation as a rite of passage.
As a joke, back in the 1990s, Julian Assange took it one step further and used to spoof responses to traceroutes in order send a fake route back to the querying node, indicating that his systems were somehow affiliated with important government or military entities. Excellent sense of humor :)