Bug#692025: linux: internet connection refused after new route

[Jonathan Nieder <jrnieder@gmail.com>]

Patrik Nilsson wrote:
> On 11/05/2012 02:59 AM, Jonathan Nieder wrote:
>> Patrik Nilsson wrote:

>>> No error messages or anything else is shown: The connection just doesn't
>>> work
[...]
>>                                            Also could you strace a
>> program that tries to connect and fails in this scenario, so we can
>> see what syscalls it makes and what response the kernel gives?
[...]
> 2012-11-11_134012 block/
> 2012-11-11_134012 block/traceiptablesdown.txt
> 2012-11-11_134012 block/traceiptablesup.txt
> 2012-11-11_134012 block/traceopenpvpn.txt
> 2012-11-11_134012 block/traceresolvconfup.txt
> 2012-11-11_134012 block/traceroutebefore.txt
> 2012-11-11_134123 pass/
> 2012-11-11_134123 pass/traceiptablesdown.txt
> 2012-11-11_134123 pass/traceiptablesup.txt
> 2012-11-11_134123 pass/traceopenpvpn.txt
> 2012-11-11_134123 pass/traceresolvconfup.txt
> 2012-11-11_134123 pass/traceroutebefore.txt
> account.txt
> down.sh
> ivacy-ca.crt
> ivacy-client.crt
> ivacy-client.key
> ivacy-client.ovpn
> ivacy-tls.key
> start.sh
> up.sh

Thanks.  I think you misunderstood, though: I meant that we need a
trace illustrating what it means that the connection just doesn't
work.