----
> Charles Farinella
> Appropriate Solutions, Inc. (www.AppropriateSolutions.com)
> [EMAIL PROTECTED]
> voice: 603.924.6079 fax: 603.924.8668
>
>
>
--
View this message in context:
http://www.nabble.com/pf-examples-needed-tf3021355.html#a8440660
Sent from the openbsd user - misc mailing list archive at Nabble.com.
Charles Farinella wrote:
On Tue, Jan 16, 2007 at 09:32:02AM -0500, Charles Farinella wrote:
I have an OpenBSD 3.9 machine with a public IP providing NAT and
firewalling for our internal network. It has 3 interfaces:
dc0: public ip from internet X.X.X.25
dc1: 192.168.100.x to internal network.
Hi Charles,
If you try to access X.X.X.25 from within 192.168.100.x it will not
work. Because of the NAT.
The same apply for 192.168.200.x.
It will be much easy to have two separate firewalls, one for browsing
and one for servers.
Rosen
Charles Farinella wrote:
Thanks to all for the help.
Charles Farinella wrote:
Thanks to all for the help.
Martin Toft wrote:
On Tue, Jan 16, 2007 at 09:32:02AM -0500, Charles Farinella wrote:
I have an OpenBSD 3.9 machine with a public IP providing NAT and
firewalling for our internal network. It has 3 interfaces:
dc0: public ip from internet
On Tue, Jan 16, 2007 at 12:23:45PM -0500, Charles Farinella wrote:
> Thanks to all for the help.
>
> Martin Toft wrote:
> >On Tue, Jan 16, 2007 at 09:32:02AM -0500, Charles Farinella wrote:
> >>I have an OpenBSD 3.9 machine with a public IP providing NAT and
> >>firewalling for our internal networ
Thanks to all for the help.
Martin Toft wrote:
On Tue, Jan 16, 2007 at 09:32:02AM -0500, Charles Farinella wrote:
I have an OpenBSD 3.9 machine with a public IP providing NAT and
firewalling for our internal network. It has 3 interfaces:
dc0: public ip from internet X.X.X.25
dc1: 192.168.100.
On Tue, Jan 16, 2007 at 04:44:03PM +0100, Martin Toft wrote:
> On Tue, Jan 16, 2007 at 09:32:02AM -0500, Charles Farinella wrote:
> > I have an OpenBSD 3.9 machine with a public IP providing NAT and
> > firewalling for our internal network. It has 3 interfaces:
> >
> > dc0: public ip from interne
On Tue, Jan 16, 2007 at 09:32:02AM -0500, Charles Farinella wrote:
> I have an OpenBSD 3.9 machine with a public IP providing NAT and
> firewalling for our internal network. It has 3 interfaces:
>
> dc0: public ip from internet X.X.X.25
> dc1: 192.168.100.x to internal network. This works well.
On Tuesday, January 16, 2007, Charles Farinella wrote:
> I have an OpenBSD 3.9 machine with a public IP providing NAT
> and firewalling for our internal network. It has 3 interfaces:
>
> dc0: public ip from internet X.X.X.25
> dc1: 192.168.100.x to internal network. This works well.
> dc2: 19
Charles Farinella wrote:
>
> I have an OpenBSD 3.9 machine with a public IP providing NAT and
> firewalling for our internal network. It has 3 interfaces:
>
> dc0: public ip from internet X.X.X.25
> dc1: 192.168.100.x to internal network. This works well.
> dc2: 192.168.200.x --> to Windows ser
I have an OpenBSD 3.9 machine with a public IP providing NAT and
firewalling for our internal network. It has 3 interfaces:
dc0: public ip from internet X.X.X.25
dc1: 192.168.100.x to internal network. This works well.
dc2: 192.168.200.x --> to Windows server.
I need to allow public access to
11 matches
Mail list logo