Hi, My question isn't really shorewall-specific, but I thought it could be of interest to the mailing list.
I use shorewall's rtrules file to route to different providers. I also do the same on the command line with: ip rule del pref 11400 ip rule add pref 11400 from 10.215.144.7 to 10.0.0.0/8 lookup PROVIDER1 ip route flush cache then I run the following to remove a route rule: ip rule del pref 11400 ip route flush cache The problem I'm seeing is the following: a) on a Linux host with IP addr. 10.215.144.7 a command such as "tracepath 10.1.2.3" works *immediately* as expected in both of the cases described above b) on a Windows machine with IP addr. 10.215.144.7 a command such as "tracert -d 10.1.2.3" works *sometimes* immediately, but at times I need to wait at least 20 seconds or so. On occasions I might also need to wait almost a full minute. On the Shorewall gateway/router I do *nothing* after the last "ip route flush cache" command. Why are these clients behaving differently? As I said before, Linux clients always behave as expected so there must be something I'm unaware of on other systems. Vieri _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
