• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

mixed dhcp, static ip lan ??

jay2472000

Gawd
Joined
Oct 6, 2008
Messages
590
Is it possible to have some of the pc's on my lan be set to static IP and some of them just get a IP from my router via dhcp? Right now I have my router set to hand out Ip's from 10.0.0.2 to 10.0.0.33. My Freenas Box sits on 10.0.0.34, and I set up my WHS on 10.0.0.24 both static ( I realize with the WHS being that IP I may have IP conflicts, but havent so far )

So if I just needed a few machines to have a static IP could I just change my router to hand out fewer dhcp ip's and then assign my static ones outside of that ? IE have the router give out 10.0.0.2 to 10.0.0.10 rather than 10.0.0.2 to 10.0.0.33 ?? I realize that would limit the number of clients that could have an ip via dhcp, and thats ok, 8 is plenty.

Or..........should I just go ahead and set the whole network to static?

Reason Im asking is because Im going to attempt to set up DynDNS ( my router supports it also) And also a lot of my Android apps use static IP's (Um, vnc, WOL ping, etc are just a couple I can think of real quick,)

Thanks in advance for any advice/guidance.

J
 
Pretty sure if you have a static ip on a machine, the router won't give it to another machine. What router do you use ? You could always do what i do, copy mac address put it into the router and tell the router to always give that mac the ip you want. ( can also set static on device )
 
Right you have occasional conflicts because the STATIC IP of the WHS is in the current DHCP Range. Then just make sure that you set your statics AROUND that threshold. Keep it organized and use Addresses not in that Range and you'll be fine. You're almost there, it looks like your're getting the hang of it.
 
Cool, figured it wouldnt hurt anything but wanted to make sure. So far I havent had any IP conflicts (10.0.0.24 is pretty high up there so DHCP hasnt tried to give it away, I did it as a test to see how setting static IP worked on win7 machine and got lazy and havent changed it back)

The router is a Westell gateway device leased from my isp. Model number 7500 I believe, its a 4 port router, WAP and a modem all in one deal. So far its ran good, havent had to set up a pfsense box yet like I had to do before to handle the constant hammering of bandwidth.

Thank you for you answers.
 
Cool, figured it wouldnt hurt anything but wanted to make sure. So far I havent had any IP conflicts (10.0.0.24 is pretty high up there so DHCP hasnt tried to give it away, I did it as a test to see how setting static IP worked on win7 machine and got lazy and havent changed it back)

The router is a Westell gateway device leased from my isp. Model number 7500 I believe, its a 4 port router, WAP and a modem all in one deal. So far its ran good, havent had to set up a pfsense box yet like I had to do before to handle the constant hammering of bandwidth.

Thank you for you answers.


You should probably set your statics much higher. My DHCP leases start @ .100 and my statics start @ .20

Not only is this best/common practice to assign a static that isnt in the DHCP lease range AT ALL, but you will avoid any possible conflicts in the future.
 
the default range is from .14-.47 on that device, so if you haven't changed it start your static's at .100 and you will be fine.

I was surprised to find out that your router doesn't support DHCP address reservation. That's how I do all my "static" IP's.
 
Back
Top