* TCP over lo
@ 2010-05-03 20:00 Chuck Lever
0 siblings, 0 replies; only message in thread
From: Chuck Lever @ 2010-05-03 20:00 UTC (permalink / raw)
To: netdev
I've got a bug report about attempting to mount a remote NFSv4 server
while the client's lo interface is down.
Apparently a TCP connection attempt over lo when it is DOWN results in
ETIMEDOUT. If I attempt a TCP connect on eth0 when it is DOWN I get
ENETUNREACH.
Is this behavior difference by design? Is there some other information
I'm missing? Just wondering how to go about addressing the issue.
Thanks in advance for advice.
--
chuck[dot]lever[at]oracle[dot]com
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-05-03 20:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-03 20:00 TCP over lo Chuck Lever
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.