Wireshark mailing list archives
netflow v9 SRC_AS_PEER and DST_AS_PEER
From: kura () iij ad jp
Date: Tue, 14 Sep 2010 19:20:34 +0900 (JST)
Hello, Currently wireshark decodes netflow v9 type=128 as "SRC_AS_PEER" and type=129 as "DST_AS_PEER". Does anyone know in which RFC or other documents they are defined? - from packet-netflow.c: |static const value_string v9_template_types[] = { |... | { 128, "SRC_AS_PEER" }, | { 129, "DST_AS_PEER" }, In RFC5102 (for IPFIX) id=128 is defined as "bgpNextAdjacentAsNumber" and id=129 as "bgpPrevAdjacentAsNumber". I think the former is equal to "DST_AS_PEER" and the latter is equal to "SRC_AS_PEER". I'd like to know whether this difference is a bug of wireshark or not. Regards, -- Tomohiko Kurahashi <kura () iij ad jp> ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe
Current thread:
- netflow v9 SRC_AS_PEER and DST_AS_PEER kura (Sep 14)
- Re: netflow v9 SRC_AS_PEER and DST_AS_PEER Bill Meier (Sep 14)
- Re: netflow v9 SRC_AS_PEER and DST_AS_PEER kura (Sep 17)
- Re: netflow v9 SRC_AS_PEER and DST_AS_PEER Bill Meier (Sep 14)