Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[kargo27]

I'm testing an older Netgear (can I say that here)  and it was a refurb.  The previous owner had the router setup as DHCP server (default setting for this router) but with 10.0.0.1 as the LAN IP address.

I switched it back to 192.168.x.x just because that's what my other routers were setup as.

I don't know if it's that network traffic got heavier in the meantime but I swear that web pages load much faster with the 10.0.0.1 setup.  Is it all in my head???   

[FurryNutz]

unless NG has programmed there routers to work better on using a different address pool, shouldn't be any different. It's just a address. I use a 6.#.#.# address for my routers.  . You might figure out the address Karl, by looking at the recently returned RMA box to your facility. 

[Hard Harry]

He probably had someone from his work IT or something set it up. 10.0.0.0 > 10.255.255.255 is used more in business environments because of the broader range of IP's. 192 are just reserved to the second octet, while 10 are reserved to the 3rd.

As for what you use. I don't think you should use a 6.x.x.x IP. That will conflict if your ever trying to access a server at that IP. 6.x.x.x is a Class A public IP range, so there servers out there with IP in that range.

[FurryNutz]

Wouldn't the NAT handle the translation from WAN to LAN though? Been using Class A for the LAN side for years with out problems. And who would be accessing my LAN side from a class A site anyways?   

[Hard Harry]

Hmm...it can still cause problems. Granted NAT would track Public traffic to private traffic, but your routing tables would over ride DNS and your DNS cache would cause issues. So say Milk.com was at 6.1.2.3, and a computer A on your network wanted to go to it, it would ask your router where Milk.com was and your router would to a DNS look up and answer 6.1.2.3 and you would get to Milk.com and computer A would store that IP in it's DNS cache. But say IP address of computer B was 6.1.2.3, when computer A would next try to go to Milk.com, it would say "oh I already know how to get there" and send traffic to 6.1.2.3, the router would take that request and send it to computer B. So that's one problem. Never-mind how it would effect the loop back in computer B's own routing tables. Overall it would just be messy.

More to the point, what is the benefit of using such a range?

[FurryNutz]

I guess I wanted to get away from 192 and the privates and since I'm a guy who likes intuitive things, making the address somewhat intuitive for me and other users kinda helps one to know what IP address pool there working from.

It can also help in troubleshooting as you and I both know, using the 192 pool can cause troubles between some routers and modems. 

[kargo27]

He probably had someone from his work IT or something set it up. 10.0.0.0 > 10.255.255.255 is used more in business environments because of the broader range of IP's. 192 are just reserved to the second octet, while 10 are reserved to the 3rd.

As for what you use. I don't think you should use a 6.x.x.x IP. That will conflict if your ever trying to access a server at that IP. 6.x.x.x is a Class A public IP range, so there servers out there with IP in that range.

Ummmm...........I thought we discussed you working all this overtime.      

[kargo27]

BTW, I think you guys are right, it was just in my head.  

Edit:  Nope, I take that back.  It's faster with the 10.x.x.x

Furry, I'm going to change my IP's to yours.    Not really.

[Hard Harry]

It can also help in troubleshooting as you and I both know, using the 192 pool can cause troubles between some routers and modems. 

How so? You mean modem/router gateways?

[FurryNutz]

Yes, there some modems and gateways that we've ran across that just happens to use the same IP address as routers. Not often though.

[Hard Harry]

BTW, I think you guys are right, it was just in my head.  

Edit:  Nope, I take that back.  It's faster with the 10.x.x.x

Furry, I'm going to change my IP's to yours.    Not really.

Yea, there is no way your IP range can have any effect on performance. It would be like saying that when my phone number has a 5 in it, it sounds clearer. Sorry, doesn't make sense. ::grin:: I think you were right the first time, its a false positive.

[kargo27]

Yea, there is no way your IP range can have any effect on performance. It would be like saying that when my phone number has a 5 in it, it sounds clearer. Sorry, doesn't make sense. ::grin:: I think you were right the first time, its a false positive.

Our phone number DOES have a 5 in it!  No wonder it's so clear.  Whut??? 

[Hard Harry]

In retrospect, it could be you have QOS rules or something pointed to the 192 IP range, that when you change a 10.x.x.x range, they don't apply. Thats the only difference I can think of.

And dude..mine has a 5 in it too! All those fake phone numbers in movies must be super clear.

[kargo27]

In retrospect, it could be you have QOS rules or something pointed to the 192 IP range, that when you change a 10.x.x.x range, they don't apply. Thats the only difference I can think of.

And dude..mine has a 5 in it too! All those fake phone numbers in movies must be super clear.

LOL!

I'll check the QoS, Harry.  You could be onto something.  Did you see where I commented about your HP 8500?  I have the same one!

[Hard Harry]

Yea I saw that. It was a mixture of compatibility issues with Vista and some confusion on the HP website exactly which package to use. Some of it may have been human error on my part too, can't rule that out, but i was pretty careful. Once Furry showed me how to find the ini, it was smooth sailing. And I was able to do it without any HP software at all, so that's a plus. I shouldn't have insulted a entire company based on a couple experiances though, thats not cool, hence my apology.