Date: Fri, 16 Nov 2001 09:00:51 -0600 From: Eric Long <eric@metrotv.com> To: <cjclark@alum.mit.edu> Cc: <freebsd-questions@FreeBSD.ORG> Subject: Re: natd redirect_address Message-ID: <B81A8643.53A3%eric@metrotv.com> In-Reply-To: <20011116014854.D9851@blossom.cjclark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Without 66.100.208.36 bound to xl0, the above simply does not work. > So, give xl0 that address. Did that, it almost works now (already sent a message to the list with the same subject in regards to the problems). >> Traffic >> to 66.100.208.34 does not get redirected to 192.168.1.6. > Uhh... Well, you wrote 66.100.208.36 above. Typo? Yes, a typo. >> With 66.100.208.36 bound to xl0, it is saying that no alias address (using >> the alias_address command) is specified, and natd won't launch. > > Let's see your natd(8) and firewall configuration in rc.conf(5) and > rc.firewall (if it's been modified). Firewall's running in open mode. Regardless, the address redirection is almost working anyway. My natd.conf is as follows: redirect_address 192.168.1.6 66.100.208.36 port 8668 interface xl0 use_sockets yes same_ports yes log_denied yes >> I'm looking for clarification on what the alias_address should be (yes, I >> read man natd) and whether or not I should be binding this public ip the >> interface xl0 for use with natd address redirection. > > Huh? You shouldn't need to set alias_address if you use the interface > argument. What exactly are you trying to do? My thoughts exactly. Simply trying to get address redirection for connections destined for a public IP to go to a private IP on my LAN. It works fine from the outside world, but from the LAN, nothing can connect to the services if they try and access the services from the public IP. The workstations on the LAN can, however, access the services via the private IP's. From a DNS standpoint, I want one host to work for both WAN and LAN connections to the server on the LAN. For example, it's an apple file server, so asip.domain.com should access the file sharing services on the box whether the connection was initiated from the WAN or LAN. Right now, it's not working from the LAN (again, see my other message to the list with the same subject "natd redirect_address" with a more in depth description of the problem). -Eric 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?B81A8643.53A3%eric>