Bug 151759

Summary: ip route flush fails
Product: [Fedora] Fedora Reporter: John Dennis <jdennis>
Component: net-toolsAssignee: Radek Vokál <rvokal>
Status: CLOSED WORKSFORME QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 4   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-03-22 15:04:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Dennis 2005-03-22 02:45:10 UTC 
% /sbin/ip route flush cache
Cannot open "/proc/sys/net/ipv4/route/flush"

The above pretty much says it all. FWIW /pro/sys/net/ipv4/route looks fully
populated, all the files are "644 root root". I filed the bug against FC4t1, but
in truth this is a rawhide machine, so its a week or two more current than FC4t1.
Comment 1 Radek Vokál 2005-03-22 15:04:25 UTC 
Ehm, I've never used this before so here're my observations

# ip route show cache
- shows a big mess of different routes

# ip --statistics route flush cache  
*** IPv4 routing cache is flushed.
(according to a man page, it should show no. of flushed routes, I'll check this)

# ip route show cache
broadcast 192.168.1.255 from 192.168.1.21 dev lo  src 192.168.1.13
    cache <local,brd,src-direct>  iif eth0

eg. it shows only one route, a broadcast message, so it might have appeard right
after the flush command. The problem of flush command is that it doesn't flush
all routes immediatelly but there's a delay which may cause dealy. If you call
`show cachce` right after flushing it there still might be old data.

This comes from my tests on FC4t1 (installed 5mins ago :)