Let me back up a little. With more careful reading I see you are doing a
dialup connection. That being the case then your scenario is legal, but
the chatter I wrote before is still good WAN chatter :)
The question now is why one PTP interface for different dialin links. What
static IP address are you using for the other connections.
>** Why? **
>The reason is that in the example you describe above you have three networks.
>1 - The ethernet connected to the PM2eR
>2 - The ethernet connected to the NT
>3 - The WAN between the PM2eR and the NT
>
>It is not legal to use an IP address from one subnet (the ethernet you're
>pm2er is connected to) and use that address on/for another network (in this
>case your WAN network).
>
>You gave the NT's WAN port and address of 206.40.43.17 which falls in the
>range of network 206.40.43.0/25 (IP range of .1 - .126). So when the
>ethernet interface and the WAN interface both establish the PortMaster will
>have two interfaces belonging to the 206.40.43.0/25 subnet. The PortMaster
>must choose one of the interfaces to router 206.40.43.0/25 out of and since
>the newest interface wins this race the 206.40.43.0/25 IP network will be
>routed through the WAN interface and your routing will be blown out of the
>water.
>
>*** How to fix ***
>You have two options:
>1. Make the WAN a point-to-point (PTP) un-numbered connection.
>2. Give the WAN connection its own IP subnet.
>
>
>1. Make the WAN a point-to-point (PTP) un-numbered connection.
>In this case NO ip address are used on the WAN ports. Each WAN port points
>to the other router's ethernet address. This works well when using one
>type of gear. Mix vendors, such as Livingston and NT, and your milage may
>vary. There is a technote at www.livingston.com that goes into detail on
>this sort of configuraton.
>
>2. Give the WAN connection its own IP subnet.
>This case would be a PTP numbered connections meaning that the WAN
>connection has its own unique IP subnet and the WAN ports of both routers
>have an IP address that are members of that unique subnet.
>
>For example, I could say that 206.40.46.96/30 is the IP subnet that I
>choose for this link.
>* This IP Subnet has a network address of .96
>* This IP Subnet has two usable IP addresses .97 and .98 (we only need two
>here).
>* This IP Subnet has a broadcast address of .99
>
>I give the WAN interface on the PortMaster and address of .97.
>I give the WAN interface on the NT and address of .98.
>
>Now, if I wanted to create a 2nd WAN connection to this PortMaster to a
>different NT box then I would need to use another, different, unique IP
>subnet for that link such as 206.40.46.100/30 (IP addresses .101 and .102)
>since I can't cross IP Subnets accross different networks.
>
>If the routers themselves do not have to access the Internet you can use an
>IP subnet from 192.168.0.0/16 that has been set aside for internal use.
>Any packet "orginating" from the router cannot be routed on the Internet
>since the IP address can only be used Internally. Packets "orginating"
>from a valid IP address will be forwarded just find. Most routers only
>need to forward packets one hop in any direction. I suspect that your NT
>boxes are used for surfing and other things other than just packet
>forwarding so this may not be for you.
> -+
>net=.0; range=.1-.126; broadcast=.126 |
>==========ethernet==206.40.43.0/25===== | Network 1
> | -+
>+---------------+
>| e0 |
>| PM2eR |
>| wan |
>+---------------+ -+
> |\206.40.46.97 |
> | WAN network: 206.40.46.96/30 |
> | net=.96; range=.97-.98; |
> | broadcast=.99 | Network 3
> |/206.40.46.98 |
>+---------------+ |
>| wan | -+
>| MS-NT |
>| ether |
>+---------------+ -+
> | |
>==========ethernet==206.40.44.160/27===== | Network 2
>net=.160; range=.161-.190; broadcast=.191 |
> -+
>
>---
>jstorms@livingston.com
>Diplomacy: The art of saying good doggie
>while seaching for a big rock.
>
>
--- jstorms@livingston.com Diplomacy: The art of saying good doggie while seaching for a big rock.