lkml.org 
[lkml]   [2012]   [Jul]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: PROBLEM: Can ping address, but traceroute gets ENETDOWN
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


[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2012-07-17 17:41    [W:3.885 / U:0.484 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site