Re: Outgoing email with exim, was Re: Strange LAN IP Address.

[mick crane]

On 2018-07-04 04:40, Mike McClain wrote:

On Tue, Jul 03, 2018 at 05:42:15PM -0500, David Wright wrote:

On Tue 03 Jul 2018 at 08:52:22 (-0700), Mike McClain wrote:
> On Mon, Jul 02, 2018 at 03:17:27PM -0400, Stephen P. Molnar wrote:
> 
> Should anyone reading this know hjow to get exim4 to connect to
> outbound.att.net I'd love to hear about it.

Curt got the wiki, and my googling landed on
https://www.att.com/esupport/article.html#!/dsl-high-speed/KM1010523
and
https://www.att.com/esupport/article.html#!/email-support/KM1240308
It looks as though these are more up to date than the wiki.

In the first, I assume that the table rows are labelled wrongly,
but it seems to show SMTP on smtp.mail.att.net ports 465 or 587
as well as the hostname you gave. I would also try port 587 on
both hostnames: it won't be the first to give the wrong one.

The second shows how to get a suitable password for your userID.
(I would use this approach merely because I don't know anything
about oath.)

Anyway, what doesn't work for you and what response do you get
from exim?


What doesn't work? Can't send mail.
Long before Verizon and Oath were involved with Yahoo.

When I switched from dialup AT had me using port 465 and at that
time I was getting some kind of authorization error but couldn't find
out what.

# /etc/exim4/update-exim4.conf.conf
dc_eximconfig_configtype='smarthost'
dc_local_interfaces='127.0.0.1'
dc_smarthost='outbound.att.net::465'

Here's an excerpt from current exim's log:
2018-07-03 19:51:29 1faXd0-0008Gb-JB Remote host
smtp.att.mail.fy4.b.yahoo.com [67.195.228.97] closed
connection in response to initial connection
2018-07-03 19:51:59 1faXd0-0008Gb-JB == nialccm.e...@gmail.com
R=smarthost T=remote_smtp_smarthost defer (-18): Remote host
smtp.att.mail.fy4.b.yahoo.com [98.136.96.82] closed connection in
response to initial connection

Switching update-exim4.conf.conf to read:
dc_smarthost='outbound.att.net::587'

exim's log now shows:
2018-07-03 20:15:24 1faYFl-6U-4d ** mikemcclain...@att.net
R=smarthost T=remote_smtp_smarthost: SMTP error from remote mail
server after MAIL FROM:<> SIZE=2464: host
smtp.att.mail.fy4.b.yahoo.com [67.195.228.97]: 550 Request failed;
Mailbox unavailable

This last message shows a further complication. I have a primary email
account with ATT as well as several aliases,. I also have a Yahoo
account, likewise gmail and am likely to use any of them as the source
(From:, ReplyTo: headers) in outgoing mail depending on where it's 
going.

I only have one, the primary, in /etc/exim4/passwd.client for ATT.

My dialup doesn't care what I call myself when I send email but
perhaps ATT/Yahoo does.

No I haven't tried to get that special password.

What I've got works, I guess I'll leave it rather than jump through
hoops for Verizon.

Thanks for the references.
Mike


think with yahoo you have to login on their web site and register the 
sending email address to use their SMTP


mick




--
Key ID4BFEBB31

Re: Outgoing email with exim, was Re: Strange LAN IP Address.

[Mike McClain]

On Tue, Jul 03, 2018 at 05:42:15PM -0500, David Wright wrote:
> On Tue 03 Jul 2018 at 08:52:22 (-0700), Mike McClain wrote:
> > On Mon, Jul 02, 2018 at 03:17:27PM -0400, Stephen P. Molnar wrote:
> > 
> > Should anyone reading this know hjow to get exim4 to connect to
> > outbound.att.net I'd love to hear about it.
>
> Curt got the wiki, and my googling landed on
> https://www.att.com/esupport/article.html#!/dsl-high-speed/KM1010523
> and
> https://www.att.com/esupport/article.html#!/email-support/KM1240308
> It looks as though these are more up to date than the wiki.
>
> In the first, I assume that the table rows are labelled wrongly,
> but it seems to show SMTP on smtp.mail.att.net ports 465 or 587
> as well as the hostname you gave. I would also try port 587 on
> both hostnames: it won't be the first to give the wrong one.
>
> The second shows how to get a suitable password for your userID.
> (I would use this approach merely because I don't know anything
> about oath.)
>
> Anyway, what doesn't work for you and what response do you get
> from exim?

What doesn't work? Can't send mail.
Long before Verizon and Oath were involved with Yahoo.

When I switched from dialup AT had me using port 465 and at that
time I was getting some kind of authorization error but couldn't find
out what.

# /etc/exim4/update-exim4.conf.conf
dc_eximconfig_configtype='smarthost'
dc_local_interfaces='127.0.0.1'
dc_smarthost='outbound.att.net::465'

Here's an excerpt from current exim's log:
2018-07-03 19:51:29 1faXd0-0008Gb-JB Remote host
smtp.att.mail.fy4.b.yahoo.com [67.195.228.97] closed
connection in response to initial connection
2018-07-03 19:51:59 1faXd0-0008Gb-JB == nialccm.e...@gmail.com
R=smarthost T=remote_smtp_smarthost defer (-18): Remote host
smtp.att.mail.fy4.b.yahoo.com [98.136.96.82] closed connection in
response to initial connection

Switching update-exim4.conf.conf to read:
dc_smarthost='outbound.att.net::587'

exim's log now shows:
2018-07-03 20:15:24 1faYFl-6U-4d ** mikemcclain...@att.net
R=smarthost T=remote_smtp_smarthost: SMTP error from remote mail
server after MAIL FROM:<> SIZE=2464: host
smtp.att.mail.fy4.b.yahoo.com [67.195.228.97]: 550 Request failed;
Mailbox unavailable

This last message shows a further complication. I have a primary email
account with ATT as well as several aliases,. I also have a Yahoo
account, likewise gmail and am likely to use any of them as the source
(From:, ReplyTo: headers) in outgoing mail depending on where it's going.
I only have one, the primary, in /etc/exim4/passwd.client for ATT.

My dialup doesn't care what I call myself when I send email but
perhaps ATT/Yahoo does.

No I haven't tried to get that special password.

What I've got works, I guess I'll leave it rather than jump through
hoops for Verizon.

Thanks for the references.
Mike
--
Where man is there will be trouble to the end of time,
if not of one sort, then of another."
- Louis L'Amour

Re: Strange LAN IP Address.

[David Wright]

On Tue 03 Jul 2018 at 19:59:18 (+0200), Pascal Hambourg wrote:
> Le 03/07/2018 à 02:42, David Wright a écrit :
> >On Mon 02 Jul 2018 at 21:58:15 (+0200), john doe wrote:
> >
> >>It could be that the ISP router went into "bridge mode" (router
> >>function was disabled).
> >
> >Which is rather worrying as you are exposed to the Internet
> >without any security.
> 
> Why "without any security" ?
> Bridge mode does not cancel the intrinsic security of the host.

We're not talking about the host(s), but the LAN side of the
modem-router, as you do here:

> Besides, the security provided by the router mode is questionable. I
> would not rely on any ISP-provided device for my LAN security.

… which was the opinion expressed in my next paragraph:

"My advice would be to ditch it and get separate units. […] have full
control over the router."

Cheers,
David.

Outgoing email with exim, was Re: Strange LAN IP Address.

[David Wright]

On Tue 03 Jul 2018 at 08:52:22 (-0700), Mike McClain wrote:
> On Mon, Jul 02, 2018 at 03:17:27PM -0400, Stephen P. Molnar wrote:
> 
> > 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 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.
> 
> ATT tech support demonstrated to me that they can change the
> settings remotely.
> If they can so can some one else.
> 
> > I spent 40 minutes, on hold for 28 of those minutes, with an AT
> > UVVerse technical () person without hearing any reasons why the
> > IP was what it was.
> 
> When I signed up with ATT Uverse I accumulated hours on the phone
> trying to get email out through their server. I gave up and used my
> dialup account.
> Their tech support -- isn't. Many of those people didn't grow up
> with computers and have no idea what goes on under the hood. Even when
> you get someone in Dallas rather than Manila answers and understanding
> can be lacking.
> 
> Should anyone reading this know hjow to get exim4 to connect to
> outbound.att.net I'd love to hear about it.

Curt got the wiki, and my googling landed on
https://www.att.com/esupport/article.html#!/dsl-high-speed/KM1010523
and
https://www.att.com/esupport/article.html#!/email-support/KM1240308
It looks as though these are more up to date than the wiki.

In the first, I assume that the table rows are labelled wrongly,
but it seems to show SMTP on smtp.mail.att.net ports 465 or 587
as well as the hostname you gave. I would also try port 587 on
both hostnames: it won't be the first to give the wrong one.

The second shows how to get a suitable password for your userID.
(I would use this approach merely because I don't know anything
about oath.)

Anyway, what doesn't work for you and what response do you get
from exim?

Cheers,
David.

Re: Strange LAN IP Address.

[Pascal Hambourg]

Le 03/07/2018 à 02:42, David Wright a écrit :

On Mon 02 Jul 2018 at 21:58:15 (+0200), john doe wrote:


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


Which is rather worrying as you are exposed to the Internet
without any security.


Why "without any security" ?
Bridge mode does not cancel the intrinsic security of the host.
Besides, the security provided by the router mode is questionable. I 
would not rely on any ISP-provided device for my LAN security.

Re: Strange LAN IP Address.

[Curt]

On 2018-07-03, Mike McClain  wrote:
>
> Should anyone reading this know hjow to get exim4 to connect to
> outbound.att.net I'd love to hear about it.
>

There's the (perhaps outdated) wiki:

https://wiki.debian.org/ATTUverseExim4

Maybe you are already aware of the wiki.

Re: Strange LAN IP Address.

[Mike McClain]

On Mon, Jul 02, 2018 at 03:17:27PM -0400, Stephen P. Molnar wrote:

> 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 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.

ATT tech support demonstrated to me that they can change the
settings remotely.
If they can so can some one else.

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

When I signed up with ATT Uverse I accumulated hours on the phone
trying to get email out through their server. I gave up and used my
dialup account.
Their tech support -- isn't. Many of those people didn't grow up
with computers and have no idea what goes on under the hood. Even when
you get someone in Dallas rather than Manila answers and understanding
can be lacking.

Should anyone reading this know hjow to get exim4 to connect to
outbound.att.net I'd love to hear about it.

Mike
--
Where man is there will be trouble to the end of time,
if not of one sort, then of another."
- Louis L'Amour

Re: Strange LAN IP Address.

[Joe]

On Tue, 03 Jul 2018 10:53:27 +0100
Jeremy Nicoll  wrote:

> On Tue, 3 Jul 2018, at 07:19, john doe wrote:
> 
> > You are correct in the case of an ADSL "router".
> > 
> > Sadly, in the case of my European ISP I'm stuck with what they give
> > me! I must say that I've never investigated how I could use my own
> > cable modem and understand the kind of restriction they're using to
> > prevent me from doing that!!! :)  
> 
> I've a Virgin Media cable connection in the UK.  They supply a
> combined modem/router.But the unit can be put into modem-only
> mode, and used with a different router.  
> 
> So far as I remember the first of these combined things that I
> received came with only very basic instructions that did not mention
> the way to do this - it was Virgin's own technical support people who
> told me how to do it.Subsequent improved models have come with
> instructions that mentioned the possibility.
> 

In general, there is no need to switch to modem only, unless you
definitely want to handle the public address directly on your firewall.
Almost always, you can put your own NAT firewall behind an existing NAT
router without problems.

I say almost, because about ten years ago, a client of mine moved
premises and was given a new router which detected any such second NAT
stage and refused to function. Not a bug, a deliberate policy. Really
quite annoying, I needed to reconfigure several network machines to
work with this router, and lost my detailed firewall control.

-- 
Joe

Re: Strange LAN IP Address.

[Jeremy Nicoll]

On Tue, 3 Jul 2018, at 07:19, john doe wrote:

> You are correct in the case of an ADSL "router".
> 
> Sadly, in the case of my European ISP I'm stuck with what they give me!
> I must say that I've never investigated how I could use my own cable 
> modem and understand the kind of restriction they're using to prevent me 
> from doing that!!! :)

I've a Virgin Media cable connection in the UK.  They supply a combined
modem/router.But the unit can be put into modem-only mode, and
used with a different router.  

So far as I remember the first of these combined things that I received
came with only very basic instructions that did not mention the way to
do this - it was Virgin's own technical support people who told me how
to do it.Subsequent improved models have come with instructions 
that mentioned the possibility.

-- 
Jeremy Nicoll - my opinions are my own.

Re: Strange LAN IP Address.

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Jul 03, 2018 at 08:19:44AM +0200, john doe wrote:

[...]

> You are correct in the case of an ADSL "router".
> 
> Sadly, in the case of my European ISP I'm stuck with what they give me!

There are people working on exactly that. One example:

  https://wiki.fsfe.org/Activities/CompulsoryRouters

[disclaimer: I support these folks]

So you could do worse than to direct your energy towards helping one of
those initiatives, instead of just being furious at "ISP" or "Europe".

If the politicians never hear from you, they'll ignore you :)

Cheers
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAls7JJ0ACgkQBcgs9XrR2kbMUQCfdzTwFLvQEIyxAIefwcv+K+bw
sKkAn2pQ2hQC85kk6V+9H4mogoDuYjBN
=OkFZ
-END PGP SIGNATURE-

Re: Strange LAN IP Address.

[john doe]

On 7/3/2018 2:42 AM, David Wright wrote:

On Mon 02 Jul 2018 at 21:58:15 (+0200), john doe wrote:

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 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
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)?


Looks like it. Here's the first hop of the OP's posting:

  Received: from 162-237-98-238.lightspeed.clmboh.sbcglobal.net (EHLO
  [192.168.1.123]) ([162.237.98.238]) by smtp431.mail.bf1.yahoo.com
  (Oath Hermes SMTP Server) with ESMTPA ID
  665b52fd3833c7e5d4ced5690502aed7 for ;
  Mon, 02 Jul 2018 19:17:29 + (UTC)


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


Which is rather worrying as you are exposed to the Internet
without any security.


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.


Sounds like you have a combined modem/router. My advice would be to
ditch it and get separate units. This means you can, if you like, use
the modem your line provider supplies (which means they can't blame
you for any incompatibilities with the wire), but you have full
control over the router. (It also gives you more flexibility with
their siting.)

It even means you can independently test the modem safely, by booting
a live system from a stick and connecting directly to the modem port.
(You will then see your address as 162.237.98.238 for the right reason.)

My own experience is that an ADSL modem should be left running 24/7 as
that prevents it having to retrain. OTOH there's no harm in rebooting
a router whenever you think it might be misbehaving.



You are correct in the case of an ADSL "router".

Sadly, in the case of my European ISP I'm stuck with what they give me!
I must say that I've never investigated how I could use my own cable 
modem and understand the kind of restriction they're using to prevent me 
from doing that!!! :)



An alternative to DDWRT is OpenWrt.

If your willing to  fealed that security gap it clearly make sence to 
check the list of compatible device (OpenWrt DDWrt ...) so if you don't 
like the stock firmware you can change it!



A fanless server solution could be:
https://www.pcengines.ch/

On that box yu could install pfsense, Debian, IPFire...

If your stuck with your ISP "router" you could try:
- Add your own router in the DMZ (you only use the ISP router for the 
modem part)
- Set your ISP modem in "bridge mode" or what ever it's called to turn 
everything off but the modem



The idea here is to have one way or an other your own "firewall" behind 
a modem.


--
John Doe

Re: Strange LAN IP Address.

[David Christensen]

On 07/02/18 12:17, 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 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 
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?

Thanks in advance.



On 07/02/18 14:03, Gene Heskett wrote:

Only if the problem continues after that router has been reflashed
with dd-wrt.


Beware that finding the correct build of dd-wrt and getting it into your 
device correctly is non-trivial.  I bricked a Netgear unit trying to 
upgrade dd-wrt.



On 07/02/18 17:42, David Wright wrote:
Sounds like you have a combined modem/router. My advice would be to 
ditch it and get separate units. This means you can, if you like,

use the modem your line provider supplies (which means they can't
blame you for any incompatibilities with the wire), but you have
full control over the router. (It also gives you more flexibility
with their siting.)

+1


There are many FOSS firewall/ router distributions -- grab an old PC, 
install a second NIC and/or WiFi card, install the distribution, 
configure it, and you're protected.  I've had good luck with:


http://www.ipcop.org/ -- Linux based, enough functionality for my SOHO 
network, not too complex.


https://www.pfsense.org/ -- FreeBSD based, huge functionality, can get 
very complex.



I alternatively ran one of the above 24x7 for years on older P3 and P4 
machines, which drew too much power and generated too much heat and 
noise.  I contemplated building a compact, energy-efficient, silent PC 
(mini-ITX, etc.), but the cost was not appealing.  I had a WiFi access 
point for WiFi devices.



After the WiFi AP died, I retired the P3/P4 FOSS router and switched to 
a Netgear WiFi firewall/ router.  I did get dd-wrt working for a while, 
but then bricked it when I tried to upgrade dd-wrt.



After asking opinions on various mailing lists, I settled on Ubiquiti 
Networks "UniFi" products:


https://unifi-sdn.ubnt.com/


I have a UniFi security gateway and a UniFi AC Lite Wifi access point. 
I disabled WiFi on my AT VDSL residential gateway and configured it to 
pass-through everything to the UniFi security gateway.  As David Wright 
mentioned, I can still connect a laptop directly to the AT gateway for 
trouble-shooting.  The AP AC Lite has plenty of coverage and bandwidth 
for my small home with 8+ WiFi devices.



For me, the killer feature of UniFi is that you adopt devices into 
networks and manage everything via a single integrated controller 
interface.  This is far simpler than trying to manage devices 
individually; especially so if/when I add a hardware controller, 
additional AP's, cameras, etc., and/or remote sites with VPN's between 
them.  I am not aware of any FOSS project offering this level of 
integration.



David

Re: Strange LAN IP Address.

[David Wright]

On Mon 02 Jul 2018 at 21:58:15 (+0200), john doe wrote:
> 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 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
> >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)?

Looks like it. Here's the first hop of the OP's posting:

 Received: from 162-237-98-238.lightspeed.clmboh.sbcglobal.net (EHLO
 [192.168.1.123]) ([162.237.98.238]) by smtp431.mail.bf1.yahoo.com
 (Oath Hermes SMTP Server) with ESMTPA ID
 665b52fd3833c7e5d4ced5690502aed7 for ;
 Mon, 02 Jul 2018 19:17:29 + (UTC)

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

Which is rather worrying as you are exposed to the Internet
without any security.

> 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.

Sounds like you have a combined modem/router. My advice would be to
ditch it and get separate units. This means you can, if you like, use
the modem your line provider supplies (which means they can't blame
you for any incompatibilities with the wire), but you have full
control over the router. (It also gives you more flexibility with
their siting.)

It even means you can independently test the modem safely, by booting
a live system from a stick and connecting directly to the modem port.
(You will then see your address as 162.237.98.238 for the right reason.)

My own experience is that an ADSL modem should be left running 24/7 as
that prevents it having to retrain. OTOH there's no harm in rebooting
a router whenever you think it might be misbehaving.

Cheers,
David.

Re: Strange LAN IP Address.

[Gene Heskett]

On Monday 02 July 2018 15:17:27 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 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
> 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?
> 
Only if the problem continues after that router has been reflashed with 
dd-wrt.   Most routers have an NSA backdoor that something or somebody 
found.  dd-wrt is not such a critter.

In 15 years of running it, no one has come thru it that I didn't give 
credentials to do so. That I think, speaks rather highly of dd-wrt.

> Thanks in advance.



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Strange LAN IP Address.

[john doe]

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 
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 
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

Strange LAN IP Address.

[Stephen P. Molnar]

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 
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 
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?

Thanks in advance.

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1