On Thu, Feb 20, 2020 at 11:48:01PM +0100, Laurent Coustet wrote:
> Hi ports@
> 
> I've fixed the last version of net/mlvpn in order to support
> OpenBSD 6.6+.
> 
> No major changes, just random fixes and version bump.
> 
> Changes:
> 
>   - Send keepalives every 1s, detect timeouts at 2s (@stapelberg)
>   - Fix calculation of loss ration with sequence of tunnel (@flohoff)
>   - Fix compiler warning (switch fall through)
>   - Fix: ERRMSGSIZ should be greather than PATHMAX
>   - Fix: OpenBSD: fix bad usage of TUNSIFINFO: missing type
>   - FIX: BSD: tun device name fix. (allow tun10+ to be used)
> 
> -- 
> Laurent Coustet

thank you for your update :)

on -current I still can't run it (didn't try on 6.6 as a client). with
ktrace I found it was producing a .core file in /var/crash which may
help finding what the issue is.

here is my client config

[general]
statuscommand = "/etc/mlvpn/mlvpn_updown.sh"
loglevel = 5
mode = "client"
mtu = 1442
tuntap = "tun"
interface_name = "tun0"
timeout = 30

password = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
cleartext_data = 0

[iwm0]
bindhost = "0.0.0.0"
remotehost = "XXXXXXXXXXXXXXX"
remoteport = 5081
bindfib = 1

[em0]
bindhost = "192.168.1.9"
remotehost = "XXXXXXXXXXXXXXX"
remoteport = 5080
bindfib = 0

When I run it

solene# mlvpn -c mlvpn.conf  --debug -vvvvv -u _mlvpn
2020-03-28T12:41:24 [ DBG] absolute maximum mtu: 1444
2020-03-28T12:41:24 [INFO/config] new password set
2020-03-28T12:41:24 [INFO/config] em0 tunnel added
2020-03-28T12:41:24 [INFO] created interface `tun0'
2020-03-28T12:41:24 [INFO] em0 bind to 192.168.1.9
solene#


In kdump output

 18793 mlvpn    GIO   fd 2 wrote 62 bytes
       "2020-03-28T12:34:22 \^[[1;34m[INFO]\^[[0m em0 bind to 192.168.1.9
       "
 18793 mlvpn    RET   write 62/0x3e
 18793 mlvpn    PSIG  SIGSEGV SIG_DFL code SEGV_MAPERR<1> addr=0x161473675b 
trapno=6
 18793 mlvpn    NAMI  "/var/crash/mlvpn.core"
 26746 mlvpn    RET   read 0
 26746 mlvpn    CALL  close(3)
 26746 mlvpn    RET   close 0
 26746 mlvpn    CALL  kbind(0x7f7ffffd6158,24,0x5f32ced114736743)
 26746 mlvpn    RET   kbind 0
 26746 mlvpn    CALL  exit(1)


in egdb

solene# egdb mlvpn /var/crash/mlvpn.core
GNU gdb (GDB) 7.12.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-openbsd6.6".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from mlvpn...(no debugging symbols found)...done.
[New process 365785]
Core was generated by `mlvpn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000015e641410250 in ?? ()
(gdb) bt
#0  0x000015e641410250 in ?? ()
#1  0x000015e64140e655 in ?? ()
#2  0x000015e92822b10f in ev_invoke_pending (loop=0x15e928234350 
<default_loop_struct>) at ev.c:3372
#3  0x000015e92822c004 in ev_run (loop=0x15e928234350 <default_loop_struct>, 
flags=<optimized out>) at ev.c:3775
#4  0x000015e64140f52b in ?? ()
#5  0x000015e64140613b in ?? ()
#6  0x0000000000000000 in ?? ()


I installed debug-mlvpn and devel-libev but the egdb output is still ??, I'm
stuck here, I don't understand how to get informations from egdb :/

Reply via email to