亚洲欧美第一页_禁久久精品乱码_粉嫩av一区二区三区免费野_久草精品视频

? 歡迎來到蟲蟲下載站! | ?? 資源下載 ?? 資源專輯 ?? 關于我們
? 蟲蟲下載站

?? remote-ext.h

?? 利用ARP 協議獲得局域網內 活動主機物理地址
?? H
字號:
/*
 * Copyright (c) 2002 - 2003
 * NetGroup, Politecnico di Torino (Italy)
 * All rights reserved.
 * 
 * Redistribution and use in source and binary forms, with or without 
 * modification, are permitted provided that the following conditions 
 * are met:
 * 
 * 1. Redistributions of source code must retain the above copyright 
 * notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright 
 * notice, this list of conditions and the following disclaimer in the 
 * documentation and/or other materials provided with the distribution. 
 * 3. Neither the name of the Politecnico di Torino nor the names of its 
 * contributors may be used to endorse or promote products derived from 
 * this software without specific prior written permission. 
 * 
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 
 * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 
 * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 
 * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 
 * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 
 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 
 * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 
 * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 
 * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 
 * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 
 * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 * 
 */


#ifndef __REMOTE_EXT_H__
#define __REMOTE_EXT_H__



// Definition for Microsoft Visual Studio
#if _MSC_VER > 1000
#pragma once
#endif

#ifdef __cplusplus
extern "C" {
#endif

/*!
	\file remote-ext.h

	The goal of this file it to include most of the new definitions that should be
	placed into the pcap.h file.

	It includes all new definitions (structures and functions like pcap_open().
    Some of the functions are not really a remote feature, but, right now, 
	they are placed here.
*/



// All this stuff is public
/*! \addtogroup remote_struct
	\{
*/




/*!
	\brief Defines the maximum buffer size in which address, port, interface names are kept.

	In case the adapter name or such is larger than this value, it is truncated.
	This is not used by the user; however it must be aware that an hostname / interface
	name longer than this value will be truncated.
*/
#define PCAP_BUF_SIZE 1024


/*! \addtogroup remote_source_ID
	\{
*/


/*!
	\brief Internal representation of the type of source in use (file, 
	remote/local interface).

	This indicates a file, i.e. the user want to open a capture from a local file.
*/
#define PCAP_SRC_FILE 2
/*!
	\brief Internal representation of the type of source in use (file, 
	remote/local interface).

	This indicates a local interface, i.e. the user want to open a capture from 
	a local interface. This does not involve the RPCAP protocol.
*/
#define PCAP_SRC_IFLOCAL 3
/*!
	\brief Internal representation of the type of source in use (file, 
	remote/local interface).

	This indicates a remote interface, i.e. the user want to open a capture from 
	an interface on a remote host. This does involve the RPCAP protocol.
*/
#define PCAP_SRC_IFREMOTE 4

/*!
	\}
*/



/*! \addtogroup remote_source_string

	The formats allowed by the pcap_open() are the following:
	- file://path_and_filename [opens a local file]
	- rpcap://devicename [opens the selected device devices available on the local host, without using the RPCAP protocol]
	- rpcap://host/devicename [opens the selected device available on a remote host]
	- rpcap://host:port/devicename [opens the selected device available on a remote host, using a non-standard port for RPCAP]
	- adaptername [to open a local adapter; kept for compability, but it is strongly discouraged]
	- (NULL) [to open the first local adapter; kept for compability, but it is strongly discouraged]

	The formats allowed by the pcap_findalldevs_ex() are the following:
	- file://folder/ [lists all the files in the given folder]
	- rpcap:// [lists all local adapters]
	- rpcap://host:port/ [lists the devices available on a remote host]

	Referring to the 'host' and 'port' paramters, they can be either numeric or literal. Since
	IPv6 is fully supported, these are the allowed formats:

	- host (literal): e.g. host.foo.bar
	- host (numeric IPv4): e.g. 10.11.12.13
	- host (numeric IPv4, IPv6 style): e.g. [10.11.12.13]
	- host (numeric IPv6): e.g. [1:2:3::4]
	- port: can be either numeric (e.g. '80') or literal (e.g. 'http')

	Here you find some allowed examples:
	- rpcap://host.foo.bar/devicename [everything literal, no port number]
	- rpcap://host.foo.bar:1234/devicename [everything literal, with port number]
	- rpcap://10.11.12.13/devicename [IPv4 numeric, no port number]
	- rpcap://10.11.12.13:1234/devicename [IPv4 numeric, with port number]
	- rpcap://[10.11.12.13]:1234/devicename [IPv4 numeric with IPv6 format, with port number]
	- rpcap://[1:2:3::4]/devicename [IPv6 numeric, no port number]
	- rpcap://[1:2:3::4]:1234/devicename [IPv6 numeric, with port number]
	- rpcap://[1:2:3::4]:http/devicename [IPv6 numeric, with literal port number]
	
	\{
*/


/*!
	\brief String that will be used to determine the type of source in use (file,
	remote/local interface).

	This string will be prepended to the interface name in order to create a string
	that contains all the information required to open the source.

	This string indicates that the user wants to open a capture from a local file.
*/
#define PCAP_SRC_FILE_STRING "file://"
/*!
	\brief String that will be used to determine the type of source in use (file,
	remote/local interface).

	This string will be prepended to the interface name in order to create a string
	that contains all the information required to open the source.

	This string indicates that the user wants to open a capture from a network interface.
	This string does not necessarily involve the use of the RPCAP protocol. If the
	interface required resides on the local host, the RPCAP protocol is not involved
	and the local functions are used.
*/
#define PCAP_SRC_IF_STRING "rpcap://"

/*!
	\}
*/





/*!
	\addtogroup remote_open_flags
	\{
*/

/*!
	\brief Defines if the adapter has to go in promiscuous mode.

	It is '1' if you have to open the adapter in promiscuous mode, '0' otherwise.
	Note that even if this parameter is false, the interface could well be in promiscuous
	mode for some other reason (for example because another capture process with 
	promiscuous mode enabled is currently using that interface).
	On on Linux systems with 2.2 or later kernels (that have the "any" device), this
	flag does not work on the "any" device; if an argument of "any" is supplied,
	the 'promisc' flag is ignored.
*/
#define PCAP_OPENFLAG_PROMISCUOUS		1

/*!
	\brief Defines if the data trasfer (in case of a remote
	capture) has to be done with UDP protocol.

	If it is '1' if you want a UDP data connection, '0' if you want
	a TCP data connection; control connection is always TCP-based.
	A UDP connection is much lighter, but it does not guarantee that all
	the captured packets arrive to the client workstation. Moreover, 
	it could be harmful in case of network congestion.
	This flag is meaningless if the source is not a remote interface.
	In that case, it is simply ignored.
*/
#define PCAP_OPENFLAG_DATATX_UDP			2


/*!
	\brief Defines if the remote probe will capture its own generated traffic.

	In case the remote probe uses the same interface to capture traffic and to send
	data back to the caller, the captured traffic includes the RPCAP traffic as well.
	If this flag is turned on, the RPCAP traffic is excluded from the capture, so that
	the trace returned back to the collector is does not include this traffic.
*/
#define PCAP_OPENFLAG_NOCAPTURE_RPCAP	4

/*!
	\brief Defines if the local adapter will capture its own generated traffic.

	This flag tells the underlying capture driver to drop the packets that were sent by itself. 
	This is usefult when building applications like bridges, that should ignore the traffic
	they just sent.
*/
#define PCAP_OPENFLAG_NOCAPTURE_LOCAL	8

/*!
	\brief This flag configures the adapter for maximum responsiveness.

	In presence of a large value for nbytes, WinPcap waits for the arrival of several packets before 
	copying the data to the user. This guarantees a low number of system calls, i.e. lower processor usage, 
	i.e. better performance, which is good for applications like sniffers. If the user sets the 
	PCAP_OPENFLAG_MAX_RESPONSIVENESS flag, the capture driver will copy the packets as soon as the application 
	is ready to receive them. This is suggested for real time applications (like, for example, a bridge) 
	that need the best responsiveness.*/
#define PCAP_OPENFLAG_MAX_RESPONSIVENESS	16

/*!
	\}
*/


/*!
	\addtogroup remote_samp_methods
	\{
*/

/*!
	\brief No sampling has to be done on the current capture.

	In this case, no sampling algorithms are applied to the current capture.
*/
#define PCAP_SAMP_NOSAMP	0

/*!
	\brief It defines that only 1 out of N packets must be returned to the user.

	In this case, the 'value' field of the 'pcap_samp' structure indicates the
	number of packets (minus 1) that must be discarded before one packet got accepted.
	In other words, if 'value = 10', the first packet is returned to the caller, while
	the following 9 are discarded.
*/
#define PCAP_SAMP_1_EVERY_N	1

/*!
	\brief It defines that we have to return 1 packet every N milliseconds.

	In this case, the 'value' field of the 'pcap_samp' structure indicates the 'waiting
	time' in milliseconds before one packet got accepted.
	In other words, if 'value = 10', the first packet is returned to the caller; the next 
	returned one will be the first packet that arrives when 10ms have elapsed. 
*/
#define PCAP_SAMP_FIRST_AFTER_N_MS 2

/*!
	\}
*/


/*!
	\addtogroup remote_auth_methods
	\{
*/

/*!
	\brief It defines the NULL authentication.

	This value has to be used within the 'type' member of the pcap_rmtauth structure.
	The 'NULL' authentication has to be equal to 'zero', so that old applications
	can just put every field of struct pcap_rmtauth to zero, and it does work.
*/
#define RPCAP_RMTAUTH_NULL 0
/*!
	\brief It defines the username/password authentication.

	With this type of authentication, the RPCAP protocol will use the username/
	password provided to authenticate the user on the remote machine. If the
	authentication is successful (and the user has the right to open network devices)
	the RPCAP connection will continue; otherwise it will be dropped.

	This value has to be used within the 'type' member of the pcap_rmtauth structure.
*/
#define RPCAP_RMTAUTH_PWD 1

/*!
	\}
*/




/*!

	\brief This structure keeps the information needed to autheticate
	the user on a remote machine.
	
	The remote machine can either grant or refuse the access according 
	to the information provided.
	In case the NULL authentication is required, both 'username' and
	'password' can be NULL pointers.
	
	This structure is meaningless if the source is not a remote interface;
	in that case, the functions which requires such a structure can accept
	a NULL pointer as well.
*/
struct pcap_rmtauth
{
	/*!
		\brief Type of the authentication required.

		In order to provide maximum flexibility, we can support different types
		of authentication based on the value of this 'type' variable. The currently 
		supported authentication methods are defined into the
		\link remote_auth_methods Remote Authentication Methods Section\endlink.

	*/
	int type;
	/*!
		\brief Zero-terminated string containing the username that has to be 
		used on the remote machine for authentication.
		
		This field is meaningless in case of the RPCAP_RMTAUTH_NULL authentication
		and it can be NULL.
	*/
	char *username;
	/*!
		\brief Zero-terminated string containing the password that has to be 
		used on the remote machine for authentication.
		
		This field is meaningless in case of the RPCAP_RMTAUTH_NULL authentication
		and it can be NULL.
	*/
	char *password;
};


/*!
	\brief This structure defines the information related to sampling.

	In case the sampling is requested, the capturing device should read
	only a subset of the packets coming from the source. The returned packets depend
	on the sampling parameters.

	\warning The sampling process is applied <strong>after</strong> the filtering process.
	In other words, packets are filtered first, then the sampling process selects a
	subset of the 'filtered' packets and it returns them to the caller.
*/
struct pcap_samp
{
	/*!
		Method used for sampling. Currently, the supported methods are listed in the
		\link remote_samp_methods Sampling Methods Section\endlink.
	*/
	int method;

	/*!
		This value depends on the sampling method defined. For its meaning, please check
		at the \link remote_samp_methods Sampling Methods Section\endlink.
	*/
	int value;
};




//! Maximum lenght of an host name (needed for the RPCAP active mode)
#define RPCAP_HOSTLIST_SIZE 1024


/*!
	\}
*/ // end of public documentation


// Exported functions



/** \name New WinPcap functions

	This section lists the new functions that are able to help considerably in writing
	WinPcap programs because of their easiness of use.
 */
//\{
pcap_t *pcap_open(const char *source, int snaplen, int flags, int read_timeout, struct pcap_rmtauth *auth, char *errbuf);
int pcap_createsrcstr(char *source, int type, const char *host, const char *port, const char *name, char *errbuf);
int pcap_parsesrcstr(const char *source, int *type, char *host, char *port, char *name, char *errbuf);
int pcap_findalldevs_ex(char *source, struct pcap_rmtauth *auth, pcap_if_t **alldevs, char *errbuf);
struct pcap_samp *pcap_setsampling(pcap_t *p);

//\}
// End of new winpcap functions



/** \name Remote Capture functions
 */
//\{ 
SOCKET pcap_remoteact_accept(const char *address, const char *port, const char *hostlist, char *connectinghost, struct pcap_rmtauth *auth, char *errbuf);
int pcap_remoteact_list(char *hostlist, char sep, int size, char *errbuf);
int pcap_remoteact_close(const char *host, char *errbuf);
void pcap_remoteact_cleanup();
//\}
// End of remote capture functions

#ifdef __cplusplus
}
#endif


#endif

?? 快捷鍵說明

復制代碼 Ctrl + C
搜索代碼 Ctrl + F
全屏模式 F11
切換主題 Ctrl + Shift + D
顯示快捷鍵 ?
增大字號 Ctrl + =
減小字號 Ctrl + -
亚洲欧美第一页_禁久久精品乱码_粉嫩av一区二区三区免费野_久草精品视频
中文字幕精品一区二区精品绿巨人| 在线观看日韩国产| 精品成人一区二区三区四区| 日产国产欧美视频一区精品| 日韩精品一区二区三区三区免费 | 久久久久97国产精华液好用吗| 激情欧美一区二区| 欧美国产激情一区二区三区蜜月| 福利一区二区在线观看| 亚洲免费视频中文字幕| 欧美视频完全免费看| 蜜桃视频一区二区三区在线观看| 久久麻豆一区二区| 91在线观看高清| 国产精品91xxx| 亚洲美女在线一区| 欧美精品在线观看一区二区| 激情图区综合网| 中文字幕中文字幕中文字幕亚洲无线| 91在线国产福利| 日本伊人精品一区二区三区观看方式| 精品对白一区国产伦| 99精品在线观看视频| 亚洲最新在线观看| 久久综合色鬼综合色| 99久久免费视频.com| 日韩精品一级二级| 中文字幕精品一区二区精品绿巨人| 欧洲精品一区二区三区在线观看| 蜜桃av噜噜一区| 中文字幕一区av| 欧美一二三区在线观看| 不卡的看片网站| 日韩电影一区二区三区| 国产精品丝袜一区| 欧美一级午夜免费电影| 99久久精品国产网站| 麻豆一区二区99久久久久| 亚洲男人的天堂在线aⅴ视频| 日韩欧美二区三区| 日本韩国欧美一区二区三区| 国产尤物一区二区在线| 夜夜亚洲天天久久| 国产午夜精品一区二区三区视频 | 中文字幕免费不卡在线| 欧美卡1卡2卡| 91麻豆免费看片| 国产精品1区2区3区| 午夜私人影院久久久久| 中文字幕一区av| 国产亚洲成年网址在线观看| 这里只有精品电影| 欧美视频精品在线| 97精品国产97久久久久久久久久久久 | 国产99一区视频免费| 日韩精品成人一区二区在线| 亚洲欧美日韩国产综合| 国产午夜精品一区二区三区视频 | 精品国产一区二区三区久久久蜜月| 欧美影视一区二区三区| 99久久久精品免费观看国产蜜| 国产最新精品免费| 麻豆成人av在线| 美女在线视频一区| 日韩精品成人一区二区在线| 亚洲国产一区视频| 一区二区三区在线免费观看 | 欧美va在线播放| 91精品黄色片免费大全| 欧美日韩dvd在线观看| 欧美网站大全在线观看| 欧美亚洲国产一卡| 色94色欧美sute亚洲13| 91猫先生在线| 91行情网站电视在线观看高清版| bt欧美亚洲午夜电影天堂| 成人深夜视频在线观看| 国产99久久精品| 成人精品免费网站| www.综合网.com| aaa国产一区| 色噜噜偷拍精品综合在线| 91久久精品一区二区三| 日本高清不卡aⅴ免费网站| 色悠久久久久综合欧美99| 色94色欧美sute亚洲线路二| 欧美中文字幕亚洲一区二区va在线| 在线观看不卡一区| 91.xcao| 精品国产乱码久久久久久老虎| 精品国产凹凸成av人导航| 久久久亚洲午夜电影| 欧美激情在线看| 亚洲欧洲在线观看av| 最新国产の精品合集bt伙计| 亚洲精品日韩一| 视频一区二区欧美| 国产做a爰片久久毛片| 成人精品国产福利| 欧美综合在线视频| 日韩一区二区三区av| 久久婷婷成人综合色| 中文字幕一区二区日韩精品绯色| 一区二区三区精品视频| 日韩国产精品91| 国产一本一道久久香蕉| 99国产麻豆精品| 欧美精品高清视频| 国产视频一区不卡| 亚洲一区视频在线| 精品一区二区免费视频| 99re热这里只有精品免费视频 | 大美女一区二区三区| 在线看日本不卡| 精品日本一线二线三线不卡| 国产精品久久久爽爽爽麻豆色哟哟| 亚洲国产精品自拍| 国产精品亚洲专一区二区三区| 色婷婷激情一区二区三区| 日韩精品一区二区三区在线观看 | 日韩限制级电影在线观看| 国产精品青草综合久久久久99| 亚洲一级二级三级| 国产又黄又大久久| 欧洲国内综合视频| 国产农村妇女精品| 日韩国产欧美在线观看| 99久久综合精品| 日韩欧美在线综合网| 亚洲激情成人在线| 国产精品资源网站| 884aa四虎影成人精品一区| 国产精品精品国产色婷婷| 日本不卡一区二区三区| 91麻豆成人久久精品二区三区| 日韩欧美一级在线播放| 一区二区三区波多野结衣在线观看 | 精品一区二区三区久久| 欧美专区在线观看一区| 中文字幕在线视频一区| 久久99精品一区二区三区三区| 色94色欧美sute亚洲线路二| 国产欧美一区二区精品久导航 | 精品久久一区二区三区| 亚洲线精品一区二区三区 | 91网站最新网址| 久久久久亚洲蜜桃| 日韩黄色免费网站| 欧美性猛交xxxx乱大交退制版| 亚洲欧洲日韩一区二区三区| 国产曰批免费观看久久久| 日韩精品中午字幕| 婷婷丁香久久五月婷婷| 日本道在线观看一区二区| 国产精品女主播在线观看| 国产高清一区日本| 26uuu国产日韩综合| 久久精品国产澳门| 欧美一区二区在线免费观看| 偷拍自拍另类欧美| 欧美日韩在线不卡| 亚洲va欧美va国产va天堂影院| 色婷婷综合久久久| 亚洲欧美日韩久久| 色婷婷av一区二区三区软件| 最新日韩av在线| 91美女片黄在线观看| 亚洲精品中文在线观看| 色欧美日韩亚洲| 亚洲午夜国产一区99re久久| 欧美亚洲一区二区三区四区| 亚洲成人免费看| 欧美片网站yy| 奇米色一区二区三区四区| 欧美精三区欧美精三区| 青青草原综合久久大伊人精品| 欧美一级在线视频| 极品少妇一区二区| 国产亚洲欧洲997久久综合| 国产**成人网毛片九色 | 精品国产在天天线2019| 国产精品中文字幕日韩精品| 欧美国产精品一区二区三区| 成人高清av在线| 亚洲精品国产视频| 欧美日韩亚洲高清一区二区| 青青草原综合久久大伊人精品优势 | 亚洲欧美激情插| 欧美色图激情小说| 蜜臂av日日欢夜夜爽一区| 久久久综合精品| 色综合久久99| 日本午夜精品视频在线观看| 精品国产一区二区精华| bt欧美亚洲午夜电影天堂| 岛国精品一区二区| 亚洲欧美日韩系列| 欧美一级免费大片| 成人晚上爱看视频| 日韩激情一区二区|