On Tue, 14 Feb 2012, douglastskill...@lavabit.com wrote:
I am experiencing a strange problem for about two weeks or so.
1 0.00192.168.178.30 127.0.0.1 DNS Standard query
A torproject.org
2 0.27192.168.178.30 127.0.0.1 DNS Standard query
On Tue, 14 Feb 2012, douglastskill...@lavabit.com wrote:
I am experiencing a strange problem for about two weeks or so.
10.00192.168.178.30 127.0.0.1 DNS Standard query
A torproject.org
20.27192.168.178.30 127.0.0.1 DNS Standard query
Hi Jérémy,
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
MASQUERADE tcp -- 192.168.179.0/24!192.168.179.0/24masq
ports:
1024-65535
MASQUERADE udp -- 192.168.179.0/24!192.168.179.0/24masq
ports:
1024-65535
MASQUERADE all --
I am incredibly sorry that my posts do not reference the right
Message-ID's. This seems to be a bug in the webmail interface I am using.
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
MASQUERADE tcp -- 192.168.179.0/24!192.168.179.0/24masq
On Tue, Feb 14, 2012 at 02:43:44AM -0500, douglastskill...@lavabit.com wrote:
1 0.00192.168.178.30 127.0.0.1 DNS Standard query
A torproject.org
2 0.27192.168.178.30 127.0.0.1 DNS Standard query
torproject.org
3 0.000155
On Tue, Feb 14, 2012 at 10:50:01AM +0100, Alexander Schrijver wrote:
The IP you're sending to and the IP you're receiving form don't match. The
glibc stub resolver probably trashes these.
Actually, the UDP datagram probably never gets received by the stub resolver,
the OS trashes it since no
On Tue, Feb 14, 2012 at 02:43:44AM -0500, douglastskill...@lavabit.com
wrote:
1 0.00192.168.178.30 127.0.0.1 DNS Standard
query A torproject.org
2 0.27192.168.178.30 127.0.0.1 DNS Standard
query torproject.org
3 0.000155
Arg, I am not even sure whether glibc is the problem. A minimal sample
application that performs lookups performs just fine.
#include string.h
#include stdio.h
#include sys/types.h
#include sys/socket.h
#include
On 2012-02-14, douglastskill...@lavabit.com
douglastskill...@lavabit.com wrote:
Hello List,
I am experiencing a strange problem for about two weeks or so.
I am using GNU/Liux (Debian 6 x86-64) and Tor 0.2.2.35 built from source.
I forward all my tcp traffic and udp traffic on port 53 to my
Arg, I am not even sure whether glibc is the problem. A minimal sample
application that performs lookups performs just fine.
[...]
Here are two strace logs, one with a working lookup and one with a failed
one.
Oops, forgot the links:
success: http://pastebin.com/waa4fgPG
fail:
On 2012-02-14, douglastskill...@lavabit.com
douglastskill...@lavabit.com wrote:
Hello List,
I am experiencing a strange problem for about two weeks or so.
I am using GNU/Liux (Debian 6 x86-64) and Tor 0.2.2.35 built from
source.
I forward all my tcp traffic and udp traffic on port 53 to
On Tue, Feb 14, 2012 at 05:34:55PM -0500, douglastskill...@lavabit.com wrote:
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
MASQUERADE tcp -- 192.168.179.0/24!192.168.179.0/24masq ports:
1024-65535
MASQUERADE udp -- 192.168.179.0/24
12 matches
Mail list logo