2018-03-28, 08:36
(2018-03-27, 10:44)allsorts Wrote: Lets take a step back. Where and what is providing the "WiFi" internet connnection that you are attempting to share via the windows PC and it's LAN card to the blitzortung controller?
How is the Windows PC connecting to the "WiFi" internet connection?
Hi Dave
Previously with my satellite connection everything was on a 192.168.1.N range - no problem. Then I changed to mobile router for much better performance.
I had my PC connected to a Vodafone wifi router (IP range 192.168.0.N) and as the controller has only a lan connection (default IP 192.168.1.235) I tried to share or bridge (both tried) the two networks. In the end I used a wifi access point which I had and set that up using its lan connection to the pc so it could communicate with the wifi router. Next step was to use pc to controller on lan to set DCHP to ON. Then swapped the pc-to-access to controller-to-access lans. For some reason Advanced IP scanner could not see the access point or the controller but Angry IP could see both. So now knowing the ip addresses that had been allocated I could communicate with the pc. Someone suggested setting static IP's outside the range normally allocated by the router to avoid any possible conflicts if the router restarted. Seemed like a oood idea as a dynamic might mean I did not know what IP had been allocated. Normally I use Google Chrome so I set an IE home page to the controller so I could use a fixed short cut and that was it. Done ! I think the answer was getting each step in the right order with some enabling/disabling the pc's connections and cable swapping and finally Angry IP telling me where to go.
Regards
Alan
Stations: 2004