Date: Sat, 9 Mar 2002 21:46:50 -0000 From: "G D McKee" <freebsd@gdmckee.com> To: "Arthur Drake" <arthurdrake@hotmail.com> Cc: "Freebsd-Questions@Freebsd. Org (E-mail)" <freebsd-questions@freebsd.org> Subject: Re: Trouble connecting to a natd machine from within the network Message-ID: <003101c1c7b3$eba6b8d0$c800a8c0@p1000> References: <F273UcpVE855jHTpqU00001ecfe@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Why not set up dynamic DHCP and DNS and this will save you typing the stuff in!! The machines will auto register when they next renew there ip address. Works a treat here!! Gordon ----- Original Message ----- From: "Arthur Drake" <arthurdrake@hotmail.com> To: <tdv94ped@cs.umu.se> Cc: <freebsd-questions@FreeBSD.ORG> Sent: Saturday, March 09, 2002 9:41 PM Subject: Re: Trouble connecting to a natd machine from within the network > Thanks a lot, adding the address of the internal machine to /etc/resolv.conf > fixed it... but unfortunately it doesn't scale too well. Almost all of the > machines on the internal network use dhcp to get an ip address, so I guess I > have to either add 250 or so entries to the /etc/hosts file, or change the > behavior of FBSD. I guess it doesn't like ip addresses that don't reverse > dns properly? Hmmm... > > Anyway, thanks a lot for the help. Now that I have a workable solution and > a starting point, I can try to find a better solution to the problem. > > Thanks, > Art > > > > Hello! I have a FreeBSD 4.3-STABLE machine running natd for the rest of > >the > > > network. It runs the command "natd -f /etc/natd.conf -i vx0" on > >startup. > > > /etc/natd.conf has only one commented out line, so it essentially has > > > nothing in it. Natd translates from the vx0 public interface to the vx1 > > > private interface on 192.168.0.1. Both interfaces use a 3Com 595 card. > > > > > > Machines outside the network have no trouble connecting to the FBSD box, > >but > > > from within the network on all ports the connection takes a very long > >time > > > to start, and many programs (ftp clients, mail clients, etc.) time out > > > waiting to connect. It takes several minutes to start an ssh or ftp > > > session. Once I get connected it runs just fine, but it takes forever > >to > > > connect. This happens regardless of whether I connect to the private > >side > > > (192.168.0.1) or the public side (68.x.x.x) from within the network. > > > > > > Anybody have any ideas? I'd greatly appreciate any help. > > > >Got help with a similar problem this day, so maybe I can help you out. > > > >First of all, look that /etc/host.conf have the following order: > >hosts # Ask the file /etc/hosts first > >bind # If not found in /etc/hosts, ask your name server > > > >Put all your computers on your internal network in /etc/hosts. For ex- > >ample: > >127.0.0.1 localhost.your-domain.com localhost > >192.168.0.5 name1.your-domain.com name1 > >192.168.0.6 name2.your-domain.com name2 > > > >Check that /etc/resolv.conf has the following info: > >domain your-domain.com # Your computers domain > >nameserver dns1.com # The first name server > >nameserver dns2.com # The second name server > > > >Hopefully you find something useful in this info and get your FreeBSD > >working as good as it can be. :-) > > > >Best regards, > >Paul > > > > > _________________________________________________________________ > Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003101c1c7b3$eba6b8d0$c800a8c0>