Your message dated Fri, 20 Jan 2017 08:09:56 -0200 with message-id <CAP+dXJcFUy=q9y9+f+epcm1bmbxfacjxx+tdm-7potysi_b...@mail.gmail.com> and subject line Re: packit: inject mode: ascii payload option broken has caused the Debian Bug report #286351, regarding packit: inject mode: ascii payload option broken 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.) -- 286351: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=286351 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: packit Version: 1.0-1 Severity: normal the "-p" option seems to be broken for ascii payloads: # packit -t UDP -c 1 -sR -dR -p 'test' Mode: Packet Injection using device: eth0 Error: Unable to build UDP header: libnet_build_udp(): payload inconsistency specifying a hex payload works: # packit -t UDP -c 1 -sR -dR -p '0x01' Mode: Packet Injection using device: eth0 UDP header: Src Port: 21051 Dst Port(s): 0 IP header: Src Address: 110.133.175.120 Dst Address: 137.44.234.202 TTL: 128 ID: 62388 TOS: 0x0 Len: 29 Writing packet(s) (1): . -| Packet Injection Statistics |-------------------------------------------- Injected: 1 Packets/Sec: 1.0 Bytes/Sec: 29.0 Errors: 0 -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.26-1-686 Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15) Versions of packages packit depends on: ii libc6 2.3.2.ds1-19 GNU C Library: Shared libraries an ii libnet1 1.1.2.1-1 Library for the construction and h ii libpcap0.7 0.7.2-7 System interface for user-level pa -- no debconf information
--- End Message ---
--- Begin Message ---Hi, This bug was solved by revision 1.0+git-devel20170118.e913e5e-1. Regards, Eriberto
--- End Message ---
