anantha narasimhan wrote:
pcap_findalldevs() does not show DAG streams that are locked (by an application thats reading off it). Probably in your case all but these two streams are currently being read from. If you have access to the dagtools, try attaching to any desired stream using dagbits. If dagbits fails to attach to a stream, it logs an error message, that might be able to give you an indication of whether the stream is locked by someone else or any other issue.
There is no problem with the Dag streams and there is nothing using the streams above 30. In fact the 2 streams that Trisul is finding are being used by an application. There is nothing wrong with the Dag card or any other application attempting to use it (Argus, Tcpdump, nTop, Snort etc.) just Trisul.
vivek [unleash] wrote:Hello Leif,
That is strange - because the --listdev option just does a pcap_findalldevs() and prints its output.
Can the stock tcpdump see the other DAG interfaces ?
You can get tcpdump to list all interfaces like this
So tcpdump -D gives the same list of interfaces as Trisul:
tcpdump -D
1.eth0
2.dag0:12
3.dag0:14
4.eth1
5.usbmon1 (USB bus number 1)
6.usbmon2 (USB bus number 2)
7.usbmon3 (USB bus number 3)
8.usbmon4 (USB bus number 4)
9.usbmon5 (USB bus number 5)
10.usbmon6 (USB bus number 6)
11.usbmon7 (USB bus number 7)
12.usbmon8 (USB bus number 8)
13.any (Pseudo-device that captures on all interfaces)
14.lo
However, as with all the other applications I run, I can pick the interface and use it just fine.
tcpdump -v -i dag0:62
tcpdump: listening on dag0:62, link-type EN10MB (Ethernet), capture size 65535 bytes
33 packets captured
33 packets received by filter
0 packets dropped by kernel
But when I try to select the interface in Trisul I continue to get:
ns-001.log:Fri May 6 09:15:27 2011.906009 DEBUG Opening and registering adapter 0 dag0:62
ns-001.log:Fri May 6 09:15:30 2011.315482 INFO Found adapter [2] dag0:12 : (No description available)
ns-001.log:Fri May 6 09:15:30 2011.315493 INFO Found adapter [3] dag0:14 : (No description available)
ns-001.log:Fri May 6 09:15:30 2011.315603 ERROR Requested adapter 0 [dag0:62] not found on this machine
ns-001.log:Fri May 6 09:15:30 2011.315622 ERROR Error initializing adapter dag0:62, see previous errors
ns-001.log:Fri May 6 09:15:30 2011.315631 INFO Removing interface dag0:62 from listener list