From owner-freebsd-current@freebsd.org Sun Jul 16 21:27:25 2017 Return-Path: Delivered-To: freebsd-current@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 73BC5C7ADCD for ; Sun, 16 Jul 2017 21:27:25 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DF6806830A for ; Sun, 16 Jul 2017 21:27:24 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.180.117.19]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LviG8-1dilGy2RVU-017VCZ for ; Sun, 16 Jul 2017 23:27:16 +0200 Date: Sun, 16 Jul 2017 23:27:15 +0200 From: "O. Hartmann" To: freebsd-current@freebsd.org Subject: Re: Inter-VLAN routing on CURRENT: any known issues? Message-ID: <20170716232715.21a42d50@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170716211441.GA63054@krenn.local> References: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> <20170713211004.13492aef@thor.intern.walstatt.dynvpn.de> <20170716230514.0c2e5c65@thor.intern.walstatt.dynvpn.de> <20170716211441.GA63054@krenn.local> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/7WK68YWbJz7a_8hfD6RIBuc"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:7XgBHqvRRaetHjFw2H8UnqMCLHd0iPqznBbDvGo2K7uQMr33HyU KXhEPnKJna6hld0FRFwEGhHOpGkVr8tpSJV35sOPtrxNdd+FE5I9HVhMxgzJ4YOO16xs1mj nzsJO0GxR03kvQy7ENf7NsWnZ1Nj7xVj7LQ54TSofaTw4XtCzFHZLeUOEGxbNt+10GgKPcn 0jbI4EtF7LSG/cvwXdvnQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:7tR0QPd/g8M=:3D4AYi8dwss9S0lShloLUQ ATT1PUVuDTwkQCmx2dPtvFBFKVlF6GRTuIp89YAUuZKp3Q/AIoGIkAsSd/GHrwSSDe1IfRPpR pHzN65QK5Qcf2oHoTZuDZwlVp0ASddT48RlYekCubOVT6w3csXauvExj6bICfUQMjQKv2jmJZ 4CuwqdGPptu7Q/KftwsfMv9s/iqmggYy3ZOK4uoJngAMZDKBYYkrgnYylceXcczgj3vRJ4NO8 QCPga34Wr01sCgjbXGJL49rhGRFznDfm6GXdezgh2URWT0RVJVyXP6Dh3swpDlfWu1nUtOWIX Rt5Vdp+FSpt86ggLg48kzWz5ipMhl1utE6D5rc+NnpAHahwfkQ6rBy35QyW1/dc7f1uZJIkUG cCZ0G4D8Bu5IcoJAlJ+o5uQhJNHQi58QgCapp0e6przGvnnyFmceyCc+c4AbBcEtVcCYZD8k+ FJR3tO/RxC1CqlIMXdlkQJDVn7MjXPfk4eyFwlzeAZ0vUrSxuLRlz4xQxBv7f0kcXhUhHy4GS Z4NbX3/7Rx606ED7RSj171Yk8lIb74MCXjTcpVh1n1u0fUQNpcuZhfmsipdmq4uSARtMOSN/h 8bS+5qgQH87MIFTqeh6OLO6OvvXOwdmop7N+uTYnA9WCNJbvPh1hlVnuvUzH5e8kR3ZOxJ6AC DUjSPA4G26l0Tj/6f7mLrUovqwSpZEkdR7RiXohWoU4wcStkqrgBvdIv6l3IqnXEnIzaF3oRt E6k6Zz1LWHQnnugMj0eE61l/+OWrcDyoeq2lzrobNEx906bz3SGGUGYgzZXuzlmudK4BEJ6o0 JtlwZaufzpq+6rV/r7ECduJwlRPbg== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jul 2017 21:27:25 -0000 --Sig_/7WK68YWbJz7a_8hfD6RIBuc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Sun, 16 Jul 2017 23:14:41 +0200 Frank Steinborn schrieb: > O. Hartmann wrote: > > I have not have any success on this and I must ask now, to not make a f= ool 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. > >=20 > > Since it is even not possible to "route" from a non-tagged igb1 to a ta= gged vlan > > igb1.2 or igb1.66 (for instance) on the same NIC, I have a faint suspec= t that I'm > > doing something terribly wrong. > >=20 > > I think everyone working with vlan should have those problems, but sinc= e I can not > > find anything on the list, I must do something wrong - my simple conclu= sion. > >=20 > > What is it? =20 >=20 > Do you have enabled net.inet.ip.forwarding? >=20 ... aber selbstverst=C3=A4ndlich doch, das ist das erste seit nunmehr 20 Ja= hren FreeBSD, was auf einem Router eingestellt wird ... Wie ich bereits beschrieben habe: pingen (ICMP) auf andere VLANs geht, nur = keine IP Dienste - und das mit oder ohne eingeschalteter IPFW. Gr=C3=BC=C3=9Fe, oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/7WK68YWbJz7a_8hfD6RIBuc Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWWvaMwAKCRDS528fyFhY lEljAf91cTIuMx2eY+itbtJdKJGmRoLEpgE77MvKu6/QxBedRoeRwF9MuXbCfprZ P9NMmvC2iumrIiYD1wKYPTlfgnyTAf9xrece+/QRLtaKxzFiRmdRI94iKWTXnru2 wOYa27HmcuNY9GeNA/U4FPaHm9O43xg6dTtNOQ1yh9DcUKdiDdhP =gIVY -----END PGP SIGNATURE----- --Sig_/7WK68YWbJz7a_8hfD6RIBuc--