
4. DSL Router Configuration Examples
Unnumbered DSL Interface with Proxy ARP Configuration Example
Customer Premises (CP)
Core
Router
155.1.3.1 |
| Console | |
|
| Port | |
|
| Connection | |
DSL |
| Ethernet | |
WAN |
| Hub | |
dsl1 | DSL | eth1 | |
Unnumbered | 155.1.3.254 | ||
Router | |||
|
|
Systems
155.1.3.2
155.1.3.3
155.1.3.4
In this unnumbered DSL Interface with Proxy ARP example:
The clients are statically configured and use the core router as the next hop router (default gateway) in order to create the LAN extension configuration.
The DSL interface is unnumbered.
The clients, the DSL router’s Ethernet interface, and the core router’s interface are all on the same logical network.
If IP Scoping is enabled at the DSL card, the eth1 and the client’s IP addresses must be placed in the client VNID table (VNID mode must be selected on the DSL cards with an ATM uplink, such as Model 8304, 8344, etc.).
The commands and syntax for this example are:
ip routing enable
ifn address eth1 155.1.3.254 255.255.255.0 ifn address dsl1 unnumbered
ip route create upstream eth1 155.1.3.1 proxy arp eth1 enable
proxy arp dsl1 enable
NOTES:
—The ip routing enable command is only required when using firmware version 4.2.5 or higher.
—FUNI/MPOA (1483 routed) link encapsulation can be used with this configuration and the DSL card Models 8304, 8314, 8344, and 8374. Link encapsulation is configured on the DSL port. This link encapsulation must match the core network encapsulation type. The ip route create upstream and proxy arp dsl1 enable commands are not necessary when using FUNI/MPOA link encapsulation.
November 2003 |