Date: Thu, 8 Feb 2007 15:43:53 +0200 From: "George Vanev" <george.vanev@gmail.com> To: "Bill Moran" <wmoran@collaborativefusion.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Routing problem Message-ID: <6f4f57f60702080543o6cc97d74qb337ef68eae94131@mail.gmail.com> In-Reply-To: <20070208083436.14bcef3f.wmoran@collaborativefusion.com> References: <6f4f57f60702080210m5d3ffbc1o33105f1b75564963@mail.gmail.com> <20070208080613.9eb65d64.wmoran@collaborativefusion.com> <6f4f57f60702080514n388e435fmfa7d46e10723be77@mail.gmail.com> <20070208083436.14bcef3f.wmoran@collaborativefusion.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > Nothing? You're able to arp 192.168.64.1 and 192.168.64.3, can you ping > them? > > Since you have an RFC-1918 address on both the inside and the outside, I > assume you're running nat on this machine to translate internal machine > traffic. It looks like you have all the routes you need, so my _guess_ > at this point is that when the public address is up, the nat is preventing > traffic from going out that interface without being translated. Once it > has a public address, it can't route properly on the 192.168.64/22 space. > > Have a look at what you're using for nat. If you can't see anything > obviously at odds, post your nat/firewall/related config. > > -- > Bill Moran > Collaborative Fusion Inc. > No I can't ping them. Just to be sure I switched off the natd... It's the same. I want the FreeBSD box to connect to both - internet and 192.168.64/22 and the I'll think of the nat -- George Vanev
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6f4f57f60702080543o6cc97d74qb337ef68eae94131>