From: James C. <jam...@hp...> - 2009-04-28 22:51:42
|
On Tue, Apr 28, 2009 at 02:57:12PM +0200, Uwe Brauer wrote: > James Cameron wrote: > > Uwe Brauer wrote: > > > so it seems that journal "thinks" my IP is 192.... instead of > > > 147.... like the browser request did not pass the tunnel. > > > > > > or there is something I fail to understand. > > > You probably fail to understand how the Linux kernel does routing. > > Not probably, surely. I cannot be sure of that. Over the years I've had many people pretend to ignorance. > > To find out what route will be used to contact a site, use the "ip > > route get" command. For example, assuming you wish to connect to a > > site www.netrek.org, type the command: > > > host www.netrek.org > > this has been extremely helpful, thanks a lot. > > However intuitively the phrase *all traffic through tunnel* at it is > used in pptpconfig seems to imply that indeed all traffic browser mail > use the tunnel and not eth1 say. The phrase *all traffic through tunnel* means that all connections, except the connection being used to transport the tunnel itself, will be directed into the tunnel. > As I understand from your remark this is a misunderstanding > *all traffic through tunnel* does not mean this. I'm not sure I understand. > The question is there any linux client which truly sends all traffic > trough the tunnel? Sorry, I don't keep a list of the software that uses pptp, nor the features of said software. Here is what I know of this software: - kvpnc, might do this, not checked, - NetworkManager with pptp plugin, might do this, not checked, - pptpconfig, did do this, but deprecated, unsupported, - pptpsetup, does not do this. Also, if you have a choice to use another tunnel protocol, OpenVPN, does do *all traffic through tunnel*, is currently supported, and in my experience works more frequently than PPTP. -- James Cameron http://quozl.netrek.org/ HP Open Source, Volunteer http://opensource.hp.com/ PPTP Client Project, Release Engineer http://pptpclient.sourceforge.net/ |