From owner-freebsd-stable@freebsd.org Fri Aug 7 14:55:25 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 01BE39B5FB2 for ; Fri, 7 Aug 2015 14:55:25 +0000 (UTC) (envelope-from gondim@bsdinfo.com.br) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [191.243.120.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ADAA0D50 for ; Fri, 7 Aug 2015 14:55:24 +0000 (UTC) (envelope-from gondim@bsdinfo.com.br) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) by mail.bsdinfo.com.br (Postfix) with ESMTP id 5ADE930FC57 for ; Fri, 7 Aug 2015 11:54:35 -0300 (BRT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bsdinfo.com.br; h=content-transfer-encoding:content-type:content-type :in-reply-to:references:subject:subject:to:mime-version :user-agent:from:from:date:date:message-id; s=dkim; t= 1438959274; x=1439823275; bh=IG9+HTEXBC+YYHlXFl1FqQU47ngDMv/Iq3T wV1uv/8s=; b=WWShnrLXH4JfHN7DefkoqPk0ScDZJIyaMTjM/nbORi3T3MuQ5Df BwM1hKuhCw92tO5RM4Yn9VVrNsTs38xLE/Yg8iOcz23DvPW4phHNBg+uet5EVYfE PAfqpA9aium/SWLequw8r2bPBXptx6lmULVs2sUTnM7Ffy13EsOJ7JQI= X-Virus-Scanned: amavisd-new at mail.bsdinfo.com.br Received: from mail.bsdinfo.com.br ([127.0.0.1]) by mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GeOhlWAWZqPN for ; Fri, 7 Aug 2015 11:54:34 -0300 (BRT) Received: from [192.168.88.29] (unknown [10.255.0.12]) by mail.bsdinfo.com.br (Postfix) with ESMTPSA id DDAF930FC08; Fri, 7 Aug 2015 11:54:34 -0300 (BRT) Message-ID: <55C4C69B.3030607@bsdinfo.com.br> Date: Fri, 07 Aug 2015 11:54:19 -0300 From: Marcelo Gondim User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: "Andrey V. Elsukov" , FreeBSD Stable Mailing List Subject: Re: Routing stops working when we create a new vlan References: <55C3E641.9060305@bsdinfo.com.br> <55C4AFC8.9030302@yandex.ru> <55C4C0BB.5070204@bsdinfo.com.br> <55C4C1CF.5070505@yandex.ru> In-Reply-To: <55C4C1CF.5070505@yandex.ru> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Aug 2015 14:55:25 -0000 On 07-08-2015 11:33, Andrey V. Elsukov wrote: > On 07.08.2015 17:29, Marcelo Gondim wrote: >> On 07-08-2015 10:16, Andrey V. Elsukov wrote: >>> On 07.08.2015 01:57, Marcelo Gondim wrote: >>>> For all work again I need to restart the router. >>>> I don't know if I could correctly explain the problem. >>> Do you have gateway_enable="YES" in your /etc/rc.conf? >>> >> I have net.inet.ip.forwarding=1 but when I create a new vlan, the system >> is changing to: net.inet.ip.forwarding=0. Why? > AFAIR, devd starts some scripts and if you don't have > gateway_enable="YES" net.inet.ip.forwarding will be reset to zero. And > since devd doesn't restart sysctl.conf you lose your gateway. > > The right way to configure router - use gateway_enable="YES" in rc.conf. > >> I try to go back to the value 1 and the system does not return to work. >> Only back to work if I restart the system. > This seems strange, are you sure? > Problem solved using gateway_enable = "YES" in /etc/rc.conf. But I still think it does wrong. Why to create a vlan I need to have this parameter configured in rc.conf? Or why it needs to change net.inet.ip.forwarding? []'s Gondim