I finally found my problem. It was an error from me (Of course!). Obviously I activated the Captive portal on my WLAN interface without allowing to contact the DNS Server ip. When they could not get an ip for any site the Captive portal would not show and there was my dead end. When I finally tried to get a site to show by its ip the portal came up and I knew what I did wrong. Long story short: Its working now, thanks for your help.

Thanks!

Hey guys, sorry to 'hijack' this thread, but what about the newest may builds? Are they as stable as the 11th april build? Thanks Jimmy

I am using NanoBSD 4GB images.  2.0 x to 2.0 y doesn't work reliably (but it does sometimes). I haven't tried from 1.2, but I wouldn't count on NanoBSD upgrades being that reliable right now. Apparently those issues are known and will be taken care of at the right time.

The rules for the shaper in 2.0 get put on the Floating tab under Firewall > Rules. Check there to see what rules were generated, and then you can edit them from there.

Correct, that is Remote Access (SSL/TLS) You do not need to import the same DH parameters, you can generate new ones and it shouldn't hurt anything. They aren't tied to the CA or Cert.

This page has the most recent info. http://doc.pfsense.org/index.php/Is_there_IPv6_support_available

i had created the L7 container to try but it never worked so was deleting and it gives error and this bug is there in redmine which is work in progress. i try to report all errors in systemlog to get them resolved so atleast other things start getting more stable, the latest was RAM consuming which i guess is due to L7 so lets hope its fixed.

Hi, this seems to be resolved with the latest snapshot. Thank you Slam

If you choose "packet loss or high latency" it includes all 3, completely down falls into the same category.

but if u look at my initial setup which was filtering on member interfaces and it wasnt working, the rules r the same under lan and opt1

If its me you are referring to, I'm just saying that it needs to flush the cache, to implement the new L7 rules….It has nothing to do with the actual routing, but more what is presented to the user searching for the site.... @ermal: With latest snaps it should not matter regarding other services like squid. Why are you saying that squid does problems for you?

After updated, the problem has solved, thank you. Version: 2.0-BETA1 built on Sun May 2 18:59:27 EDT 2010 FreeBSD 8.0-STABLE

http://redmine.pfsense.org/issues/show/567 Please post anything 2.0 related in the 2.0 board, we can't watch all the others as closely so issues on other boards can be overlooked.

You're either missing a firewall rule to allow that, or possibly your vswitch(es) aren't configured to allow multiple MACs.

Snap from May 1 works. Thank god! (On my network i'm heavily dependent on ftp) Thanks for the info xbipin

There have been several date bumps on RELENG_8 between March and now, something must have changed there in FreeBSD for your card.

@rcfa: But if I can't be 100% sure that a specific physical port is always going to be the LAN because at boot time the system may discover one or the other USB interface first… Shouldn't, though I stay away from USB networking at all costs so I'm not sure, but it should be like PCI/PCI-e/PCI-X, where it'll never change from what it is (unless you rearrange the cards in that case), the detection isn't some random process.

confirmed tftp-proxy is all working correctly on  Fri Apr 30 22:00:04 EDT 2010  build thanks alot!