Hi cmb,

thx for reply… yeah i know :( but i figured out that my problem is there http://forum.pfsense.org/index.php/topic,52196.0.html

Hope u can help me.

ty cya

went with plan b.  just moved the printers.

I was able to put the Pep Wave AP One access points into bridged mode. I believe Apple TV is working now. Since the site is 2000 miles away from me, I'll have to wait for the devices to be tested. I have a test setup, with the same equipment, in my office and it's working fine. Thank you jimp!

And what is the IP address of the system on which you are trying to access pfSense? What is reported when you attempt the access? (The error message from the application is nearly always more informative than the "high level summary": "can't access")

On System -> General where you have listed your desired name servers, do you have the box Allow DNS server list to be overridden by DHCP/PPP on WAN ticked? (It shouldn't be!)

Upgrade to latest stable and a reboot seems to have cured it ;-0

You're a genius Thanks.

For anyone that ever has this issue. The exact steps i took are below.

Removed Default gateway from the WAN gateway how ever many you have.
Reboot modem.
delete the default gateway made by the system (this makes a new one)
all working.

I was not familiar with the 'raw filter logs' option for the firewall log which lead me to believe your install may have had a more serious problem since your logs appeared to be completely ****ed.
However that was my mistake, sorry about that.  :-[

Steve

Thank you sooo much! FYI-It does seem to happen under a more heavy load and time of day.

Here is my plan.
1 - Have the customer replace the network cable to dc0.
2 - If there is still an issue, I built up a new HP Pentium 4 system and added two Intel cards to it and disabled the on-board NIC and disabled PnP. I restored the config to it and will have the customer start using this one.

I will let you know the results!

No.  That job will just run on the first day (1) of every month.  It will not run once a week.  If you want to run it once a week your cron should look like this:

0  0  *  *  0  root  /root/squidGuard_blacklist_update.sh

0 = Sunday … 6 = Saturday

whcms in my billing-accounting system which sends attributes to my nas.whcms is using mikrotik dictionary.I wanted to use pfsense as nas but as you said it does not support mikrotik dictionary.so i have to use mikrotik which costs 250usd apparently..

@cpthk:

The request first arrives at the LAN interface, but shouldn't LAN interface pass the request to WAN ? (just like any other website you go to, those requests get past to WAN and to ISP) So the WAN should also get the request. Is this not true?

What request?
1. Suppose an access to the IP address of the DMZ server. That will go out the DMZ interface.
2. Suppose an access to the IP address of the hardware interface that is the pfSense WAN interface. That addresses the pfSense box itself so goes no further - it does not go out the WAN interface in the hope that the upstream router will loop it back and hence it is not received (seen by the receive input) by the hardware interface that is the pfSense WAN interface.

Does that answer the question?

Pretty much what I said above then.  ;)
Glad to know I wasn't wrong.

Steve

Very interesting comments.

wallabybob, I don't think that iperf is the bottleneck. We did several tests running iperf as both the client and the server on machines and were able to get performance that was very high. I don't have the numbers handy from the workstations that we were testing on, but I was just able to get 2.43Gbps running both the iperf server and client on an old Atom 230 server that I have handy. We also did the test with the workstations on the same sub-net/VLAN, taking the routing performance of the pfSense box out of the equation, and were able to get much better numbers.

idmud, thanks for the suggestion. I'll give that a try when we have a spare moment.

cmb, I understand the issue with a single source-destination pair and LACP. In all cases we were using at least three pairs of machines, with several tests using eight pair. Your point about the switches is well-taken and probably spot-on. I may PM you regarding suggestions for better switches. (I have some money left in a budget for experimentation, only a month to make use of it, and switches had my attention anyway.)

I've used a similar 802.11n TP-Link wireless access point and it also had that.  They call it WDS in the configuration, but others prefer to call it 4 address frame mode to distinguish it from what is typically called WDS.  It transmits an additional MAC address in the packets that allows bridging to work, but the access point on the other end must support it (and accept it).  The great thing about this mode is that it works with WPA/WPA2 and I think anything else that exists or will exist, since it is simply a normal connection with additional data in the packet headers (or something like that).  This particular mode is a Linux implementation and is compatible with any Linux-based device that uses it (I've used this mode to make a bridge with a TP-Link TL-WA901ND and another AP running OpenWrt, for example).  FreeBSD has a similar mode, but I've heard it is incompatible with the Linux implementation, unfortunately (so if pfSense eventually supports it, it will only work with other FreeBSD-based devices and not Linux-based devices).

There was a whole big debate/thread on that on the mailing list - feel free to peruse the archive for the results.