@cmb:
We do actually have support for wildcard hostnames in a private build right now, it's still under development and being tested, but it appears to work nicely. It just snoops all the DNS responses, and if you allow *.example.com it allows every IP that's returned via DNS for *.example.com. No extra overhead in doing additional DNS lookups or anything else crazy like that.
When or whether that hits the open source side, I'm not sure yet.
@deltaend:
Does pfSense support setting up a password protected proxy system so we can program TeamViewer and other allowed programs to byass the captive portal by going through the proxy with a username/password?
Could probably do that with Squid.
I love you guys. Hopefully wildcards gets some attention for the next release build as this is very important for captive portal builds.
Regarding setting up Squid to bypass the Captive portal, it doesn't appear as if that works. If I have both Captive portal and Squid on the same interface, Captive portal will always require authentication before allowing itself to be used as a proxy. If I try to set up a virtual interface and bridge it with the WAN, Captive portal will throw a warning and won't turn on saying that it can't be activated on a bridged connection. So, short of having two firewalls, I don't see another way to make that work.
