DOCSLIB.ORG

Apex Filters User Guide Table of Contents

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Apex Filters User Guide Table of Contents Apex Filters User Guide Table of Contents Chapter 1: Apex filters.........................................................................................................................4 Boolean operators used in filter expressions............................................................................................7 app..................................................................................................................................................................8 browser...........................................................................................................................................................9 browserPlatform.........................................................................................................................................10 browserVersion........................................................................................................................................... 11 dataSource.................................................................................................................................................. 12 ethertype......................................................................................................................................................13 fixRequest.................................................................................................................................................... 15 fixResponse..................................................................................................................................................17 flowidx..........................................................................................................................................................19 flowidxclient................................................................................................................................................20 flowidxserver...............................................................................................................................................21 flowsystem...................................................................................................................................................22 flowsystemclient......................................................................................................................................... 23 flowsystemserver........................................................................................................................................ 24 ip................................................................................................................................................................... 25 ipclient..........................................................................................................................................................26 ipproto..........................................................................................................................................................27 ipserver.........................................................................................................................................................28 link................................................................................................................................................................ 29 mac...............................................................................................................................................................30 macclient..................................................................................................................................................... 31 macserver.................................................................................................................................................... 32 mpls.............................................................................................................................................................. 33 mplsclient.................................................................................................................................................... 34 mplsserver................................................................................................................................................... 35 networkType................................................................................................................................................36 port............................................................................................................................................................... 37 portclient......................................................................................................................................................38 portserver.................................................................................................................................................... 39 sql..................................................................................................................................................................40 streamId.......................................................................................................................................................41 streamName................................................................................................................................................42 subnetRange............................................................................................................................................... 43 url..................................................................................................................................................................44 vlan...............................................................................................................................................................45 voipCall........................................................................................................................................................ 46 voipDeviceIp................................................................................................................................................47 voipIpType................................................................................................................................................... 48 voipStationIp...............................................................................................................................................49 Index....................................................................................................................................................50 Table of Contents (23 Jan 2016) — Archive/Non-authoritative version 3 1 Chapter 1: Apex filters Conventions used in this document: Filters typed by the user will be shown in Bold Courier ♦ Filter names are written in red. ♦ Angled brackets < and > surround required arguments. ♦ Square brackets [ and ] surround optional arguments. ♦ Choices are separated by a vertical bar |. ♦ Single quotes ' ' are required for any parameter or text containing a space. ♦ Filter names are case sensitive (for instance, fixRequest or networkType). ♦ Parameters are case-insensitive. app (page 8) Application or derived application being transported across the network. browser (page Brand of the web browser being used. 9) browserPlatform Type of device on which the web browser was used. (page 10) browserVersion Version of the web browser. (page 11) dataSource (page Business group or probe instance name. This is required if you 12) want to drill into GigaStor data. ethertype (page Layer 3 protocol encapsulated in the first two octets of an 13) Ethernet frame. fixRequest (page Request in the financial trading FIX protocol. 15) fixResponse (page Response in the financial trading FIX protocol. 17) flowidx (page NetFlow interface. 19) flowidxclient (page NetFlow Client interface when using the NetFlow Interface 20) Index - Client key. flowidxserver (page NetFlow Server interface when using the NetFlow Interface 21) Index - Server key. flowsystem (page Netflow Autonomous System. 22) flowsystemclient Client of a Netflow Autonomous System when using the (page 23) Netflow Autonomous System - Client key. flowsystemserver Server of a Netflow Autonomous System when using the (page 24) Netflow Autonomous System - Server key. ip (page 25) IPv4 or IPv6 address or range of addresses. ipclient (page IPv4 or IPv6 address (or range of addresses) of a client if you are 26) using the IP - Client key. ipproto (page IP-based protocol that works with the Application and 27) Protocol keys. ipserver (page IPv4 or IPv6 address (or range of addresses) of a server if you are 28) using the IP - Server key. link (page 29) Link protocol from the logical link control layer of a switch. mac (page 30) MAC address macclient (page MAC address of a client when using the MAC - Client key. 31) mpls (page 33) MPLS label. mplsclient (page MPLS label for a client when using the MPLS Label - Client key. 34) mplsserver (page MPLS label for a server when using the MPLS Label - Server 35) key. networkType (page Kind of network generating the traffic when using the Network 36) Type key. port (page 37) Trading multicast port when using any of the Port, Port - Client, or Port - Server keys. portclient (page Trading multicast port on a client when using the Port - Client 38) key. portserver (page Trading multicast port on
Load more

Recommended publications
  • Logical Link Control and Channel Scheduling for Multichannel Underwater Sensor Networks
    ICST Transactions on Mobile Communications and Applications Research Article Logical Link Control and Channel Scheduling for Multichannel Underwater Sensor Networks Jun Li ∗, Mylene` Toulgoat, Yifeng Zhou, and Louise Lamont Communications Research Centre Canada, 3701 Carling Avenue, Ottawa, ON. K2H 8S2 Canada Abstract With recent developments in terrestrial wireless networks and advances in acoustic communications, multichannel technologies have been proposed to be used in underwater networks to increase data transmission rate over bandwidth-limited underwater channels. Due to high bit error rates in underwater networks, an efficient error control technique is critical in the logical link control (LLC) sublayer to establish reliable data communications over intrinsically unreliable underwater channels. In this paper, we propose a novel protocol stack architecture featuring cross-layer design of LLC sublayer and more efficient packet- to-channel scheduling for multichannel underwater sensor networks. In the proposed stack architecture, a selective-repeat automatic repeat request (SR-ARQ) based error control protocol is combined with a dynamic channel scheduling policy at the LLC sublayer. The dynamic channel scheduling policy uses the channel state information provided via cross-layer design. It is demonstrated that the proposed protocol stack architecture leads to more efficient transmission of multiple packets over parallel channels. Simulation studies are conducted to evaluate the packet delay performance of the proposed cross-layer protocol stack architecture with two different scheduling policies: the proposed dynamic channel scheduling and a static channel scheduling. Simulation results show that the dynamic channel scheduling used in the cross-layer protocol stack outperforms the static channel scheduling. It is observed that, when the dynamic channel scheduling is used, the number of parallel channels has only an insignificant impact on the average packet delay.
    [Show full text]
  • Comodo System Cleaner Version 3.0
    Comodo System Cleaner Version 3.0 User Guide Version 3.0.122010 Versi Comodo Security Solutions 525 Washington Blvd. Jersey City, NJ 07310 Comodo System Cleaner - User Guide Table of Contents 1.Comodo System-Cleaner - Introduction ............................................................................................................ 3 1.1.System Requirements...........................................................................................................................................5 1.2.Installing Comodo System-Cleaner........................................................................................................................5 1.3.Starting Comodo System-Cleaner..........................................................................................................................9 1.4.The Main Interface...............................................................................................................................................9 1.5.The Summary Area.............................................................................................................................................11 1.6.Understanding Profiles.......................................................................................................................................12 2.Registry Cleaner............................................................................................................................................. 15 2.1.Clean.................................................................................................................................................................16
    [Show full text]
  • HTTP Cookie - Wikipedia, the Free Encyclopedia 14/05/2014
    HTTP cookie - Wikipedia, the free encyclopedia 14/05/2014 Create account Log in Article Talk Read Edit View history Search HTTP cookie From Wikipedia, the free encyclopedia Navigation A cookie, also known as an HTTP cookie, web cookie, or browser HTTP Main page cookie, is a small piece of data sent from a website and stored in a Persistence · Compression · HTTPS · Contents user's web browser while the user is browsing that website. Every time Request methods Featured content the user loads the website, the browser sends the cookie back to the OPTIONS · GET · HEAD · POST · PUT · Current events server to notify the website of the user's previous activity.[1] Cookies DELETE · TRACE · CONNECT · PATCH · Random article Donate to Wikipedia were designed to be a reliable mechanism for websites to remember Header fields Wikimedia Shop stateful information (such as items in a shopping cart) or to record the Cookie · ETag · Location · HTTP referer · DNT user's browsing activity (including clicking particular buttons, logging in, · X-Forwarded-For · Interaction or recording which pages were visited by the user as far back as months Status codes or years ago). 301 Moved Permanently · 302 Found · Help 303 See Other · 403 Forbidden · About Wikipedia Although cookies cannot carry viruses, and cannot install malware on 404 Not Found · [2] Community portal the host computer, tracking cookies and especially third-party v · t · e · Recent changes tracking cookies are commonly used as ways to compile long-term Contact page records of individuals' browsing histories—a potential privacy concern that prompted European[3] and U.S.
    [Show full text]
  • Web Browser Pioneer Backs New Way to Surf Internet (Update 2) 7 November 2010, by MICHAEL LIEDTKE , AP Technology Writer
    Web browser pioneer backs new way to surf Internet (Update 2) 7 November 2010, By MICHAEL LIEDTKE , AP Technology Writer (AP) -- The Web has changed a lot since Marc Facebook's imprint also is all over RockMelt, Andreessen revolutionized the Internet with the although the two companies' only business introduction of his Netscape browser in the connection so far is Andreessen. He also serves on mid-1990s. That's why he's betting people are Facebook's board of directors. ready to try a different Web-surfing technique on a new browser called RockMelt. RockMelt only works if you have a Facebook account. That restriction still gives RockMelt plenty The browser, available for the first time Monday, is of room to grow, given Facebook has more than built on the premise that most online activity today 500 million users. revolves around socializing on Facebook, searching on Google, tweeting on Twitter and After Facebook users log on RockMelt with their monitoring a handful of favorite websites. It tries to Facebook account information, the person's minimize the need to roam from one website to the Facebook profile picture is planted in the browser's next by corralling all vital information and favorite left hand corner and a list of favorite friends can be services in panes and drop-down windows. displayed in the browser's left hand pane. There's also a built-in tool for posting updates in a pop-up "This is a chance for us to build a browser all over box. again," Andreessen said. "These are all things we would have done (at Netscape) if we had known The features extend beyond Facebook and Twitter.
    [Show full text]
  • Medium Access Control Layer
    Telematics Chapter 5: Medium Access Control Sublayer User Server watching with video Beispielbildvideo clip clips Application Layer Application Layer Presentation Layer Presentation Layer Session Layer Session Layer Transport Layer Transport Layer Network Layer Network Layer Network Layer Univ.-Prof. Dr.-Ing. Jochen H. Schiller Data Link Layer Data Link Layer Data Link Layer Computer Systems and Telematics (CST) Physical Layer Physical Layer Physical Layer Institute of Computer Science Freie Universität Berlin http://cst.mi.fu-berlin.de Contents ● Design Issues ● Metropolitan Area Networks ● Network Topologies (MAN) ● The Channel Allocation Problem ● Wide Area Networks (WAN) ● Multiple Access Protocols ● Frame Relay (historical) ● Ethernet ● ATM ● IEEE 802.2 – Logical Link Control ● SDH ● Token Bus (historical) ● Network Infrastructure ● Token Ring (historical) ● Virtual LANs ● Fiber Distributed Data Interface ● Structured Cabling Univ.-Prof. Dr.-Ing. Jochen H. Schiller ▪ cst.mi.fu-berlin.de ▪ Telematics ▪ Chapter 5: Medium Access Control Sublayer 5.2 Design Issues Univ.-Prof. Dr.-Ing. Jochen H. Schiller ▪ cst.mi.fu-berlin.de ▪ Telematics ▪ Chapter 5: Medium Access Control Sublayer 5.3 Design Issues ● Two kinds of connections in networks ● Point-to-point connections OSI Reference Model ● Broadcast (Multi-access channel, Application Layer Random access channel) Presentation Layer ● In a network with broadcast Session Layer connections ● Who gets the channel? Transport Layer Network Layer ● Protocols used to determine who gets next access to the channel Data Link Layer ● Medium Access Control (MAC) sublayer Physical Layer Univ.-Prof. Dr.-Ing. Jochen H. Schiller ▪ cst.mi.fu-berlin.de ▪ Telematics ▪ Chapter 5: Medium Access Control Sublayer 5.4 Network Types for the Local Range ● LLC layer: uniform interface and same frame format to upper layers ● MAC layer: defines medium access ..
    [Show full text]
  • Böngésző Programok 23. Tétel
    23.tétel 1.0 Böngész ő programok használata, összehasonlítása. Az információ keresés technikái. Bogdán;Sleisz Böngész ő programok (Használata, összehasonlítása. Az információ keresés technikái) 23. tétel Az Internet kialakulása 20. század második felére helyezhet ő. Az ARPA rendszerb ől fejl ődött tovább az USA-ban, azóta folyamatosan fejlesztgetik a különböz ő protokollokat, illetve technológiákat, az adatforgalom sebességének növelése érdekében. Komoly tévhitet képez a világban, hogy az Internet az a böngész őben megjeleníthet ő weboldalak összessége. Nagy tévedés, ugyanis ez csak a HTTP protokoll által szolgáltatott tartalom, amely a teljes internetes adatforgalomnak kevesebb, mint az 1/10-ét képezi. Az internetet úgy kell elképzelni, mint egy hardvereszközt, ami az egész világot lefedi, a rajta elérhet ő szolgáltatásokat pedig nevezzük "szoftvereknek". Kétségkívül az egyik legelterjedtebb szolgáltatás ("szoftver") a 80-as port -on kommunikáló HTTP protokoll, amihez tartozik egy kommunikációs nyelv is. A HTTP protokoll célja hagyományos esetben- a távoli "szerveren/kiszolgálón" elhelyezked ő weboldal letöltése a helyi számítógépre. 1. A böngész ő a HTTP kommunikációs nyelven megfogalmazott kérést küld a szerver felé, hogy szeretnénk megjeleníteni a kért weboldalt 2. A szerver válaszol. Többféle üzenetet küldhet vissza a böngész őnek, és minden üzenethez tartozik egy azonosító szám is, úgynevezett Status Code. A legismertebb visszatérési érték talán a Not Found (a keresett weboldal nem található), melynek Status Code-ja a 404. Ilyet könnyedén el őidézhetünk, ha pl. nem létez ő oldalt próbálunk letölteni. A leggyakoribb azonban, ha a 200-as üzenetet kapjuk vissza, vagyis megjelenik az oldal. 3. Ezek után a böngész ő elkezdi letölteni a kért oldal forráskódját . A forráskód egy olyan leíró kód nagyrészt HTML nyelven, amely leírja, hogyan néz ki a weboldal.
    [Show full text]
  • GS970M Datasheet
    Switches | Product Information CentreCOM® GS970M Series Managed Gigabit Ethernet Switches The Allied Telesis CentreCOM GS970M Series of Layer 3 Gigabit switches offer an impressive set of features in a compact design, making them ideal for applications at the network edge. STP root guard ۼۼ Overview Management (UniDirectional Link Detection (UDLD ۼۼ Allied Telesis Autonomous Management ۼۼ Allied Telesis CentreCOM GS970M Series switches provide an excellent Framework™ (AMF) enables powerful centralized management and zerotouch device installation and Security Features access solution for today’s networks, recovery Access Control Lists (ACLs) based on Layer 2, 3 ۼۼ supporting Gigabit to the desktop for Console management port on the front panel for and 4 headers ۼۼ maximum performance. The Power ease of access Configurable auth-fail and guest VLANs ۼۼ Eco-friendly mode allows ports and LEDs to be ۼۼ over Ethernet Plus (PoE+) models Authentication, Authorization, and Accounting ۼۼ provide an ideal solution for connecting disabled to save power (AAA) Industry-standard CLI with context-sensitive help ۼ and remotely powering wireless access ۼ ۼ Bootloader can be password protected for device ۼ ,points, IP video surveillance cameras Powerful CLI scripting engine security ۼۼ ۼ and IP phones. The GS970M models BPDU protection ۼۼ -Comprehensive SNMP MIB support for standards ۼ feature 8, 16 or 24 Gigabit ports, based device management ۼ DHCP snooping, IP source guard and Dynamic ARP ۼ and 2 or 4 SFP uplinks, for secure (Built-in text editor Inspection
    [Show full text]
  • Detecting and Analyzing Insecure Component Integration
    Taeho Kwon December 2011 Computer Science Detecting and Analyzing Insecure Component Integration Abstract Component technologies have been widely adopted for designing and engineering software ap- plications and systems, which dynamically integrate software components to achieve desired func- tionalities. Engineering software in a component-based style has significant benefits, such as im- proved programmer productivity and software reliability. To support component integration, oper- ating systems allow an application to dynamically load and use a component. Although developers have frequently utilized such a system-level mechanism, programming errors can lead to insecure component integration and serious security vulnerabilities. The security and reliability impact of component integration has not yet been much explored. This dissertation systematically investigates security issues in dynamic component integration and their impact on software security. On the conceptual level, we formulate two types of insecure component integration—unsafe component loading and insecure component usage—and present practical, scalable techniques to detect and analyze them. Our techniques operate directly on soft- ware binaries and do not require source code. On the practical level, we have used them to discover new vulnerabilities in popular, real-world software, and show that insecure component integration is prevalent and can be exploited by attackers to subvert important software and systems. Our research has had substantial practical impact and helped
    [Show full text]
  • Communications Programming Concepts
    AIX Version 7.1 Communications Programming Concepts IBM Note Before using this information and the product it supports, read the information in “Notices” on page 323 . This edition applies to AIX Version 7.1 and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2010, 2014. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this document............................................................................................vii How to use this document..........................................................................................................................vii Highlighting.................................................................................................................................................vii Case-sensitivity in AIX................................................................................................................................vii ISO 9000.....................................................................................................................................................vii Communication Programming Concepts................................................................. 1 Data Link Control..........................................................................................................................................1 Generic Data Link Control Environment Overview...............................................................................
    [Show full text]
  • Tutorial on Network Communications and Security
    Lecture Notes Introduction to Digital Networks and Security Raj Bridgelall, PhD © Raj Bridgelall, PhD (North Dakota State University, College of Business) Page 1/23 Table of Contents PART I – NETWORKING CONCEPTS.....................................................................................4 1 INTRODUCTION..................................................................................................................4 2 DATA COMMUNICATIONS ..............................................................................................4 2.1 THE OSI MODEL ...............................................................................................................4 2.2 NETWORKING DEVICES .....................................................................................................5 2.3 TCP/IP ..............................................................................................................................6 3 MOBILE IP ............................................................................................................................7 3.1 FIREWALLS........................................................................................................................9 3.2 DHCP AND DNS ..............................................................................................................9 3.3 IPV6 ................................................................................................................................10 PART II – CRYPTOGRAPHY AND NETWORK SECURITY .............................................12
    [Show full text]
  • 1.2. OSI Model
    1.2. OSI Model The OSI model classifies and organizes the tasks that hosts perform to prepare data for transport across the network. You should be familiar with the OSI model because it is the most widely used method for understanding and talking about network communications. However, remember that it is only a theoretical model that defines standards for programmers and network administrators, not a model of actual physical layers. Using the OSI model to discuss networking concepts has the following advantages: Provides a common language or reference point between network professionals Divides networking tasks into logical layers for easier comprehension Allows specialization of features at different levels Aids in troubleshooting Promotes standards interoperability between networks and devices Provides modularity in networking features (developers can change features without changing the entire approach) However, you must remember the following limitations of the OSI model: OSI layers are theoretical and do not actually perform real functions. Industry implementations rarely have a layer‐to‐layer correspondence with the OSI layers. Different protocols within the stack perform different functions that help send or receive the overall message. A particular protocol implementation may not represent every OSI layer (or may spread across multiple layers). To help remember the layer names of the OSI model, try the following mnemonic devices: Mnemonic Mnemonic Layer Name (Bottom to top) (Top to bottom) Layer 7 Application Away All Layer 6 Presentation Pizza People Layer 5 Session Sausage Seem Layer 4 Transport Throw To Layer 3 Network Not Need Layer 2 Data Link Do Data Layer 1 Physical Please Processing Have some fun and come up with your own mnemonic for the OSI model, but stick to just one so you don't get confused.
    [Show full text]
  • Mobile Web Development for the Modern Coder Written: 9/18/2013
    Mobile Web Development for the Modern Coder Written: 9/18/2013 By: Brian Dainis of Curotec.com Table of contents 1. Introduction 2. Designing a good user interface 1. Considering usability 2. Keeping it simple 3. Consider the various screen sizes and resolutions 4. Simple navigation 5. No Flash 3. Content and images 4. Mobile ecommerce 5. Types of mobile sites 1. Parallel mobile sites 2. Responsive mobile sites 3. Dynamic serving mobile sites 4. Native mobile applications 5. Using all the technology together 6. Implementation methods 1. Parallel mobile site 2. Dynamic serving 3. Responsive design 4. User initiated methods 5. Pros and cons of each method 7. Mobile web frameworks 8. Debugging issues 9. Improving load time and lowering bandwidth 10. Conclusion 11. Brian Dainis's bio [1] Introduction The Internet has really come a long way in the last 20 years from its early less mainstream form in the 90's. I remember the days of coding HTML sites in tables and using all those very ugly inline style attributes. As I type this I'm reminded of how thankful I am for CSS! Fast forward to 2013 and the Internet has taken on a whole new shape. We are more connected than ever before with the world’s largest information bank in our pockets. It’s no wonder why companies and organizations have taken full advantage of this global market place, which has changed the world in more ways than one. Enter the web developer. As web developers, we are challenged with understanding our client’s objectives, creating an easy to use platform to express those objectives and making sure this platform is cross compatible over various devices and browsers.
    [Show full text]