ichilton

I really like the Unifi - i've run it for a while and not had a single problem.

I do have a big gripe though - it has a hard wired limit of 4x SSIDs for each access point.

I run a number of VLANs, each with their own SSID - and it means I can only have the Unifi provide my main ones and have to run an old Netgear router on different wifi channels to provide the rest :(

I've never quite understood why my cheap routers running OpenWRT can seemingly have unlimited (or at least a lot of) SSIDs, where an expensive Unifi will only provide 4.

It sounds more like a new product, new direction than Vagrant 2.0....

The hn code doesn't seem to work?

Nifty - useful for quick testing tasks.

The concerns though are the sustainability - if instances are paid for and not free tier + bandwidth, it could not be around for long, particularly if it gets abused.

Also, privacy/security - there is no guarantee that instances are destroyed/erased after use and won't get assigned to someone else or logged into. Probably don't want to put private code/IPR on there just in case.

For quick commands (eg, testing a firewall setup from the outside or checking something from an external ip) then it's very cool indeed.

What's he using to benchmark that? - anyone know?

What's the best benchmark tool for drives and/or network shares?

Is there anywhere to register to receive more information on your book when you get nearer?

Does anyone know technically how LXC compares to OpenVZ?

I would think he meant what you said.... symlinks in the repo doesn't sound a good idea.

I always ran Ubuntu for Desktops and Debian (stable) on servers, but lately i've used Ubuntu for some servers simply because the packages are more up-to-date...

If you don't run ssh on port 22, it's been proved that it receives a lot less outside login attempts and stops the logs filling up with login failures apart from anything else.

It's good practise first login as another user and then gain root priv's. This is auditable and if your sshd won't allow root login's, the can't be brute forced directly.

Is there any performance impact of having so many rules?

I've seen a number of conference organisers complain of this so it must happen often!

I hope he securely erased the data rather than just deleting it, otherwise it might not be just the FBI who have potentially got a copy...

Thanks - i'll look into this

The problem with Google Analytics is that I need the data to be tied to the user_id of the logged in user.

Yes, I use this but the problem is still that if you fire large amounts of traffic at it then you get a lot of these building up and still create a bottleneck.

This is something I considered but i'm unsure of the best way to store these so they are retrievable without looking up the key.

I tried that but didn't get any replies at all....

I'm probably looking at up to a few hundred req/sec.

Thanks for the advice.