Installation guide

Packet filtering 30-10
Chapter 30: Understanding Wave Data Networking
Wave Global Administrator Guide
Static routes
In a small (single subnet) network environment, particularly with only one point of entry to the
Internet, you can use static routing instead of configuring RIP or OSPF. In static routing, the
routes do not change once you set them. However, this also means that if any network failures
occur, there are no other paths available in the network to route around the failure.
The Wave Server uses RRAS, a software router, as a LAN-to-LAN, LAN-to-WAN, and
WAN-to-WAN router for IP traffic. RRAS IP routing is installed and enabled by default, so
LAN routing configuration is, for the most part, automatic. Depending on your particular Wave
configuration, you may need to configure routing protocols and/or LAN-to-WAN interfaces.
Routing protocols for static routes
The Wave Server supports two protocols for dynamic routing: RIP and OSPF. Without RIP or
OSPF enabled, IP only forwards packets between static routes on subnets. In addition, the Wave
Server supports IPX for routing between Novell NetWare servers.
For information about configuring RIP, see “Configuring routing information protocol (RIP)”
on page 21-3.
Packet filtering
Packet filtering is a way of restricting network traffic on an interface to just those packets that
match a given pattern. This is typically done to provide a level of security against untrusted
networks (such as the Internet) or to conserve bandwidth on WAN interfaces.
Since the patterns are fairly simple, packet filtering does not afford the same level of security or
configuration as a network firewall or proxy. However, it is sufficient for many environments,
and can also be used in addition to more sophisticated methods. Packet filters in Wave only
support the Internet Protocol (IP) and those that utilize IP, such as TCP, UDP, and ICMP.
The following sections describe packet filters and how to use them in different environments.
In many cases, multiple environments might apply. For example, Wave can support one or more
interfaces with filters for a private network, a DMZ network, the Internet, and port filters.
Release 2.0
September 2010