Bob Pocius wrote: > I'm using Bering as a platform to help me route between buildings connected > to my network. In some cases, routing has to hop more than once (up to 3 > times). Using standard routing commands, I don't seem to be able to fix > this. Here is what my network looks like. Site 1 is the main segment. Site 2 > connects directly to Site 1. Site 3 connects directly to Site 2. Below are > the (what I feel are necessary) routes to make things work. > > Site 1: 10.10.1.0 > Destination Mask Gateway > 0.0.0.0 0.0.0.0 10.10.1.254 > 10.10.12.0 255.255.255.0 192.168.1.253 > 10.10.13.0 255.255.255.0 192.168.1.253
Why doesn't data destined for the 10.10.12.0 network go out a nic that's on the 10.10.12.0 network? It looks like you're trying to move that data out a nic that's not even on the same subnet. > Site 2: 10.10.12.0 > Destination Mask Gateway > 0.0.0.0 0.0.0.0 192.168.1.254 > 10.10.12.0 255.255.255.0 10.10.12.254 > 10.10.13.0 255.255.255.0 192.168.2.253 > > Site 3: 10.10.13.0 > Destination Mask Gateway > 0.0.0.0 0.0.0.0 192.168.2.254 > 10.10.13.0 255.255.255.0 10.10.13.254 > > I've been using this command to create my tables. > #ip route add <address> /<masklen> via <gateway> > > Any thoughts or suggestions would be appreciated. > > Bob In addition to what I mentioned above, how does the 10.10.12.0 network know how to route packets back to the 10.10.1.0? I don't see any route to get that data back there. How does the 10.10.13.0 network know how to get data to the 10.10.12.0 network? I think that needs a route also. Without return routes, the data goes out the default GWs. Is that where you want them going? Do you ipchains or iptables? Feel like posting the ruleset? It might help if the routes aren't the problems, but I think they are. Regards, Matthew _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
