Defining the network on the LAN side, and defining the address of the LAN router port.
Defining the network on the WAN side, and defining the address of the WAN router port. Note: All clients dialed into the WAN see the same address for this WAN router port.

Each client dialing in requires a unique IP address. The 833IS supports multiple methods for defining and supplying IP addresses to clients.

For the 833AS/IS router to be able to route IP packets, it has to know how to reach the destination.
The 833AS/IS supports the following methods:

RIPV1
RIPV2
Default gateway.
Static routes.
Proxy ARPs.

Device's on the LAN need to be able to route IP packets to the Perle's WAN network using the above methods.

WAN Network Address:

All dial in IP devices that are dialed into the WAN appear as if they are on their own IP network. This network is referred to as the "Internal WAN Network". The 833AS/IS also requires one address on this network for the router port. This section defines the Internal WAN Network used by the 833IS and should be completed after consulting with your IP Network Administrator.

In general, it is recommended to define the Internal WAN network distinct from the LAN network.
example:
Perle Server IP Address = 165.154.129.1 / 255.255.255.0
Perle WAN IP Address = 165.154.130.1 /255.255.255.0

Ensure that LAN devices have information on how to route packets back to the WAN network.

It is possible to define the Internal WAN network as a subnet of the LAN network, but there are limitations:
The WAN will be defined as a subnet of the LAN and this subnet must be exclusive to the Perle
Routers on the LAN using RIP V1 cannot discover the Internal WAN network, and will not be able to route to the dial in clients on the Internal WAN network
DHCP is not supported for IP allocation

example:
Perle Server IP Address = 165.154.129.1 / 255.255.255.0
Perle WAN IP Address = 165.154.129.129 / 255.255.255.128

Defining the Internal WAN network as a subnet can still be useful if:

Routers on the LAN use RIP V2. RIP V2 sends subnet information and any routers on the LAN network using RIP2 will learn about the Internal WAN network.
Static routes are defined.
The "Enable Proxy ARP" setting is used.

To set the WAN Network Address, the following fields are used on the IP configuration screen:

IP Address

Enter the IP address that will be used by the 833AS/IS on the Internal WAN Network for its router port. Be careful to ensure that this address does not conflict with any dial-in client IP addresses.

Subnet Mask

Enter the subnet mask for the internal WAN network

All dial-in client IP addresses, regardless of how they are acquired, must belong to the network defined by this IP Address and Subnet Mask.

Enable Proxy ARP:

Device that are connected on the same IP network discover each other by sending a message on the local network known as an ARP (Address Resolution Protocol). On the 833IS, the Internal WAN network is usually defined as a different network from the LAN network, and ARPs are not used. If the Internal WAN network is defined as a subnet of the same LAN network (as described in "WAN Network Address" in the manual ), Proxy ARPs can be enabled so that a device on the LAN can discover a dial in client. There are some limitations associated with Proxy ARP:

IP broadcasts will not be forwarded in this mode. Most applications will work, but IP applications that rely on broadcasts or multicasts (such as NetBEUI over IP) are not supported.
There is a small performance penalty if Proxy ARPs are enabled.
The "Enable Proxy ARP" fields has been added to the IP configuration screen. When checked, Proxy ARP will be enabled.

DHCP (not supported with Proxy ARP)

In DHCP a "scope" is defined as "An administrative grouping of computers running the DHCP client". These computers are grouped according to a range of IP addresses. Simply put, all dial in clients on an 833AS/IS share the same scope, namely the range of addresses defined for the Internal WAN network.

On the DHCP server, you must define a scope that matches the IP address range for the dial in clients on Internal WAN network. Ensure that the IP address of the Internal WAN network itself is excluded from the scope, so the DHCP server does not attempt to assign this address to a dial in client.

Note that only the DNS and WINS nameserver DHCP scope options will be negotiated with the dial-in client.

The 833AS/IS has the ability to forward the address of a DNS or WINS server to a dial in client.