Forgot completely about the rtti lib. Sorry about that. Strictly it's not
needed I don't think, but I have a tendency to use exceptions so I usually
put it in without thinking about it.
The installation of the driver works like this:
* Stick it in \Windows
This is the conventional location for such files. CE doesn't have a
configurable 'PATH' per se, but that directory is implictly used for module
lookup.
* Create the required NDIS keys. You can do that with the TapTester via
the button labelled 'SetupNDISKeys', and you just have to do it once.
Eventually, when everything is working, I intend to make a .cab installer
which will do the registry setup.
That the basic installation and will make available a device called TAP1:
which is the tap driver. The driver will automatically be loaded upon
bootup via soft reset. Also, you can cause it to be loaded immediately
(without soft reset) with the TAP tester button labelled 'RegisterAdapter'
How to remove:
* mostly for dev, you can unload the driver immediately via the TapTester
button labelled 'DeregisterAdapter'. This is useful for dev/testing
because you can't install a newly built driver if one is already loaded.
* more important: since the system will load the driver automatically when
you soft reset, it is important to use the 'DeleteNDISKeys' button if you
don't want that to happen. When the keys are deleted, then the system will
not know about the driver and not load it.
Quick check that it is loaded:
1) There is a button labelled 'SqooshIt' (sorry for the silly name), that
will list all loaded NDIS adapters, you will see the TAP driver if it is
loaded.
2) You can drill down through the standard network settings and you will
see an adapter named:
'TAP1: Virtual Ethernet Device' listed along with all the other adapters on
your device. I can't tell you how to get there because they move this
around, but on my PPC2003 device, it can be accessed from the network icon
at the top of the screen: settings, advanced, network card, network
adapters; and then there is a listbox with the names in it.
This should be a drop kick, but I am interested if there is any lock-down
for unsigned drivers on PPC-Phone Edition which is what your PPC-6700 is
running I think. I'm interested in SmartPhone, too, but I don't know anyone
with one of those devices to try it out on. Maybe you have a friend?
Notes on current status:
1 currently, I have hacked forward.c to have the following commented out
around line 1215:
if (flags & IOW_WAIT_SIGNAL)
wait_signal (c->c2.event_set, (void*)&err_shift);
the consequence is that you don't have a means (like ctrl-c) to stop the
openvpn app. I have to do this for the moment until I can figure out
either: a way to get a real event handle for the console, or a different
mechanism altogether to provide the signals thus emulated. So you can
terminate it from the control panel, or if you use something like 'magic
button' the X button will really close the app (instead of 'smart minimize',
which really just hides it behind the desktop).
2 You must not use the 'nobind' option in the client config.
3 I haven't figured out why my dhcp is not configuring correctly, however I
have had luck with the 'ip-win32 ipapi' 'ifconfig l rp' options.
4 I am a configuration newby to openvpn, and I know my test setup is not
correctly configured. I am using a windows client as my control during
experiments. It's not working correctly either, so I know I have something
wrong -- don't know what yet.
FWIW, my client config contains:
#begin
client
dev tap
dev-node TAP1:
proto udp
remote 192.168.1.10 1194
#don't like this but work-around until I fix/emulate nobind
local 192.168.1.129
#dhcp not working for some reason, this gets past that
ip-win32 ipapi
#interestingly, I still get a 10.8.0.51 address on the TAP, which is from
the DHCP pool! curious....
ifconfig 10.8.0.40 255.255.255.0
#openssl stuff
ca "\\ca.crt"
cert "\\ipaq4150.crt"
key "\\ipaq4150.key"
comp-lzo
verb 5
#end
though don't take this as a reccomendation, just as a reference point as to
where I am now.
FWIW: you may wish to download nettools_arm_setup.exe from somewhere which
will give you the usual network tools like route, ipconfig, netstat, et al.
-Dave
-----Original Message-----
From: openvpn-devel-ad...@lists.sourceforge.net
[mailto:openvpn-devel-ad...@lists.sourceforge.net] On Behalf Of Iftikhar
Qureshi
Sent: Monday, March 27, 2006 10:57 AM
To: Dave
Cc: openvpn-devel@lists.sourceforge.net
Subject: RE: [Openvpn-devel] OpenVPN for PocketPC
Dave,
I got updated code and built TAPTester successfully. I had to get RITTI
package for Ccrtrtti.lib.
What is the recommended way of installing tap-ce.dll? ...I just copied it in
the same folder as the TAPTester application which worked.
Salamz,
-IQ
Dave <d...@ziggurat29.com> wrote:
...
Iftikhar: I updated the source and also I fixed the problem I mentioned
previously about the driver not handling the power-off state correctly; you
can power on and off to heart's content.
-Dave
