On Sun, 2012-11-04 at 17:59 -0800, Jonathan Nieder wrote: > Patrik Nilsson wrote: > > > No error messages or anything else is shown: The connection just doesn't > > work when I try it. It is why I suspect that if a (background) program > > holds a socket open, the kernel can't set the route. Although it reports > > the correct route. > > I don't know anything about these things --- Ben is the networking > expert here. :) While the existence of a socket can make the kernel hold onto routing information that has otherwise been deleed, this is not supposed to affect routing for any new sockets. Ben. > Anyway, could you send "ip r" output from before and after connecting > to your openvpn server, just to humor us? 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? -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part