I was going to do a big walkthrough to installing FreeNAS, but my apathy knows no bounds. Plus, google can tell you how to install it. I think you can install it falling over, actually.
- Download FreeNAS from http://sourceforge.net/projects/freenas/
- Burn CD - imgBurn or the like will be a-ok
- Pop into CD drive, set BIOS to boot from CD and reboot
- FreeNAS will boot, and run off the CD
- Youll want to install it to a HDD or CF card (you can get IDE -> CF card adaptors)
- I went for a Full install + swap. Swap is always fun. Keep in mind that booting the OS off your RAID (if you have a hardware RAID card) is a terrible idea. Grab either the IDE->CF card or a 40/80GB HDD and boot it off that.
- Once its installed (all what, 15 seconds?) remove the CD and reboot. This time it will be off the HDD
- Youll end up back at the same menu now. (It runs off the CD exactly the same, however you dont want it to run off the CD permantly - it wont perform all that well)
- Now press 1. and setup the network (It's likely it guessed all that for you, but configuring it cant hurt) Youll have to select which network device to use (you may well only have 1 so go nuts) Im not sure how its wireless support goes here - I would advise against it anyway.
- Once thats configured, press 2. Here you should select DHCP (unless you want to manually enter a IP address) and select no for IPv6. It will now give you a funky IP address.
- FIN
The steam special is insanity. Oh, and also FreeNAS is shown.
Youll want to set up your hard drives first before hand, obviously.
This post will leave you to play with the webui. Google is your friend here.
Stay tuned for:
- Transmission (Torrent client) blocklist
- Transmission RSS auto-downloader
- Transmission RSS auto-downloader email hack
- Custom script ive used for email status reports
- PS3 Media server setup (The pre-installed uPNP server is shite, sorry)
- Performance Tweaks?
Hi! Love your Nat's Tech Corner stuff on Freenas. For an old sometimes self-admitted tech Luddite like myself, your instructions are great. I installed Freenas 0.7.1 v5127 w/o a hitch, was up and running along with the transmission bittorrent client. Also did it for 3 other friends, and we all love it---especially for all our legal (cough, cough) torrent downloads and share repository. We did want to ask you something: we are all facing the same problem, and since we all live in different locations, with DD-WRT routers, regular Linksys routers, a Philips router, and a Netgear (we all use Comodo firewall on the pcs, and two of us also us a PFSense perimeter firewall. One of the things we notice with the Freenas transmission daemon client is it seems, no matter what we do with blocklists, to be easily attacked by the torrent fighters using Syn Flood, Smurfs, ICMP Redirects. These attacks eventually, for everyone of us, overwhelms our ADSL routers (all have firewalls) causing the every local network computer to lockup, except for the still running Freenas and its torrent client. We end up having to reboot once or twice or a day, but it is annoying. Are you noticing this? Any hints on the firewall inside Freenas (of course, we have the correct torrent port forwarded in Freenas and the routers)? What Freenas firewall settings can we use on the internal network stopping these "inbound/outbound from PPPoe1" attacks occurring? We know our network and any attached computer is secure because if we shut down Freenas, and run, say, utorrent from one of the computers (remember, it's behind Comodo and also the router(s) firewalls), the torrents run flawlessly and the perimiter and internal network sees none of these inbound/outbound smurf, ICMP redirects, SYN Flood attacks. Any advice and/or hints??
ReplyDeleteThanks again!!
Sorry for such a delay in a reply.
ReplyDeleteI had the exact same problem. Transmission seems to work differently than other Torrent clients! I used uTorrent for quite a while and it used to kill my router every 24 hours. However, when i swapped to FreeNAS, Transmission immediatly locked up my entire LAN except itself. When i had a look into my cheap and nasty router, I found its internal firewall was detecting torrent traffic as a SYN FLOOD. I think the upshot of it was the CPU of the router was working overtime trying to sort out the traffic and it locked up all other traffic.
The solutuon to me was to fork out a little (AU$190) on a half-decent router (Dlink DSL-2740B) - as soon as I swapped everything ran fine.
Unfortunatly, router firmware varies and some of the cheaper routers WONT let you disable some of their filters/features. Unfortunatly, sometimes if their firewall is a little too restrictive you can politely ask it to stop on the cheaper models.
While its strange that such a variety of routers would exhibit such behavior, what your describing exactly matches the problems i had.
The 'attacks' i found not to be attacks at all, just the firewall thinking Torrent traffic to be a attack. It seems to just be the way Transmission runs!