On Tue, Mar 3, 2015 at 9:10 AM, Brent Cook <[email protected]> wrote: > On Tue, Mar 3, 2015 at 5:58 AM, Alexander Haensch > <[email protected]> wrote: >> Today is good day for crashes, as i reinstalled one client, the crash >> happens very fast. > > I'm trying to reproduce this by having a client reconnect in a loop > with the sample keys: > > while true; do sudo openvpn --remote 192.168.1.2 --proto tcp-client > --dev tun1 --ifconfig 10.0.0.1 10.0.0.2 --tls-client --ca ca.crt > --cert client.crt --key client.key --inactive 2; sleep 2; done > > with a server listening like so: > > sudo gdb --args openvpn --remote 192.168.1.1 --proto tcp-server --dev > tun1 --ifconfig 10.0.0.2 10.0.0.1 --tls-server --dh dh2048.pem --ca > ca.crt --cert server.crt --key server.key > > but haven't seen anything so far. Valgrind did complain a bit about an > uninitialized variable in blowfish encrypt, but I think this was a > false-postitive. Is there anything I could change above (algorithms, > etc.) that would make this simulation closer to your configuration?
A short time later, I got a crash, though completely different than yours :P. It was easy enough to reproduce, so I will dig in a little more deeply. Program received signal SIGSEGV, Segmentation fault. 0x0000064fce25d090 in print_sockaddr () from /usr/local/sbin/openvpn (gdb) bt #0 0x0000064fce25d090 in print_sockaddr () from /usr/local/sbin/openvpn #1 0x0000064fce25d611 in print_sockaddr () from /usr/local/sbin/openvpn #2 0x0000064fce21dc5f in management_show_net_callback () from /usr/local/sbin/openvpn #3 0x0000064fce21eb0d in management_show_net_callback () from /usr/local/sbin/openvpn #4 0x0000064fce236dd4 in mroute_addr_hash_function () from /usr/local/sbin/openvpn #5 0x0000064fce2093d1 in ?? () from /usr/local/sbin/openvpn #6 0x0000000000000000 in ?? ()
