Menu
▾
▴
Re: topology does work on mac osx with a manual work arround (was Re: [Openvpn-users] topology subnet 2.1beta7 mac osx - ifconfig: ioctl (SIOCAIFADDR): Destination address required
|
From: Mathias S. <ma...@op...> - 2005-11-30 21:59:50
|
On Wed, 30 Nov 2005, Mathias Sundman wrote: > On Wed, 30 Nov 2005, Jon Bendtsen wrote: > >> Sundman from #openvpn had some suggestions and they appears to be working. >> i had to remove the pull/client statement from the client.conf and run this >> manually >> sudo ifconfig tun0 192.168.123.253/24 192.168.123.253 >> sudo route add -net 192.168.123.0 192.168.123.253 255.255.255.0 >> >> It does work. >> I can ping, and if i add a route to the network beyond the VPN network i >> can >> ping and surf on those hosts as well >> sudo route add -net 192.168.119.0 192.168.123.34 255.255.255.0 >> >> So topology does work on mac OSX. > > Alright Jon, try this patch and see if it helps... > > It tries to use the following syntax for --dev tun --topology subnet on mac > OSX: > > ifconfig tun0 192.168.123.253 192.168.123.253 netmask 255.255.255.0 mtu xxx > up > > instead of previous > ifconfig tun0 192.168.123.253 netmask 255.255.255.0 mtu xxx up > that didn't work... My last patch had a typo, attached is a working one. Jon has verified that the patch does work on macOSX. The tun interface now gets its IP and mask set, but to reach the whole subnet assigned to the tun interface he still had to add a route as above: route add -net 192.168.123.0 192.168.123.253 255.255.255.0 So, the question is, should we make OpenVPN always add a network route for the "local network" assigned to the tun interface when in --dev tun, --topology subnet mode on macOSX, or is it up to the user to push such a route? How does other OSs work? If we push such a route, we don't want to break other OSs... -- _____________________________________________________________ Mathias Sundman (^) ASCII Ribbon Campaign OpenVPN GUI for Windows X NO HTML/RTF in e-mail http://openvpn.se/ / \ NO Word docs in e-mail |
