InformAction Forums

A bit more help, usually when the modem craps and renews the IP, since all DSL/Cable users have dynamic IPs now unless you pay for a static, given your pool name, you are getting DSL and you have a dynamic IP that can change anytime, although usually within the same block assigned to your ISP; the OS automatically gets the updated information and all is well in the world. Windows updates pretty well.

HOWEVER, occassionally the network layer is stuck and your Layer 2 and 3 don't update right. Just open a command prompt, type ipconfig /renew and wait a few and it will release the old information, force the adapters to update and you are golden. Sometimes if it has REALLY gone bad, which is rare but happens, no biggie. 1) unplug the router/mode (usually they are one unit nowadays but if two units, plug the MODEM back in first and THEN the router, make sure your PPPoE information is correct), then 2) reboot your machine and all will be well. Good luck.

therube wrote:

> The advice is to never start your default P with -no-remote

There's no real reason to say that. The "default" is immaterial. So long as one Profile, regardless of which one, is started without the -no-remote switch you won't run into the issue you mentioned (& depending, you may not run into them anyway).

Sure, but the "advice" is for the bewildered Fx user, not the superiorly equipped Seamonkey maven
If you got a couple profiles running, make sure you remember which one is -no-remote before you close it, or just never run your usual daily "default" -no-remote.
Nice extra power-user contribution by you, as always

Going to whatsmyip.com displays a different ip address than the one you labeled me with. Is that because it is being generated dynamically?
Thanks for your feedback. Regretfully I did not understand much because my skills in this area are rather basic.

Yes.

At least we an say I'm an 86'er whatever that means!

7leagues wrote:Going to whatsmyip.com displays a different ip address than the one you labeled me with. Is that because it is being generated dynamically?
Thanks for your feedback. Regretfully I did not understand much because my skills in this area are rather basic.

Yes, chances are by the time you went to check the IP had changed and you were assigned a new dynamic IP.

7leagues wrote:At least we an say I'm an 86'er whatever that means!

Well I'll tell you what it means. You are or more likely your ISP a client of France Telecom S.A. and they have been given a batch of public addresses (86.192.0.0/16) which means they can assign IPs in the range of 86.192.0.0 through 86.255.255.255 to their clients or for their own uses. So your 86.192-86.255 precursors, gives away that you belong to their batch of addresses and pretty much who your provider and location is, that's all. Now keep in mind the 86.192.0.0 is a network address, so not usable and also the 86.255.255.255 is a broadcast address, again not usable, so technically its the rest that can be assigned

Very informative! Yes, I am indeed a client of France Telecom. The only thing that falls down in the equation is my location which my browser always identifies as Clermont-Ferrand. It may be that this is the closest large city however I am exactly 346 km from Clermont-Ferrand so not very accurate.

7leagues wrote:Very informative! Yes, I am indeed a client of France Telecom. The only thing that falls down in the equation is my location which my browser always identifies as Clermont-Ferrand. It may be that this is the closest large city however I am exactly 346 km from Clermont-Ferrand so not very accurate.

Your geolocation based on your ISP/IP address are ALWAYS inaccurate, in fact it is VERY rare unless you are your own provider that it would be accurate because the center/hub where the networks are located that serve the customer are NEVER where the customer lives. So that means it would always show much further away than you actually live. HOWEVER, that being said, generally if you are an ISP client, you are living within 1500 yards of a distribution center as longer than that and ISP signals break down, unless they use repeater and booster stations.

So its a roughly close enough estimate to guess where a person is, even if truly speaking useless and inaccurate. So since you are being served by AClermont-Ferrand-551-1-206-122.w86-207.abo.wanadoo.fr that means this pool has to be close enough to your location to support the signal limitation needed. Although not a bullseye on your location, a good indicator of the region you are in. Let's analyze the servers data to say, the region would be Champagne-Ardenne and the city would be approximately Feuges and the coordinates Longitude 4.112, Latitude 48.398 giving an accessible highway regions of E17/A26 and E54/A5. Look at the map, close enough?



Anyway, have fun and enjoy

GµårÐïåñ wrote:Let's analyze the servers data to say, the region would be Champagne-Ardenne and the city would be approximately Feuges and the coordinates Longitude 4.112, Latitude 48.398 giving an accessible highway regions of E17/A26 and E54/A5. Look at the map, close enough?

Nope, way off!

As I have said from the beginning, it doesn't matter no one cares where YOU live, just where your ISP is located and that is accurate and is a matter of fact. Your distance to it is often obscured by the fact that boosters and pinelines extend through substations that don't have identifiers and are just dummy relays. When my address is not showing up in Germany and rest of Europe while I live in the US, it still shows me over 140 miles off from where I ACTUALLY live, but the ISP location is good indicator at the very least as to what state, region and county you are in. The rest if someone is motivated can come from ISP records to located your billing address. Just has to be worth it and usually it is not. Hope that helps you understand what I was trying to show you.

I understood from the outset. I was just amused at how this technology led you to the area you posted in that map because it was completely in the opposite direction from the initial point of departure (i.e. Clermont-Ferrand). I do thank you for all your explanations however; you have been most helpful.

Naming convention used by the ISP is not necessarily accurate to the actual location, just what they consider to be an appropriate indicator on their records. For example, you have your equipment and servers in Paris (just an example) and then you lose that location or choose to relocate to say Nice, the severs and IP records might still say Paris, but not worth the cost to reidentify or reassign new location identifiers. Specially if you are serving some off beat location or subletting your lines to other companies. As a high level network engineer, I can tell you, there are A LOT of cost and time and need factors that go into these things and you would not be surprised to hear that companies take the cheapest, easiest and laziest approach to save money. It annoys perfectionists like myself but unless you get the approved budget to do it, you are stuck. I usually do it on my own time to make myself feel better about the setup but even then you have to clear it with the IT inventory people, who are usually in charge of updating the database records and prefer to not do it.