Tunji,
I think the reasoning behind Ciaron's suggestion was to limit the
propagation
of the various host routes generated by the addition of every user that made
a
dailin connection. This would have quite impact depending on the size of
your network.
Based on the configs you posted, I was working on the assumption that the
3640 device, eth0 was on a globally routable IP segment. I must admit I'm a
bit lost!
I do have a few questions on which device act as your CE, and how does it
connect to you ISP's
PE device. You mentioned that the 2611(Internet gateway) has a rfc1918
compliant
address assigned to the serial connection between you and your ISP, is this
correct?.
This is not a problem as some providers tend to use this option. There has
been a
number of different threads that discussed the "pros" and "cons" to this
approach.
You mentioned that NAT did not seem to work What "debugs" did you use to
confirm
or isolate the problem for what you observed. The 2611 at the
moment is as you mentioned not the problem, however I would like to see the
entire
configuration of the 3640 NAS device. There is definitely something
incorrectly
configured that is responsible for any of the async connected devices
inability to reach
the e0(directly connected) interface
Nigel
----- Original Message -----
From: "Tunji Suleiman"
To:
Sent: Saturday, August 03, 2002 2:22 PM
Subject: Re: Routing with IP Unnumbered Loopback [7:50581]
> Thanks Ciaron and Nigel, I removed the route statements
>
> network 192.168.200.0 and
> network 192.168.1.0
>
> from the 2611 and 3640 respectively, without any effect on the route
tables.
> Apparently, the eigrp process informs the routers of the connected
networks
> on the far sides of each other, making the network statements unnecessary.
>
> I posted the most relevant parts of the configs, assuming it will be
obvious
> that my ppp config is ok, since I can dialin to the 3640. The 3640 is a
> production NAS connecting users b4 with a global IP pool.
>
> I would have configured NAT on the 2611 Internet gateway, but even that
has
> rfc1918 address on the serial link to the Internet. What I did was
configure
> NAT on the 3640, making the LoO the inside and E0/0 the outside. But even
> that is not working, with traffic both ways ending at Lo0.
>
> If I can get a dialin user on the async line to ping e0/0 of the 3640,
then
> the issue should be resolved.
>
> TIA
>
>
>
>
> >From: "Nigel Taylor"
> >Reply-To: "Nigel Taylor"
> >To: [EMAIL PROTECTED]
> >Subject: Re: Routing with IP Unnumbered Loopback [7:50581]
> >Date: Sat, 3 Aug 2002 10:17:44 GMT
> >
> >Tunji,
> > See Inline...
> >
> >----- Original Message -----
> >From: "Tunji Suleiman"
> >To:
> >Sent: Saturday, August 03, 2002 5:20 AM
> >Subject: Routing with IP Unnumbered Loopback [7:50581]
> >
> >
> > > Hi all,
> > >
> > > I am reposting this because there were no responses to the first post.
I
> >am
> > > trying to conserve IP addresses by using private IPs for dialin users.
> >
> >NT: Ok, so as you mentioned you're trying to conserve IP address by
using
> >private IPs for dialin users. Question? When you make use of those
> >private(rfc1918) addresses are they routable?
> >
> > >From
> > > clients I can dial in to network but cant get beyond 3640 NAS, cant
even
> > > ping 3640 E0/0 LAN IP address. From 3640, I can ping Lo0 from E0/0
and
> >vice
> > > versa; I can ping connected client on any Async sourcing Lo0, but not
> >E0/0;
> > > and I can ping Internet hosts eg www.yahoo.com sourcing e0/0 but not
> > > loopback0.
> >
> >To answer part of the question; "Yes" the outbound packet will be
routable
> >"only"
> >because you have a 0/0 route, that will route any packet to the
"next-hop"
> >based on
> >the static default route. We all know routing is bi-directional(I'm
hoping
> >:->), which
> >now begs the question, "How does this private block of IPs you use get
> >routed back to
> >you(your network)? Will anyone in the Internet route these packets back
to
> >you?
> >
> >Once you answer these questions.. then check out this link!
> >http://www.cisco.com/warp/public/556/12.html
> >
> >
> >HTH
> >
> >Nigel
> >
> >
> >From 2611 Internet gateway, I can ping 3640 E0/0 and Lo0, but not
> > > a connected dialin user on any Async with private IP address assigned
by
> > > 3640 from IP pool. I have a routing issue that makes traffic in both
> > > directions get to and disappear at 3640 Lo0, but strangely all
necessary
> > > routes (that I can think of) are installed in the route tables. Can
> >somebody
> > > pls point out what I'm missing? Below are my configs and route tables:
> > >
> > > 3640-NAS Config:
> > > interface Loopback0
> > > ip address 192.168.200.254 255.255.255.0
> > > !
> > > interface Ethernet0/0
> > > ip address 216.199.175.12 255.255.255.224
> > > !
> > > interface Group-Async1
> > > ip unnumbered Loopback0
> > > peer default ip address pool PRIVATE
> > > !
> > > router eigrp 10
> > > network 192.168.1.0
> > > network 192.168.200.0
> > > network 216.199.175.0
> > > no auto-summary
> > > !
> > > ip local pool PRIVATE 192.168.200.41 192.168.200.88
> > > ip classless
> > > ip route 0.0.0.0 0.0.0.0 216.199.175.1
> > >
> > > 3640-NAS Route Table:
> > > Gateway of last resort is 216.199.175.1 to network 0.0.0.0
> > >
> > > 216.199.175.0/27 is subnetted, 1 subnets
> > > C 216.199.175.0 is directly connected, Ethernet0/0
> > > 192.168.200.0/24 is variably subnetted, 2 subnets, 2 masks
> > > C 192.168.200.52/32 is directly connected, Async101
> > > C 192.168.200.0/24 is directly connected, Loopback0
> > > 192.168.1.0/30 is subnetted, 1 subnets
> > > D 192.168.1.0 [90/2195456] via 216.199.175.1, 00:58:16, E0/0
> > > S* 0.0.0.0/0 [1/0] via 216.199.175.1
> > >
> > >
> > > 2611-Gateway Config:
> > > interface Ethernet0/0
> > > ip address 216.199.175.1 255.255.255.224
> > > !
> > > interface Serial0/0
> > > ip address 192.168.1.2 255.255.255.252
> > > !
> > > router eigrp 10
> > > network 192.168.1.0
> > > network 192.168.200.0
> > > network 216.199.175.0
> > > no auto-summary
> > > !
> > > ip classless
> > > ip route 0.0.0.0 0.0.0.0 192.168.1.1
> > >
> > > 2611-Gateway Route Table:
> > > Gateway of last resort is 192.168.1.1 to network 0.0.0.0
> > >
> > > 216.199.175.0/27 is subnetted, 1 subnets
> > > C 216.199.175.0 is directly connected, Ethernet0/0
> > > 192.168.200.0/24 is subnetted, 1 subnets
> > > D 192.168.200.0 [90/409600] via 216.199.175.12, 07:51:45, Et0/0
> > > 192.168.1.0/30 is subnetted, 1 subnets
> > > C 192.168.1.0 is directly connected, Serial0/0
> > > S* 0.0.0.0/0 [1/0] via 192.168.1.1
> > >
> > > TIA
> > >
> > > Tunji
> > >
> > >
> > > _________________________________________________________________
> > > Chat with friends online, try MSN Messenger: http://messenger.msn.com
> _________________________________________________________________
> Join the worlds largest e-mail service with MSN Hotmail.
> http://www.hotmail.com
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=50609&t=50581
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
