linux-kernel - Re: PROBLEM: Can ping address, but traceroute gets ENETDOWN

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 17 Jul 2012 11:03:39 -0400
From:	Terry Phelps <tgphelps50@...il.com>
To:	Paul Rolland <rol@...be.net>
Cc:	Eric Dumazet <eric.dumazet@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: Can ping address, but traceroute gets ENETDOWN

On Tue, Jul 17, 2012 at 9:55 AM, Paul Rolland <rol@...be.net> wrote:
> Hello,
>
> On Tue, 17 Jul 2012 09:41:27 -0400
> Terry Phelps <tgphelps50@...il.com> wrote:
>
>> On Tue, Jul 17, 2012 at 9:30 AM, Eric Dumazet <eric.dumazet@...il.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

(Paul, I'm resending this so it goes to the list.)

The interface is certainly up, because when I'm doing the traceroute
that gets the ENETDOWN, I'm SSH'ed into the box through eth0. And
other processes on the machines are running just fine.

And no, there are no messages in /var/log/* about eth0 that I've ever
seen. Everything works just fine except:
1. My desktop can't ping the box.
2. The box can't traceroute (but CAN ping!) my desktop.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/