Date: Thu, 19 May 2005 09:56:09 +0300 From: Matti Saarinen <mjsaarin@cc.helsinki.fi> To: freebsd-current@freebsd.org Subject: CURRENT: ifconfig tap0 results in core dump Message-ID: <yq3jekc34sc6.fsf@lagavulin.it.helsinki.fi>
next in thread | raw e-mail | index | archive | help
I'm not sure if the problem I'm seeing is caused by OpenVPN or some
code change related to ifconfig. Or perhaps both are to blame.
When I open an OpenVPN connection in tap mode the openvpn process
creates tap0 inteface and assigns an IP address to it. If I now do
ifconfig tap0 it displays the information correctly. Now, when quit
the openvpn session, the tap0 interface still stays there but it has
not address. If I now try see the status of it with ifconfig it dumps
core. From tap0, ifconfig manages to display the inet6 line and then
it receives a segementation fault. If I restart the openvpn process,
the tap0 interface works but ifconfig tap0 still dumps core.
An example:
OpenVPN is running:
% ifconfig tap0
tap0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::2bd:9ff:fe7c:100%tap0 prefixlen 64 scopeid 0x5
inet 128.214.182.158 netmask 0xffffffc0 broadcast 128.214.182.191
ether 00:bd:09:7c:01:00
Opened by PID 584
Now, I've terminated PID 584 (openvpn)
% ifconfig tap0
tap0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::2bd:9ff:fe7c:100%tap0 prefixlen 64 scopeid 0x5
zsh: segmentation fault (core dumped) ifconfig tap0
I remember that ifconfig didn't dump core when my laptop ran CURRENT
from a few months ago.
Cheers,
--
- Matti -
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?yq3jekc34sc6.fsf>