Date: Tue, 13 Mar 2001 10:51:44 -0500 (EST) From: Peter Brezny <peter@black.purplecat.net> To: freebsd-net@freebsd.org Subject: route clarification Message-ID: <Pine.BSF.4.05.10103131046140.16675-100000@black.purplecat.net>
next in thread | raw e-mail | index | archive | help
I've managed to get things working, but I've still got a question or two. Here's what i'm working with > internet ---- firewal/nat box ---- client firewall ---- client lan. > pub pub/10.30.1.1 10.30.1.20/10.20.21.1 10.20.21.x From Right to Left, each machine's default GW is the internal address of the machine to it's left. So the workstations on the client lan have their GW set to 10.20.21.1 and so on. With this config, the workstations on the client lan could ping both the inside and outside interface of the client firewall, but not the firewall/nat box. the client firewall could ping everything on either side. FInally with some help i figured out that packets were probably making it to the firewall/nat box due to the default route, but wern't finding their way out of the firewall/nat box back to where they came from. placing a route route add -net 10.20.21.124 10.30.1.20 on the firewall/nat box fixed this problem. My question is, why didn't routed or something figure this out on its own? Is this normal? or is the firewall on the firewall/nat box causing problems? Thanks in advance for your help. pb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.10103131046140.16675-100000>