Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (ASCEND) 6.1.7 and randomness of the Max IP address....

I would guess it has something to do with OSPF and/or stacking.  We use
RADIUS to assign the route to the user and have both numbered and
unnumbered routes connecting to us.  Usually, customers using Pipelines
are set up using unnumbered routes and people w/ Ciscos are given numbered
routes.  Then we have the modem and NAT users that are randomly assigned
IPs.

The IP address that the MAX broadcasts via traceroute (even if you
traceroute to the max itself) is the one that we assign to our unnumbered
Pipeline dial-in users.

Here's a better explanation:

Let's say the ethernet address of the MAX is 10.0.0.21.  I assign Joe
Pipeline User an IP range of 10.0.1.1/24.  We tell RADIUS to give the MAX
an IP address of 10.0.0.254/24 (i.e. "Ascend-PPP-Address = 10.0.0.254")
since there's no telling which box he hits.

Whenever I traceroute to Joe or anyone else for that matter the MAX
reports its address as 10.0.0.254 (even if I report to the max).

Hope that makes sense. :)

-Rob-


On Mon, 24 Aug 1998, Neale Banks wrote:

> Interesting... I'm running 6.1.7 (very plain, no OSPF or stacking) and can't
> seem to reproduce this.  My methodology was to take the output of "show
> users" and traceroute to each IP in turn - in all cases the secon-last hop
> was the ethernet interface of the MAX (and yes, we do have some customers
> using numbered interface link).  Is there something else I need to see this
> problem?
> 
> Regards,
> Neale.
> 
> At 19:38 23/08/98 -0500, Rob Myers wrote:
> >I am experiencing a strange problem similar to what you are seeing with
> >6.1.7.  When I do a traceroute to a customer's ISDN device or modem from
> >our cisco or one of our UNIX boxes I no longer get the Ethernet IP address
> >of the MAX.  I would prefer to get this address since I can find out what
> >one of our MAXen they are connected to. :)
> >
> >This is the only thing I have seen with 6.1.7 so far that I have had any
> >problems with.  I'd like to see it fixed in a future release but it is
> >more of an annoyance than a crippling problem.
> >
> >-Rob-
> >
> >> From: Raul Zighelboim <rzig@verio.net>
> >> Date: Fri, 21 Aug 1998 23:11:19 -0500
> >> Subject: (ASCEND) 6.1.7 and randomness of the Max IP address....
> >> 
> >> Hello there;  I wander is anyone else is experiencing this problem with
> >> 6.1.7:
> >> 
> >> I assigned numberred point to point links to isdn dialup; 1 /30 ip on my
> >> end, and another /30 ip in the customer end.
> >> Up to now, it all worked well.
> >> 
> >> With the last release of Ascend, the Max IP Address (used to always be
> >> the ip assigned to the Ethernet port) follows the WAN ip of the last
> >> incoming call.
> >> 
> >> So, A traceroute would show : Ethernet -> WAN13-local_ip ->
> >> WAN27-remote_ip  when it used to be :
> >>                                             Ethernet -> MAX-Ethernet_ip
> >> - -> WAN27-remote_ip...
> >> 
> >> Strange.... will Ascend ever be able to deliver code with V.90 ?  I wish
> >> the would leave 5.0p24 alone, replacing only the rockwell microcode.
> 

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