On Fri, 29 Nov 2002, Michael Steinhart wrote:
> ip route 66.250.201.16 255.255.255.255 ATM1/1/0.319
> ip route 66.250.201.22 255.255.255.255 ATM1/1/0.319
> ip route 66.250.203.16 255.255.255.248 66.250.201.22
> ip route 66.250.203.24 255.255.255.248 66.250.201.16
I just ran into this myself, and I THINK I've got the answer:
This happens because the WAN subnet mask for the CPE is probably
255.255.255.0, which is fine -- UNLESS you need to route to any other IP in
the 66.250.201 block !
Solution: CPE needs a route for 66.250.201.x , probably to 66.250.201.1 ( I
haven't actually TRIED it myself since the problem was on my own network,
and I had already worked around it by the time it hit me what was
happening).
-Chris
==========================================================
Chris Candreva -- chris@westnet.com -- (914) 967-7816
WestNet Internet Services of Westchester
http://www.westnet.com/
Recent archives of the list can be found at
http://www.westnet.com/verizonisp/
Send 'unsubscribe' in the body to verizonisp-request@westnet.com to leave.
Received on Mon Dec 2 12:53:22 2002
This archive was generated by hypermail 2.1.8 : Wed Aug 27 2003 - 13:27:17 EDT