Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Jun 2005 08:59:26 +0400
From:      Dmitry Mityugov <dmitry.mityugov@gmail.com>
To:        =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= <bkoenig@cs.tu-berlin.de>
Cc:        Peter <peterpub1@aboutsupport.com>, "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   Re: Simple ipfw problem :(
Message-ID:  <b7052e1e050623215936897bc7@mail.gmail.com>
In-Reply-To: <42BAA90E.3060309@cs.tu-berlin.de>
References:  <42BAA0A9.3090808@aboutsupport.com> <42BAA90E.3060309@cs.tu-berlin.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On 6/23/05, Bj=F6rn K=F6nig <bkoenig@cs.tu-berlin.de> wrote:
...
> Actually you don't need ipfw or any other packet filter to set up a
> simple internet access point for clients in a LAN. This configuration
> should be enough:
>=20
> ---- ppp.conf ----
> myisp:
>    set device PPPoE:<interface>
>    set log Phase IPCP CCP Warning Error Alert
>    add! default HISADDR
>    set authname <username>
>    set authkey <password>
> ----
> Note: <interface> is your external network interface, i.e. neither rl0
> nor tun0.
>=20
> ---- rc.conf ----
> gateway_enable=3D"YES"     # "sysctl net.inet.ip.forwarding=3D1" at start=
up
> ppp_enable=3D"YES"
> ppp_mode=3D"ddial"
> ppp_profile=3D"myisp"
> ppp_nat=3D"YES"            # alternatively "nat enable yes" in ppp.conf
> ----
>=20
> I hope I didn't forget about something.

nat deny_incoming yes might be a good addition to this list.

--=20
Dmitry

"We live less by imagination than despite it" - Rockwell Kent, "N by E"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b7052e1e050623215936897bc7>