[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Best Hardware for TOR server..
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Best Hardware for TOR server..
- From: "F. Fox" <kitsune.or@xxxxxxxxx>
- Date: Fri, 14 Dec 2007 17:20:08 -0800
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Fri, 14 Dec 2007 20:20:21 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; bh=fINCp4QliIVi6R7bpR4wxPOKWjGLy8VBcisoPc78Ojg=; b=oBrub1UA8TXgzc8bNBVBeixPKyuDRqFdiRxjieE3vszFNkbanP34gpeX01u0JTLqqhLkDC5P7cs8MQ8hZ0hwLPuI6mdhxhpngBKh3KjBCX0YXsuznwumczbReixfH1G539U21cJAaUJozgbYm4w4Ya0YiEZqsWGvmXxgIIoR02E=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=OMsOkpbt5HM5o/Y1M0c5U+2EgLH9gW+aZsF7L7OdpCtaQjhYXbonHScuWw2AcMKlyujGkfkyBZT6Jxiw4jx1fFm2s3xsoVZesJ9zllM6rTQmpWuVFbnHf3qpkH7vy7HesY5hWosF3s9b0aUwMzo5q7bbiOqu2/erR2mxe7gsbdQ=
- In-reply-to: <200712131015.lBDAFKEi002846@xxxxxxxxxxxxx>
- References: <200712131015.lBDAFKEi002846@xxxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
- User-agent: Thunderbird 2.0.0.9 (Windows/20071031)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Scott Bennett wrote:
> On Thu, 13 Dec 2007 08:31:43 +0100 Eugen Leitl <eugen@xxxxxxxxx>
> wrote:
>> On Wed, Dec 12, 2007 at 10:44:17PM -0800, algenon flower wrote:
>>
(snip)
>>
>>> behind a Linksys Firewall Router.
>> Make sure this is not your weak spot. OpenWRT is a good firmware here.
>> In general, it is always a good idea to buy a WRAP or ALIX (or its
>> Soekris equivalent) piece of kit, and flash it with a decent firewall,
>> like m0n0wall or pfSense.
>
> I've had problems with every Linksys router I've dealt with so far,
> but mainly with wireless service. The built-in DHCP server, when presented
> with a request from a machine to which it has already issued a lease, fails
> to recognize that that machine is a current leaseholder and to issue it a
> copy of the existing lease. Instead, it denies the request. This is a
> worse problem for Windows than for FreeBSD in that Windows is far more
> likely to decide it has lost contact with a Linksys wireless router than
> FreeBSD is.
(snip)
My Linksys router is a wireless one - albeit with a custom firmware.
However, the machine running "kitsune" is hard-wired to its Ethernet
switches; I'd never run a service over a wireless link. IMHO, it's far
too flaky.
(Regardless, the WLAN is - of course - running WPA2-PSK/AES with a
63-character pseudorandom key, for my own piece-of-mind...)
>>> **Comcast always adds their own modem, I am wondering if the usual
>
> Not necessarily so. We saved a small amount per month by providing
> a modem and router ourselves. Comcast's equipment was returned to them, and
> they stopped billing for it.
(snip)
Good point - I bought a modem outright, and I no longer pay a rental fee
(I've owned the router from day one). Well worth the investment, IMHO -
it'll pay for itself within a year, under many plans.
- --
F. Fox: A+, Network+, Security+
Owner of Tor node "kitsune"
http://fenrisfox.livejournal.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHYyvIbgkxCAzYBCMRAl9BAJ0W5AODjCblxidTSmvE/CqgpqUcbACfQNon
hBLH9yM+XOq16euR+e2GglA=
=GYO7
-----END PGP SIGNATURE-----