Date: Tue, 26 Sep 2000 21:28:16 +0000 From: Craig Cowen <craig@allmaui.com> To: John F Cuzzola <vdrifter@ocis.ocis.net> Cc: freebsd-security@FreeBSD.ORG Subject: Re: ipfw + natd + Novell Message-ID: <39D114F0.46A3251@allmaui.com> References: <Pine.LNX.4.21.0009262042200.11911-100000@ocis.ocis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--------------FFAE8E796D64C9D8F931E9BD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Correct me if I am wrong but the 0 in your private network is an error. try making it a 1. Craig Cowen John F Cuzzola wrote: > Hello everyone, > I have a Novell Server that has been moved from a public ip to a private > one (192.168.0.6). The 192.168.0.xxx segment gets internet access through > a FreeBSD box using ipfw/natd. The Novell server needs to be accessable > from the internet from source addresses 142.42.22.xxx. So I tried to set > up a NAT for it as follows: > > natd -p 7500 -redirect_address 192.168.0.6 0.0.0.0 -a 207.24.168.5 > > ipfw add 10 divert 7500 ip from 142.42.22.0/24 to 207.24.168.5 > ipfw add 20 divert 7500 ip from 207.24.168.5 to 142.42.22.0/24 > > So 142.42.22.0/24 should be able to get to the novell server using > 207.24.168.5 as its ip. Using the Windows Client they can connect and see > the NDS tree but when they try to log in the connection times-out. I know > there are some programs that wont work through NAT (like the ones that > insist on reporting back the private ip address). I was wondering if > anyone has had experience logging into a Novell Server with NAT. Can it > be done? > > Thank-you > JohnC > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message -- Craig Cowen 408-394-6673 Cell craig-pager@allmaui.com --------------FFAE8E796D64C9D8F931E9BD Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> Correct me if I am wrong but the 0 in your private network is an error. <br>try making it a 1. <p>Craig Cowen <p>John F Cuzzola wrote: <blockquote TYPE=CITE>Hello everyone, <br>I have a Novell Server that has been moved from a public ip to a private <br>one (192.168.0.6). The 192.168.0.xxx segment gets internet access through <br>a FreeBSD box using ipfw/natd. The Novell server needs to be accessable <br>from the internet from source addresses 142.42.22.xxx. So I tried to set <br>up a NAT for it as follows: <p>natd -p 7500 -redirect_address 192.168.0.6 0.0.0.0 -a 207.24.168.5 <p>ipfw add 10 divert 7500 ip from 142.42.22.0/24 to 207.24.168.5 <br>ipfw add 20 divert 7500 ip from 207.24.168.5 to 142.42.22.0/24 <p>So 142.42.22.0/24 should be able to get to the novell server using <br>207.24.168.5 as its ip. Using the Windows Client they can connect and see <br>the NDS tree but when they try to log in the connection times-out. I know <br>there are some programs that wont work through NAT (like the ones that <br>insist on reporting back the private ip address). I was wondering if <br>anyone has had experience logging into a Novell Server with NAT. Can it <br>be done? <p>Thank-you <br>JohnC <p>To Unsubscribe: send mail to majordomo@FreeBSD.org <br>with "unsubscribe freebsd-security" in the body of the message</blockquote> <pre>-- Craig Cowen 408-394-6673 Cell craig-pager@allmaui.com</pre> </html> --------------FFAE8E796D64C9D8F931E9BD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39D114F0.46A3251>