IP Address in Derby, I'm in London

Paul_Herring

old_codger1 wrote: »

Trust me, they are.

I believe my definition of 'anyone' substantially differs from yours.

There are too many people using IP geolocation for inappropriate things. i.e. more than one.

For example, those relying on it for (area) targetted advertising are a prime example of not being aware of the limitation.

Paul_Herring

old_codger1 wrote: »

This might be worth reading for those interested in such things.
[...]
The allocation of your IP address happens before you can get any websites, emails or whatever.

And geolocation relies on leases being long enough to last through outages such as
x) turning off your router to your ISP for 5 seconds
x) turning off your router to your ISP for 5 weeks

Which is why it's not reliable. It's a guide, certainly, but cannot be relied upon.

<going off topic...>
Simplistic example - my office PC(s) - I occasionally need to access it from home (over VPN) - I generally know which address on 192.168.0/24 it's at, but it occasionally changes.

Unnoticed changes involve me using nmap, and other stuff, to find out which box on that network will accept my ssh keys. (Yes, I know there's a solution to this - it's not worth doing it at the moment.)
</off></topic>

old_codger1

Paul_Herring wrote: »

I believe my definition of 'anyone' substantially differs from yours.

probably!!!

Paul_Herring wrote: »

There are too many people using IP geolocation for inappropriate things. i.e. more than one.

For example, those relying on it for (area) targetted advertising are a prime example of not being aware of the limitation.

Well, it's certainly true to say many people's idea of the way stuff works is often incorrect but I think they'll find out sooner rather than later.

old_codger1

Paul_Herring wrote: »

And geolocation relies on leases being long enough to last through outages such as
x) turning off your router to your ISP for 5 seconds
x) turning off your router to your ISP for 5 weeks

Which is why it's not reliable. It's a guide, certainly, but cannot be relied upon.

Er.... OK! :Confused:

Paul_Herring wrote: »

<going off topic...>
Simplistic example - my office PC(s) - I occasionally need to access it from home (over VPN) - I generally know which address on 192.168.0/24 it's at, but it occasionally changes.

Unnoticed changes involve me using nmap, and other stuff, to find out which box on that network will accept my ssh keys. (Yes, I know there's a solution to this - it's not worth doing it at the moment.)
</off></topic>

Can't you tell your dhcp server to attach 192.168.1.20, or whatever, to your mac address? In 'nix you'd put something like...

host codger (
hardware ethernet xx:xx:xx:xx:xx:xx;
fixed-address 192.168.1.20;
)

in /etc/dhcpd.conf file. The ('s should be open and close curly braces of course.

Obviously, you'd have to put the IP address outside the pool.