0

I'm running a Mac Mini server, IP 192.168.2.2. When users connect remotely, often they have issues because their network at home (or wherever) happens to also be 192.168.2.x. So I instructed server.app to hand out VPN IP's from an unlikely IP range: 192.168.168.x. Now, that's all working fine, but some users need to send some of their traffic over the VPN, so they have the 'send all traffic over VPN' box checked. Here's my question: it's not allowing them to get out to the internet, because there's no route between 192.168.168.x and 192.168.2.x. I've tried everything I can think of to try and make this happen but I'm having no luck. Help, please? I need traffic to flow both ways, from WAN to the server to the VPN network to the client and vice versa.

  • What is your network mask? Sounds like your server is not in the same network as the VPN IPs? – not2savvy May 25 '17 at 9:49
  • @not2savvy yes, exactly. /24 – Harv May 25 '17 at 17:55
  • I think they should be in the same network. Never saw such a configuration like yours. – not2savvy May 25 '17 at 18:16
  • @not2savvy you have, actually. Your external (public) IP is a very different network/subnet than your internal, private IP. That works by creating appropriate routes to effectively build a bridge. I've seen, and done, this before; it can work, you just need to know how, and I'm stumped this time for some reason – Harv May 25 '17 at 18:29
  • You're right, but in this case, you have two local networks. Your router (which I suppose is not your Mac server) must route both of them to the WAN. I'm not sure if all routers will do so. But you might just change your local network mask to /16 on the router to make it work. – not2savvy May 25 '17 at 18:42

You must log in to answer this question.

Browse other questions tagged .