Web lists-archives.com

Re: Strange LAN IP Address.




On 7/2/2018 9:17 PM, Stephen P. Molnar wrote:
I have my principle Debian Stretch platform on the LAN in our home. Two towers (both Linux platforms) and a HP Printer have wired connections, my Win 10 Laptop and two Android smartphones use WiFi connections.

This morning when I

When I tried using WinSCP on the Laptop to transfer a file from the principle Linux platform the connection attempt failed!

When I ran ifconfig on the Linux platform it showed the unet connection to be 162.237.98.238!!?????  The LAN modem employs DCHP set with allowed IP range as 192.168.1.64 through 192.168.1.253, which was set by the T&T installer when we switched to a fiber optic network.

Further examination of the modem settings showed IP Passthrough status as on (Public IP Address), which was, in fact the IP.

I spent 40 minutes, on hold for 28 of those minutes, with an AT&T UVVerse technical (????) person without hearing any reasons why the IP was what it was.

Note the tense at the end of the above sentence, because subsequent rebooting the modem restored the IP address to the correct DHCP range. I suppose the moral of this - first reboot the modem.

The question that I have, however, is how did this happen in the first place? Or is the reason lost in the black hole of the Internet?

Is this indicative of a hardware problem?


Could be hardware failure or could also be an software bug!

While searching for that IP I get:

https://www.ipligence.com/ip-address?ip=162.237.98.238

is this your public IP (IP assigned by your ISP)?

It could be that the ISP router went into "bridge mode" (router function was disabled).

Most of the time ISP router are not the best and I would suggest to anyone to not reley on that router for firewalling capability especially when ISPs can remotely control that thing!

In the case of my ISP I need to reboot my ISP router every week or so to get stable services.

--
John Doe