Ok i did reset the Pre Auth URL to "nothing", but nothing changed.

After i did check the config of the DHCP on the COMPLAN Interface i found out that i did set custom DNS Servers (DNS) for this HotSpot, turns out that was my problem…
After i set all back to nothing it works just fine, so i'm just a bit stupid  :D

Tank you for this Hint, Problem solved.

Greetings Chris-The-Tuner

Yep, it looks like current validation isn't strong enough :  http://www.w3.org/TR/xml11/#sec-common-syn 
The first char (also called NameStartChar ) has limitations :

":" | [A-Z] | "_" | [a-z] | [#xC0-#xD6] | [#xD8-#xF6] | [#xF8-#x2FF] | [#x370-#x37D] | [#x37F-#x1FFF] | [#x200C-#x200D] | [#x2070-#x218F] | [#x2C00-#x2FEF] | [#x3001-#xD7FF] | [#xF900-#xFDCF] | [#xFDF0-#xFFFD] | [#x10000-#xEFFFF]

Also, are the DNS servers whitelisted on CP?

@doktornotor:

Sorry, you told us you want ANY request redirected to xyz.com "with no error message at all". For that, you need exactly ONE IP configured via the blackhole zone, and a webserver configured accordingly. Dunno really what's this talk about today.abc.com or tomorrow.abc.com. Not interested in moving targets here. Specify exactly what you want.

Back on the job, I edited my last post to make the thought process more contiguous.

I appreciate your help.

gdelong

https://redmine.pfsense.org/issues/3932

Those are broadcasts.  Who cares?

Yeah, fix your custom pages which have port 8000 apparently hardcoded.

https://doc.pfsense.org/index.php/Using_Captive_Portal_with_FreeRADIUS#Amount_of_Bandwidth

Hi itlab you dont have to find it anywhere .

create an HTML file in whatever HTML editor you have

goto Services -> Captive portal -> scroll down to "Portal page contents"

copy this

somewhere in your HTML file between     … save.

back to pfsense upload the HTML file you just created to pfsense. done

please note that if you have image references in your HTML you have to upload them too through  File Manager

"Services -> Captive portal -> File Manager"
also note that the image files will be renamed to captiveportal_xxx.jpg so you have to rename them accordingly in your HTML

ok

thanks again

Hi,

Initial voucher settings don't need to be modified, ones setup correctly.

According to me, creating a new role with vouchers is a matter of clicking in the plus ( + ) button and then the blue ! button will show them all. print or save the page and that it.
I agree, all these setting called bits, keys, ticket, checksum etc look daunting.

But, hey, don't worry, you can tell you clients that "driving a car" or "piloting a plane" needs some understanding, training.
Managing a firewall like pfSense isn't exempted to this.

But: a partial solution is possible.
Knowing that voucher code are generated buy pfSense, you could store them "some where" in a file on the pfSense system.
All you have to do is adding a new tab on this page: "Status: Captive portal" where you list all created vouchers, and for each voucher you could show if it is being used, how much time is left, a "block" button to disable it, etc.
This means you could it make a easy for your client as you decide : your coding skills will determine the final result.
=> Kortom: werk aan de winkel ;)

Btw : "overall performance" is vague. many screens are can inform the admin about what's going on.

Is there option for Group bandwidth?

Like 5 mbps for some group, and its shared with its users.
Another group having  2 mbps  like that?

Instead of saying what you think you've done, post what you;ve done.

Was this did on 2.0.1 or did you do this on 2.2?

And what's the trouble with actually whitelisting the IP cam's address in CP and embedding the stream?

Yes, I have another router, and thank you the fast answer!

@doktornotor:

Dude, you realize this is a firewall, right? And the portal page is supposed to be a simple form for login/voucher input/click through some TOS. What on earth you cannot fit into 1MB?

I'm turning into into an epic captive portal device instead of a firewall. You can call it whatever you want, but for me, it's PFCaptivePortalOfAwesome.