<div class="gmail_quote">On Sun, Feb 17, 2013 at 2:39 PM, Colin Law <<a href="mailto:clanlaw@googlemail.com" target="_blank">clanlaw@googlemail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> On 17 February 2013 21:13, JD <<a href="mailto:jd1008@gmail.com">jd1008@gmail.com</a>> wrote: > > > > On Sun, Feb 17, 2013 at 2:08 PM, Avi Greenbury <<a href="mailto:lists@avi.co">lists@avi.co</a>> wrote: >> >> Ron Fish wrote: >> > If he can opening a terminal and ping <a href="http://yahoo.com" target="_blank">yahoo.com</a> then the browser is not >> >> > getting along with the hotspot software. >> >> Not necessarily - if the hotspot works by lying in DNS and making >> everything resolve to an IP address that is serving the captive portal >> he will be able to ping yahoo absolutely fine, it'll just be on the >> wrong IP address. >> >> > most likely it is failing >> > on a certificate check from the hotspot. In firefox go into edit > >> > preferences > advanced > encryption > validation and uncheck OCSP. >> >> In this case surely he'd get an SSL error message? >> >> -- >> Avi >> >> > > I googled and found many people are still the victims of this problem > when using ubuntu/firefox. So it is ok with Chromium browser, or another browser then? Colin</blockquote><div> Well, I have not tried Linux version of Chromium. But it is a good point. I will try it tomorrow when I am at a hotspot. Also, to answer Avi, I did set the proxy to auto in Firefox. Did not solve the problem. Also, This is a problem I need solved, but the FF devs seem to be unaware of it, and the bug is still not assigned to any developer. <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=583228">https://bugzilla.mozilla.org/show_bug.cgi?id=583228</a> </div></div>