Tor will bind to one inside address hung on a firewall leg. Portforward ingress traffic hitting the entire public range to the inside ToR host and pool nat egress traffic.
http://forum.pfsense.org/index.php/topic,8929.0.html http://www.openbsd.org/faq/pf/pools.html No guarantee that it'll work. But it should generate traffic over the entire assigned block. Greg -----Original Message----- From: Eugen Leitl [mailto:eu...@leitl.org] Sent: 11 March 2010 4:26 PM To: discussion@pfsense.com Subject: Re: [pfSense-discussion] filling network with meaningful traffic On Thu, Mar 11, 2010 at 04:20:32PM +0000, Greg Hennessy wrote: > tor natted behind an address pool should do the trick. Hmm, Tor typically binds to one address though. How can I make it spread traffic across a network? I could 1:1 NAT a /24 to an internal /24 network, check. But I still would have to run a very large number of Tor instances throttled behind that, which would overwhelm my current hardware resources. This is probably not what you had in mind. Can you explain a bit more please? Thanks. > Greg > > > ________________________________________ > From: Eugen Leitl [eu...@leitl.org] > Sent: 11 March 2010 16:17 > To: discussion@pfsense.com > Subject: [pfSense-discussion] filling network with meaningful traffic > > I've just got a bit of an ultimatum from my hoster, as my newly assigned > networks don't have traffic yet, and I would have to give them back > unless the situation changes asap. > > I wouldn't have issues to make all the addresse pingable and > produce some light bogus traffic, but there should a way to make it more > meaningful/constructive. > > Have you got any suggestions how to fill up some three /24er > quickly and putting to good use? Ok, I could run Tor servers and > rotate them through the address space daily, or so. I could host > mirrors of something and spread the traffic by round robin DNS. > I'd rather not burn more than a TByte or two traffic/month right now, > though. > > Any other suggestions? > > -- > Eugen* Leitl <a href="http://leitl.org";>leitl</a> http://leitl.org > ______________________________________________________________ > ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org > 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE > > --------------------------------------------------------------------- > To unsubscribe, e-mail: discussion-unsubscr...@pfsense.com > For additional commands, e-mail: discussion-h...@pfsense.com > > Commercial support available - https://portal.pfsense.org > --------------------------------------------------------------------- > To unsubscribe, e-mail: discussion-unsubscr...@pfsense.com > For additional commands, e-mail: discussion-h...@pfsense.com > > Commercial support available - https://portal.pfsense.org -- Eugen* Leitl <a href="http://leitl.org";>leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE --------------------------------------------------------------------- To unsubscribe, e-mail: discussion-unsubscr...@pfsense.com For additional commands, e-mail: discussion-h...@pfsense.com Commercial support available - https://portal.pfsense.org --------------------------------------------------------------------- To unsubscribe, e-mail: discussion-unsubscr...@pfsense.com For additional commands, e-mail: discussion-h...@pfsense.com Commercial support available - https://portal.pfsense.org
