Mountain Lion Server changing its own default gateway when VPNing in?

[wuchtbrumme]

a very strange thing just happened to me. I was opening a VPN to a OS X Mountain Lion server (10.8.5 with 2.2.2 server.app, using iPad) and when i tried to fetch some new brew packages on the server, i got timeouts from the server to the internet. Looked onto netstat -rn and found a second (!) default gateway to the VPN client. None of that makes any sense.

Of course, now the connection is broken, i will never be able to reconnect until the machine is rebooted, which to my pleasure, i will have to perform onsite.

What a *********** ************.

What am i missing here?

 

[wuchtbrumme]

ok, found a hole in the bottle and could reconnect and get the whole stuff restarted and it turns out, it is rather an issue with brew than with the routing table as other stuff is just downloading fine. But it really strikes me why to hell a server would change its own network configuration just to make a VPN possible. Just add a host route, maybe, if at all needed. But why default?

 

[wuchtbrumme]

i dont understand as you write "a second gateway to the VPN client" which does not imply an issue with the server. That having said i observed a lot of stunning things with the server, i.e. changing the MTU (!). I suggest going to a recent server version which implies a recent OS X. I'd say 10.10 and 5.x is reasonably ok.

 

[chrfr]

i dont understand as you write "a second gateway to the VPN client" which does not imply an issue with the server. That having said i observed a lot of stunning things with the server, i.e. changing the MTU (!). I suggest going to a recent server version which implies a recent OS X. I'd say 10.10 and 5.x is reasonably ok.

Note that you are replying to your own posts from almost 3 years ago.