MediaWiki API result

{
    "batchcomplete": "",
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "11": {
                "pageid": 11,
                "ns": 0,
                "title": "VPN Bug Report Unix",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "== Introduction ==\n\nThis guide describes what information should be included when submitting a VPN Client for Linux/BSD bug report to the vpn-help mailing list. Please read this information carefully as the likelihood of getting a problem corrected is usually directly related to the quality of the bug report being submitted.\n\n== Describe Your Problem Clearly ==\n\nPlease describe the problem symptoms and the circumstance under which the problem occurs. It is also very important to note how the problem can be re-produced.\n\n== Include Your Client and Gateway Information ==\n\nPlease include your client and gateway information with each new problem report. The following information should be stated.\n\n* VPN Client Version\n* Linux or BSD OS Version\n* Gateway Make/Model\n* Gateway OS Version ( if known )\n\n== Include Debug Output if Requested ==\n\nAfter posting your initial problem report to the vpn-help mailing list, we may request that you provide additional information. The Shrew Soft VPN Client has several options that can be enabled which produce valuable debug output. This information is often essential to help isolate and resolve a reported problem. To gather this information, perform the following steps.\n\n==== Enable IKE Daemon Debug Output ====\n\nTo enable the IKE daemon debug output, open your iked.conf file with a text editor. Modify the daemon section of the file by seting the log_level option to debug and specifying a custom log output file path. Also specify a path for the pcap_decrypt option ( if requested ).\n\n daemon\n {\n     socket ike 500;\n     socket natt 4500;\n \n     log_level debug;\n     log_file \"/var/log/iked.log\";\n \n     pcap_decrypt \"/var/log/dump-ike-decrypt.cap\";\n }\n\nRestart the IKE daemon. If your platform provides a Linux init script or BSD rc script, use it to restart the daemon.\n\n # /etc/init.d/iked restart\n\nTo manually restart the service, first locate the iked process id and use the kill utility to stop the daemon. Afterwords you can restart the daemon. You will need root equivalent privileges to perform these steps.\n\n # ps aux | grep iked\n root    54252  0.0  1.1  4536  2896  ??  Ss    7:53PM   0:00.01 iked\n # kill 54252\n # iked\n\n==== Reproduce Your Problem ====\n\nWhile reproducing your problem, the VPN Client will capture debug output to be submitted with your bug report.\n\n==== Copy IKE Daemon Debug Output Files ====\n\nTo make a copy of the IKE daemon debug output, perform the following steps.\n\n* Make sure the IKE daemon is not running\n* Copy the following files to a temporary directory\n** /var/log/iked.log\n** /var/log/dump-ike-decrypt.cap\n\nFor example:\n\n mkdir ~/ikedebug\n cp /var/log/iked.log ~/ikedebug/\n cp /var/log/dump-ike-decrypt.cap ~/ikedebug/\n\n==== Disable IKE Daemon Debug Output ====\n\nTo disable the IKE daemon debug output, open your iked.conf file with a text editor. Modify the daemon section of the file by seting the log_level option to none. Also remove or comment out the pcap_decrypt option. Afterwards you can restart the daemon.\n\n==== Archive the Debug Output ====\n\nUse the tar utility to store the debug output files in a compressed archive.\n\nFor example:\n\n cd ~\n tar zcvf ikedebug.tgz ikedebug\n\nIf you plan to post debug output to the vpn-help mailing list, please be sure to remove sensitive information from log files such as your gateway IP address. Alternately, you can send your archive attachment directly to your Shrew Soft contact in a separate email.\n\nNOTE: Never post decrypted binary packet dump information to the mailing list. Also, never post log output using a level higher than debug. This output may include information that could be used to compromise the security of your gateway.\n\n== Example Bug Report ==\n\n Problem:\n \n The VPN client fails to connect to my gateway when I have firmware\n version 3.7 installed. After clicking connect, the client reports\n it has received an invalid message from the gateway. Downgrading\n my gateway firmware to version 3.6 allows me to connect again.\n \n To Reproduce:\n \n Connect to any SuperEX 1510 VPN Gateway using firmware revision 3.7.\n \n VPN Client Version = 2.1.0 RC1\n Unix OS Version = FreeBSD 6.3-RELEASE\n Gateway Make/Model = SuperEX 1510\n Gateway OS Version = 3.7\n \n ikedebug.tgz [attachment]\n \\ikedebug\\iked.log\n  ikedebug\\dump-ike-decrypt.cap ( if requested )"
                    }
                ]
            },
            "10": {
                "pageid": 10,
                "ns": 0,
                "title": "VPN Bug Report Windows",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "== Introduction ==\n\nThis guide describes what information should be included when submitting a VPN Client for Windows bug report to the vpn-help mailing list. Please read this information carefully as the likelihood of getting a problem corrected is usually directly related to the quality of the bug report being submitted.\n\n== Describe Your Problem Clearly ==\n\nPlease describe the problem symptoms and the circumstance under which the problem occurs. It is also very important to note how the problem can be re-produced.\n\n== Include Your Client and Gateway Information ==\n\nPlease include your client and gateway information with each new problem report. The following information should be stated.\n\n* VPN Client Version\n* Windows OS Version\n* Gateway Make/Model\n* Gateway OS Version ( if known )\n\n== How to Include Debug Output if Requested ==\n\nAfter posting your initial problem report to the vpn-help mailing list, we may request that you provide additional information. The Shrew Soft VPN Client has several options that can be enabled which produce valuable debug output. This information is often essential to help isolate and resolve a reported problem. To gather this information, perform the following steps.\n\n==== Enable IKE Service Debug Output ====\n\nTo enable the IKE Service debug output, start the VPN Trace application using Administrative privileges and perform the following steps.\n\n* Click the IKE Service Tab and Stop the Service\n* Open the File Menu and Select Options\n** Set the Log output level to ''debug''\n** Check the ''Enable packet dump of decrypted IKE traffic'' option ( if requested )\n** Click the OK Button\n* Click the IKE Service Tab and Start the Service\n\n==== Reproduce Your Problem ====\n\nWhile reproducing your problem, the VPN Client will capture the debug output for submission.\n\n==== Copy IKE Service Debug Output Files ====\n\nTo make a copy of the IKE Service debug output, start the VPN Trace application using Administrative privileges and perform the following steps.\n\n* Click the IKE Service Tab and Stop the Service\n* Copy the following files from <VPN Client>\\debug to a temporary directory\n** iked.log\n** dump-ike-decrypt.cap\n\n==== Disable IKE Service Debug Output ====\n\nTo disable the IKE Service debug output, start the VPN Trace application using Administrative privileges and perform the following steps.\n\n* Click the IKE Service Tab and Stop the Service\n* Open the File Menu and Select Options\n** Set the Log output level to ''none''\n** Uncheck the ''Enable packet dump of decrypted IKE traffic'' option\n** Click the OK Button\n* Click the IKE Service Tab and Start the Service\n\n==== Archive the Debug Output ====\n\nUse [http://www.7-zip.org/ 7zip], [http://www.winzip.com/ Winzip] or a similar utility to store the debug output files in a compressed archive. If you plan to post debug output to the vpn-help mailing list, please be sure to remove sensitive information from log files such as your gateway IP address. Alternately, you can send your archive attachment directly to your Shrew Soft contact in a separate email.\n\nNOTE: Never post decrypted binary packet dump information to the mailing list. Also, never post log output using a level higher than debug. This output may include information that could be used to compromise the security of your gateway.\n\n== Example Bug Report ==\n\n Problem:\n \n The VPN client fails to connect to my gateway when I have firmware\n version 3.7 installed. After clicking connect, the client reports\n it has received an invalid message from the gateway. Downgrading\n my gateway firmware to version 3.6 allows me to connect again.\n \n To Reproduce:\n \n Connect to any SuperEX 1510 VPN Gateway using firmware revision 3.7.\n \n VPN Client Version = 2.1.0 RC1\n Windows OS Version = Windows XP SP2\n Gateway Make/Model = SuperEX 1510\n Gateway OS Version = 3.7\n \n debug.zip [attachment]\n \\iked.log\n  dump-ike-decrypt.cap ( if requested )"
                    }
                ]
            }
        }
    }
}