Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
It's more fun to confuse people and use a /23 or larger and then use .0 or .255 as the router IP.
I tend to use the last ip in the range for the gateway.
I tend to use the last ip in the range for the gateway.
I tend to use the last ip in the range for the gateway.
Why? What's the point?
My take on this is that you might as well use .1 as the gateway to keep things simple. If you are trying to confuse potential "hackers", the last IP in the range is their second guess, followed by .2 and .254 lol. If that is what you are going for, I would use a completely random IP somewhere in the middle of the range.
It's all about a standard. He likes his use last IP standard, you like your use first IP standard. As long as it's followed everywhere, it doesn't really matter whether it's the first or last IP in the scope, as long as everything is the same to make things simple.
But last IP is NOT the standard. Even if he's not the only person to do it, regardless, it is not the standard, and should be considered wrong. When he leaves his job, his replacement shouldn't have to figure out all the stupid little things he did like that. Is it a big deal? Okay, no, not really. But is it wrong? Yes.
I don't think first IP is standard either. Maybe a convention, but not a standard.
Because someone decides to use an addressing convention that you don't like they're "WRONG" (all caps WRONG even)?It's by FAR the closest to a standard compared to anything else. I'd be willing to bet that .1 is used for a gateway more than everything else combined.
If you have a real reason not to follow the standard/convention of .1, fine, but if you're just doing it because you like to be different, then WRONG. Again, of all the things a network admin could do, this is FAR from the worst, but it's still a slight annoyance. Network administration is a science, not an art.
Because someone decides to use an addressing convention that you don't like they're "WRONG" (all caps WRONG even)?
It's not a standard, and there's no reason anyone should feel they should use it.
I've seen many that are .2, .50, .99, .240, and .254 - even on home networks (biggest local telco uses .254 on their equipment). Not so many .1's in my experiences.
I think the point he is trying to make is that the admin should have a good reason to use a gateway other than .1. You cannot deny that people traditionally expect the gateway to be .1- This is how networking is taught to students (that the gateway is normally .1).
Personally, our network is set up using .2 as the gateway, which was not my doing.
If you expect .1 to be the gateway then you're taught wrong, plain and simple. There is no standard, only conventions.
The only reasoning I can follow is to put the gateway top or bottom, anywhere in the middle is whacky, although I can't see why it matters. DNS and DHCP exist.
What's the problem having a PDC on .1 ?Lots of twits also use .1 for PDC. Giant pain in the ass. I had some networks where some genious put the PDC .1 then gateway at .10 . They installed a 2nd adapter and bridged.
Hmm..
For some reason we ran into a situation where this caused problems. Symptoms were the network connection being dropped often and not coming back online (wired network).
The environment is a PC with 2 NICs. One NIC is dedicated to a private secure VLAN while the other is on our normal production VLAN for remote access. When the NIC for the private VLAN was assigned 192.168.60.1 (.60 vlan), it became unstable.
The PC acts as a server for a video surveillance system, so technically there is no gateway as networks are not being traversed, however changing this IP from 192.168.60.1 to 192.168.60.10 resolved the issue.
Sounds like a duplicate IP on the network. What gateway do you have configured on your private network interface? (it should be empty). Also, you are using the term VLAN incorrectly, as VLANs have nothing to do with what you are trying to achieve. You can have two distinct IP networks on the same LAN or VLAN without issue.
What is the output of "route print" on this machine? There should be no persistent routes.