Hi,
For some reason Trisul is not picking up the dag62:0 interface that you created. The other interfaces in the log are just Trisul enumerating the available interfaces.
Back to the log:
ns-001.log:Wed May 4 11:51:18 2011.613957 INFO Libpcap run mode is set to 0
I was expecting to find "mode is set to 1"
ns-001.log:Wed May 4 11:51:18 2011.654410 DEBUG Opening and registering adapter 0 dag0:62
ns-001.log:Wed May 4 11:51:20 2011.858590 INFO Found adapter [2] dag0:12 : (No description available)
ns-001.log:Wed May 4 11:51:20 2011.858600 INFO Found adapter [3] dag0:14 : (No description available)
I also expected to see adapter [1].
I made some changes to the trisul build that might fix this.
Can you download from
www.unleashnetworks.com/lib/private/trisul_1.2.708_amd64.deb
Remove old package (dpkg -r) and install the new one.
Once done - run this command to list all interfaces seen by trisul
trisul --listdev
You should see all your dag interfaces, including the dag62:0. This is just a call to pcap_findalldevs() so the DAG API must recognize the interface.
If you can see dag62 then, just start Trisul. It should work. If you are on a very high bandwidth environment you can try to disable the packet store for now and add it in later.
I hope this does the trick. Please let me know how it goes.
Thanks,
Vivek