rdr question

Hi list, is it possible to have the following: rdr on $ext_if proto tcp from any to any port 80 -> $server re-written as: rdr on $ext_if proto tcp from any to domain.com port 80 -> $server where "$server" an internal web server and "domain.com" a specific domain name? In general I would like

apachectl -> "Too many open files"

Hi there, when using the "apachectl" command I get the following: /usr/sbin/apachectl: /etc/rc.conf.local[90]: .: /etc/rc.conf.local: Too many open files why is that? Thanks

pf.conf troubles

Hi there, I just created the following: - ext_if="vr0" int_if="rl0" tcp_services = "{ 80, 20, 21, 22, 25, 110, 113 }" icmp_types = "echoreq" priv_nets = "{ 127.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12, 10.0.0.0/8 }" set block-policy return set loginterface $ext_if scrub in a

Re: pf.conf troubles

well, the silly one is simply me! I didn't see that after a "pf=YES" entry, it was one with a "NO"!!! Thanks George On Monday 09 May 2005 17:53, Jason Opperisano wrote: > On Sun, May 08, 2005 at 11:10:38PM +0200, GV wrote: > > Now, the above should normally

sshd and port 22

Hi there, Suddenly I have a strange situation. "sshd" is running but when I do via nmap a port scanning from another machine, port 22 isn't open!!! As a result I can't ssh to this machine! Also, when the server starts, following entry can be found in the "messages" file: inetd[7653]: could no

Re: sshd and port 22 [SOLVED]

I appreciate for your replies! It was a problem with the machine (a LINUX box!) I was initiating ssh! A firewall was running in the background and didn't realize! Thanks a lot for your time and support On Tuesday 10 May 2005 21:34, Jordan Klein wrote: > Take a look at your /etc/ssh/sshd_config

rdr to internal web server (pf.conf)

Hi, based to the given port number, I want to redirect an external call to my public IP to different web servers (they listen locally to port 80!) located inside my LAN. For example: IP:8000 --> 192.168.1.100 (on port 80!) IP:8001 --> 192.168.1.101 (on port 80!) when I try the above, pf is blo

Re: rdr to internal web server (pf.conf)[SOLVED]

Indeed. Thank you for your support George On Thursday 12 May 2005 21:41, Jason Dixon wrote: > On May 12, 2005, at 3:03 PM, GV wrote: > > based to the given port number, I want to redirect an external call to > > my > > public IP to different web servers (they list

openning ports on internal machines to the internet (pf.conf)

Hi, I have following LAN configuration: [ COMP_1 ] ... [ COMP_n ] || ADSL ---+--+-+--- int_if [ OpenBSD ] ext_if ( Internet ) "comp_1" ... "comp_n" are running a web base application and a number of ports on each machine h

exposing an internal server to the Internet

Hi, I have a situation where an internal (located in a LAN and behind a OpenBSD firewall/NAT) has to be fully exposed to the Internet! What's the best way to acieve that? Thanks George

Re: exposing an internal server to the Internet

for your support George On Saturday 14 May 2005 23:46, Abraham Al-Saleh wrote: > From man (5) pf.conf: > > "binat > A binat rule specifies a bidirectional mapping between an external > IP netblock and an internal IP netblock." > > read the pf.conf manual page for more in

Re: exposing an internal server to the Internet

d your question. If you only need mail > server ports, then use the rdr statement, which you can again read about in > the pf.conf man page. Otherwise, you will need to alias another ip to your > obsd box and binat traffic destined to that address to your mail server. > > On 5/14/05, GV

Re: exposing an internal server to the Internet [SOLVED]

YES! That was the problem! Thanks a lot! George On Sunday 15 May 2005 01:02, Arnaud Bergeron wrote: > On 5/14/05, GV <[EMAIL PROTECTED]> wrote: > > no, I don't need any port of that machine to be exposed to the Internet. > > Only a certain range. >

Re: exposing an internal server to the Internet

the pf.conf. George On Saturday 14 May 2005 23:42, Jason Dixon wrote: > On May 14, 2005, at 5:25 PM, GV wrote: > > Hi, > > > > I have a situation where an internal (located in a LAN and behind a > > OpenBSD > > firewall/NAT) has to be fully exposed to the Internet!

Re: openning ports on internal machines to the internet (pf.conf)

Thank you for your comments. George On Sunday 15 May 2005 00:57, Arnaud Bergeron wrote: > Sorry if this seems a bit out of order, because I commented as it came to > me. > > On 5/13/05, GV <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I have following

Re: exposing an internal server to the Internet

c between the target machine and the rest of your network > > > Internet PF target PF bridge private network. PF > bridge could be same HW as that which pf runs on. just need a couple > NIC's. > > Reg > > GV wrote: > >Hi, > >

Re: exposing an internal server to the Internet

for requires an > external IP for each of the internal servers. After that it is just a > matter of forwarding all ports from an external ip to an internal one, > applying firewall rules either on the gateway/router box or on the > internal server. > > Andreas > > On Sun, 2005-05-

Re: exposing an internal server to the Internet [SOLVED]

YES! That was the problem! Thanks a lot! George On Sunday 15 May 2005 01:02, Arnaud Bergeron wrote: > On 5/14/05, GV <[EMAIL PROTECTED]> wrote: > > no, I don't need any port of that machine to be exposed to the Internet. > > Only a certain range. >