On this page you can do some more advanced and rarely used things with your network setup.

NOTE: Press "Apply" after your changes!

Hostname - The name of this unit.

Add routes - Use this, for example, to make a routed subnet reachable through the unit. Changes are reflected on the page "Network Status".
For an 'interface route', enter '0.0.0.0' in the "Gateway" field (or leave empty) and select the interface (under "Type").

Additional IP addresses - If you have additional global IP addresses available (apart from the one used as WAN IP address of this device), you can specify here how you want to use those other addresses.
Using an address for IP redirection will allow you, for example, to redirect all or parts of IP traffic to the specified address to a dedicated inside host on the local LAN (setup port or IP redirection on the security profile page).
With IP-Alias you can also redirect traffic, but the address can also be used for internal applications like SIP. IP aliases can be assigned to any interface.
Other options allow you to bridge through a WAN IP address to an inside interface, so you can have a unit with that global IP address on your LAN. Even though it is possible to mix units having such global IP addresses with units having local IP addresses on the same interface we recommend against doing so. For increased security you are recommended to have local and global IP address units separated (eg local units on ET1, units with global IP on ET4). It is possible to add firewall rules for the bridged addresses manually using the security profile pages, by default everything is passed through.

ATM Encapsulation - Very few users have reason to use other than "Auto". This setting overrides the default ATM (RFC1483) protocol for the ADSL WAN connection.

PPP IP address handling - Very few users have reason to use other than "Auto". This setting makes it possible to manually enter IP address and the default gateway on the Network page, instead of letting the PPP/IPCP protocol negotiate and set these values.

Extra WAN Interfaces - This page is used to configure the use of multiple WAN interfaces on the 4:th ethernet port, possibly with VLAN tags. The reason for such additional WAN connections may be for sending prioritized data (e.g. voice/telephone traffic) on separate WAN IP "channels". A common configuration of this is the "TriplePlay", where voice and video are sent by "ipwan2", "ipwan3" etc. and other Internet traffic uses the standard WAN interface "et4".
The separation between WAN IP "channels" may be done by VLAN tags, if external network is VLAN-tagged. All or none of the VLAN Id fields must be filled in. If VLAN tags are used and a single interface should receive non-tagged traffic, its VLAN Id field should be set to the (fictitious) value 4096.
In case of no VLAN tags, the separation between different WAN interfaces is done by different subnets - each interface having its own IP address/mask and its own MAC address.

IGMP Proxy - Check this if the interface is the upstream interface for the IGMP Proxy. This is typically used for multicast traffic, such as video. NB! Only one such interface may be selected. If none are selected, the normal WAN interface is the upstream IGMP interface. If multicast is to be used, it must be enabled on the security settings too.

QoS routing - By setting one or more "QoS tag values" on a WAN interface, this interface will be the sender of the upstream packets marked with one of these values. The QoS marking is done by a classifier on the incoming packets on the LAN ports, or internally by client or proxy modules. Notably, the SIP traffic is specially marked by values 4, 7, 261 or 262. The value 4 corresponds to the "Use WAN Interface with special SIP QoS" checkbox on the SIP page.
The "et4" interface should have no QoS routing - it is the default internet interface.

Protection against overload - If set, in case of higher downstream traffic flow than the unit can process, the "ipwan2", "ipwan3" etc. will be prioritized, possibly on the cost of the "et4" interface where incoming packets may be dropped.

Extra QoS classifiers - As packets come in on a LAN port they may be marked with QoS tags, this is done by the "classifiers". The QoS tag value, if set, will force the router to send the packet out by a particular WAN interface - if one is configured for that "QoS routing" value. By setting up the search profiles in the table here, one may direct packets with certain source/destination IP addresses/ports, DiffServ bits etc. to the correct WAN interface. Select the WAN interface implicitly by using the "QoS routing" dropdown box. Additionaly, one can use the "Set DiffServ bits" field (7 bits, e.g. "1000000") to set DiffServ bits in those packets that match the profile.