Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 16 Jul 2017 23:14:41 +0200
From:      Frank Steinborn <steinex@nognu.de>
To:        "O. Hartmann" <ohartmann@walstatt.org>
Cc:        "Andrey V. Elsukov" <bu7cher@yandex.ru>, FreeBSD CURRENT <freebsd-current@freebsd.org>, FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: Inter-VLAN routing on CURRENT: any known issues?
Message-ID:  <20170716211441.GA63054@krenn.local>
In-Reply-To: <20170716230514.0c2e5c65@thor.intern.walstatt.dynvpn.de>
References:  <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> <c9679df1-e809-3d2b-9432-88664aae3b0a@yandex.ru> <20170713211004.13492aef@thor.intern.walstatt.dynvpn.de> <ca7a9e76-9ca3-33f9-c1ef-4c0afd0761ff@yandex.ru> <20170716230514.0c2e5c65@thor.intern.walstatt.dynvpn.de>

next in thread | previous in thread | raw e-mail | index | archive | help
O. Hartmann <ohartmann@walstatt.org> wrote:
> I have not have any success on this and I must ask now, to not make a fool out of my
> self, whether the concept of having several vlan over one single NIC is possible with
> FreeBSD (12-CURRENT, as of today, r321055.
> 
> Since it is even not possible to "route" from a non-tagged igb1 to a tagged vlan igb1.2
> or igb1.66 (for instance) on the same NIC, I have a faint suspect that I'm doing
> something terribly wrong.
> 
> I think everyone working with vlan should have those problems, but since I can not find
> anything on the list, I must do something wrong - my simple conclusion.
> 
> What is it?

Do you have enabled net.inet.ip.forwarding?




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