This bug was fixed in the package ngrep - 1.45.ds2-11
---
ngrep (1.45.ds2-11) unstable; urgency=low
* Use Linux target code on hurd-i386 to fix FTBFS.
* Fix (harmless) -Wformat warnings in tcpkill patch.
ngrep (1.45.ds2-10) unstable; urgency=low
* Enable hardening via
** Changed in: ngrep (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/567286
Title:
ngrep ipv6 support seems broken
To manage notifications about this bug
** Branch linked: lp:debian/ngrep
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/567286
Title:
ngrep ipv6 support seems broken
To manage notifications about this bug go to:
** Bug watch added: Debian Bug tracker #615138
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615138
** Also affects: ngrep (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615138
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: ngrep (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/567286
Title:
ngrep ipv6 support seems broken
To manage notifications about this bug go to:
It seems payload size calculation is incorrect for ipv6 packets. I attached a
patch that fixes ipv6 tcp, udp and icmp6 payload size calculation for ngrep
1.45.ds2-9.
My patched ngrep is behaving as expected now on my 10.04 and 9.10 hosts.
** Patch added: ngrep-fix-ipv6-support.patch
