issue gone more worse, kindly check details on redmine.

I just booted up today's snapshot and it asked me for WAN, LAN, and OPT interfaces as expected.

Okay, thanks…Intel can keep their headache.

But i think just add the qOthersDefault to the rule that sends traffic to p2p like you have done in the screenshot and it should be ok. Thanks for the reply … After reading you reply I tried a different approach. I've looked into the Advanced property of my P2P software and I found that I can force it to use the same port as the listening port for outgoing connection. This will make my life easier. Also if others is following this thread, you should probably tell your P2P software to ignore connection from/to clients that use port 80 and 1723, very popular port to defeat ISP QoS and also defeating your QoS; their traffic will get prioritized. update: Finally found the uT doesn't use the setting I found ... I ended up creating a virtual IP on my interface on my uT machine and I have binded this IP address into Advanced settings of uT and then shaped this new ip address... And it works pretty good right now ...

additional config screens   [image: Nat.jpg] [image: Nat.jpg_thumb]

I guess this is the same issue here. http://forum.pfsense.org/index.php/topic,27127.0.html Pitty that there still seems to be noway to load balance with same gateways. I guess I will have to stik to ClearOS then.

Yes, the command works. But all the ARP entries is cleared when the dhcpd/dnsmasq service starts (and that is after shellcmd is run). As a quick workaround I set the ARP cache to 4 hours. Should be fine for a while in an home network environment… I created an new entry under: System: Advanced: Miscellaneous: System Tunables Tunable Name                              Description                                            Value net.link.ether.inet.max_age                ARP Cache 14400 seconds (default 1200 seconds)            14400

Unlikely to be a bug, sounds like an IP conflict most likely (or misbehaving proxy ARP on another firewall on the segment), that's been the cause of every scenario like that I've seen.

You can non-statefully fail over that way, which is probably adequate. No way to retain states across 3G like that since there's no way two systems can share the same IP (aside from a separate 3G router device as Jim mentioned).

http://doc.pfsense.org/index.php/How_can_I_access_the_webGUI_from_the_WAN%3F

I installed the new version 2.8.6 pkg see 1.31, but still does not work here's the log: Aug 9 21:11:28 SnortStartup [45354]: START RULE Interface for 1_35187_em1_vlan2 … Aug 9 21:11:28 snort [45329]: FATAL ERROR: Invalid pidfile suffix: 35187em1_vlan2. Suffix Less Than 11 characters and must not Have '..' or '/' in the name. Aug 9 21:11:28 snort [45329]: FATAL ERROR: Invalid pidfile suffix: 35187em1_vlan2. Suffix Less Than 11 characters and must not Have '..' or '/' in the name. someone managed to get it to work? greetings Simone

Has this feature been implemented? Thanks

As we've been saying this entire thread: no, that isn't possible just with settings in pfSense on a wired network. The ISP network is probably vastly more complex (and expensive) than just a normal DHCP server, a switch, and some cable.

Hi, Some new errors appear : bwi0: need multicast update callback bwi0: need multicast update callback bwi0: need multicast update callback bwi0: need multicast update callback firmware_register: cannot register image bwi_v3_pcm4, firmware table full! module_register_init: MOD_LOAD (bwi_v3_ucode_fw, 0xc3f7ec80, 0) error 6 bwi_v3_ucode: firmware image loaded, but did not register bwi0: request firmware bwi_v3_ucode failed bwi0: bwi_init_statechg: error 12 on MAC init bwi_v3_ucode: could not load firmware image, error 17 bwi0: request firmware bwi_v3_ucode failed bwi0: bwi_init_statechg: error 12 on MAC init i don't know what i can do  :-\

It also appears that the 64-bit builds are not available in an embedded flavour at this point.

I just realized while working on something else that if you look at the ID numbers, that may tell you the order the rules will be parsed.  I haven't looked at the code to confirm this, though.

http://forum.pfsense.org/index.php/topic,27197.msg142050.html#msg142050

Thanks you all for the suggestions! I will plan to stay current and will report back any problems that I find. In the past, I used PFSense for quite some time but then decided to give Astaro a try. Saw the new 2.0 BETA and thought it would be a good time to circle back and see what changes and improvements have been made. I must say, this software is very straight forward to work with and is very quick! I am quite impressed. Great work! I look forward to further involvement with this forum! Thanks, Ray

I thought that was fixed, but it may not be. Try using /boot/loader.conf.local instead.