I haven't worked extensively with OpenVPN, fair warning. But the first place I'd start trying to verify things would be with the client machine. IIRC, OpenVPN uses its own network adapter for all traffic, which should be the one the bits are flowing through if everything's working correctly.
I suspect your client machine is using some *nix flavor, so I can't say for sure how exactly to do this, but, what I'd do is disable the non-OpenVPN adapter(s) on the system as a first step and see if I can still get to the internet. If so, then it's a pretty good sign things are working.
Another thing to check is your routing tables on the client machine. If they're set up to direct everything through the OpenVPN-defined interface, again, you should be able to rest easy.
As for the non-UDP traffic... I think it might turn out to be connection-related traffic, specific to maintaining the VPN but not actual content, if that makes sense. I'm on unfamiliar ground there -- my VPN setup uses Cisco software and is Windows-based to boot, so, yeah.
--sofaspud
--"Listening to your kid is the audio equivalent of a Salvador Dali painting, Spud." --OpMegs
I suspect your client machine is using some *nix flavor, so I can't say for sure how exactly to do this, but, what I'd do is disable the non-OpenVPN adapter(s) on the system as a first step and see if I can still get to the internet. If so, then it's a pretty good sign things are working.
Another thing to check is your routing tables on the client machine. If they're set up to direct everything through the OpenVPN-defined interface, again, you should be able to rest easy.
As for the non-UDP traffic... I think it might turn out to be connection-related traffic, specific to maintaining the VPN but not actual content, if that makes sense. I'm on unfamiliar ground there -- my VPN setup uses Cisco software and is Windows-based to boot, so, yeah.
--sofaspud
--"Listening to your kid is the audio equivalent of a Salvador Dali painting, Spud." --OpMegs