On Tue, 19 Apr 2022 09:45:02 +0100, Hamish McIntyre-Bhatty wrote:
> On 19/04/2022 07:27, Terry Coles wrote:
> > On Monday, 18 April 2022 20:26:36 BST Patrick Wigmore wrote:
> >> If there isn't a suitable route to 192.168.0.0/24 on the VPN
> >> client
> >> computer, then manually adding one temporar
On 19/04/2022 07:27, Terry Coles wrote:
On Monday, 18 April 2022 20:26:36 BST Patrick Wigmore wrote:
If there isn't a suitable route to 192.168.0.0/24 on the VPN client
computer, then manually adding one temporarily might be a worthwhile
experiment.
Hmmm. I've been struggling to find the corre
On Monday, 18 April 2022 20:26:36 BST Patrick Wigmore wrote:
> If there isn't a suitable route to 192.168.0.0/24 on the VPN client
> computer, then manually adding one temporarily might be a worthwhile
> experiment.
Hmmm. I've been struggling to find the correct iptables command to do that.
Sho
On Monday, 18 April 2022 20:26:36 BST Patrick Wigmore wrote:
> I suppose one thing to check is whether, while connected to the VPN,
> you have any other (conflicting) routes to 192.168.0.0/24. Or, indeed,
> whether there is a route to 192.168.0.0/24 at all. E.g. run
>
> $ ip route show
>
> on
On 18/04/2022 20:26, Patrick Wigmore wrote:
On Mon, 18 Apr 2022 10:23:19 +0100, Terry Coles wrote:
When a VPN client connects to the Web Server, in theory the web
server would see that connection coming in from a 10.1.10.0/24
address, not a 192.168.0.0/24 one. So, it is a given that the
Webserve
On Mon, 18 Apr 2022 10:23:19 +0100, Terry Coles wrote:
> > When a VPN client connects to the Web Server, in theory the web
> > server would see that connection coming in from a 10.1.10.0/24
> > address, not a 192.168.0.0/24 one. So, it is a given that the
> > Webserver has to be configured to accep
Patrick,
Thanks for your extremely detailed response; it's taken me a while to get
through it and I hope that I've understood what you are saying properly.
BTW. I've learned quite a bit :-)
See my responses below.
On Sunday, 17 April 2022 15:17:04 BST Patrick Wigmore wrote:
> If I understand
On Sun, 17 Apr 2022 08:32:23 +0100, Terry Coles wrote:
> 10.1.10.0/24 is the network set up by
> the VPN Server to forward remote traffic on and each device on the
> WMT Network is allocated an address in that range
If I understand you correctly, I think you are saying that each device
on the WMT
On Saturday, 16 April 2022 21:47:06 BST Peter Merchant via dorset wrote:
> Not sure about this, but from the 'bottom' network, you are trying to
> access a webserver that gets it's IP address from itself as you have
> Hostapd and dnsmasq running on the machine. So does the VPN server not
> know th
Not sure about this, but from the 'bottom' network, you are trying to access a
webserver that gets it's IP address from itself as you have Hostapd and dnsmasq
running on the machine. So does the VPN server not know the address of the
Webserver as this address has been obtained by DHCP?
But i
Hi,
Sorry to raise this again but *some* progress has been made with the access
issues that
I've been having at the WMT. There is a diagram showing the physical
arrangement of the
devices on site (and in my local test rig) at:
https://hadrian-way.co.uk/Misc/Network_Configuration.png[1]
As w
11 matches
Mail list logo