A bit more info -- I checked out the latest tagged release (v0.5.8-rc5), and I could no longer repro the problem. Additionally, the error was seen on a VMware VM, and when I transmitted the same config fiel on a physical host I did not see the issue (still on commit e1af615aca2fa6e5927645eaa944db6fa89f61a4).
Let me know if there are diags that would be useful to grab if you think this is a bug and want to investigate, but I have this running now, so don't need assistance on this one. Cheers On Monday, March 10, 2014 11:12:53 AM UTC-7, [email protected] wrote: > On Monday, December 23, 2013 11:11:10 AM UTC-8, Daniel Borkmann wrote: > > On 12/23/2013 08:06 PM, Robert Edmonds wrote: > > > > > Hi, > > > > > > > > > > I'm seeing the error message "Flushing TX_RING failed: No such device or > > > > > address!" when I try to run trafgen on Debian kernel 3.12.6, but not on > > > 3.11. > > > > > Here is the full trafgen output: > > > > > > > > A PF_PACKET stable patch for the kernel is on it's way to address that > > issue. > > > > I expect the next stable kernel or the one after that to contain this. In > > case > > > > you need it earlier than that, feel free to backport [1] to your kernel. > > > > > > > > [1] > > https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=66e56cd46b93ef407c60adcac62cf33b06119d50 > > > > > > > > > # trafgen -V -i ./trafgen.cfg -o eth1 -P 1 -n 1000 > > > > > [0] pkt > > > > > len 85 cnts 0 rnds 6 > > > > > payload 00 25 90 86 bd d6 00 25 90 d9 dd 81 08 00 45 00 00 47 00 00 > > > 00 00 40 11 00 00 c0 a8 00 01 c0 a8 00 35 00 00 00 35 00 33 00 00 00 00 > > > 01 00 00 01 00 00 00 00 00 01 03 77 77 77 06 67 6f 6f 67 6c 65 03 63 6f > > > 6d 00 00 01 00 01 00 00 29 10 00 00 00 00 00 00 00 > > > > > rnd0 off 18 > > > > > rnd1 off 19 > > > > > rnd2 off 34 > > > > > rnd3 off 35 > > > > > rnd4 off 42 > > > > > rnd5 off 43 > > > > > 1 packets to schedule > > > > > 85 bytes in total > > > > > Running! Hang up with ^C! > > > > > > > > > > No kernel support for PACKET_QDISC_BYPASS (kernel < 3.14?) > > > > > TX,V2: 238.41 MiB, 122064 Frames, each 2048 Byte allocated > > > > > Flushing TX_RING failed: No such device or address! > > > > > > > > > > And the relevant strace output: > > > > > > > > > > bind(3, {sa_family=AF_PACKET, proto=0000, if3, pkttype=PACKET_HOST, > > > addr(0)={0, }, 20) = 0 > > > > > setgid(0) = 0 > > > > > setuid(0) = 0 > > > > > setitimer(ITIMER_REAL, {it_interval={0, 10}, it_value={0, 10}}, NULL) = 0 > > > > > --- SIGALRM (Alarm clock) @ 0 (0) --- > > > > > sendto(3, NULL, 0, MSG_DONTWAIT, NULL, 0) = -1 ENXIO (No such device or > > > address) > > > > > > > I'm seeing this error on Ubuntu kernel 3.5.0-47-generic, with the latest > netsniff-ng version in master (e1af615aca2fa6e5927645eaa944db6fa89f61a4). > > Is this a different issue? The above discussion suggests that the bug causing > this issue was introduced > 3.11. If so, any suggestions for > debugging/diagnosis? -- You received this message because you are subscribed to the Google Groups "netsniff-ng" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
