[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Routing problem
- To: "Bill Moran" <wmoran_(_at_)_collaborativefusion_(_dot_)_com>
- Subject: Re: Routing problem
- From: "George Vanev" <george_(_dot_)_vanev_(_at_)_gmail_(_dot_)_com>
- Date: Thu, 8 Feb 2007 15:43:53 +0200
- Cc: FreeBSD Questions <freebsd-questions_(_at_)_freebsd_(_dot_)_org>
- Reply-to: George_(_dot_)_Vanev_(_at_)_gmail_(_dot_)_com
Nothing? You're able to arp 192.168.64.1 and 192.168.64.3, can you ping
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.
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
freebsd-questions_(_at_)_freebsd_(_dot_)_org mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscribe_(_at_)_freebsd_(_dot_)_org"
Visit your host, monkey.org