The standard IP access list has for a very long time been the exception to the rule that entries in an access list appear in the order in which they were entered. The standard IP access list will reorder entries so that any host specific entry appears before any subnet or network entry.
I have not seen it reorder host specific entries. But I guess that it is a possible effect of the reorder mechanism.
Or I wonder if there is some other possible explanation. Is it possible that in the version of access list 12 that you deleted was the 192.168.250.26 perhaps the first entry in the list? I have seen a few instances where there appears to be some persisting memory of things that were configured and then removed (the most obvious example are Frame Relay subinterfaces which still show up in show ip interface brief even after they are deleted from the config). If you remove the access list, reboot the router and then recreate the list does it still change the order? Or if you remove access list 12 and then create access list 13 (where no 13 had previously existed) does it still change the order?
interesting! I played a bit whith Davi's acl on a 3640 router running code 12.3 for sake of seeing how ios compliles acl in this particular example and it turns out if 172.25.2.254 is placed between 192.168.155.205 and 26 the order is seen proper..I could not still decipher why would the acl needed to be in this order to get proper acl order output, if I enter the acl in the order original implemented I would get a different output in the acl order.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...