Is your ISP doing NAT for you or is the obsd firewall the demarc? Just forward ports 80, 25, and probably 110 to the internal address of the server and you should be OK.
--TimH On Fri, 12 Dec 2003 22:29:18 +0000 "john marten" <[EMAIL PROTECTED]> wrote: > > We have had a range if ip addy's(xxx.xxx.xxx.xx) we've used forever. > Now our office > > is moving and our ISP says we will now be getting our #'s from them > (dhcp?) > > and that we don't need to do anything and that everything will work > > just fine. I'm pretty sure he's right about the Win pcs and the > > obsd firewall (packetfiltering bridge). but what about the obsd > > server that runs our web and email services? In resolve.conf it lists: > > search ourdomain.com > > lookup file bind > > nameserver xxx.xxx.xxx.xx > > nameserver ###.###.###.## > > Our nameservers will remain the same but our new addressing scheme is > something like > > 10.0.0.# > > Is there something he doesn't know about that I will probably have > > to change? Or is he right and everything will just plug and play? > > thoughts, comments, experiences? Regards, j > > _________________________________________________________________ > > [1]Winterize your home with tips from MSN House & Home. > > References > > 1. http://g.msn.com/8HMAENUS/2746??PS= > _______________________________________________ > EuG-LUG mailing list > [EMAIL PROTECTED] > http://mailman.efn.org/cgi-bin/listinfo/eug-lug _______________________________________________ EuG-LUG mailing list [EMAIL PROTECTED] http://mailman.efn.org/cgi-bin/listinfo/eug-lug
