Hi Roy, hi all,

why the hell I should do it that way? Both, m0n0 and this DD-WRT thing, 
do have an integrated PPTP server which could be used... I use the m0n0 
as the PPTP server for the DD-WRT to connect to. That's not the problem 
so far.

The problem is the routing, nothing more, nothing less... And the 
problem is not on the DD-WRT box, it's on the m0n0 box, which seems to 
loose the knowledge of how to reach the DD-WRTs Subnet after a reconnect 
of that tunnel...

The configuration is as follows:

m0n0: PPTP-Server, PPTP-IP 10.2.0.1, Routing to 10.3.3.1/29 via 10.2.0.16
DD-WRT: PPTP-Client, PPTP-IP 10.2.0.16, Routing to 194.77.75.96/27 via 
10.2.0.1

If I do a traceroute from my subnet to the clients one (without 
reconnect), I get the following:
194.77.75.110 -> 194.77.75.97 (m0n0) -> 10.2.0.16 -> 10.3.3.3

If the tunnel, for some reason, goes down and up again, the routing is 
as followed:
194.77.75.110 -> 194.77.75.97 (m0n0) -> ... Nothing, m0n0 tries to route 
these packets to the external interface

A traceroute from DD-WRT to the m0n0 box:
10.3.3.3 -> 10.3.3.1 (DD-WRT) -> 10.2.0.1 -> 194.77.75.110

After reconnecting, it looks like this:
10.3.3.3 -> 10.3.3.1 (DD-WRT) -> 10.2.0.1 (where it stucks and gets no 
reply, due to the m0n0 problem routing the packets to the external 
interface)...

I hope, this is better for understanding..

Tim