Bad pool size

Hello all. Im trying to set up a router. Rigt now it has a pool size of 128. I want it to be 400+.

Im trying to changing the subnet to 255.255.254.0 when ip is 192.168.1.1 but it wont accept when i tell the pool size to be 510.

Poolsize is set to 510. The ZyWall 30 wont accept that and goes back to 128.

When i click apply, it will go back to 128. What am i missing?
Mike KristensenIT administratorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Don JohnstonInstructorCommented:
You don't indicate what brand/model device so there's no way to know for sure. But there are two possibilities:

1) This device does not allow for super-netting. So change the IP address to a non-class C address. Try 172.16.0.0 with a /23 mask.

2) The device does not allow for a mask shorter than 24-bits.
0
Mike KristensenIT administratorAuthor Commented:
oki. Its a ZyXel ZyWall 35.

Is there any specific thing i neda look for when trying to figure out the above you tell me?
I managed to get the pool to 253 when using subnet 255.255.252.0 but i aint really 100% sure how it works. Also because i might not understand it, due to a hidden limitation which i dont know of.
0
Don JohnstonInstructorCommented:
I managed to get the pool to 253 when using subnet 255.255.252.0
You mean a pool size of 253?  If you have a mask of 255.255.252.0, then you have a pool of 1022 addresses.

For the sake of consistency, if you're going to be using a mask shorter than /24 (255.255.255.0), then you should be using an address of 192.168.0.0.  It will work with 192.168.1.0, but things could get confusing. And like I said before, a 172.16.0.0 address would be even better. This is especially true since it appears you're running RIP.
0
Mike KristensenIT administratorAuthor Commented:
Am i running RIP? What is that?

Why 172.16.0.0? And why 192.168.0.1 over 192.168.1.1? Im so lost. Normally i was running a server with range 192.168.1.1 - 192.168.3.254 was this bad?

The Zywall 35 wont let me increase the poolsize over 253, so i believe it might be a limitation from its perspective. I will read up on this in the Zywall datasheets.
0
Don JohnstonInstructorCommented:
Oh my... ;-)

RIP is a routing protocol. It's used to distribute the list of networks to other routers.

Because RIP is a classfull routing protocol, it expects a certain mask.  Because 192.x.x.x addresses default to a 255.255.255.0 mask (which you can make longer but run into problems making it shorter), that may be part of the problem.  Since a 172.x.x.x address has a default mask of 255.255.0.0,  using that address may solve the issue.

But it sounds like this is way beyond your knowledge level.  It may be prudent to bring in a network consultant to help.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Network Operations

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.