> The problem here is that you have USE_DEFAULT_RT=No and copy routes from
> the main table to the provider cable. The main table had that route and
> it has been copied into the 'dmz' table. That was a bug in the
> CLEANUP.patch I sent. The attached DUPLICATE.patch should eliminate the
> problem.
>
Nope, the same thing is still there.
>> When I have statements of the sort of:
>>
>> routes
>> ~~~~
>> main 10.0.0.0/8 blackhole
>> main 172.16.0.0/12 blackhole
>> main 192.168.0.0/16 blackhole
>>
>> That seems to be translated to:
>>
>> run_ip route add blackhole 10.0.0.0/8 table 254
>> echo "$IP -4 route del blackhole 10.0.0.0/8 table 254 >
>> /dev/null 2>&1" >> ${VARDIR}/undo_main_routing
>> run_ip route add blackhole 172.16.0.0/12 table 254
>> echo "$IP -4 route del blackhole 172.16.0.0/12 table 254 >
>> /dev/null 2>&1" >> ${VARDIR}/undo_main_routing
>> run_ip route add blackhole 192.168.0.0/16 table 254
>> echo "$IP -4 route del blackhole 192.168.0.0/16 table 254 >
>> /dev/null 2>&1" >> ${VARDIR}/undo_main_routing
>>
>> (note table numbers instead of names).
>>
>
> BUILTINTABLES.patch corrects this problem.
>
This has indeed been fixed.
------------------------------------------------------------------------------
Own the Future-Intel® Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game
on Steam. $5K grand prize plus 10 genre and skill prizes.
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
_______________________________________________
Shorewall-devel mailing list
Shorewall-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-devel
