DHCP Question...
-
So, .1 is not reserved. You can put your gateway anywhere in your range. It is simplest, and typical to put it at .1. The reason why organizations do not create space in their DHCP scope for static addresses is that they are managing devices that would have been assigned static addresses in the past, via other means. One way is using DHCP reservations. Another is using a utility or print server so that the end point never needs to know the current IP address of a printer.
-
@JaredBusch posted several years ago about how he does it, and I've adopted it.
He avoids static whenever possible. There are times where you should absolutely use static (hypervisors/iLo/iDrac, etc).
But for things like servers and printers - instead of static, used DHCP reservations. This allows you to change IP settings for these devices from the DHCP stack instead of visiting each device and changing them manually.
You can still use a reservation for a device you set statically as well, just the DHCP server will never hand out that reservation, but you'll have a single list of what is assigned at least to the MAC level.
-
.1 isn't reserved, it's just a practice that people keep using.
-
.1 isn't reserved, but it's the practice that's most used .
Understood. -
@Kelly said in DHCP Question...:
Another is using a utility or print server so that the end point never needs to know the current IP address of a printer.
Have you found this to work? Even on print servers, I print to IP, and the server print queue is static to that IP.
I haven't used WSD ports on a server yet - have you? -
@DustinB3403 said in DHCP Question...:
.1 isn't reserved, it's just a practice that people keep using.
yeah, the places I came from used .254 as the gateway - so the whole .1 thing was weird for me.... but .1 is seen by all consumer gear today, and likely most commercial as well.
-
Yep I agree with others. Just don't use static IPs at all. If you don't have to use reservations that's even better.
-
@Dashrender said in DHCP Question...:
@Kelly said in DHCP Question...:
Another is using a utility or print server so that the end point never needs to know the current IP address of a printer.
Have you found this to work? Even on print servers, I print to IP, and the server print queue is static to that IP.
I haven't used WSD ports on a server yet - have you?I haven't tbh. I know about it, but it wasn't worth the investment to implement in prior environments. Now I have nothing to do with it.
-
@IRJ said in DHCP Question...:
Yep I agree with others. Just don't use static IPs at all. If you don't have to use reservations that's even better.
It's likely best to use DNS names when possible, because - who cares what the IP address is?
-
@Dashrender said in DHCP Question...:
@IRJ said in DHCP Question...:
Yep I agree with others. Just don't use static IPs at all. If you don't have to use reservations that's even better.
It's likely best to use DNS names when possible, because - who cares what the IP address is?
Yes and it makes restoring servers and services so much easier. It's nearly a must have for good DR.
-
@DustinB3403 said in DHCP Question...:
.1 isn't reserved, it's just a practice that people keep using.
Do you just reply to threads because you are bored?
-
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
.1 isn't reserved, it's just a practice that people keep using.
Do you just reply to threads because you are bored?
I've only replied to this thread. I'm not sure what you're on about.
-
@DustinB3403 said in DHCP Question...:
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
.1 isn't reserved, it's just a practice that people keep using.
Do you just reply to threads because you are bored?
I've only replied to this thread. I'm not sure what you're on about.
With zero relevant information
-
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
.1 isn't reserved, it's just a practice that people keep using.
Do you just reply to threads because you are bored?
I've only replied to this thread. I'm not sure what you're on about.
With zero relevant information
Gent Bent?
He asked stated .1 as being reserved. I proved it wasn't. I can't help it that @Kelly responded faster than I did.
-
@DustinB3403 said in DHCP Question...:
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
.1 isn't reserved, it's just a practice that people keep using.
Do you just reply to threads because you are bored?
I've only replied to this thread. I'm not sure what you're on about.
With zero relevant information
Gent Bent?
He asked stated .1 as being reserved. I proved it wasn't. I can't help it that @Kelly responded faster than I did.
At least his response was helpful. Taking a screenshot of you having gateway to
.50
isn't a convincing argument. -
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
.1 isn't reserved, it's just a practice that people keep using.
Do you just reply to threads because you are bored?
I've only replied to this thread. I'm not sure what you're on about.
With zero relevant information
Gent Bent?
He asked stated .1 as being reserved. I proved it wasn't. I can't help it that @Kelly responded faster than I did.
@Kelly made an intelligent response and
@DustinB3403 said in DHCP Question...:
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
.1 isn't reserved, it's just a practice that people keep using.
Do you just reply to threads because you are bored?
I've only replied to this thread. I'm not sure what you're on about.
With zero relevant information
Gent Bent?
He asked stated .1 as being reserved. I proved it wasn't. I can't help it that @Kelly responded faster than I did.
At least his response was helpful. Taking a screenshot of you having gateway to
.50
isn't a convincing argument.How is it not convincing? It's empirical proof that .1 isn't reserved for the purported purpose.
-
Take your arguing BS somewhere else ; keep it off my thread.
-
@DustinB3403 said in DHCP Question...:
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
.1 isn't reserved, it's just a practice that people keep using.
Do you just reply to threads because you are bored?
I've only replied to this thread. I'm not sure what you're on about.
With zero relevant information
Gent Bent?
He asked stated .1 as being reserved. I proved it wasn't. I can't help it that @Kelly responded faster than I did.
@Kelly made an intelligent response and
@DustinB3403 said in DHCP Question...:
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
@IRJ said in DHCP Question...:
@DustinB3403 said in DHCP Question...:
.1 isn't reserved, it's just a practice that people keep using.
Do you just reply to threads because you are bored?
I've only replied to this thread. I'm not sure what you're on about.
With zero relevant information
Gent Bent?
He asked stated .1 as being reserved. I proved it wasn't. I can't help it that @Kelly responded faster than I did.
At least his response was helpful. Taking a screenshot of you having gateway to
.50
isn't a convincing argument.How is it not convincing? It's empirical proof that .1 isn't reserved for the purported purpose.
If Dustin has a screenshot it must be undeniable evidence of something.
-
@WrCombs said in DHCP Question...:
Take your arguing BS somewhere else ; keep it off my thread.
You had your question answered. So whats the issue?
-
@IRJ said in DHCP Question...:
@WrCombs said in DHCP Question...:
Take your arguing BS somewhere else ; keep it off my thread.
You had your question answered. So whats the issue?
That's my Point: It's been answered, I don't want/nor need to see you guys Arguing about what ever the hell is it Dustin did or didn't do, or what your issue is with his replies.