Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 Aug 2022 12:42:11 +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:  <90b59493-95d6-5b2a-b0dc-2fece0a9df7b@puchar.net>
In-Reply-To: <57a9cad0-c2ef-6e1f-2185-0f7563fe3758@grosbein.net>
References:  <d36e56ff-c7cd-1634-dbc-f76bdb46503c@puchar.net> <623ac39e-2915-463a-9e4c-9f99bae28c69@puchar.net> <bfa7d65a-95d6-1605-8fb0-cf397b79d549@grosbein.net> <c3ce6ec-60c7-f9b7-9c73-1fdcdfee505@puchar.net> <57a9cad0-c2ef-6e1f-2185-0f7563fe3758@grosbein.net>

next in thread | previous in thread | raw e-mail | index | archive | help
>>> 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?
>
> Some scripts (f.e. from /etc/devd.conf) invoke /etc/pccard_ether $subsystem start
> (the name "pccard_ether" is just historic, it serves any cloned network interface).
>
> It runs "/etc/rc.d/netif quietstart" $ifn that runs "/etc/rc.d/routing static any $_if"
> that may reset net.inet.ip.forwarding=0 unless you have gateway_enable="YES" in /etc/rc.conf
> despite you could have set net.inet.ip.forwarding=1 via sysctl.conf.
>
>
>
>
Thanks. Fortunately i don't use devd on any servers.

Anyway - with ip.forwarding on ssh still disconnect randomly. Just after 
much larger amount of data transmitted (like 10-100MB, not <1MB)

Just on this server. Any ideas what may be wrong?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?90b59493-95d6-5b2a-b0dc-2fece0a9df7b>