* Jason Dixon <[email protected]> [2009-05-06 22:52]: > On Wed, May 06, 2009 at 05:38:51PM -0300, Giancarlo Razzolini wrote: > > > > Well, i wasn't OT with my reply. And i use openvpn from the beginning of > > the project, even made a plugin for it. So i know i little of it. My > > suggestion was to avoid what you might be already suspecting. You will > > have to mess with openvpn code and recompile it to do what you want. The > > solution i suggested is a viable one, even if already have queueing > > policies on that interface. It'll only require a little adaptation on > > your altq rules. I guess you won't get far with an attitude like that, > > being rude with people that are trying to help you. That said, you might > > want to take a look at openvpn source code, mainly tun.c and tun.h files. > > Regardless of how much you claim to know about it, the fact remains that > there's no way to have OpenVPN bind to an existing tun device. Thanks > for the roundabout answer.
actually... the way he proposes should work, even in your usage case. really. the tags telling altq where to queue survive the tun encapsulation (i think). so you can queue on the real interface based on classification done for traffic inside the tunnel. -- Henning Brauer, [email protected], [email protected] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg & Amsterdam
