I guess the man pages I were using are old then lol. That would make sense why it isn't running in Daemon mode :)
Thanks! Mike On Aug 25, 2014, at 11:42 AM, TOoSmOotH <[email protected]> wrote: > Having an issue getting netsniff-ng to run in daemon mode. > > When I run this everything runs great: > > netsniff-ng -i eth1 -o /nsm/pcap/ -s --prefix snort.log. --verbose > --ring-size 50MiB --interval 50MiB > > > When I run it this way to drop it into daemon mode I get this: > > netsniff-ng -i eth1 -o /nsm/pcap/ -s --prefix snort.log. --verbose > --ring-size 50MiB --interval 50MiB -D -P /var/run/netsniff-ng.pid -L > /var/log/netsniff-ng.log -S /tmp/netsniff-ng.uds > > tcpdump-capable pcap: > > magic: 0xa1b2c3d4 (swapped: 0xd4c3b2a1) > > features: > > timeval in us > > packet length > > packet cap-length > > tcpdump-capable pcap with ns resolution: > > magic: 0xa1b23c4d (swapped: 0x4d3cb2a1) > > features: > > timeval in ns > > packet length > > packet cap-length > > Alexey Kuznetzov's pcap: > > magic: 0xa1b2cd34 (swapped: 0x34cdb2a1) > > features: > > timeval in us > > packet length > > packet cap-length > > packet ifindex > > packet protocol > > packet type > > netsniff-ng pcap: > > magic: 0xa1e2cb12 (swapped: 0x12cbe2a1) > > features: > > timeval in ns > > timestamp source > > packet length > > packet cap-length > > packet ifindex > > packet protocol > > hardware type > > packet type > > > Then it just exits. Any ideas? Am I missing something simple here? > > Thanks > > Mike > > -- > 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. -- 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.
