There are several classifications of firewalls depending on where the communication is taking place, where the communication is intercepted and the state that is being traced. Network layer firewalls, also called packet filters, operate at a relatively low level of the TCP/IP protocol stack, not allowing packets to pass through the firewall unless they match the established rule set. The firewall administrator may define the rules; or default rules may apply. The term "packet filter" originated in the context of BSD operating systems. Network layer firewalls generally fall into two sub-categories, stateful and stateless. Stateful firewalls maintain context about active sessions, and use that "state information" to speed packet processing. Any existing network connection can be described by several properties, including source and destination IP address, UDP or TCP ports, and the current stage of the connection's lifetime (including session initiation,handshaking, data transfer, or completion connection). If a packet does not match an existing connection, it will be evaluated according to the ruleset for new connections. If a packet matches an existing connection based on comparison with the firewall's state table, it will be allowed to pass without further processing. Stateless firewalls require less memory, and can be faster for simple filters that require less time to filter than to look up a session. They may also be necessary for filtering stateless network protocols that have no concept of a session. However, they cannot make more complex decisions based on what stage communications between hosts have reached. Modern firewalls can filter traffic based on many packet attributes like source IP address, source port, destination IP address or port, destination service like WWW or FTP. They can filter based on protocols, TTL values, netblock of originator, of the source, and many other attributes. Commonly used packet filters on various versions of Unix are ipf (various), ipfw (FreeBSD/Mac OS X), pf (OpenBSD, and all other BSDs),iptables/ipchains (Linux). Application-layer firewalls work on the application level of the TCP/IP stack (i.e., all browser traffic, or all telnet> or ftp> traffic), and may intercept all packets traveling to or from an application. They block other packets (usually dropping them without acknowledgment to the sender). In principle, application firewalls can prevent all unwanted outside traffic from reaching protected machines. On inspecting all packets for improper content, firewalls can restrict or prevent outright the spread of networked computer worms and trojans. The additional inspection criteria can add extra latency to the forwarding of packets to their destination.Network layer and packet filters
Application-layer
A web hosting service is a type of Internet hosting service that allows individuals and organizations to make their own website accessible via the World Wide Web. Web hosts are companies that provide space on a server they own or lease for use by their clients as well as providing Internet connectivity.
Blog Archive
-
▼
2009
(30)
-
▼
November
(24)
- web servers...
- Overload causesAt any time web servers can be over...
- web hosting
- web hosting Service scope
- web hosting uptime
- types of web hosting
- types of web hosting cont'd...
- Obtaining web hosting
- Firewall
- types of firewall
- function of firewall
- history of firewall
- history of firewall First generation - packet filters
- firewall-other generations
- firewall types
- proxy
- Network address translation
- what is spam ?
- E-Mail Spam
- spam overview
- types
- Spam techniques
- What Is a Yahoo Domain?
- server overview
-
▼
November
(24)
12:36 PM
Main article: Application layer firewall
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment