Posted: 12/6/2012 10:19:54 PM EDT
|
am I that much of a dinosaur?
why does every "new" device limit their networking options to just DHCP? I have a static IP system that I've had all components networked on for the past 12+ years I just tried the new Roku and Netgear streaming video boxes, and they're DHCP only. the Netgear box couldn't handle my encryption and the Roku box was able to find my WAP and the encryption was fine, I just couldn't establish a connection because I have a static system. my wap (b/g/n) has a hidden ssid, mac filtering and wpa2P encryption I have no problem connecting with my sony, apple, wii and android devices. I've got over 12 devices that are working in harmony on my network, I shouldn't have to change all of them for one "new" device. |
|
Quoted: am I that much of a dinosaur? why does every "new" device limit their networking options to just DHCP? I have a static IP system that I've had all components networked on for the past 12+ years I just tried the new Roku and Netgear streaming video boxes, and they're DHCP only. the Netgear box couldn't handle my encryption and the Roku box was able to find my WAP and the encryption was fine, I just couldn't establish a connection because I have a static system. my wap (b/g/n) has a hidden ssid, mac filtering and wpa2P encryption I have no problem connecting with my sony, apple, wii and android devices. I've got over 12 devices that are working in harmony on my network, I shouldn't have to change all of them for one "new" device. Just set your DHCP block outside the range you use for static. I.e. DHCP at 192.168.1.100 - 254 and static below .100. That way you can do whatever you want. DHCP only is part of the dumbing down of america and the proliferation of apple product users that think things "just work". Plus, it's less of a tech-support hassle, if there is a setting, users will fuck with it and not realize it broke something doing so. Solution: remove the setting and tech support calls go down.
|
|
Why does your WAP not issue IP addresses based on what device is connecting? You don't need static IPs, there's really no reason to have them, just setup your WAP to always issue the same IPs to each device and you get the advantages of using fixed IPs without the hassle of dealing with a non-dhcp network.
Of course, if you've turned off your SSID and are using MAC filtering, you're actively trying to make devices you attach to your network *not* work, so I'd correct that error in configuration first. Neither of those improves your network security in any way, they will, however, cause problems with some devices. |
|
Quoted:
DHCP only is part of the dumbing down of america and the proliferation of apple product users that think things "just work". Plus, it's less of a tech-support hassle, if there is a setting, users will fuck with it and not realize it broke something doing so. Solution: remove the setting and tech support calls go down. 
|
|
Quoted:
Quoted:
DHCP only is part of the dumbing down of america and the proliferation of apple product users that think things "just work". Plus, it's less of a tech-support hassle, if there is a setting, users will fuck with it and not realize it broke something doing so. Solution: remove the setting and tech support calls go down. I started to type out a reply to that, but I decided it was so far removed from reality it didn't even merit a response. |
|
I have been battling static items since I took over my job 6 months now. Why in gods green earth would you run a company of 24 employees on a /16. I had to change DNS servers about 3 months ago due to a system failure. It has been one thing after another that's broken because of it. DHCP can be a very useful tool when it comes to troubleshooting and major network wide changes. Almost all of my static items on my network are getting changed over to a DHCP reservation on its own VLAN and subnet.
|
|
Quoted:
Quoted:
Static can be useful in specific scenarios. Most of the time you'll be better off using DHCP and setting up reserved IPs for specific devices. Well put. Even in home use, I like to have networked printers and NAS devices on fixed addresses. True but you might as well set up DHCP to give the static address. That way you don't have to worry about setting up anything on the specific device and if it happens to lose it's settings down the road you won't have to look up what it was supposed to be set to |
|
Quoted: Quoted: Quoted: Static can be useful in specific scenarios. Most of the time you'll be better off using DHCP and setting up reserved IPs for specific devices. Well put. Even in home use, I like to have networked printers and NAS devices on fixed addresses. True but you might as well set up DHCP to give the static address. That way you don't have to worry about setting up anything on the specific device and if it happens to lose it's settings down the road you won't have to look up what it was supposed to be set to Which is what I do. I have the router set aside specific IP's for specific devices but everything is still DHCP. |
|
Quoted:
Quoted:
Create MAC address reservations for all your static devices. Yup! That's exactly what I did on my router. Posted Via AR15.Com Mobile ok ok ok I updated my router firmware today, it just came out last month.... so a whole reconfig was needed anyway set up a DHCP, and assigning IP's by MAC. now going about changing all the units on the lan.... I hope you're all happy now! 
|