NgTech-LTD/gns3-server
2
0
Fork 0
mirror of https://github.com/GNS3/gns3-server.git synced 2026-08-27 12:30:13 +03:00
Code Issues Packages Projects Releases Wiki Activity

fix: update search_fields examples to use existing field names

Browse Source
This commit is contained in:
YueGuobin 2026-05-12 14:48:37 +08:00
parent 73e0de7706
commit 09b0fbcfea
No known key found for this signature in database
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
gns3server/agent/gns3_copilot/tools_v2/packet_analysis_tool.py
View File

@ -83,7 +83,8 @@ class PacketAnalysisTool(BaseTool):
Input (JSON format) — field search mode (no capture needed):
- action (str): "search_fields"
- query (str): Single keyword for literal substring search (e.g., "ospf.lsa", "bgp")
- query (str): Single keyword, e.g. "ospf.lsa", "bgp.open", "bgp.type"
Use dot-notation like "protocol.field" for precise results.
Common tshark argument patterns:
-Y "<filter>" Display filter
@ -98,10 +99,11 @@ class PacketAnalysisTool(BaseTool):
Instead of analysis, you can search tshark's field registry directly for
valid field names:
{"action": "search_fields", "query": "ospf.lsa"}
{"action": "search_fields", "query": "bgp"}
Uses literal substring matching (not regex). Returns matching field names,
types, and descriptions. Use this to find correct -e field names before
building tshark_args.
{"action": "search_fields", "query": "bgp.open"}
Uses literal substring matching (not regex). Only one keyword allowed.
Use dot-notation like "ospf", "ospf.lsa", "bgp.peer" for precise results.
Returns matching field names, types, and descriptions. Use this to find
correct -e field names before building tshark_args.
"""
@classmethod