On Friday, 15 June 2018 11:37:53 BST Ralph Corderoy wrote: > I don't understand the problem. What parameter is it in > https://github.com/nodogsplash/nodogsplash/blob/master/resources/nodogsplash > .conf that needs a fixed IP address on the external side of the Pi? > GatewayInterface wants an interface name, e.g. `ens35', not an IP > address.
Thanks for pointing that out. I think that I may have mis-understood the config file commentary (I haven't actually done that bit yet), but I found the following at line 170: # This should be autodetected on an OpenWRT system, but if not: # Set GatewayAddress to the IP address of the router on # the GatewayInterface. This is the address that the Nodogsplash # server listens on. # # GatewayAddress 192.168.1.1 I assumed that this was referring to the IP address of the Internet side of the Pi, but see now that they are probably referring to the IP Address of the router. Actually that still may be a problem, because the manual for the Router said that the Admin pages could be accessed by typing its IP Address into the browser, eg http://192.168.1.253, but that never worked. However, typing the router name - http://dsldevice.lan produced the correct login dialog. I know that the DHCP range is 192.168.1.xxx, because ipconfig on the Office computer yielded a number in that range. However, that's all I know. I still intend to implement the NoDogSplash software on the Pi Webserver, if only to get the auto Landing Page. If after I've got it to work here, it then works at the WMT, then I'll be quite a happy bunny :-) -- Terry Coles -- Next meeting: Bournemouth, Tuesday, 2018-07-03 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:[email protected] / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
