Your message dated Tue, 26 Jun 2012 14:00:53 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-vsquare-devel] Bug#492747: Bug#492747: liblwipv6-2:
seqv when using mstack ... ip link depending on path
has caused the Debian Bug report #492747,
regarding liblwipv6-2: seqv when using mstack ... ip link depending on path
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
492747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492747
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: liblwipv6-2
Version: 1.2a-1
Severity: normal
depending on the path where I start umview I get strange results, otr a seqV:
achim@debian64:~/.wine/drive_c/Program Files$ umview -p umnet bash
This kernel supports: ppoll
UMView will use: ppoll
umnet init
achim@debian64:~/.wine/drive_c/Program Files$ !moun
mount -t umnetlwipv6 -o tn0=tap0 none /dev/net/yourip
achim@debian64:~/.wine/drive_c/Program Files$ !ms
mstack /dev/net/yourip ip link
1: lo0: <LOOPBACK,UP> mtu 0
link/loopback
2: tn0: <> mtu 65535
link/void ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:74:6e:00:40:00:02:ff:ff:ff:ff:ff:
brd ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:
Segmentation fault
achim@debian64:~/.wine/drive_c/Program Files$
One up:
chim@debian64:~/.wine/drive_c$ !umv
umview -p umnet bash
This kernel supports: ppoll
UMView will use: ppoll
umnet init
!moachim@debian64:~/.wine/drive_c$ !moun
mount -t umnetlwipv6 -o tn0=tap0 none /dev/net/yourip
achim@debian64:~/.wine/drive_c$ !ms
mstack /dev/net/yourip ip link
1: lo0: <LOOPBACK,UP> mtu 0
link/loopback
2: tn0: <> mtu 32
link/[244] 04:00:00:00:00:00:00:20:00:00:74:6e:00:40:00:02 brd
ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff
achim@debian64:~/.wine/drive_c$ exit
(Actually I got sometimes as well a SEQV, and somethmes no strange link line
for tn0)
one uo:
achim@debian64:~/.wine$ umview -p umnet bash
This kernel supports: ppoll
UMView will use: ppoll
umnet init
!achim@debian64:~/.wine$ !moun
mount -t umnetlwipv6 -o tn0=tap0 none /dev/net/yourip
achim@debian64:~/.wine$ !ms
mstack /dev/net/yourip ip link
1: lo0: <LOOPBACK,UP> mtu 0
link/loopback
2: tn0: <> mtu 0
link/generic
achim@debian64:~/.wine$
This is always fine
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages liblwipv6-2 depends on:
ii libc6 2.7-12 GNU C Library: Shared libraries
ii libpcap0.8 0.9.8-5 system interface for user-level pa
ii libvdeplug2 2.2.2-1 Virtual Distributed Ethernet - Plu
liblwipv6-2 recommends no packages.
Versions of packages liblwipv6-2 suggests:
ii vde2 2.2.2-1 Virtual Distributed Ethernet
-- no debconf information
--- End Message ---
--- Begin Message ---
tags 492747 + unreproducible
thanks
On Fri, Jan 20, 2012 at 00:18:41 +0100, Ludovico Gardenghi wrote:
> Do you still have this problem? I am going to upload a new release of
> lwipv6. Unless you're able to confirm that the issue is still there in
> lwipv6-1.5a-1 (which should in Debian by tomorrow) I'll close this bug.
I'm closing the bug, as I got no reply in 6 months and there has been
no feedback since 2008.
Ludovico
--
<[email protected]> IRC: garden@freenode
OpenPGP: 1024D/63D2D5D907F89BB8 Jabber/gtalk: [email protected]
--- End Message ---
