Wireshark: Capture SQL Traffic: Difference between revisions

From OnnoCenterWiki
Jump to navigationJump to search
Onnowpurbo (talk | contribs)
No edit summary
Onnowpurbo (talk | contribs)
No edit summary
 
(One intermediate revision by the same user not shown)
Line 4: Line 4:
  Capture Options (ctrl-K).
  Capture Options (ctrl-K).


Untuk mem-filter komunikasi ke SQL server, kita butuh informasi


host <sql-server-ip>
port <sql-server-port>


Wireshark has display filters and capture filters. The capture filter captures only certain packets, resulting in a small capture file. Capture filters are set in Capture Options (ctrl-K). An example to capture SQL Server traffic would be:
Filter yang diberikan dapat menggunakan format,
 
host <sql-server-ip> and port <sql-server-port>
 
A display filter is set in the toolbar. A display filter does not reduce the size of the capture. You can change a display filter while the capture is running. An example display filter:


  ip.addr == <sql-server-ip> && tcp.port == <sql-server-port>
  ip.addr == <sql-server-ip> && tcp.port == <sql-server-port>


The default SQL Server port is 1433.
Biasanya SQL Server port adalah 1433
 
 
You can use only tds to identify the traffic between SQL Server's client and server, this fill filter a lot of noise packet.
 
Or you can append the tds with the and or && operator after other filters if you want to filter more specific traffic.
 





Latest revision as of 04:23, 18 April 2017

Kadang kala kita perlu menangkap komunikasi antara server Web dengan database server. Melalui wireshark kita data memfilter

Capture Options (ctrl-K).

Untuk mem-filter komunikasi ke SQL server, kita butuh informasi

host <sql-server-ip>
port <sql-server-port>

Filter yang diberikan dapat menggunakan format,

ip.addr == <sql-server-ip> && tcp.port == <sql-server-port>

Biasanya SQL Server port adalah 1433


Referensi