https://bugzilla.novell.com/show_bug.cgi?id=259698#c7 --- Comment #7 from Friedrich Lobenstock <fl@fl.priv.at> 2007-11-27 11:11:55 MST --- No it's not that. Let me try to describe it again: * first we do DHCP on eg. eth0 and get a default route * then we do PPTP to a PPTP-Server which is reachable via the current default route * Now the PPTP connection changes the default route to point into the tunnel * Oops, how do we get to the tunnel endpoint? It was only reachable via the default route which now points INTO the tunnel device. 0.0.0.0/1 plus 128.0.0.0/1 gives the sam problem here. In this setup we'd need to detect that if the tunnel endpoint lives "behind" the default route we need to install a host route to that endpoint first before trying to build the tunnel. This host route will then "defeat" any other less specific routes as 0.0.0.0/0, 0.0.0.0/1 or 128.0.0.0/1. I could not find an entry point early enough to be able to hook in a script which does the "endpoint behind default route" and adding of the host route. Have a look into my modifications to /etc/ppp/ip-up, function add_PtProute(), which are sadly called to late in the tunnel building process. The only solution was to add the host route manualy everytime just before letting Kinternet "dial" the connection. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.