On Sep 22 2007 22:10, ben soo wrote: > > i used to add proxy arp's on the router when i had problems like this. Dunno > if it's the recommended fix, but it worked.
There is certainly no Proxy ARP required here since you do not do subnet sharing or funny games like that. > http://en.wikipedia.org/wiki/Proxy_arp > > Carlos Narváez wrote: >> +---------------+ . +----------------+ >> ¦ 192.168.251.1 +---+ 192.168.251.10 ¦ . +----------------+ >> +---------------+ . ¦ 192.168.254.17 +---+ 192.168.254.16 ¦ >> . . . . . . . . . . +----------------+ . +----------------+ >> >> - A route has been configured on 192.168.251.1 to point all traffic >> for 192.168.254.0/24 to 192.168.251.10. >> >> - A route has been configured on 192.168.254.16 to point all traffic >> for 192.168.251.0/24 to 192.168.254.17. >> >> - The command "iptables -I FORWARD -j ACCEPT" has been executed. Well, and do the counters increase? >> Now.. here's what happens. 192.168.251.10 can ping both interfaces on >> the router. 192.168.254.16 can also ping both interfaces on the >> router. However, 192.168.251.1 cannot ping 192.168.254.16, and >> likewise, 192.168.254.16 cannot ping 192.168.251.1. >> >> What have I forgotten? Default GWs (though if you ahve routes, ok..). On 251.1, use `ip r g 192.168.254.16` and it should show "192.168.254.16 via 192.168.251.10 dev eth0 ...". Same on the other side. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/