[pfSense] order of firewall rules

2014-09-24 Thread Gerald Waugh
I had my firewall rules ordered from top to bottom with the ACCEPTED aliases at the top Yesterday I noted that some accepted IP addresses were being blocked Went to the admin GUI and noted in the Firewall Rules display that the accepted aliases had moved to the bottom. How would that happen? TIA

Re: [pfSense] webConfigurator authentication error

2014-08-27 Thread Gerald Waugh
://lists.pfsense.org/mailman/listinfo/list -- Gerald Waugh Front Street Networks (318) 734-4779 (318) 401-0428 ___ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list

Re: [pfSense] Firebox-X20e

2014-01-03 Thread Gerald Waugh
/list ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list -- Gerald Waugh Front Street Networks (318) 734-4779 (318) 401-0428 ___ List mailing list List

Re: [pfSense] pfSense and Cable Modem Throughput

2013-09-12 Thread Gerald Waugh
On 09/12/2013 02:34 PM, Adam Piasecki wrote: It sounds like my issue, i'll have to get the cable provider to change the settings as they won't allow me access into the modem. This is a Motorola SB6580G in bridge mode. Best to get your own cable modem. We had trouble with comcast modem setup,

Re: [pfSense] filterdns: host_dns: failed looking up blocked: hostname nor servname provided, or not known

2013-07-28 Thread Gerald Waugh
On 07/21/2013 03:44 PM, Gerald Waugh wrote: I see this error in the system log *filterdns: host_dns: failed looking up blocked: hostname nor servname provided, or not known * I have checked rules and aliases, but see nothing wrong. Is there someplace else to look? TIA Bump; Same Rules

[pfSense] Microsoft Outlook Blocked

2013-03-17 Thread Gerald Waugh
I have searched the archives, and googled it, but have not found a solution firewall is working great except MS Outlook is being blocked, all other email clients work OK filter.log does not give a clue. no blocking shown for the Outlook users IP Sendmail/Dovecot Server maillog Disconnected:

Re: [pfSense] Microsoft Outlook Blocked

2013-03-17 Thread Gerald Waugh
On 03/17/2013 02:14 PM, Chris Bagnall wrote: On 17/3/13 6:38 pm, Gerald Waugh wrote: thanks for the response, I have ports set for '*' any I moved this rule to the top of the rules list TCP/UDP * * * * * none Internet to servers Out of curiosity, have you

Re: [pfSense] Microsoft Outlook Blocked

2013-03-17 Thread Gerald Waugh
On 03/17/2013 04:47 PM, Ermal Luçi wrote: On Sun, Mar 17, 2013 at 8:57 PM, Gerald Waugh gwa...@frontstreetnetworks.com mailto:gwa...@frontstreetnetworks.com wrote: On 03/17/2013 02:14 PM, Chris Bagnall wrote: On 17/3/13 6:38 pm, Gerald Waugh wrote: thanks

Re: [pfSense] Microsoft Outlook Blocked

2013-03-17 Thread Gerald Waugh
On 03/17/2013 05:36 PM, Chris Buechler wrote: On Sun, Mar 17, 2013 at 4:47 PM, Ermal Luçi e...@pfsense.org wrote: Try enabling on the rule to allow ip options. It might be that the packets are being dropped due to having ip options in them. Outlook shouldn't be using IP options, we'd have had

Re: [pfSense] 2.0.1-RELEASE Not blocking

2013-02-21 Thread Gerald Waugh
On 02/21/2013 12:06 PM, David Burgess wrote: On Thu, Feb 21, 2013 at 11:03 AM, Gerald Waugh gwa...@frontstreetnetworks.com wrote: I must be missing something basic. I have setup several pfSense systems, but my latest one in not blocking. I have several firewall rules for the WAN port, and none

Re: [pfSense] 1:1 NAT on pfSense 2.0.1

2012-12-18 Thread Gerald Waugh
On 12/18/2012 10:06 AM, Marcio Merlone wrote: Greetings, I am trying to make a dead simple 1:1 NAT from one wan address to an internal server. I was assigned the x.x.x.152/29 address for my WAN from my ISP, and designated the ip x.x.x.154 for pfsense while x.x.x.153 is its gateway. I can use

Re: [pfSense] 1:1 NAT on pfSense 2.0.1

2012-12-18 Thread Gerald Waugh
On 12/18/2012 11:56 AM, Marcio Merlone wrote: Em 18-12-2012 15:39, Gerald Waugh escreveu: AFAIK there is no 1:1 NAT There is on 2.0.x. My first description of the problem was the correct setup, I may have missed something and it got working later. Oh, I was thinking 1.2.x What was your