static public ip confusion

[entropy5]

I will be setting up a network that has been assigned a static public IP. SBC has given a range of "usable" IPs as well. For instance:

Modem IP = 172.xxx.xxx.x (is this simply the setup GUI IP?)

Public IP= 68.xxx.xxx.38 (is this the Gateway IP?)

"Usable Range"= 68.xxx.xxx.33 - 37 (are these the IPs I set as static on each PC in the network? 2 of which are video surveillance servers, the 3rd just needs internet access)

DNS = xxx.xxx.xxx.xxx, yyy.yyy.yyy.yyy

With this set-up, I have gotten conflicting info concerning hardware; 1 camp says "use the Linksys router you were using when you had a dynamic IP with port forwarding to the same private IPs --the modem will sort them out", another camp says, "buy a switch and use the above mentioned static "usable range' IPs and a software firewall port forwarding". I am inclined to believe the switch camp would be less hassle.

What do I need to do?

 

[n0cmonkey]

Either should work. Personally, I'd consider just using the linksys to keep things simple. File sharing should be a lot simpler, plus the added security of NAT is hard to say no to.

 

[tweekah]

172.168.0.1 sounds like the 2wire modem/router. I noticed your location shows IL which has been using sticky ips for awhile. The gateway IP should be pulled down to your 2wire when you authenticate with uid@static.sbcgl...versus pure static where gateway ip is built on rback/juniper router. Since the 2wire is a router itself, simplicity would suggest using a switch behind it. If you decide to keep the linksys route, I'd suggest bridging the 2wire. If you keep NAT on you'll have to either add pinholes or ip maps.

 

[entropy5]

After posting, I went to the SBC DSL help site and did find that the IP 172.xxx.xxx.xxx seems to be a 2wire modem/router. This now makes more sense to me concerning the "usable range" IPs and IP/port mapping/forwarding. My client did not mention any new hardware, but then again, I haven't talked to him personally. Sounds like it should be a cruise.:thumbsup:

 

[entropy5]

Well, tweakah was correct.

The appliance was indeed a 2Wire Modem/Router all-in-one. And it was quite easy to set up; I first bridged networks to allow the public IPs to be used as private (after assuring all firewall ports were closed), then I made each of the 3 PCs "fixed" in the router (no need to do this in XP, the router handles this), then I created and opened the appropriate ports to the 2 servers. And voila! Instant access via the web and the proprietary software.