TRENDnet TDM-E400 - Manual (Page 83)

Chapter 6. Configuring the System Operating Modes
83
Scenario 3: Routed and Bridged Connections to ISP
In this configuration, the LAN is like that described in Scenario 1, but
also includes PCs that use a bridged Internet connection. You
would then need to establish bridging services in addition to routing.
This would also be necessary if the LAN contains PCs that use non-
IP networking protocols, such has AppleTalk or IPX. This
configuration would have these features:
f An Ethernet (and/or USB) interface with an IP address and
network mask that identify it as being in the same subnet
as the LAN PCs. See Chapter 4 for instructions.
f An WAN interface for the routing path. This can be a PPP
or EoA interface and must be IP-enabled, as described in
Scenario 1.
f A WAN interface for the bridging path. This must be an
EoA interface. If an EoA interface was created for the
routing path, the bridging path may be able to use the
same interface. Check with your ISP.
f Bridging is enabled on the LAN interface (eth-0 and/or
usb-0) and on the EoA interface to be used for the bridging
path. If separate interfaces are created for the bridging and
routing paths, then enable bridging only on the EoA
interface to be used for bridging. See “Making Interfaces
Bridgeable (Bridge-Enabled)” on page 79.
f The bridging service is enabled. See “Enabling Bridging
Mode” on page 80.
f For the PCs that will use the routing path, the LAN
interface's IP address should be specified as the IP
gateway, whether assigned statically or dynamically from a
DHCP server.
f For the PCs that will use the bridging path, the ISP should
provide setup instructions for the LAN PC(s), which may
involve installing software to enable logging in to their
servers (called a "PPPoE client"). The PC's gateway IP
address should be configured as the IP address of the ISPs
access server.
In the System View page in the Home tab, the Mode field will reflect
you the Mode field will now reflect Routing and Bridging.