Wildcards and Smoothwall
I am trying to set up devices using meraki online management for iOS and Andriod tablets, they have to register via http://m.meraki.com however the devices cannot complete this because they are getting filtered by Smoothwall.
I need to add in to the exceptions *.meraki.com and meraki.com* and *.amazon.com as per Meraki advice but I cannot due to smoothwall not excepting wildcards.
Subdomains are assumed, so just add meraki.com and it will allow m.meraki.com and what.ever.you.like.meraki.com/seriously/anything automatically.
I'd like to follow this thread with interest as SWGfL are having problems getting the firewall rules right for us to allow the meraki cloud to communicate with our iPADs.
We've had more luck with ios5 than 6 but nothing is working reliably at the moment.
In similar situatuion, hating smoothwall. Not getting anywhere.
@sonofsanta is right, the smoothwall is clever in that if you input domain.com/whatever, it will only filter that exact URL and other URLs containing that string so domain.com/whatever/blahblahblah, but if you simply put domain.com the smoothwall will filter anything with that string in it so in a sense, the smoothwall 'auto-wildcards'.
It is very likely that if you are using applications there may possibly be authentication issues going on, so you may want to try adding the domains to authentication bypass:
Guardian 3 users:
Browse to Guardian > Policy Objects > User defined
If there is a category called 'Authentication exceptions' add the domain to this category. If not, please create it and add the problem domains to this custom category.
Browse to Web proxy > Authentication > Exceptions
Add the following categories to Auth exceptions:
Browse to Guardian > Web Filter > Policy Wizard
Create a policy with the following conditions:
What: Authentication Exceptions, SSL/CRL, Software Updates
Confirm and save this rule.
Browse to Guardian > Web Filter > Policies
Move the policy you created up the table until it is above any block or blanket block in place for the group Unauthenticated IPs. You may have this group in a policy folder in position 2 in the table by default if you did not have Unauthenticated IPs allowed to use the web proxy prior to migrating. If this is a fresh install please check whether Unauthenticated IPs is included in the aforementioned policy folder.
Save and restart the web proxy.
@ThePalmist - drop me an email, tell me your woes, I will do what I can to get the right people pointed in your direction - don't like to see someone not getting value out of their smoothie.
We have a similar problem with Cloudon. Its because it doesn't support transparent proxy :(