public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed

From: Brian Rak <brak@vultr•com>
To: netdev@vger•kernel.org
Subject: Missing IPv4 routes
Date: Fri, 23 Oct 2015 17:34:11 -0400	[thread overview]
Message-ID: <562AA7D3.9030905@vultr.com> (raw)

I've got a weird situation here.  I have a route that the kernel knows 
about, but won't display via the general RTM_GETROUTE call, but will 
display if I query for that particular route:

# ip -4 route show | grep 108.61.171.x
# ip route get 108.61.171.x
108.61.171.x dev MYIF
     cache
# cat /proc/net/route | grep 108.61.171.x
#
# cat /proc/net/route  | grep -i 6c3dac
#
# ip route add 108.61.171.x dev MYIF
RTNETLINK answers: File exists
# ip route del 108.61.171.x  <---- it deletes successfully once
# ip route del 108.61.171.x
RTNETLINK answers: No such process


This is on a machine running 4.1.3, but I have seen it on earlier 
versions in the past.

I don't have great reproduction steps here, I've seen this 4-5 times in 
the past few months (on different hardware).  So far, I haven't really 
found any way of fixing it (deleting and readding the route has no 
effect).  I thought at first this might be related to 
e55ffaf457bcc8ec4e9d9f56f955971f834d65b3, but as far as I can tell that 
only relates to /proc/net/route.

Any suggestions on further troubleshooting here?  I'm all out of ideas 
(and since I can't easily reproduce it yet, I can't reboot to a newer 
kernel to see if it goes away)

next             reply	other threads:[~2015-10-23 21:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 21:34 Brian Rak [this message]
2015-10-23 22:32 ` Missing IPv4 routes Alexander Duyck
2015-10-24 13:32   ` Brian Rak
2015-10-26 15:28     ` Alexander Duyck
2015-10-26 16:57       ` Brian Rak
2015-10-27 20:01         ` Brian Rak
2015-10-27 20:29           ` Alexander Duyck

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=562AA7D3.9030905@vultr.com \
    --to=brak@vultr$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox