From: James C. <jam...@hp...> - 2002-12-29 22:05:54
|
On Mon, 2002-12-30 at 08:43, James Stone wrote: > Your new routing script looks fine. I still need the explicit routes to > my ISPs DNS or it doesnt work.. but could just be an isolated problem > with me. Yes, I'd say so. You should try changing your /etc/resolv.conf to point at the DNS server that is accessible through the tunnel. If you've tunnelled into a network that stops you from being able to send DNS queries to your ISP's BIND server, then presumably the tunnelled network has it's own BIND server. Changing /etc/resolv.conf then becomes another task for the ip-up script. (As for me, I have a local BIND server that splits the queries between the external and tunnelled network BIND server). > In Debian, the pppd environment > variables are set in ip-up and it doesn't seem possible to set them > again in scripts in ip-up.d I agree. It depends on the distribution. I use Debian, and indeed the $1 through to $6 arguments are not given to the scripts run by run-parts from /etc/ppp/ip-up.d ... so I've changed the scripts to accept either positional arguments or the Debian ip-up environment variables. > so you need to use: PPP_IPPARAM for "CONNECTION" and > IFNAME for "TUNNEL" Yes to the first, no to the second. IFNAME is actually set by pppd, not by the ip-up script. I've used PPP_IFACE. > also you should point out that if the tunnel script in /etc/ppp/peers > should be named tunnel for the route script to work, or otherwise, the > route script can be changed accordingly. I thought it was the ipparam option that did this, not the script name. pppconfig sets up ipparam. I've added a comment to that effect, thanks. Changed revision date to 30th. http://pptpclient.sourceforge.net/routing.phtml#all-to-tunnel -- James Cameron (jam...@hp...) http://quozl.linux.org.au/ (or) http://quozl.netrek.org/ |