Page 91 / 131 Scroll up to view Page 86 - 90
6381-A4 Router Users Guide
91
4.
For additional security with RIPv2 check
Enable Password
and enter a password.
Dynamic routing does not required the additional security. RIP v2 provides simple plain-text
password-based authentication to RIP packets. The
Enable Password
field is disabled if
RIP v1 protocol is selected.
5.
From the
Interface
Direction
drop down select the appropriate direction for each interface.
Direction
determines the direction that RIP routes will be updated.
In
The router will only incorporate received RIP information.
Out
The router will only send out RIP information.
Both
The router will incorporate received RIP information and send out updated RIP
information.
None
Dynamic routing is disabled for this interface. Use when dynamic routing is
enabled for other interfaces.
To match the example above:
LAN group 1
:
Both
LAN group 2
:
Both
You also need to enable dynamic routing on the routers 2 and 3.
6.
Click
Apply
The Apply button will temporarily save this connection. To make the change permanent, click
Tools
(at the top of the page) and select
System Commands
. On the
System Commands
page, click
Save All
.
Page 92 / 131
6381-A4 Router Users Guide
92
Quality of Service (QoS)
Quality of Service permits network administrators to prioritize how packets are handled, so that
information with differing requirements, voice, video and data, will work properly. Network
administrator configure routers to handle the different priority packets, however different networks
use differing QoS marking.
Note:
QoS pages are for use by network administrators or Internet Service Providers
(ISP). Users should not configure the Policy Database, Ingress, Egress or Shaper
pages unless directed to do so by their ISP.
A ToS network (Type of Service) uses flags in the IP header to set priorities. A DSCP network
(Differentiated Services Code Point) uses a field in an IP packet to describe different levels of
service to assign to traffic. A VLAN (Virtual LAN as used with Level 2 bridges) uses priority bit in
the VLAN header. WLAN use WLAN QoS header.
To work with the differing means of prioritizing packets and bandwidth, the 6381 maps the other
priority schemes either to or from the CoS priority that it uses. Upon ingress (when the packet
arrives on the WAN or LAN interface of the 6381) the priority is translated to CoS. Upon egress
(when the packet leaves on the WAN or LAN interface of the 6381) the priority is translated from
CoS. These mappings are set by a traffic conditioning agreement (TCA) for each interface:
Ingress = domain mapping to CoS, Egress = CoS mapping to domain. There are also options for
honoring (trusted mode) or not honoring (untrusted mode).
The 6381 uses a Class of Service (CoS) to define priorities. The 6381 uses six classes of CoS:
CoS1, CoS2, CoS3, CoS4, CoS5, and CoS6. CoS1 is the highest priority and CoS6 the lowest.
Page 93 / 131
6381-A4 Router Users Guide
93
Terms:
Ingress: Packets arriving into the RG from a WAN/LAN interface.
Egress: Packets sent from the RG to a WAN/LAN interface.
Trusted mode: Honors the domain mapping (ToS byte, WME, WLAN user priority).
Untrusted mode: Does not honor domain mapping. This is the default QoS setting.
Forwarding rules based on CoS are:
CoS1 has absolute priority and is used for expedited forwarding (EF) traffic. This is always
serviced till completion.
CoS2-CoS5 are used for assured forwarding (AF) classes. They are serviced in a strict round
robin manner using the following priority scheme:
CoS2 > CoS3 > CoS4 > CoS5
CoS6 is for best effort (BE) traffic. This is only serviced when there is no other class of
service. If QoS is not enabled on your RG, all traffic will be treated as best effort.
QoS is defined in the following four GUI pages:
Policy Database
for configuring QoS for multiple connections
Ingress
for ingress mapping from an outside domain
Egress
for egress mapping to an outside domain
Shaping
for determining the servicing of the CoS queues including rate limiting.
Page 94 / 131
6381-A4 Router Users Guide
94
Policy Database
The Policy Database page allows you to configure QoS for multiple WAN connections; you can
classify packets based on fields in the packet. The
Ingress
and
Egress
pages allow you to
configure QoS per interface.
Fields that can be configured for setting policies:
Field
Description
Ingress Interface
The incoming traffic interface for a Policy Routing rule. Selections include LAN
interfaces, WAN interfaces, Locally generated (traffic), and not applicable.
Examples of Locally generated traffic are: voice packets, packets generated by
applications such as DNS, DHCP or other applications.
Destination Interface
The outgoing traffic interfaces for a Policy Routing rule. Selections include LAN
Interfaces and WAN interfaces.
DiffServ Code Point
The diffServ code point (DSCP) field value ranges from 1 to 255. This field
cannot be configured alone; additional fields like IP, Source MAC, and/or
Ingress Interface should be configured.
Class of Service
The selections are (in the order of priority): CoS1, CoS2, CoS3, CoS4, CoS5,
CoS6, and N/A.
Source IP
The IP address of the traffic source. (Wild cards are allowed.)
(Source)
Mask
The source IP netmask. This field is required if the source IP has been entered.
(Wild cards are allowed.)
Destination IP
The IP address of the traffic destination. (Wild cards are allowed.)
(Destination)
Mask
The netmask of the destination. This field is required if the destination IP has
been entered. (Wild cards are allowed.)
Protocol
The selections are TCP, UDP, ICMP, Specify, and none. If you choose Specify,
you need to enter the protocol number in the box next to the Protocol field.
This field cannot be configured alone; additional fields like IP, Source MAC,
and/or Ingress Interface must also be configured.
The
Protocol
field is also required if the source port or destination port has
been entered.
Page 95 / 131
6381-A4 Router Users Guide
95
Source Port
The source protocol port. You cannot configure this field without entering the
protocol first.
Destination Port
The destination protocol port or port range. You cannot configure this field
without entering the protocol first.
Source MAC
The MAC address of the traffic source.
Local Routing Mark
The
Local Routing Mark
field is enabled only when Locally Generated is
selected in the
Ingress Interface
field. The mark for DNS traffic generated by
different applications are described below:
Dynamic DNS: 0xE1
Dynamic Proxy: 0xE2
Web Server: 0xE3
MSNTP: 0xE4
DHCP Server: 0xE5
IPtables Utility: 0xE6
PPP Daemon: 0xE7
IP Route: 0xE8
ATM Library: 0xE9
NET Tools: 0xEA
RIP: 0xEB
RIP v2: 0xEC
UPNP: 0xEE
Busybox Utility: 0xEF
Configuration Manager: 0xF0
DropBear Utility: 0xF1
Voice: 0
Policy routing if selected, uses the egress interface. The ingress interface is not applicable if
policy routing is used.
Currently routing algorithms make decision based on destination address, i.e., only Destination IP
address and subnet mask is supported. The Policy Routing page enables you to route packets on
the basis of various fields in the packet. The following fields can be configured for Policy Routing:
Destination IP address/mask
Source IP address/mask
Source MAC address
Protocol (TCP, UDP, ICMP, etc)
Source port
Destination port
Incoming interface
DSCP

Rate

3.7 / 5 based on 3 votes.

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top