Real Time Ascend Maling List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Ascend TNT and large IP-Pools
You can chain pools together in 7.2.3, and 7.0.22, but I believe it
chains ALL of them together into one big hairball.
Denny
Quoting Steve Meier (steve@gigabell.net):
> Hi Oliver,
>
> we are experiencing the same problem with our TNTs. :(
>
> As far as I know the fact is that there is no way around that in
> Ascend's TAOS
> releases 7.x.x. I've read that there is a so called pool-chaining
> feature in TAOS 8.0.0+
> which should solve that problem but I haven't tried that yet although
> one of our boxes is running TAOS 8.0.0.
>
> I would greatly appreciate any comments on that. :)
>
> Steve
>
>
> Oliver Stettner wrote:
>
> > Hello everybody,
> >
> > we have a problem with our new Ascend TNT, which we couldn't solve so
> > far. Perhaps someone of you has an idea.
> >
> > We have two "classes" of IP-addresses - for commercial customers and
> > for non-commercial customers. They are handled differently in our
> > network and they are distinguished by their IP-addresses.
> >
> > So in our TNT we want to have two IP-Pools, like this (the
> > IP-addresses are just examples):
> >
> > pool-base-address 1 = 192.168.0.1
> > assign-count 1 = 1022
> >
> > That would be the network 192.168.0.0/22, or in other words:
> > Network: 192.168.0.0
> > Netmask: 255.255.252.0
> > Broadcast: 192.168.3.255
> >
> > pool-base-address 2 = 172.16.0.1
> > assign-count 2 = 1022
> >
> > And this would be the network 172.16.0.0/22, or in other words:
> > Network: 172.16.0.0
> > Netmask: 255.255.252.0
> > Broadcast: 172.16.3.255
> >
> > With this configuration (which works perfectly for us) it is possibly
> > for a dialin user to be assigned the IP-address 192.168.1.255/22 or
> > 192.168.1.0/22 which are absolutely correct IP-addresses. But
> > addresses of that kind are troblesome with Windows Clients and
> > througout the internet because many routers/servers do not expect
> > addresses like those.
> >
> > So I am looking for a solution to exclude those .0 and .255 addresses
> > from the two pools. But I didn't find anything so far. And our
> > reseller said he has no idea neither. :-(
> >
> > Oliver.
> > --
> > Oliver Stettner | os@landshut.org
> > Laendgasse 120 | http://www.landshut.org/bnla01/members/os/
> > D-84028 Landshut | http://www.fh-landshut.de/~os/
> > ++ Ascend Users Mailing List ++
> > To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> > To get FAQ'd: <http://www.nealis.net/ascend/faq>
>
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd: <http://www.nealis.net/ascend/faq>
--
Denny Reiter | denny@reiters.org
Madison River Communications | reiterd@madisonriver.net
FreeBSD: The Power to Serve | www.freebsd.org
Linux Users Group Galesburg Area | www.lugga.org
Can I trade this job for what's behind door #2?
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>