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 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>