Date: Tue, 15 Feb 2000 18:51:22 -0800 From: "Fred J. Lomas" <aj@8hill.com> To: "Ryan Thompson" <freebsd@sasknow.com> Cc: <freebsd-questions@freebsd.org> Subject: RE: Natd Message-ID: <LPBBKHJOEEAHCKOFDBKFEEBHCAAA.aj@8hill.com> In-Reply-To: <Pine.BSF.4.10.10002151944120.63285-100000@sasknow.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It's getting clearer now, but I do not have a file called natd.conf I have rc.conf ,so now what do I do?? like I stated this version of BSD has been tweaked to do this web server stuff so, I mean it doesn't even have the man pages on it , but the ipfw and natd are the standard stuff.......so Hmmmmmm. I do have version 3.3 installed on another box that I have been messing with but I am not to deep into yet, I just installed it last night that went ok so I can at least look at the man pages there, any other suggestions. I greatly appreciate everyone's comments!!!!!!!!! :-) -----Original Message----- From: Ryan Thompson [mailto:freebsd@sasknow.com] Sent: Tuesday, February 15, 2000 5:53 PM To: Fred J. Lomas Cc: freebsd-questions@freebsd.org Subject: Re: Natd On Tue, 15 Feb 2000, Fred J. Lomas wrote: > so that command you sent me where would I add that at, I checked for > that natd.conf and I don't have it, this version of bsd has been > tweaked out, but the ipfw and natd stuff is standard bsd version 2.2.7 , You add that command (redirect_port...) in a file called natd conf in /etc/. I don't know what editor you use, but if you are a total NEWBIE, as you say, you probably want something with lots of help plastered all over it. Try ee :-) So, type the following while you are logged in as root: ee /etc/natd.conf .. Which will bring up a nice editor window with a blank file. natd.conf doesn't exist already, because you DON'T really need it, but it helps keep your natd_flags line short in rc.conf. My natd.conf is over 1K... I would shudder at throwing all those options on a single line in rc.conf :-) Then... Type in the necessary options. In my two previous posts, I've given you many different options to put in /etc/natd.conf. Your natd.conf might look something like: # This is a comment # The name of your network interface belongs here: interface pn0 # Redirect all packets addressed to port 27015 to the machine # 192.168.101.12, on port 27015. redirect_port tcp 192.168.101.12:27015 27015 Save the file. Be sure to edit /etc/rc.conf and make the changes I mentioned earlier. Add the following lines, if they are not there already: natd_enable="YES" natd_flags="-f /etc/natd.conf" > so if you need more if a description I can send you exactly what I am > trying to do and my whole setup . sorry I am really trying to get the > hang of this, please be patient with me people, I am a total NEWBIE!! If you still can't get going after these instructions, do send us your exact configuration and exactly what you are trying to do :-) Last message quoted in full for reference: > Ryan Thompson wrote: > > > > On Tue, 15 Feb 2000, Fred J. Lomas wrote: > > > > > Cool, that side is cool all that works , what I want to be able to do is > > > come from the internet to my Internal LAN through a NT terminal server > > > client and I want to be able to put my game server online which is on my > > > NT box and setup a FTP server. so i guess I need to tell it when I come > > > in through the WAN IP to forward it to the certain ports on the NT box, > > > > >From NATD(8): > > > > -redirect_port proto targetIP:targetPORT [aliasIP:]aliasPORT > > [remoteIP[:remotePORT]] > > Redirect incoming connections arriving to given port to an- > > other host and port. Proto is either tcp or udp, targetIP is > > the desired target IP number, targetPORT is the desired tar- > > get PORT number, aliasPORT is the requested PORT number and > > aliasIP is the aliasing address. RemoteIP and remotePORT can > > be used to specify the connection more accurately if neces- > > sary. For example, the argument > > > > tcp inside1:telnet 6666 > > > > means that tcp packets destined for port 6666 on this machine > > will be sent to the telnet port on the inside1 machine. > > > > > Im just not sure about how to do that I need to tell it to go from > > > x.x.x.x to the internal LAN which is 192.168.101.12:27015 which is my > > > game server am I making sense or just confusing my self more.... HAHA! > > > thanks for your help too > > > > Your description WAS a bit confusing... Perhaps you can clarify with some > > examples what you are trying to do. For example, in /etc/natd.conf of > > the machine that will be doing the nat: > > > > redirect_port tcp 192.168.101.12:27015 27015 > > > > I haven't tested it, but that should redirect all connections directed at > > your (FreeBSD) machine that is doing the NAT to your game server on the > > internal lan (192.168.101.12) from port 27015 to port 27015. > > > > - Ryan Thompson -- Ryan Thompson <ryan@sasknow.com> 50% Owner, Sysadmin SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 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?LPBBKHJOEEAHCKOFDBKFEEBHCAAA.aj>