(ASCEND) Yippie!

[Ken Kirchner <kenk@shreve.net>]

After some mysterious unsubscribing, I am back! Rejoice! :)

But calm yourselves, I have a problem...

A customer with a SuperPipe 155 would like to do both real IP's and NAT on
his unit.  We already route him a class C over a point-to-point T1.  That
part is working fine.  The NAT is a recent addition and that does not seem
to be working at all for him.  Whenever he enables NAT he loses all
connectivity, even on his real IP's.

So he calls up Lucent (at $3 a minute or so) and the tech tells him that
it's not possible with his current firmware, so he gives him rev 7.4.8
which supposedly allows this feature.  They still cant get it to work. The
customer then 3-ways the tech and myself to get things straightened out.
They explain the situation and it doesnt sound complicated to me.  I could
configure a Cisco 2500 to do this no sweat, but I am not up on my
Pipelines.  Anyway, the tech starts explaining to me how NAT works.  It
doesnt sound at all like I think NAT works, but I havent read the RFC so I
dont know for sure.  What he describes to me sounds more like DHCP, so I
think he's clueless.  He starts asking me how we authenticate.  I try to
explain to him that this is a point-to-point nailed up T1 and that there
is no authentication, but he doesnt buy it.  He says unless we have some
way to authenticate this customer's pipeline he wont be able to use NAT.

This sounds like complete BS, but I thought I'd ask here and go read the
RFC before I declare anyone stupid.

The customer wants to do NAT on his SuperPipe over a T1 while still doing
real IP traffic for his class C space.  Can this be done?  How do we do
it?  How do I specify the IP or pool of IP's the superpipe is to use for
the masquerading?  Is the NAT feature limited to dial-up configs only?

-Ken

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>