>
> Our customer is setting up a Webramp router on an ISDN connection to our
> PM3's. The ethernet address of the PM3 is on the 207.12.120. network.
> The address of the Webramp is 207.208.91.126 with a netmask of
> 255.255.255.192. When the Webramp dials up and connects to the PM3, I can
> ping any node on the 207.208.91.64 subnet from anywhere on the 207.12.120
> network. In other words, I can access the dialup LAN from anywhere on the
> network that is directly connected to the PM3. Anywhere, that is, but from
> the router on that network. The router is a Cisco 7500. And, of course,
> I can't reach the 207.208.91.64 subnet from anywhere outside the network
> directly connected to the PM3.
>
> OK, you might say, it must be the Cisco whose routing tables are screwed up.
> But if I look at the routes on the cisco, it shows the ripped route to the
> Webramp to be via the appropriate PM3. And if you traceroute to the
> Webramp or any of it's internal nodes from the Cisco, the trace goes
> straight to the PM3 then dies (you know, 3 * * *, etc.). Also, tracing
> from devices on other networks shows that packets addressed to the
> 207.208.91.64 network bounce from the PM3 to the Cisco and back to the
> PM3 and back to the Cisco until the trace quits. This seems to be saying
> that the PM3, even though it sees a route to the 207.208.91.64 network
> through the appropriate port when you do a "show route", doesn't know
> how to route the packet when it comes from the router on its network.
>
> Anyone have any suggestions?
Which version of ComOS?
Since you are using RIP make sure you are not trying to do VLSM (i.e. is
the entire 207.208.91.x network subnetted with a consistent netmask of
255.255.255.192?). Are you using the netmask table? Do a "show routes"
on the PM. When you do a "show ip route" on the _Cisco_ what is the mask?
If I remember correctly if the Cisco is getting an inconsistent mask it
should detect it and say that you are using VLSM. Are there any other
clients using the other subnets in 207.208.91.x?
>
> Thanks for listening,
>
> Mike Denka
> WhidbeyNet
> mdenk@whidbey.net
Josh Richards - <jrichard@livingston.com>
Beta Engineer
Lucent Technologies (Remote Access Business Unit)
(previously Livingston Enterprises, Inc.)
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.