| ||||||||
RefBan
Monday, December 10, 2012
Top Stories from the last 24 hours
Turn Your FreeNAS Box Into the Ultimate Anonymous Downloading Machine
December 10th, 2012Top StoryTurn Your FreeNAS Box Into the Ultimate Anonymous Downloading MachineBy Whitson Gordon
We've shown you how to turn an old computer into a networked backup, streaming, and torrenting machine with FreeNAS, and even gone a little further and installed some Usenet and media management programs on it. But even with all that power, our downloading machine is missing a few things. Namely:
In this guide, we'll show you how to add both of these features, turning your home server into the ultimate anonymous downloading machine. Note: If you're just starting out, we recommend checking out our other FreeNAS guides first. Our original guide will show you how to set up FreeNAS 7, while our second guide will show you how to install programs manually, using Usenet as an example. Keep in mind that, while we're still referring to it as FreeNAS to keep some consistency with earlier guides, these guides use the FreeNAS 7 project, now known as NAS4Free, instead of the more current FreeNAS 8 (which we won't be using). This guide should work whether you have an old FreeNAS 7 box or a new NAS4Free box—they're essentially the same piece of software. Set Up a VPN for Anonymous DownloadingWe've said it once, and we'll say it again: the only way to stay anonymous is by using a proxy or VPN service. Yes, it costs money—usually around $10 a month or so—but these days, you shouldn't download without one. Unfortunately, FreeNAS doesn't come with a VPN, so you'll need to do it from scratch. Luckily, that isn't too hard—you just need to find a VPN service that works for you. What You Should Look For in a VPNThere are a lot of great VPN services out there, and everyone has different needs, so you'll want to find one that works for you. Here are the features you may need to look for:
For this guide, we'll be using a VPN service called Mullvad as an example, but I highly recommend you research other VPN services that fit your specific needs. Everyone is different, and what VPN you choose will be based on how you're using your NAS and what kind or privacy features or services you want. Photo by Pavel Ignatov (Shutterstock). Step One: Set Up a Jail for Installing New ProgramsWe'll need to install OpenVPN from the FreeBSD command line, just like we did with SABnzbd and Sick Beard in our previous guide. Before you do so, you'll need to set up a "jail" on your system, which allows you to install programs on one of your NAS' drives (since our FreeNAS installation resides on a flash drive). If you followed our guide to setting up SABnzbd and Sick Beard, you can skip this step and move on to step two of this guide, since you've already done all of this. First, SSH into your NAS. Windows users should download PuTTY, and type in the IP address of your NAS on the main page. You'll want to log in as ssh -l root 192.168.0.10 Where Once you've logged in as cd /mnt/SEAGATE mkdir extensions cd extensions mkdir var mkdir usr mkdir tmp mount_unionfs -o w /mnt/SEAGATE/extensions/usr/ /usr/ umount -f /var mount_unionfs -o w /mnt/SEAGATE/extensions/var/ /var/ This puts your mount_unionfs -o w /mnt/Media/extensions/usr/ /usr/ When you're done, head to step two. Step Two: Install OpenVPNWe're going to use OpenVPN to connect to our VPN service. Assuming you're running the newest version of NAS4Free, which is based on FreeBSD 9, run the following commands: setenv PKG_TMPDIR /mnt/SEAGATE/extensions/tmp/ setenv PACKAGESITE "ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-current/Latest/" pkg_add -rv openvpn If you're using an older version of FreeNAS, check what version of FreeBSD it's based on from the home page of the Web interface. Chances are, it's FreeBSD 7.3, in which case you'll want to install OpenVPN with the following commands instead: setenv PKG_TMPDIR /mnt/SEAGATE/extensions/tmp/ setenv PACKAGESITE "http://ftp6.us.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-7.3-release/Latest/" pkg_add -rv openvpn Everyone's NAS may be a little bit different, so make sure you're installing the correct package for your NAS' software. You'll also want to replace Step Three: Set Up OpenVPN with Your VPN Service
client dev tun proto udp remote openvpn.mullvad.net 1194 resolv-retry infinite nobind persist-key persist-tun ca master.mullvad.net.crt cert mullvad.crt key mullvad.key remote-cert-tls server comp-lzo verb 3 ping-restart 120 ping 10 Usually it'll have some instructions inside, too, so you know what each setting does. Most of the defaults should be fine, but if you have any trouble, try some of the above settings and see if they work (obviously using your VPN's server under When you're done, SSH back into your NAS and run the following command: mkdir /mnt/SEAGATE/extensions/usr/local/etc/openvpn
Lastly, open up your NAS' web interface and head to System > Advanced > rc.conf and add the following variables:
Once you've saved those variables, continue to the next step to try running OpenVPN for the first time. Step Four: Start OpenVPNOnce all your config files are in place and your ports are forwarded, it's time to try running OpenVPN for the first time. Open up your NAS' web interface and go to Advanced > Command. Type the following command into the "Command" box and press Execute: /usr/local/etc/rc.d/openvpn start /usr/local/etc/openvpn/openvpn.conf
If it didn't work, you may need to change some settings in your config file. Look for any errors you see in your log and try it again. If OpenVPN is running but you can't connect, you'll need to go to Advanced > Command and run This is the hardest part of the process, and troubleshooting the problem is different for everyone depending on your VPN service and the other things you have running on your NAS. Don't give up, and make sure to follow all the instructions to the letter to get everything working. If you're using BitTorrent, now would be a good time to check your torrent client's IP using CheckMyTorrentIP.com, as described in step three of our BitTorrent anonymization guide. If you get your VPN's IP, then you've successfully set up an anonymous downloading NAS! Step Five: Set Up Your FirewallThe last thing you should do, once your VPN is up and running, is set up a firewall on your NAS that blocks all traffic except your VPN connection. That way, if your VPN goes down, your NAS won't fall back on your regular connection, which can expose your actual IP and destroy any anonymity you may have had. In your NAS' web interface, go to Network > Firewall. Everyone's firewall may be a bit different, but here's a template you can use to create your rules: Click on the image for a closer look. Going number by number in the image, here's what each set of rules does:
Again, your firewall may differ a bit, but this is a good place to start. Click the Plus sign to add each individual rule, and when you're done, check the Enable box and click "Save and Restart" in the bottom left corner. Head back to your SSH window and try to Once everything's working properly, give yourself a pat on the back, because you've now anonymized all the traffic coming in and out of your NAS! It's not an easy process, especially because it's a little different for everyone, but it can be done—it just takes a little patience and a little knowledge about how all everything works. Monitor Your Downloads From Afar with Dynamic DNSSo you've got yourself a kickass downloading machine, but what happens when you're out and about and come across a file you'd like to download? Or maybe you want to check in on your server and see what TV shows you've downloaded or ripped to your home theater PC? By default, you can't access your NAS from outside your home network, but all it takes is a few tweaks to make this possible. Then you can monitor downloads, start new ones, and check in with your NAS from your laptop, phone, or even someone else's computer while on-the-go. Step One: Sign Up for a Dynamic DNS ServiceWe've talked about how to do this before, and the process is pretty similar with your NAS. To start, you'll want to sign up for a service like DynDNS or No IP, which will give your home network an easy-to-remember domain name like Before you sign up, check your router's admin page to see which services your router supports. Mine only supports DynDNS, for example, so that was the one I had to use. Other routers may support different services, so check the Dynamic DNS settings of your router for more info. Step Two: Set Up Dynamic DNS on Your Router and NAS
Next, do the same thing on your NAS. Open up your NAS' web interface and go to Services > Dynamic DNS. Pick your provider, type in your domain name and credentials, then check the Enable box in the upper-right corner. Click the Save and Restart button to start the service. Step Three: Forward Any Necessary PortsLastly, you'll probably need to forward a few ports on your router so your NAS is accessible from the outside world. Once again, we've talked about this before, so check our guide to port forwarding if this is the first time you've done it.
You'll also need to set up port forwarding from your VPN service's web site. Otherwise, your VPN won't know who you are when you try to connect from the outside world (since a number of other users are using the same VPN as you). Head to your VPN's home page, log in, and look for the section on port forwarding. (If you're using Mullvad, it's on the main page after you log in). Click the New button to add a new port. Your VPN service decides how many you're allowed to have; many limit you to just a few so you don't hoard them from other users.
Step Four: Try Accessing Your NAS From ElsewhereLastly, just try to access one of your web interfaces using your new hostname. For example, if your hostname is http://myawesomenas.dynalias.org:12345/transmission/web/ Again, repeat this process for any other services you have running, like SABnzbd or Sick Beard. If everything works, then congratulations! Now you can monitor your downloads, add new downloads, and otherwise keep track of your NAS from anywhere on any device. It isn't a simple process, and it can be a little different for everyone, but all the setup is well worth it. When you're done, you'll have a quiet, low-power machine that stays on 24/7 and downloads all your files for you, completely anonymously, with easy access from wherever you are. If you run into any problems during setup, be sure to check out the NAS4Free forums, the OpenVPN forums, the FreeBSD forums, or right here in the comments of this post. Good luck!  |
|
The Good And Bad of Battlefield 3, One Year (Or So) Later
December 10th, 2012Top StoryThe Good And Bad of Battlefield 3, One Year (Or So) LaterBy by David Veselka
More than a year after the release, after more than a year of patches, updates, rule-changes and several massive expansions, how has Battlefield 3 held up? Battlefield 3 was built to last. 14 months into it and only now are we seeing the emergence of Aftermath, Battlefield 3's fourth expansion pack, with a fifth still on the way in March. Bearing this in mind, it might still be too early to peek into the looking glass and speculate the future of the Battlefield franchise. But having passed the one-year mark, perhaps a bit of debriefing is in order. How has DICE's approach to this generation of AAA shooters fared so far? What has worked and what has not? How does their idea of post-launch support rate? Is their Premium service really all that "premium?" It's tough for a first-person shooter to produce multiplayer expansions in the real sense of the word. Realistically, the only type of content that can be 'added,' in this case, is perhaps a set of new maps/locations, weapons or customization options. Compare this to single player-based DLC that can not only deliver all of the above, but also chapters of new story content, new characters, and/or new gameplay elements. I find that the Call of Duty series in particular struggles with this. Personally, I have a harder time coughing up dough for something like Modern Warfare 3's ELITE Premium subscription when all I'm really getting in return are new maps. Otherwise, it's the same experience over and over again. That's why I know I will be throwing down cash upfront for Battlefield 4's Premium service without a second thought and why Call of Duty is going to have to step its game up in order to earn my investment. DICE's approach to DLC , which has all been wrapped together in one neat package called Battlefield 3 Premium, differs in that each new piece of content has introduced the player to a new experience and has truly expanded the base product. Take, for example, the contrasting Close Quarters and Armored Kill themed expansion packs: One built on action-packed, fast-paced gameplay set in tight, claustrophobic environments versus the slower, more grandiose vehicle-based warfare taking place in wide-open and breathtaking landscapes. The former, released last June, certainly posed a risk for the team, as many considered its speedy, arcade-like nature untrue to the spirit of Battlefield. But the reason why it worked—and the reason why I believe it's worth the price—is that it was (and still is) an experience which cannot be found in the standard Battlefield 3 package. It plays different, it feels different, and it keeps things fresh. Similarly, Armored Kill, released last September, gave "true" Battlefield fans what they always wanted: Insane, all-out vehicle warfare—something many felt was lacking in Battlefield 3 standard. While it didn't quite gel with the consoles' limited player count due to its large map sizes, PC players certainly felt right at home. With both Close Quarters and Armored Kill, I feel DICE struck a nice balance catering to both the dedicated, hardcore Battlefield audience and those just wanting to shoot people in the face. The latest add-on, Aftermath, plays similar to the throwback expansion Back to Karkand, released back in December, 2011. It features similar urban war zones with a good mix of infantry and vehicle combat. But at the same time, it literally "shakes" things up with the concept of fighting and surviving in a post-earthquake environment. The new Crossbow (or XBow) for example, adds new gameplay elements while the deformed terrain creates a battlefield you might not be used to. That's why I know I will be throwing down cash upfront for Battlefield 4's Premium service without a second thought and why Call of Duty is going to have to step its game up in order to earn my investment. DICE has shown that they're not here to cough up more of the same and call it DLC. With their own distinct theme and feel, all of Battlefield 3's current add-ons have literally expanded the experience with new ways to play. I expect nothing but the same for End Game. Later in Battlefield 3's life cycle, DICE granted players on both the Xbox 360 or PlayStation 3 the ability to rent and customize their very own servers—a first for a console FPS. Players then not only had the choice of entering standard DICE-run servers, but a wide range of player-run servers as well. As an unfortunate side-effect, this spread the butter too thin, so to speak, and led to under-populated servers while rendering the matchmaking experience much more complicated than it should have been. "Quick Match" would no longer always send you along your way to a server featuring a playlist of your chosen game mode. Feeling in the mood for some Conquest? Sure, "Quick Match" might stick you in a nice game of flag-capping goodness on a player-run server, let's say. What it doesn't know, however, is that the next map in the rotation is customized to run a game of Team Deathmatch. Probably not what you were looking for. The problem is that a lot of newcomers don't even know what they are looking for. They just want to get in on the action in a predictable manner. The problem is that a lot of newcomers don't even know what they are looking for. They just want to get in on the action in a predictable manner. I shouldn't have to explain how find a 'normal' playlist and avoid any wonky or bizarre game settings to a friend who has picked up Battlefield 3 some time after the introduction of rentable servers. Likewise, no newcomer should have to unknowingly fall victim to abusive administrators who create their own, sometimes-absurd rules. What irks me is that rules like "no shotguns," "no explosives," or "knives-only" are enforced by the server admin only, not by the built-in game settings, as there are no actual options to restrict weapons or equipment. Because many of these "special" servers are public, anyone could be thrown into one at any moment and not everyone who's paid $60 USD for a game appreciates being subjected to someone telling them that they can't even use half their arsenal. What's worse are admins who kick you for either "playing like a noob" or for simply being "too good." While I would hope that this sort of feature would stick around for future Battlefield titles on consoles, I believe some fine-tuning is in order to streamline the process and keep the community playing together, rather than having everyone off doing their own thing. I also think abnormal server "rules" should be kept strictly private and not public. "Pistol-only" matches can indeed be fun, but not if you aren't looking for one. While this mostly only applies to the console audience, and perhaps the more casual audience, it is their larger audience in the end. That leaves something to be said for the PC side of life, where the Battlefield series found its original home. If there is one thing DICE could have done to have kept Battlefield 3's life span healthy and constantly rejuvenated, it would have been to allow PC mod tools. Look at what happened to Bohemia Interactive's Arma 2. We got the Day Z zombie mod, soon to be its own standalone title. Bethesda's The Elder Scrolls V: Skyrim has also been turning heads with its beautiful texture mods. It's not even a multiplayer game and yet there is a healthy community of modders constantly finding ways to make an already content-rich game even beefier. I think we could see some pretty amazing things coming from a community of dedicated Battlefield modders, should DICE be able to work past the technical issues and complexities of the Frostbite 2 engine in order to allow it. At the present moment, Battlefield 3 is a very different game than it was back in October of 2011. It raises the question, however, "was Battlefield 3 even finished when it shipped?" Being the first Battlefield title powered by the brand new Frostbite 2 engine, developers clearly had a hard time covering up the number of bugs that came along with it. Nevertheless, it is without question that DICE has done a commendable job at supporting their product post-launch. One could even argue that Battlefield 3 would never have reached the stature it has today without the feedback of the millions of gamers that have had a chance to sink some serious time into it after launch. While the patching process may have been slow and cumbersome, and some particularly game-breaking issues were dealt with rather last-minute, patches were almost little pieces of DLC in themselves. Again, though support in general was top notch, perhaps smaller, more frequent patches would yield a happier community. Moving forward, into Battlefield 4, or whatever DICE may have in store for the future, I believe asking themselves the following questions would prove beneficial, if they haven't done so already:
Considering the amount of experimentation that went on over the past 14 months—new DLC model, new engine, the Battlelog, bigger audience, etc.—it will be interesting to see how DICE acts upon their findings and where the battlefield takes them in the future. Until then, you know how the saying goes: "See you on the battlefield." David Veselka spends his time running and managing multiplayer-centric gaming website MP1st.com and loves him some online FPS action. You can say hi to him on Twitter by following @N7Veselka.  |
|
Unemployment Stories, Vol. 19: 'This Shit Is Real and Humbling'
December 10th, 2012Top StoryUnemployment Stories, Vol. 19: 'This Shit Is Real and Humbling'By Hamilton Nolan
The dispatcher
Circling the drain
Powerless
Lowered standards
All my fault
Previously [Thanks to everyone who wrote in. You can send your own unemployment story here.]  |
|
![The Kitten All of Hollywood Is Trying to Date: Who Is Demi Moore's Mystery Cat? [UPDATE: Nicky Hilton Kidnapped It]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_sJzu913seRNTLhTOQMjXP7s_bvj9ihzXPMwKNdlxUX-pOx3sH89G4USeWu7lC7W7D5e-qRPpbgT_snRyReMu_D0gPJWOnU6L_OsBK2AsXU-4f0k3OS2u5bWzrJ7uL8=s0-d "The Kitten All of Hollywood Is Trying to Date: Who Is Demi Moore's Mystery Cat? [UPDATE: Nicky Hilton Kidnapped It]")
Subscribe to:
Posts (Atom)