Using a block of IP's without applying them to an interface

This question has been asked before as PART of another question previously posted.  

I've been issued a block of public ip's 57.57.57.128 /25 to 57.57.57.254 /25 - Labled as "Ethernet/lan" by the isp

I've been assigned 63.63.63.102  /30 labled as " WAN IP"

I called the ISP as I want to nat the public IP's to internal addresses on a cisco 2620.  I was told to apply the 63.63.63.102 to S0 and apply 192.168.1.1 to E0.  In other words, do not apply the 57.X.X.X address to any interface and just nat them the same way I had before.

Example:
ip nat inside source static tcp 192.168.1.10 80 57.57.57.129 80 extendable <-- for www server

Two questions:

1. Will this work as described and/or is there anything else that I need to do like adding the 57.X.X.X network as a static entry?

2. Do I need to specify the ISP's router address (63.63.63.101) anywhere on the router as a gateway?

I was told that I don't need to be concerned with the  57.X.X.X network as it is an entry on the ISP's routers but this was information by an engineer who was in an obvious hurry and  felt that since we did not buy the router from them that  it was some sort of  "privilage" for me to ask any questions at all. Question 3.  I can still cancel. Should I even bother setting up service with this ISP?

Thanks for your help!

LVL 1
zenportafinoAsked:
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.

EladlaCommented:
Interesting configuration.
Why would you need so meny public ips?
That kind of beats the point of having a firewall/router.
Anyway, I think you have the right idea. Map each internal IP to one of the external IPs.
What I also think you should do is make all the private IPs static as to keep the integrity of your configuration. In other words, DON`T use DHCP after you map the IPs in the router, thats just looking for trouble.
Good luck.
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
Ancient_OrangeCommented:
Looks good to me so far.
But it really depends on your ISP an how they do things in their network.

how do you hook up to the internet by the way ?

is it.

ISP Router --- your router -------your intranet ?

my isp for example gave me  4  public IP's and they just gave me a configured router with 4 ports where each port represents a IP.

but i don't know how this is managed by your isp.

it sounds to me like you only got one port and all 4 ip*s are routed trough 1:1 to that port ?.

if so i guess all you have to do is to set your routers gateway to the ip of your isp's modem/router and then just simply set up the nat rules for the specific source ip's so lets say if ithe packet is comign from 57.57.57.129
redirect it to maschine 192.168.0.2 on port 80.

Please note that i' am not yet a expert in terms of networking i'm only learning.
but as far as i know about it your matter should work just fine with that configuration altough it still depends on your ISP.

What do you mean by "you can still cancel" you mean the contract with your ISP?
Thats a decision imo that no one can take for you it depends on if you are happy with that what you get for your money from your ISP.
with best regards AO

0
Ancient_OrangeCommented:
i can see no problem with using dhcp since you can reserve certain ip adressess for example the 192.168.0.2 for the web server.
and anyway dhcp servers tend to give a maschine the same ip it got last time if not already taken.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

EladlaCommented:
"and anyway dhcp servers tend to give a maschine the same ip it got last time if not already
taken"

But you can`t count on that.....and it`s just askin for trouble.
0
zenportafinoAuthor Commented:
This is a relatively small network and we really only use about 10 IP's.  I didn't place the order.  The servers are of course static internal IP's so there will be 10 or so nat translations.  The nat translation above is just an example for the www server. There will be 9 others.

Question 3 is an injection of humor but on the serious side I'm apprehensive to do business with a company that in essence is telling me at the start that when I need support, I can expect allot of attitude and very little help.  

0
EladlaCommented:
I hate it when ISPs act up!

Anyway, back to the matter at hand.
You need to map every internal IP to an external IP in the router.
You might want to get the ISP to do this, but that will only work if you got the router from them.
0
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
Networking

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.