Static IP

Will post my reasoning in a moment, just finishing up with some other stuff here.

Looking forward to this, always struggle to explain stuff like this to laymen
None of the analogies I use make sense to them
 
Looking forward to this, always struggle to explain stuff like this to laymen
None of the analogies I use make sense to them

:o ... I started ... then stopped, realizing it will take more than 2 minutes. Will return when I have more than 2 minz to spare.
 
Thanks man - really appreciate! Makse no difference to me - but curious as to why that IP?
Or a technical reason?

Your DHCP server, your router, issues (leases) IPs within a fixed range*. Device 1 will tend to always get the 1st IP in the range x.x.x.001. Device 2 then gets x.x.x.002 and so forth for every device becoming active on the network. This means that each device has a unique IP in the end. If you now want to introduce a static IP device onto this network your best bet would be to always assign a high IP within the range (in this case I went for x.x.x.240) as the chance of your (home?) network having enough devices to actually saturate the range all the way to x.x.x.240 is rather slim. In other words, for your router to actually issue the ip x.x.x.240 and cause an IP conflict (something that we don't want) it would need to have issued all the 240 odd IPs before that already to 240 odd live devices in your network. Once again, I assumed this was a home network and that you would not have so many devices. To add to this, I never go for the top range x.x.x.(250-255) as I've seen some routers use this for their own.

In your specific case the gateway/router was 192.168.10.001 and I assumed that 192.168.10.240 would not be issued and thus be available.

*I've had a look at your router and it is set, by default, to only issue IPs from a fixed range/pool of 100 IPs starting from ~192.168.10.101. The IP we assigned to your PC is 192.168.10.240 and is thus outside of any IP conflict danger. We could have used any IP, 192.168.10.249, as long as long as it was not in use or was in danger of being issued by your router easily in the course of normal use. :D

... that worries me.

Why?
 
Last edited:
Thanks - appreciate it!

Did we not post information that shouldn't be available in the public, such as the IP? Wasn't sure if his comment on good information was sarcastic?
 
Did we not post information that shouldn't be available in the public, such as the IP? Wasn't sure if his comment on good information was sarcastic?

Do not stress. Your router makes use of a completely private IP namespace: 192.168.0.0 - 192.168.255.255
None of these IPs can be 'reached' in a manner of speaking by the internet as they are only designated for private internal network use.

Pinging 192.168.10.240 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
Thanks for the detailed help and explanation! All working perfectly - was just paranoid ... hehe
 
As mentioned above, 8.8.8.8 is a service provided by our dear old Google. Should your ISP have some kind of a DNS failure your PC will route DNS requests to the secondary DNS. It is also easy to remember - a big plus. In the past DNS failures happened more than what one would like to admit but these days not so much. I just tend to still do it ... 'just in case'.

The DNS converts the www.mybroadband.co.za, that you type in, to the actual computer IP, 41.203.21.137 in this case, so that your computer knows who to call up each time you open up this site. :D
 
Top
Sign up to the MyBroadband newsletter
X