Date: Fri, 29 Oct 2004 09:52:51 +0200 (CEST) From: Peter Ulrich Kruppa <root@pukruppa.de> To: freebsd-stable@freebsd.org Subject: Re: ppp -nat broken [solved] Message-ID: <20041029090017.I827@pukruppa.net> In-Reply-To: <20041026141721.X816@pukruppa.net> References: <20041026141721.X816@pukruppa.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 26 Oct 2004, Peter Ulrich Kruppa wrote:
> I wonder if userland ppp's nat option is broken or if I missed
> something new.
First of all: My humble apologies to everybody for setting you on
the wrong track. Indeed -nat works all-right. My problems were
caused by recent changes of named and BIND.
Big thanks for all hints which helped me to analyze this. For
details look further down.
> I am using my freebsd (5.3-STABLE) machine as internet gateway.
> Everything works all-right from the gateway itself. From my
> workstations I can ping any IP in the internet, but domain
> names won't be resolved ("unknown host").
>
> These are my rc.conf lines:
>
> kern_securelevel_enable="NO"
> inetd_enable="YES"
> gateway_enable="YES"
> named_enable="YES"
> ppp_enable="YES"
> ppp_mode="ddial"
> ppp_nat="YES"
> ppp_profile="my-profile"
This configuration starts named as a local nameserver. I never
had to do anything else. This stopped working "out of the box"
some time ago. From /usr/src/UPDATING (20040928, 20040925) I
learn that named and BIND have changed. I did the respective
changes and edited two entries in /var/named/etc/named/named.conf
1) I commented
listen-on {127.0.0.1;};
2) I put my two nameserver IPs (from /etc/resolv.conf) into
forwarders {
195.62.99.42;
195.62.97.177;
};
After restarting named everything worked as before: my clients
accept my gateway's IP as gateway *and* nameserver.
Thanks and regards,
Uli.
+---------------------------+
| Peter Ulrich Kruppa |
| Wuppertal |
| Germany |
+---------------------------+
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041029090017.I827>