On Tuesday 03 June 2003 16:20, giangy wrote:
remote nets local net 10.30.2.0 bridge 10.30.3.0 -------router--------10.30.1.0----------firewall ----- router to internet
Chain PREROUTING (policy ACCEPT) target prot opt source destination .... REDIRECT tcp -- 10.30.1.108 anywhere tcp dpt:http redir ports 3128 REDIRECT tcp -- 10.30.3.141 anywhere tcp dpt:http redir ports 3128
10.30.1.108 works fine 10.30.3.141 no answer ...
Do you have a routing table entry for net 10.30.3.x? This doesn't look like a bug to me. What do the rule counters say? What about tcpdump?
Bart
IT WORKS!!!
adding routing table entries for remote nets now redirect works!
Since I could reach remote hosts WITHOUT routing entries... why does the kernel need it???
thanks gianluca
_______________________________________________ Bridge mailing list [EMAIL PROTECTED] http://www.math.leidenuniv.nl/mailman/listinfo/bridge
