From: "Paul Rolland" <rol@witbe.net>
To: Terry Phelps <tgphelps50@gmail.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
linux-kernel@vger.kernel.org, rol@witbe.net
Subject: Re: PROBLEM: Can ping address, but traceroute gets ENETDOWN
Date: Tue, 17 Jul 2012 15:55:39 +0200 [thread overview]
Message-ID: <20120717155539.1a6dbfc4@tux.DEF.witbe.net> (raw)
In-Reply-To: <CAMUfR_vpEJ=Spd+A5tunDxOttdVk_0RXWHX91HGUf9hGdEa10w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
Hello,
On Tue, 17 Jul 2012 09:41:27 -0400
Terry Phelps <tgphelps50@gmail.com> wrote:
> On Tue, Jul 17, 2012 at 9:30 AM, Eric Dumazet <eric.dumazet@gmail.com>
> wrote:
> > On Tue, 2012-07-17 at 09:04 -0400, Terry Phelps wrote:
> >> socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
> >> setsockopt(3, SOL_IP, IP_MTU_DISCOVER, [0], 4) = 0
> >> setsockopt(3, SOL_SOCKET, SO_TIMESTAMP, [1], 4) = 0
> >> fcntl(3, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
> >> setsockopt(3, SOL_IP, IP_TTL, [1], 4) = 0
> >> setsockopt(3, SOL_IP, IP_RECVERR, [1], 4) = 0
> >> connect(3, {sa_family=AF_INET, sin_port=htons(33434),
> >> sin_addr=inet_addr("192.168.118.22")}, 28) = 0
> >> sendto(3, "@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_"..., 40, 0, NULL, 0) = -1
> >> ENETDOWN (Network is down)
ENETDOWN should mean your interface is no more in the UP status.
Could it be you have some processes running that could turn down and up
your interfaces ? Anything in /var/log/messages about eth0 ?
Paul
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-07-17 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 13:04 Terry Phelps
2012-07-17 13:30 ` Eric Dumazet
2012-07-17 13:41 ` Terry Phelps
2012-07-17 13:55 ` Paul Rolland [this message]
2012-07-17 15:03 ` Terry Phelps
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120717155539.1a6dbfc4@tux.DEF.witbe.net \
--to=rol@witbe.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tgphelps50@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®