Re: [pfSense Support] rule not working correctly

2008-09-05 Thread BSD Wiz
yeah, seems like the port forward option is working as it should. i don't know why i didn't set it up this way to begin with. + as you already pointed out i had the 1:1 rule messed up.. thanks, -phil On Sep 5, 2008, at 10:43 PM, Bill Marquette wrote: I think you're dancing all around

Re: [pfSense Support] rule not working correctly

2008-09-05 Thread BSD Wiz
sounds good. i'm going to give the port forward option a shot. thanks, -phil On Sep 5, 2008, at 10:43 PM, Bill Marquette wrote: I think you're dancing all around the solution :) You need an inbound NAT or port forward for UDP ports 1-65535 pointing to 10.0.0.1. Alternately, a 1:1 NAT usin

Re: [pfSense Support] rule not working correctly

2008-09-05 Thread Bill Marquette
I think you're dancing all around the solution :) You need an inbound NAT or port forward for UDP ports 1-65535 pointing to 10.0.0.1. Alternately, a 1:1 NAT using YOUR external IP, not the IP of the service (ie. 216.181.136.7 in your example below should be whatever your external IP is, not that

Re: [pfSense Support] rule not working correctly

2008-09-05 Thread BSD Wiz
Here is the raw logs of a call getting blocked. Sep 5 21:52:07 fw-bsd-1.gnet pf: 20. 251565 rule 122/0(match): block in on rl1: (tos 0x0, ttl 110, id 51208, offset 0, flags [DF], proto: UDP (17), length: 854) 216.181.136.7.5065 > 75.129.xx.xx.58562: UDP, length 826 Sep 5 21:52:08 fw-bsd-1

Re: [pfSense Support] rule not working correctly

2008-09-05 Thread Chris Buechler
On Fri, Sep 5, 2008 at 10:17 PM, BSD Wiz <[EMAIL PROTECTED]> wrote: > man O man still getting blocked, > > tried calling my VoIP phone from my cell phone and the traffic was blocked > again by the default drop all rule. below is the log entry of the blocked > traffic. > > > WAN 216.181.136

Re: [pfSense Support] rule not working correctly

2008-09-05 Thread BSD Wiz
man O man still getting blocked, tried calling my VoIP phone from my cell phone and the traffic was blocked again by the default drop all rule. below is the log entry of the blocked traffic. WAN 216.181.136.7:5065 xx.xx.xx.xx:63792 this after allowing source 216.181.136.7

[pfSense Support] Redirected traffic on multiple interfaces...

2008-09-05 Thread Tim Nelson
Hello fellow pfSense'ers! I've been using NAT to redirect TCP/80 traffic on a subnet to a squid proxy server for quite some time. However, I've found that if I use this functionality on any additional interfaces, connectivity to the squid box gets extremely flaky. Running a constant ping shows t

[pfSense Support] ntop package install fails

2008-09-05 Thread JJB
I've tried to install the ntop package numerous times. It always stalls out, sometimes at 2% sometimes at 20% download and never completes. Any suggestions? - Thanks - Joel - To unsubscribe, e-mail: [EMAIL PROTECTED] For addi

Re: [pfSense Support] Trouble with NAT states

2008-09-05 Thread Fridtjof Busse
* Paul Mansfield <[EMAIL PROTECTED]>: > Fridtjof Busse wrote: > > My ISP disconnects the PPPoE every 24h and upon reconnect, I get a > > new IP address. > > worth paying for a static IP? My provider doesn't offer static IPs and those that do cost significantly more. I'd prefer a fix in pfSense r

Re: [pfSense Support] Trouble with NAT states

2008-09-05 Thread Fridtjof Busse
* "Fuchs, Martin" <[EMAIL PROTECTED]>: > Hi ! > > We're currently working on this afaik... Thanks for the info. Any intermediate solution? -- Fridtjof Busse - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands,

[pfSense Support] experiences with pfsense

2008-09-05 Thread Claus Marxmeier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there! This is no bug report - it's the opposite. I am running pfsense embedded since 2005 now. My current project www.netecdb.de depends a lot of 2 boxes in front of theservers to run stable and failsafe. The only outage i had during this time

Re: [pfSense Support] Brute Force

2008-09-05 Thread Igor
Yeahh.. I've tried and this works fine.. :-) There's any way to check blocked hosts? And how I can allow this host again? Thanks a lot Regards On Wed, Sep 3, 2008 at 03:22, Jeppe Øland <[EMAIL PROTECTED]> wrote: > What I did was simply set the firewall rule advanced settings. Here I > set "2 Ma

Re: [pfSense Support] Trouble with NAT states

2008-09-05 Thread Paul Mansfield
Fridtjof Busse wrote: > My ISP disconnects the PPPoE every 24h and upon reconnect, I get a new > IP address. worth paying for a static IP? I found with our office's standby adsl service that they gave me a static IP for free instead of charging $16/month when I phone to cancel service! -

Re: [pfSense Support] rule not working correctly

2008-09-05 Thread Paul Mansfield
BSD Wiz wrote: > > ah, i don't have any 1:1 nat entries, or static routes for this firewall > issue. so when the traffic hits the WAN interface perhaps it's not > always finding it's way to the voip box in the dmz? > > i have added a 1:1 mapping as follows: > > Interface External IP

AW: [pfSense Support] Trouble with NAT states

2008-09-05 Thread Fuchs, Martin
Hi ! We're currently working on this afaik... Regards, Martin -Ursprüngliche Nachricht- Von: Fridtjof Busse [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 5. September 2008 10:52 An: support@pfsense.com Betreff: [pfSense Support] Trouble with NAT states Hi, I'm running pfSense 1.2-RELEA

[pfSense Support] Trouble with NAT states

2008-09-05 Thread Fridtjof Busse
Hi, I'm running pfSense 1.2-RELEASE and have a problem with NAT-states: My ISP disconnects the PPPoE every 24h and upon reconnect, I get a new IP address. pfSense reconnects just fine, but the old NAT-states are still there. Now the applications using those states (mostly keepalive) cannot communi