[hipl-dev] [Branch ~hipl-core/hipl/trunk] Rev 6433: Updated manual on the use of tcpdump for HIP-related traffic.
- From: noreply@xxxxxxxxxxxxx
- To: HIPL core team <hipl-dev@xxxxxxxxxxxxx>
- Date: Fri, 11 Oct 2013 11:23:27 -0000
------------------------------------------------------------
revno: 6433
committer: Miika Komu <miika@xxxxxx>
branch nick: hipl
timestamp: Fri 2013-10-11 14:22:11 +0300
message:
Updated manual on the use of tcpdump for HIP-related traffic.
Filtering of ESP encapsulated traffic was documented, but now also an
example to filter HIP-based traffic without ESP encapsulation is
documented in the manual.
modified:
doc/HOWTO.xml.in
--
lp:hipl
https://code.launchpad.net/~hipl-core/hipl/trunk
Your team HIPL core team is subscribed to branch lp:hipl.
To unsubscribe from this branch go to
https://code.launchpad.net/~hipl-core/hipl/trunk/+edit-subscription
=== modified file 'doc/HOWTO.xml.in'
--- doc/HOWTO.xml.in 2013-08-06 19:14:00 +0000
+++ doc/HOWTO.xml.in 2013-10-11 11:22:11 +0000
@@ -556,6 +556,9 @@
"tcpdump -n -i any esp or proto 139 or port 10500"
to catch HIP-only traffic. It should be taken into account
that LSIs are local identifiers, so they are not on the wire.
+ If you prefer to see inside the ESP packets, you can use
+ "tcpdump -n -i any net 2001:0010::/28", but please note that
+ this displays only incoming datagrams, not outgoing.
</para>
</section>
Other related posts:
- » [hipl-dev] [Branch ~hipl-core/hipl/trunk] Rev 6433: Updated manual on the use of tcpdump for HIP-related traffic. - noreply
