|
Potential there... However I'm not up to speed in linux notation. In IBM
i terminology NETSTAT *IFC shows up 127.0.0.1 on a line description of
*LOOPBACK. What would that be for Linux?
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Roberto José Etcheverry Romero" <yggdrasil.raiker@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: 08/08/2018 08:39 AM
Subject: Re: HMC: IBM recommended I turn off local loopback.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Ah but I think that is not a case of "turn off the loopback interface"
which, IIRC, is lo0 but take off the IP from a real interface that's not
in
use.
Maybe having the loopback IP on a not-in-use interface messes with the
real
loopback?
Roberto
On Tue, Aug 7, 2018 at 5:09 PM, DrFranken <midrange@xxxxxxxxxxxx> wrote:
I would want to know why. Almost any computer today 'talks to itself'some
using the loopback. Linux is no exception. HMC is Linux.
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 8/7/2018 3:51 PM, Rob Berendt wrote:
While working with a serviceable event on my HMC they had me send in
thedumps.
A tangent on their analysis was that they recommended that I turn off
listlocal loopback.This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
HMC Management
Network Settings
Change network settings.
Select eth0, Details
Change from:
Specify an IP address
TCP/IP interface address: 127.0.0.1
TCP/IP interface network mask: 255.0.0.0
to:
No IPv4 address
I wasn't really given a reason why. Should I just do it?
eth3 is the one really in use.
Rob Berendt
--
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.