While I can not provide any specific help for this issue, I did want to point out, that under 10.5, for over a year, I had VPN services working by doing little more than settings up a plist, and installing a launchd item to keep it going.
I found iVPN, and was annoyed that there was such a high price on an app that in my opinion, at least at the time, installed two files, and loaded a launchd startup item. I bought it anyway, and could not get the license code to work, so returned it and nuked everything that it put in. >From there, I just started reading, and managed to hobble together the right >configs to use the built in OS X VPN server. It was not too bad. I updated >to 10.6 Snow Leopard on the machine I was VPN'ing into, so I have not had a >chance to set it all back up again. I also put 10.6 Server on the machine, which apparently has one click VPN built in, so I may just use that. I thought you may want to try to set this up by hand, as I do not see any need for additional software. I was actually going to make a port that installed those two files for you, just have not had time. I will look into it again, as it was not a lot of trouble at all, and just worked. -- Scott * If you contact me off list replace talklists@ with scott@ * On Jan 30, 2010, at 2:54 AM, Michael Hieb wrote: > Apologies if this is covered in the documentation or archives. I've looked > and not found the clue I need. > > Problem: openvpn2 (@2.1.1.1) installed as default or universal on snow > leopard has a bug in which it is unable to detect the default gateway and > consequently cannot set up the proper routing tables. This was covered in a > ticket from last year. > > http://trac.macports.org/ticket/22689 > > To my knowledge no progress on the macport, though there is a patch > apparently submitted to openvpn for linux and windows. > > http://openvpn.net/archive/openvpn-devel/2006-07/msg00003.html > > The macport ticket reports that if openvpn2 is installed as an i386 > executable that the bug can be circumvented. The problem is that I haven't > been able to figure out how to build openvpn2 as an i386 executable. > Preferably I'd like to change the settings only for openvpn2 and not the > entire macports installation. > > I have tried to date setting the configure.cflags-append in the openvpn2 > portfile. e.g. > > configure.cflags-append = "-arch i386" > > and find the executable fails to build with multiple architectures (i386 and > x86_64) > > I also tried to use a build_arch directive in the portfile but that is > apparently not the correct place to use this directive. > > Apologies if I have overlooked the obvious and thanks for any clue provided. _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
