[astol]

Thanks for reply.

The thing is to create a shaper that only shapes, because implementing NAT automatically implies that I should implement a lot of other functionality and finally it’ll be something like Traffic Inspector – the outcome I want to avoid. To be specific I intend to use Traffic Inspector and since it’s shaping module is really bad implemented I want to write my own. If I do NAT, then I’ll have to somehow forbid TI’s NAT and I don’t know if he’s capable to work without it.

But… Wait a minute. TI doesn’t NAT. It uses Windows’s Routing and remote access. Ha, my problem is solved. I’ll do NAT and shaping, and let TI do anything else like authentication, traffic metering and else.

Thanks a lot! 🙂

PS: Hmm… And how does TI shape NATted connection!?…

[Author]

Posts