Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 Aug 2022 10:04:37 +0200 (CEST)
From:      Wojciech Puchar <wojtek@puchar.net>
To:        Eugene Grosbein <eugen@grosbein.net>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: ipfw nat problem
Message-ID:  <c3ce6ec-60c7-f9b7-9c73-1fdcdfee505@puchar.net>
In-Reply-To: <bfa7d65a-95d6-1605-8fb0-cf397b79d549@grosbein.net>
References:  <d36e56ff-c7cd-1634-dbc-f76bdb46503c@puchar.net> <623ac39e-2915-463a-9e4c-9f99bae28c69@puchar.net> <bfa7d65a-95d6-1605-8fb0-cf397b79d549@grosbein.net>

next in thread | previous in thread | raw e-mail | index | archive | help
>> found a reason. forwarding was set to 0 in sysctl
>
> Never set net.inet.ip.forwarding=1 manually or via /etc/sysctl.conf.
>
> Always use gateway_enable="YES" in /etc/rc.conf, or else system scripts started with devd

I don't use devd on servers.

> on any interface creation (tunX, ngX, etc.) will switch forwarding to 0 again.

Well - i do create tun or other interfaces without problems. Can you point 
an example of this?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c3ce6ec-60c7-f9b7-9c73-1fdcdfee505>