[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Tor and iptables

To: or-talk@xxxxxxxxxxxxx
Subject: Re: Tor and iptables
From: Peter Palfrader <peter@xxxxxxxxxxxxx>
Date: Fri, 15 Sep 2006 15:17:14 +0200
Delivered-to: archiver@seul.org
Delivered-to: or-talk-outgoing@seul.org
Delivered-to: or-talk@seul.org
Delivery-date: Fri, 15 Sep 2006 09:17:25 -0400
In-reply-to: <450A877A.1090507@gabrix.ath.cx>
Mail-followup-to: or-talk@xxxxxxxxxxxxx
References: <450A877A.1090507@gabrix.ath.cx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Mutt/1.5.9i

On Fri, 15 Sep 2006, gabrix wrote:

> > Sep 15 09:43:58 argo kernel: ip_conntrack: table full, dropping packet.
> > Sep 15 09:43:58 argo kernel: ip_conntrack: table full, dropping packet.
> > Sep 15 09:43:58 argo kernel: ip_conntrack: table full, dropping packet.

.) cat /proc/sys/net/ipv4/netfilter/ip_conntrack_max
.) note number.  multiply by 2 or 4 or whatever seems like a good measure
.) echo $newnumber > /proc/sys/net/ipv4/netfilter/ip_conntrack_max

On my machines ip_conntrack_max is between 8 and 64k.  Something around
30k should be way enough.

References:
- Tor and iptables
  - From: gabrix

Prev by Author: Re: tor libevent1 dependencies problem
Next by Author: Re: TOR ON FREEBSD 6.1 "Could not bind to,127.0.0.1:9050: Can't assign requested address"
Previous by thread: Tor and iptables
Next by thread: Tor appliance
Index(es):
- Author
- Thread