Plan D can be don't use DHCP for your client and set a static IP that way - no router configuration needed. Just set it to something outside the DHCP lease range ( often 192.168.1.1<http://192.168.1.1> - 100)
Hamish On 14 Jun 2018, at 18:01, Terry Coles <d-...@hadrian-way.co.uk<mailto:d-...@hadrian-way.co.uk>> wrote: Hi, At the Meeting last week, our half of the table was talking about providing limited access to the internet for our private network at the Wimborne Model Town. The object of this is to allow Android phones access to their special sites to make them think they have full Internet Access. This problem has gone through several iterations: Plan A was to spoof the Google check sites from the local Webserver - this originally worked and still does in a limited way, but doesn't work with later versions of Android. Plan B was to apply for and obtain a full SSL Certificate for the WMT website and re-use it on the RPi Webserver - that failed because the WMT website maintainer doesn't seem to want to play along with that. Plan C was to interpose a URL filter between the local Webserver and the Office Router; we discussed that at the Meeting and on this list and the solution proposed was to use SquidGuard. Subsequently, I found that the reconfiguration needed to SquidGuard to turn it from a Kids Guard tool to what we needed was pretty mega and someone on the RPi Forums suggested NoDogSplash, which provides a Captive Portal. Since a Captive Portal is exactly what we need (now I know what one is), I set out to do it. Unfortunately that has now failed because it seems that the WMT's ISP has locked down the supplied Router and do not allow admin logins. Without that, I cannot use a fixed IP Address on the Internet side of the RPi (which will have two Ethernet Adaptors) and so I cannot configure NoDogSplash to point the users at it. The WMT Manager does not want to change the ISP/Router mid-season, (quite reasonable since the Point of Sale equipment is connected to it), so I feel that I've run out of solutions and therefore have no Plan D at present. However, someone has just suggested Cascading Routers. I've looked into this, but it seems to me that this solution suffers from the same problem as Plan C, because the 2nd Router needs to have a fixed IP Address too. (In fact, I feel that we would be cascading three routers even if we could get it to work, since the RPi (with it's extra Ethernet Adaptor connected) is a router in its own right. Any ideas for Plan D/E? -- Next meeting: Bournemouth, Tuesday, 2018-07-03 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
