|
||||||||
So, the questions still stands, will m0n0 handle 5 public ips the way I want it to in this instance. And will it act as a VPN endpoint the way I am looking for? Thanks. -J On 8/29/06, Steve Thomas <sthomas at consultant dot com> wrote: > > > Sure Jimmy! > > >>what would work best given the use? > > You could use the same config I suggested. > Keep the Dlink for the web server, and use m0n0wall for the LAN. > > If they need to upload code to the web server, they could just use > RDP (forward 3389 through the Dlink). > > I always do whatever I can to avoid double NAT configs and just > have the web server on it's own network. > > > > > ----- Original Message ----- > > From: "Jimmy Bones (Mhottie)" <mhottie at gmail dot com> > > To: m0n0wall at lists dot m0n0 dot ch > > Subject: Re: [m0n0wall] Multiple Public WAN IPs and VPN endpoint. > > Date: Tue, 29 Aug 2006 04:21:32 -0400 > > > > > > Thank you, Steve. > > > > I should have mentioned, it is a small network used primarily for > in-house > > development of VB, and web apps. They use all servers internally for > > different things, then want the webserver to have it's own public IP > because > > they host these apps for testing. Aside from the errors of having code > on a > > public machine, and multi using servers (these aren't things that are > going > > to change) what would work best given the use? > > > > They currentlly have the cable modem going to a crappy d-link router > that > > then port forwards 80 -> web server. So they are only using 1 of their 5 > ips > > right now (for the Dlink, everything else is NAT) and want to utilize > more > > of them. > > > > -J > > > > > |