Hot answers tagged

2

A little late , but I did get this working. In ipsec.conf, I had to update the ciphers and the rightauth. I'd prefer to use something better, but at the time it connects. rightauth=eap-tls ike=3des-sha1-modp1024 esp=3des-sha1-modp1024 BTW: even with connecting, I still get the above errors/warnings. Update: I found that the mobileconfig profile needed ...


1

Your router is not responsible to route packets from 192.168.0.0 to 192.168.56.0, but the VM host is. You have to keep the static route 192.168.56.0 -> 192.168.0.2 on the router though. I don't know what's the purpose of the second route 192.168.57.0 -> 192.168.0.2 - probably a second NAT adapter on the host. To reach your VM from other OS X devices in ...


1

The old driver probably doesn't work with El Capitan. As indicated on the Linksys website Belkin is working on creating a Linksys driver package for the OS X 10.11. Meanwhile you may try the RealTek beta driver here.


1

There is no need to use the same network. Usually you can simply populate your DNS-server with the IPs and the names of the hosts in the 192.168.2.0 network. If you restricted allowed DNS queries to a particular network (i.e 10.0.100.0/24), you have to extend this to the 192.168.2.0/24 net. In the network settings of the devices in the 192.168.2.0/24 ...


1

You Mac is getting a single IP address on the LAN. To enable multiple devices to access the LAN, it creates a new private network on the Wi-Fi interface, and does NAT (Network Address Translation) between that network and the LAN. This is the same thing that happens when you connect your LAN (using private addresses) to the Internet using a router that gets ...


1

I have been having the same problem. Changing the name of the SSID fixes it immediately. But if I ever happen to switch off the router and switch it back on, the problem recurs and I have to think of yet another name.



Only top voted, non community-wiki answers of a minimum length are eligible