[pfSense Support] 0.75.1 ISO ..... Problems

2005-08-12 Thread David Strout

All,I see that there is a new ISO this morning and I pulled it down to try it and I get thevery same symptoms (all be it on the GX260 ... where you have pri master = HDD, sec master = CD-R/RW/ROM).It hangs STILL on the Waiting for Backend screen and I tried running the lua cammand that Scott had me try last night and get a different set of messages, but it still hangs and I have to CTRL-C out (twice).--David L. StroutEngineering Systems Plus, LLC




Re: [pfSense Support] Ping issue

2005-08-12 Thread Chris Buechler
On 8/12/05, Bill Marquette [EMAIL PROTECTED] wrote:
 Let me guess, the hosts initiating the PING are running Windows?  I'm
 pretty sure we've recently fixed this bug.  Care to try it?
 

With ipfilter 3.x (and hence m0n0wall) it doesn't matter if the hosts
are Windows or not.  It isn't even as smart as PF's behavior prior to
that latest patch.  Just doesn't work from multiple sources behind NAT
no matter what.

But yes, should be completely fixed here.  

-cmb

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [pfSense Support] ISO problems ... still on 0.75 / 0.75.1 iso version error?

2005-08-12 Thread Wesley Joyce
I am now only getting as far as 63% during the install when the CDROM is on
the secondary bus.  This is using pfSense-LiveCD-0.75.1 which for some
strange reason still boots and display 0.75 as the version.  Should I
download this from a different mirror?

 -Original Message-
 From: Scott Ullrich [mailto:[EMAIL PROTECTED]
 Sent: Friday, August 12, 2005 12:27 AM
 To: Wesley Joyce
 Cc: David Strout; support@pfsense.com
 Subject: Re: [pfSense Support] ISO problems ... still on 0.75
 
 0.75.1 is making its way to a mirror near you to fix a Lua bug.
 
 Scott
 
 
 On 8/12/05, Wesley Joyce [EMAIL PROTECTED] wrote:
 
 
 
  You're kidding right!?  I was able to get it to work with your last
 scenario
  and 0.74.8.  I will be trying 0.75 today (Friday)
 
 
 
  H.. how about trying a new IDE cable.
 
 
 
 
   
 
 
  From: David Strout [mailto:[EMAIL PROTECTED]
   Sent: Thursday, August 11, 2005 10:08 PM
   To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
   Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; support@pfsense.com
   Subject: [pfSense Support] ISO problems ... still on 0.75
 
 
 
 
  I can't say the same here ..
   I've tried the following ..
 
   pri master = 10GB HDD
   pri slave = empty
   sec master = empty
   sec slave = Samsung CD-ROM
 
   NOT WORKING !! Still hangs on the Waiting for Backend
 
   Next I tried .
   pri master = 10GB HDD
   pri slave = empty
   sec master = Samsung CD-ROM
   sec slave = empty
 
   NOT WORKING !! Same results
 
   Lastly I tried .
   pri master = 10GB HDD
   pri slave = Samsung CD-ROM
   sec master  slave = empty
 
   NOT WORKING !! Same results
 
 
   --
   David L. Strout
   Engineering Systems Plus, LLC
 
 
 
 
 
  - Original Message -
   Subject: Re: [pfSense Support] ISO problems ... still
   From: [EMAIL PROTECTED]
   To: [EMAIL PROTECTED]
   Date: 08-11-2005 8:02 pm
 
 
   Ok, I can second Dimitri. Moving the CD from Secondary Master to
   Primary Slave did the trick for me as well. On both pfSense on
   DesktopBSD. Haven't done FreeBSD or PCBSD yet but this looks
   promising.
 
   Dimitri, what hardware are you running?
 
   I'm...
   MSI K7T Pro2
   Duron 1.2
   256 - PC2700
   Maxtor 6L040J2 (40Gig)
   ATI AIO Pro128
   Samsung 52x CDROM
 
   On 8/11/05, Scott Ullrich [EMAIL PROTECTED] wrote:
On 8/11/05, Dimitri Rodis [EMAIL PROTECTED] wrote:
 Yup, that did it.

 All I did was move the CDROM from Secondary Master to Primary Slave
 and
 the install went right thru. This was on 0.73.8.
   
Okay thanks. ! Let me see if this can help us narrow down the
 problem.
   
Scott
   
   
  -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
 
  -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [pfSense Support] ISO problems ... still on 0.75 / 0.75.1 iso version error?

2005-08-12 Thread Scott Ullrich
On 8/12/05, Wesley Joyce [EMAIL PROTECTED] wrote:
 I am now only getting as far as 63% during the install when the CDROM is on
 the secondary bus.  This is using pfSense-LiveCD-0.75.1 which for some
 strange reason still boots and display 0.75 as the version.  Should I
 download this from a different mirror?

It was only a installer fix so I didnt bump the system version.  That is normal.

What do you mean getting as far as 63%?   What happens?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [pfSense Support] 0.75.1 ISO ..... Problems

2005-08-12 Thread Scott Ullrich
On 8/12/05, David Strout [EMAIL PROTECTED] wrote:
  All,
 It hangs STILL on the Waiting for Backend screen and I tried running the
 lua cammand that Scott had me try last night and get a different set of
 messages, but it still hangs and I have to CTRL-C out (twice).

Send me the messages.

Scott

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [pfSense Support] Ping issue

2005-08-12 Thread Bill Marquette
On 8/12/05, Chris Buechler [EMAIL PROTECTED] wrote:
 On 8/12/05, Bill Marquette [EMAIL PROTECTED] wrote:
  Let me guess, the hosts initiating the PING are running Windows?  I'm
  pretty sure we've recently fixed this bug.  Care to try it?
 
 
 With ipfilter 3.x (and hence m0n0wall) it doesn't matter if the hosts
 are Windows or not.  It isn't even as smart as PF's behavior prior to
 that latest patch.  Just doesn't work from multiple sources behind NAT
 no matter what.

Ahhh, didn't realize IPFilter still sucked that hard.  I've never used
it with NAT.  I thought it at least knew about the ICMPID though.

 But yes, should be completely fixed here.

:)  The patch for those that care (it's commited in OpenBSD now I think) is
http://marc.theaimsgroup.com/?l=openbsd-pfm=112316815028454w=2
and see
http://marc.theaimsgroup.com/?l=openbsd-pfm=112299265510286w=2
for an explanation of what the patch actually does.

The patch has been in since at least the hackathon, so all versions
newer than .74 should have this fixed.

--Bill

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [pfSense Support] Alert about pf rules syntax errors... again...

2005-08-12 Thread Scott Ullrich
This is not the correct fix.  Try this /etc/inc/vpn.inc.

http://pfsense.com/cgi-bin/cvsweb.cgi/pfSense/etc/inc/vpn.inc?rev=1.69;content-type=text%2Fplain

On 8/12/05, M. Kohn [EMAIL PROTECTED] wrote:
 Hi,
 
 small hint abut IPSec bug (I hope...):
 (pfSense 0.75)
 
 The function filter_rules_generate() in
 /etc/inc/filter.inc rules will try to set
 the rules for IPSec:
 
 Line 2093 in /etc/inc/filter.inc:
 ---
 if(is_array($config['ipsec']['tunnel'])) {
 foreach ($config['ipsec']['tunnel'] as $tunnel) {
 $remote_gateway = $tunnel['remote-gateway'];
 ---
 
 Normally no problem, but there is an empty tunnel definition
 in $config['ipsec']['tunnel'], but I don't know why...
 
 So I added the following patch as a workaround, checking if
 $tunnel['remote-gateway'] is empty:
 
 (see attached filter.diff)
 
 
 PS: Should I better use CVSTRAC for such things?
 
 
 --- filter.inc.org  Fri Aug 12 12:56:44 2005
 +++ filter.inc  Fri Aug 12 16:11:20 2005
 @@ -2091,6 +2091,7 @@
 }
 if(is_array($config['ipsec']['tunnel'])) {
 foreach ($config['ipsec']['tunnel'] as $tunnel) {
 +   if (!empty($tunnel['remote-gateway'])) {
 $remote_gateway = $tunnel['remote-gateway'];
 $local_subnet = 
 return_vpn_subnet($tunnel['local-subnet']);
 $ipfrules .= pass quick on  . $wanif .  proto udp 
 from  . $ipsec_ip .  to  . $remote_gateway .  port = 500 keep state label 
 \IPSEC: . $tunnel['descr'] . udp\\n;
 @@ -2104,6 +2105,7 @@
 
 $ipfrules .= pass quick on  . $lanif .  from  . 
 $tunnel['remote-subnet'] .  to  . $local_subnet .  keep state label 
 \IPSEC:   . $tunnel['descr'] .\\n;
 $ipfrules .= pass quick on  . $lanif .  from  . 
 $local_subnet .  to  . $tunnel['remote-subnet'] .  keep state label 
 \IPSEC:   . $tunnel['descr'] .\\n;
 +   }
 }
 }
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[pfSense Support] 0.75.1 ISO .. Problems - lua results

2005-08-12 Thread DLStrout

/usr/local/bin/lua50c51 /usr/local/share/dfuibe_lua/main.lua 
dir.root=/FreeSBIE/ option.booted_from_install_media=true

[Fri Aug 12 15:50:31 2005]
Loading configuration file '/usr/local/share/dfuibe_lua/conf/uinavctl.lua'...
BSD Installer started
Loading configuration file '/usr/local/share/dfuibe_lua/conf/cmdnames.lua'...
DFUI connection on tcp: successfully established
[Fri Aug 12 15:50:32 2005]
`/FreeSBIE/sbin/sysctl -n hw.physmem` returned: 511139840
`/FreeSBIE/sbin/sysctl -n kern.disks` returned: ad0
Surveying Disk: ad0, 9.31G: 19386/16/63
Surveying Partition: 1: 63,19541025:165/true
[Fri Aug 12 15:50:33 2005]
Surveying Subpartition on ad0s1: a: 0,13249569: 4.2BSD  F=1024, B=8192
Surveying Subpartition on ad0s1: b: 13249569,2097152: swap  F=0, B=0
Surveying Subpartition on ad0s1: c: 0,19541025: unused  F=0, B=0
Surveying Subpartition on ad0s1: d: 15346721,4194304: 4.2BSD  F=2048, B=16384
WARNING: couldn't open '/FreeSBIE/var/log/dmesg.boot'
WARNING: couldn't open '/FreeSBIE/var/log/dmesg.boot'
WARNING: couldn't open '/FreeSBIE/var/log/dmesg.boot'
WARNING: couldn't open '/FreeSBIE/var/log/dmesg.boot'
WARNING: couldn't open '/FreeSBIE/var/log/dmesg.boot'
WARNING: couldn't open '/FreeSBIE/var/log/dmesg.boot'
WARNING: couldn't open '/FreeSBIE/var/log/dmesg.boot'
WARNING: couldn't open '/FreeSBIE/var/log/dmesg.boot'
WARNING: couldn't open '/FreeSBIE/var/log/dmesg.boot'
/usr/local/bin/lua50: /usr/local/share/dfuibe_lua/lib/package.lua:415: bad 
argument #1 to `ipairs' (table expected, got nil)
stack traceback:
   [C]: in function `ipairs'
   /usr/local/share/dfuibe_lua/lib/package.lua:415: in function 
`enumerate_installed_on'
   /usr/local/share/dfuibe_lua/main.lua:143: in main chunk
   [C]: ?
^C
#



Scott Ullrich wrote:


On 8/12/05, David Strout [EMAIL PROTECTED] wrote:
 


Send me the messages.

Scott



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [pfSense Support] ISO problems ... still on 0.75 / 0.75.1 iso version error?

2005-08-12 Thread Wesley Joyce
During the cpdup command processing after the partitioning, formatting, it
faults at the 63% progress indicator during the installation.

 -Original Message-
 From: Scott Ullrich [mailto:[EMAIL PROTECTED]
 Sent: Friday, August 12, 2005 11:02 AM
 To: Wesley Joyce
 Cc: support@pfsense.com
 Subject: Re: [pfSense Support] ISO problems ... still on 0.75 / 0.75.1 iso
 version error?
 
 On 8/12/05, Wesley Joyce [EMAIL PROTECTED] wrote:
  I am now only getting as far as 63% during the install when the CDROM is
 on
  the secondary bus.  This is using pfSense-LiveCD-0.75.1 which for some
  strange reason still boots and display 0.75 as the version.  Should I
  download this from a different mirror?
 
 It was only a installer fix so I didnt bump the system version.  That is
 normal.
 
 What do you mean getting as far as 63%?   What happens?



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [pfSense Support] ISO problems ... still on 0.75 / 0.75.1 iso version error?

2005-08-12 Thread Scott Ullrich
Again, I need more info.   What faults?   FreeBSD?  The backend?   The
installer front end?

Scott


-- Forwarded message --
From: Wesley Joyce [EMAIL PROTECTED]
Date: Aug 12, 2005 12:07 PM
Subject: RE: [pfSense Support] ISO problems ... still on 0.75 / 0.75.1
iso version error?
To: Scott Ullrich [EMAIL PROTECTED]
Cc: support@pfsense.com


During the cpdup command processing after the partitioning, formatting, it
faults at the 63% progress indicator during the installation.

 -Original Message-
 From: Scott Ullrich [mailto:[EMAIL PROTECTED]
 Sent: Friday, August 12, 2005 11:02 AM
 To: Wesley Joyce
 Cc: support@pfsense.com
 Subject: Re: [pfSense Support] ISO problems ... still on 0.75 / 0.75.1 iso
 version error?

 On 8/12/05, Wesley Joyce [EMAIL PROTECTED] wrote:
  I am now only getting as far as 63% during the install when the CDROM is
 on
  the secondary bus.  This is using pfSense-LiveCD-0.75.1 which for some
  strange reason still boots and display 0.75 as the version.  Should I
  download this from a different mirror?

 It was only a installer fix so I didnt bump the system version.  That is
 normal.

 What do you mean getting as far as 63%?   What happens?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[pfSense Support] 0.75.1 - php: There were error(s) loading the rules

2005-08-12 Thread Wesley Joyce








After disabling the default LAN rule I immediately got this
notice. 



System log from web gui

Aug 12 12:13:41 php: There were error(s) loading the rules:
/tmp/rules.debug:108: syntax error /tmp/rules.debug:109: syntax error
/tmp/rules.debug:110: syntax error /tmp/rules.debug:111: syntax error
/tmp/rules.debug:112: syntax error /tmp/rules.debug:113: syntax error
/tmp/rules.debug:114: syntax error pfctl: Syntax error in config file: pf rules
not loaded - The line in question reads [108]: pass quick on xl1 proto esp from
146.226.152.86 to keep state label IPSEC: esp proto





pfSense# cat notices 

a:2:{i:1123863221;a:5:{s:2:id;s:11:filter_load;s:6:notice;s:462:There
were error(s) loading the rules: /tmp/rules.debug:108: syntax error

/tmp/rules.debug:109: syntax error

/tmp/rules.debug:110: syntax error

/tmp/rules.debug:111: syntax error

/tmp/rules.debug:112: syntax error

/tmp/rules.debug:113: syntax error

/tmp/rules.debug:114: syntax error

pfctl: Syntax error in config file: pf rules not loaded The
line in question reads [108]: pass quick on xl1 proto esp from 192.168.152.86
to keep state label IPSEC: esp
proto;s:3:url;s:0:;s:8:category;s:13:Filter
Reload;s:8:priority;i:1;}i:1123863257;a:5:{s:2:id;s:11:filter_load;s:6:notice;s:462:There
were error(s) loading the rules: /tmp/rules.debug:108: syntax error

/tmp/rules.debug:109: syntax error

/tmp/rules.debug:110: syntax error

/tmp/rules.debug:111: syntax error

/tmp/rules.debug:112: syntax error

/tmp/rules.debug:113: syntax error

/tmp/rules.debug:114: syntax error

pfctl: Syntax error in config file: pf rules not loaded The
line in question reads [108]: pass quick on xl1 proto esp from 192.168.152.86
to keep state label IPSEC: esp proto;s:3:url;s:0:;s:8:category;s:13:Filter
Reload;s:8:priority;i:1;}}pfSense#





pfSense# cat rules.debug 

# System Aliases 

lan = { xl0 }

wan = { xl1 }

pptp = { ng1 ng2 ng3 ng4 ng5 ng6 ng7 ng8 ng9 ng10 ng11
ng12 ng13 ng14 }

pppoe = { ng1 ng2 ng3 ng4 ng5 ng6 ng7 ng8 ng9 ng10
ng11 ng12 ng13 ng14 }

# User Aliases 



set loginterface xl1 

set loginterface xl0 

set optimization normal



scrub on xl1 all 





nat-anchor pftpx/*

nat-anchor natearly/*

nat-anchor natrules/*

nat on xl1 from 192.168.9.0/24 port 500 to any - (xl1)
port 500

nat on xl1 from 192.168.9.0/24 to any - (xl1)

#SSH Lockout Table

table sshlockout persist





# spam table 

table spamd persist





# Load balancing anchor - slbd updates

rdr-anchor slb

# FTP proxy

rdr-anchor pftpx/*

rdr on xl0 proto tcp from any to any port 21 - 127.00.1
port 8021







anchor firewallrules



# loopback

anchor loopback

pass in quick on lo0 all label pass loopback

pass out quick on lo0 all label pass loopback



# package manager early specific hook

anchor packageearly





# carp

anchor carp



# enable ftp-proxy

anchor ftpproxy

anchor pftpx/*

pass in quick on xl1 inet proto tcp from port 20 to (xl1)
port  49000 user proxy flags S/SA keep state label FTP PROXY: PASV
mode data connection



# allow access to DHCP server on LAN

anchor dhcpserverlan

pass in quick on xl0 proto udp from any port = 68 to
255.255.255.255 port = 67 label allow access to DHCP server on LAN

pass in quick on xl0 proto udp from any port = 68 to 192.168.9.1
port = 67 label allow access to DHCP server on LAN

pass out quick on xl0 proto udp from 192.168.9.1 port = 67
to any port = 68 label allow access to DHCP server on LAN



# WAN spoof check

anchor wanspoof

block in log quick on xl1 from 192.168.9.0/24 to any label
WAN spoof check



# allow our DHCP client out to the WAN

# XXX - should be more restrictive

# (not possible at the moment - need 'me' like in ipfw)

anchor wandhcp

pass out quick on xl1 proto udp from any port = 68 to any
port = 67 label allow dhcp client out wan

block in log quick on xl1 proto udp from any port = 67 to 192.168.9.0/24
port = 68 label allow dhcp client out wan

pass in quick on xl1 proto udp from any port = 67 to any
port = 68 label allow dhcp client out wan



# LAN/OPT spoof check (needs to be after DHCP because of
broadcast addresses)

antispoof for xl0





# block anything from private networks on WAN interface

anchor spoofing

block in log quick on xl1 from 10.0.0.0/8 to any label
block private networks from wan block 10/8

block in log quick on xl1 from 127.0.0.0/8 to any label
block private networks from wan block 127/8

block in log quick on xl1 from 172.16.0.0/12 to any label
block private networks from wan block 172.16/12

block in log quick on xl1 from 192.168.0.0/16 to any label
block private networks from wan block 192.168/16

# Support for allow limiting of TCP connections by
establishment rate

anchor limitingesr

table virusprot



# let out anything from the firewall host itself and
decrypted IPsec traffic

# pass out quick on xl1 all keep state label let out
anything from firewall host itself

# pass traffic from firewall - out

anchor firewallout

pass out quick on xl1 all keep state label let out

[pfSense Support] Re: 0.75.1 - php: There were error(s) loading the rules

2005-08-12 Thread Scott Ullrich
Same problem as reported a few hours ago.   Try the vpn.inc that I
asked the other person to try.

On 8/12/05, Wesley Joyce [EMAIL PROTECTED] wrote:
  
  
 
 After disabling the default LAN rule I immediately got this notice.   
 
   
 
 System log from web gui 
 
 Aug 12 12:13:41 php: There were error(s) loading the rules:
 /tmp/rules.debug:108: syntax error /tmp/rules.debug:109: syntax error
 /tmp/rules.debug:110: syntax error /tmp/rules.debug:111: syntax error
 /tmp/rules.debug:112: syntax error /tmp/rules.debug:113: syntax error
 /tmp/rules.debug:114: syntax error pfctl: Syntax error in config file: pf
 rules not loaded - The line in question reads [108]: pass quick on xl1 proto
 esp from 146.226.152.86 to keep state label IPSEC: esp proto 
 
   
 
   
 
 pfSense# cat notices 
 
 a:2:{i:1123863221;a:5:{s:2:id;s:11:filter_load;s:6:notice;s:462:There
 were error(s) loading the rules: /tmp/rules.debug:108: syntax error 
 
 /tmp/rules.debug:109: syntax error 
 
 /tmp/rules.debug:110: syntax error 
 
 /tmp/rules.debug:111: syntax error 
 
 /tmp/rules.debug:112: syntax error 
 
 /tmp/rules.debug:113: syntax error 
 
 /tmp/rules.debug:114: syntax error 
 
 pfctl: Syntax error in config file: pf rules not loaded The line in question
 reads [108]: pass quick on xl1 proto esp from 192.168.152.86 to  keep state
 label IPSEC:  esp
 proto;s:3:url;s:0:;s:8:category;s:13:Filter
 Reload;s:8:priority;i:1;}i:1123863257;a:5:{s:2:id;s:11:filter_load;s:6:notice;s:462:There
 were error(s) loading the rules: /tmp/rules.debug:108: syntax error 
 
 /tmp/rules.debug:109: syntax error 
 
 /tmp/rules.debug:110: syntax error 
 
 /tmp/rules.debug:111: syntax error 
 
 /tmp/rules.debug:112: syntax error 
 
 /tmp/rules.debug:113: syntax error 
 
 /tmp/rules.debug:114: syntax error 
 
 pfctl: Syntax error in config file: pf rules not loaded The line in question
 reads [108]: pass quick on xl1 proto esp from 192.168.152.86 to  keep state
 label IPSEC:  esp
 proto;s:3:url;s:0:;s:8:category;s:13:Filter
 Reload;s:8:priority;i:1;}}pfSense# 
 
   
 
   
 
 pfSense# cat rules.debug 
 
 # System Aliases 
 
 lan = { xl0  } 
 
 wan = { xl1  } 
 
 pptp = { ng1 ng2 ng3 ng4 ng5 ng6 ng7 ng8 ng9 ng10 ng11 ng12 ng13 ng14 } 
 
 pppoe = { ng1 ng2 ng3 ng4 ng5 ng6 ng7 ng8 ng9 ng10 ng11 ng12 ng13 ng14 } 
 
 # User Aliases 
 
   
 
 set loginterface xl1 
 
 set loginterface xl0 
 
 set optimization normal 
 
   
 
 scrub on xl1 all 
 
   
 
   
 
 nat-anchor pftpx/* 
 
 nat-anchor natearly/* 
 
 nat-anchor natrules/* 
 
 nat on xl1 from 192.168.9.0/24 port 500 to any - (xl1) port 500 
 
 nat on xl1 from 192.168.9.0/24 to any - (xl1) 
 
 #SSH Lockout Table 
 
 table sshlockout persist 
 
   
 
   
 
 # spam table 
 
 table spamd persist 
 
   
 
   
 
 # Load balancing anchor - slbd updates 
 
 rdr-anchor slb 
 
 # FTP proxy 
 
 rdr-anchor pftpx/* 
 
 rdr on xl0 proto tcp from any to any port 21 - 127.00.1 port 8021 
 
   
 
   
 
   
 
 anchor firewallrules 
 
   
 
 # loopback 
 
 anchor loopback 
 
 pass in quick on lo0 all label pass loopback 
 
 pass out quick on lo0 all label pass loopback 
 
   
 
 # package manager early specific hook 
 
 anchor packageearly 
 
   
 
   
 
 # carp 
 
 anchor carp 
 
   
 
 # enable ftp-proxy 
 
 anchor ftpproxy 
 
 anchor pftpx/* 
 
 pass in quick on xl1 inet proto tcp from port 20 to (xl1) port  49000 user
 proxy flags S/SA keep state label FTP PROXY: PASV mode data connection 
 
   
 
 # allow access to DHCP server on LAN 
 
 anchor dhcpserverlan 
 
 pass in quick on xl0 proto udp from any port = 68 to 255.255.255.255 port =
 67 label allow access to DHCP server on LAN 
 
 pass in quick on xl0 proto udp from any port = 68 to 192.168.9.1 port = 67
 label allow access to DHCP server on LAN 
 
 pass out quick on xl0 proto udp from 192.168.9.1 port = 67 to any port = 68
 label allow access to DHCP server on LAN 
 
   
 
 # WAN spoof check 
 
 anchor wanspoof 
 
 block in log quick on xl1 from 192.168.9.0/24 to any label WAN spoof check
 
   
 
 # allow our DHCP client out to the WAN 
 
 # XXX - should be more restrictive 
 
 # (not possible at the moment - need 'me' like in ipfw) 
 
 anchor wandhcp 
 
 pass out quick on xl1 proto udp from any port = 68 to any port = 67 label
 allow dhcp client out wan 
 
 block in log quick on xl1 proto udp from any port = 67 to 192.168.9.0/24
 port = 68 label allow dhcp client out wan 
 
 pass in quick on xl1 proto udp from any port = 67 to any port = 68 label
 allow dhcp client out wan 
 
   
 
 # LAN/OPT spoof check (needs to be after DHCP because of broadcast
 addresses) 
 
 antispoof for xl0 
 
   
 
   
 
 # block anything from private networks on WAN interface 
 
 anchor spoofing 
 
 block in log quick on xl1 from 10.0.0.0/8 to any label block private
 networks from wan block 10/8 
 
 block in log quick on xl1 from 127.0.0.0/8 to any label block private
 networks from wan block 127/8 
 
 block in log quick on xl1 from 172.16.0.0/12 to any label block private
 networks from wan 

Re: [pfSense Support] Traffic Graphs

2005-08-12 Thread DLStrout
Is ther a fix or a plan for a fix?...and has anyone considered a 
RRDTools replacement such as ifGraph as an alternative to SVG?


Bill Marquette wrote:


Yup.  IE 6 apparently doesn't love us.

--Bill

On 8/12/05, David Strout [EMAIL PROTECTED] wrote:
 


Yes, I am running the WebGUI in https mode ... is this a known problem?
--
David L. Strout
Engineering Systems Plus, LLC



- Original Message -
Subject: Re: [pfSense Support] Traffic Graphs
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: 08-12-2005 12:10 am


https?

--Bill

On 8/11/05, David Strout [EMAIL PROTECTED] wrote:
   


Did I miss a post or are the traffic graphs still not working w/ 0.74.8

I have the current SVG 3.0.3 plug-in running w/ IE 6
--
David L. Strout
Engineering Systems Plus, LLC


 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


   




---
avast! Antivirus: Inbound message clean.
Virus Database (VPS): 0532-3, 08/10/2005
Tested on: 8/12/2005 3:31:56 PM
avast! - copyright (c) 2000-2004 ALWIL Software.
http://www.avast.com




 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [pfSense Support] Packages

2005-08-12 Thread Scott Ullrich
Check your DNS?   It works fine here.

Scott


On 8/12/05, Mike Sr [EMAIL PROTECTED] wrote:
  
  
 
 I am running version 0.75 upgraded from 0.74.8 and in either version I am
 unable to see any packages. It says Unable to retrieve package info from
 www.pfesnse.com. Cached data will be used. 
 
   
 
 I received the same error from the 0.74.8 version. 
 
   
 
 I could see them in the 0.74.0 version. 
 
   
 
 Any ideas? 
 
   
 
 Mike 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]