Hi,
1.any documentation how to use Bro to read and analyze
ipv6 traces?
2.I use Bro-1.4 install from FreeBSD ports by add
--enable-brov6 to CONFIGURE_ARGS=
but bro fail to read ipv6 traces.
3.does bro can read ip6 multicast traces?
2.I use Bro-1.4 install from FreeBSD ports by add
--enable-brov6 to CONFIGURE_ARGS=
but bro fail to read ipv6 traces.
Make sure that you set your capture filter to include ipv6 traffic. It's not set to include it by default. From the command line you can do -f"ip and ip6" to include all ipv4 and ipv6 traffic.
3.does bro can read ip6 multicast traces?
I don't see why it would have any trouble with multicast.
2.I use Bro-1.4 install from FreeBSD ports by add
--enable-brov6 to CONFIGURE_ARGS=
but bro fail to read ipv6 traces.
Make sure that you set your capture filter to include ipv6 traffic.
It's not set to include it by default. From the command line you can do
-f"ip and ip6" to include all ipv4 and ipv6 traffic.
i use tcpdump to capture packet. #tcpdump -c 10000 -s 1500 -w ip6.pcap -nvvi em2 ip6 #tcpdump -s 1500 -nvv -w tcp6.pcap -r ip6.pcap tcp #bro -r tcp6.pcap
1231818666.514747 weird: spontaneous_FIN
there are no *.log files (conn.log, etc).
3.does bro can read ip6 multicast traces?
I don't see why it would have any trouble with multicast.
1.any documentation how to use Bro to read and analyze
ipv6 traces?
Nothing extra is needed other than --enable-brov6.
Note though that Bro doesn't correctly deal with packets that have options
(this is a BPF/pcap limitation, rather than something specific to Bro).
2.I use Bro-1.4 install from FreeBSD ports by add
--enable-brov6 to CONFIGURE_ARGS=
but bro fail to read ipv6 traces.
As usual, reports of failures work much better if you include a trace and
command-line invocation that demonstrates the problem, so we can try to
reproduce it.
3.does bro can read ip6 multicast traces?
It should be able to read them (as UDP, if that's what they are), but
doesn't do any interesting analysis on them.