How does a static IP address work?

[cearlp]

I know the subject seems a bit general but I am having a problem getting a static IP address with an Actiontec Q1000 router.
Here is my situation:
I have Qwest/Centurylink as the ISP.
I have three PC's connected to it. One a MAC, one running Linux and one running Windows 7/8.
I want one static IP address and want to configure the Q1000 to direct traffic with that IP address to go to one of the three PC's. Being able to reconfigure the router to direct that traffic to whichever PC I choose.
Qwest says I need a static IP address for each PC and will have to configure each OS to handle it's specific traffic.
That doesn't sound correct to me, because previously I had the same scenario with a wireless ISP (radio antenna to tower antenna) with a Belkin router and only one static IP address. I could configure the Belkin as to which internal IP address the traffic was routed to.
Shouldn't this scenario be possible on the Q1000 also, or is my understanding of a static IP address somewhat lacking?

 

[kevnich2]

Um, I think you're confusing terminologies. What you're actually trying to accomplish is port forwarding. Which to accomplish it correctly, long term, does need a static IP address.

What it sounds like you need to do is whatever computer you want traffic to go to from the internet, assign it an IP address outside of DHCP range, then setup your port forwarding for whatever the internet ports that you need forwarded are and set it to go to that IP address.

 

[JackMDS]

Maybe this can Help.

http://www.howtogeek.com/howto/19249/how-to-assign-a-static-ip-address-in-xp-vista-or-windows-7/

 

[cearlp]

So, as I understand it now, one static IP address will get all unsolicited incoming traffic to my router and if I want only one of my attached PCs to get, say web server and ftp traffic. I need to configure the router to forward those internet ports to the private IP address of that PC.
Any traffic initiated from the PCs on the router will have a port generated and returning traffic will then go back to that specific PC.
Correct?

 

[JackMDS]

Yes, to the Static Private IP.

Private is all the IPs behind the Router.

Static is the ones that do not change and thus pair with the ports that are forward toward them.

 

[QuietDad]

The router gets assigned the static IP the internet see's. You then set static IPs yourself on the equipment. YOu then can Use the DMZ feature of the modem to direct EVERYTHING to one of the PCs. https://internethelp.centurylink.com/internethelp/modem-q1000-adv-dmz.html

 

[VirtualLarry]

First question - do you really have a Static IP from your ISP? Because usually they come in blocks. They would have given you a netmask and a default gateway, as well as several DNS servers to plug into your router.

If you didn't get all of this info from your ISP, then you may not have a static IP.

Are you a residential or business subscriber?

 

[kevnich2]

I hate to say this but honestly, if you're asking these types of questions relating a static IP addressing and what not and at the same time, asking about hosting web and ftp server's on your home connection....you're in over your head. You're missing alot of fundamental knowledge that you need BEFORE opening your internet connection up at the firewall to allow incoming traffic directly to an internal machine.

That's just my .02 in this matter. Rant over...

 

[cearlp]

Seriously, Many Thanks for all the replies.
The DMZ configuration on the Q1000 is interesting and I will look into configuring one.
The use of the word static can be confusing when used to refer to both public and private addresses without being specific.
I do have a static IP from the ISP and therefore it is the router's Public Static IP address. The IP addresses assigned by the router to the PC's plugged into it have never changed, so I have never had to configure private static IP addresses for them.
Before switching to Centurylink as the ISP I had a Public IP address and used one of my PCs to host a website that only the people I gave the IP address to accessed it. (I did not have a Domain Name) There is no critical info to be had if by chance somebody happened to key in the IP address. However, I will consider a DMZ.

 

[kevnich2]

If you have a system that people on the internet can log in to remotely, you need to be taking the necessary precautions. In this day and age, it's usually hacked into in a matter of HOURS without proper precautions.

Not using a domain name has no bearing on this. Not sure what the system is but if it is accessible from the internet without proper security, consider it infected before too long. Those systems can also be used to gain access to your entire network after it's infected.

 

[JackMDS]

Most attacks on normal end users are Not intentional they are usually generated by random probes done on ISPs IPs bands.

Thus keeping a network on DMZ is "Not Smart".

 

[cearlp]

If keeping a network on DMZ is 'Not Smart' what do you recommend?

 

[Emulex]

VPN is the wisest method with dyndns.org for dynamic dns. most routers worth a crap can do both of these!

Punching holes in the firewall to specific hosts on the private ip side is second best

with UPNP being the least secure method of punching holes (as you might get unintended services open)!