Raspberry Pi Fritz Box Traffic Monitor

Reference Manual

HOW TO capture Fritz!Box     DSL traffic in real time

HOW TO capture Fritz!Box  WLAN traffic in existent fourth dimension

HOW TO capture Fritz!Repeater    traffic in real fourth dimension

HOW TO capture interface traffic and brandish it in Wireshark

Be certain to enter your FritzBox password with control: prepare fbpwd mypassword

DSL Stats, DSL Graph, Calls, Phone call List (CSV)

DSL Stats, DSL Graph, Calls, Call List (CSV) Calls

Introduction

Both the Fritz!Box and the Fritz!Repeater have a bundle trace characteristic that works by requesting a special URL that returns a traffic trace for a specified interface in the form of a libpcap formatted file. When the trace is terminated, the saved trace file tin can be viewed using software such equally WireShark that displays the traffic in a readable form.

While this feature is quite useful, it has the major disadvantage that one cannot view the traffic in real time. The trace must be started, run for as long as is required, and so stopped. Only then can Wireshark exist started in lodge to display the trace.

NAT32 can request a trace from the Fritz!Box or the Fritz!Repeater and and then pipage the received data to a trounce command (tdump) that decodes the data and prints it to the standard output device. The standard output tin can exist redirected to a NAT32 Monitor window for subsequent brandish. The display tin exist started and stopped every bit needed and can also exist saved to a file for subsequent examination.

Because the NAT32 shell (dissimilar the Windows cmd.exe shell) executes each command of a pipeline in a separate thread, the display of the trace data occurs in real time and the user tin can immediately notice (and respond to) whatsoever unwanted Net traffic originating from connected computers. This feature tin be very useful for detecting viruses and applications (e.1000. Skype) that may consume large amounts of DSL bandwidth for no useful purpose (from the user's signal of view).

Script Files

A script file to solicit the trace from the Fritz!Box, decode it and display it in the Monitor window is shown below:

monitor on set fbtrace ane sid fbgetr "http://fritz.box/cgi-bin/capture_notimeout?start=0" | tdump > monitor &        

A script file to cease the trace is shown below:

sid fbgetr "http://fritz.box/cgi-bin/capture_notimeout?cease=0" sid clear set fbtrace 0        

The above scripts are contained in files fritz_on and fritz_off and can be invoked from the main NAT32 spider web page or the NAT32 Console.
Similar files are bachelor for the Fritz!Repeater (fritzr_on and fritzr_off).

Notes

If your Fritz!Box requires a countersign for browser admission, please utilise the NAT32 fix command to store that countersign in the environs variable fbpwd equally follows:

gear up fbpwd myPassword        

NAT32 Version ii uses the following TCL script to compute the required Fritz!Box Session ID:

        #!tcl      #     # sid - set or clear the FritzBox SID in global var fbsid (Fritz!Os prior to 5.50)     #       For subsequently Fritz!OS versions, please encounter file 'sid' in your NAT32 distribution.      if {$argc > 1} {         error "Usage: sid [clear]"     }      if {$argc == 1} {         if {$fbsid == ""} {             error "Fault: unknown SID"         }         set cmd "httppost http://fritz.box/cgi-bin/webcm \"security:command/logout=1&sid=$fbsid\""         exec $cmd         gear up fbsid ""         get out     }      gear up xml [exec "httpget http://fritz.box/cgi-bin/webcm?getpage=../html/login_sid.xml"]      if {[regexp "<iswriteaccess>(1)</iswriteaccess>" $xml tmp]} {         regexp "<SID>(.*)</SID>" $xml sid         regsub "<SID>" $sid "" tmp2         regsub "</SID>" $tmp2 "" consequence         ready fbsid $result         go out     }      if {[regexp "<Claiming>(.*)</Challenge>" $xml claiming]} {         regsub "<Challenge>" $challenge "" tmp1         regsub "</Claiming>" $tmp1 "" tmp2         if {$fbpwd == ""} {             error "Error: unknown password"         }         set challenge "$tmp2-$fbpwd"         set hash [exec "hash $challenge"]           # Encounter note below         set h "$tmp2-$hash"         prepare cmd "httppost http://fritz.box/cgi-bin/webcm \"login:command/response=$h&getpage=../html/login_sid.xml\""         set tmp1 [exec $cmd]         regexp "<SID>(.*)</SID>" $tmp1 sid         regsub "<SID>" $sid "" tmp2         regsub "</SID>" $tmp2 "" result         set fbsid $upshot     }      

Annotation the use of the NAT32 control hash in the above script. Considering it is implemented in C, it computes the MD5 hash of the specified string very rapidly.

NAT32 Version 2 contains additional script files (fritzr_on) and fritzr_xon) that brandish the trace information in the Monitor window or the Trace window. In the latter case, all packet data is displayed, including protocol headers and payload data.

See Also

Fritz!Box Tips and Tricks, External Routers, httpget

---

setTimeout(f, 1000); function f() { id_write_html(GetFbDsl(), 'result1'); id_write_html(GetFbSet(), 'result2'); }

Source: https://www.nat32.com/v2/fritzm.htm

Posted by: suggsopme1984.blogspot.com

Share this post