tag 404956 + moreinfo unreproducible
thanks

Hello!

I'm having a look at an old iproute bug, http://bugs.debian.org/404956,
where you have reported that the semantics of ip rule flush changed.
The bug was filed against version 20061002-3 and I've tried to see how
it acted in previous versions.

I've now tried all of these old upstream releases:

iproute2-2.6.11-050310.tar.gz  iproute2-2.6.14-051107.tar.gz
iproute2-2.6.11-050314.tar.gz  iproute2-2.6.15-060110.tar.gz
iproute2-2.6.11-050330.tar.gz  iproute2-2.6.16-060323.tar.gz

... and for me they all work the same as the current version when it
comes to ip rule flush, meaning they delete every rule they can when
flushing (which is what I would expect of a flush command). This leaves
only the one rule that can not be deleted:
        0:      from all lookup local 


There seems to be two possible problems mentioned in the bugreport:
- change in what a command does between iproute versions
- command does something else then expected.

The first one would clearly not be very nice, but as I've tried several
of the previous versions and can't see any change in what happens I need
more info to reproduce that problem - for now I'll have to treat it as
"if you can't see it, it's not there".

The second problem might be a bit more fuzzy, and should probably be
discussed more - since it might just as well be a misunderstanding of
the command rather then a bug.

The ip manpage contains description of what the default rules are, and
it also mentions that the 0 rule is special and can't be deleted. This
is not stated for the other two default rules, so if you want to use ip
rule flush to restore the defaults you should also add back these two
other rules. Flush doesn't mean "restore defaults" for any ip commands
as far as I know. It means delete everything. Flush should, if used at
all, always be used very carefully.

Could you please provide some more insight into this bugreport?

-- 
Regards,
Andreas Henriksson




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to