Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Jul 2017 16:41:38 +0300
From:      korg@tune-it.ru
To:        "O. Hartmann" <ohartmann@walstatt.org>, Frank Steinborn <steinex@nognu.de>
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:  <019eb889-ebc1-3c38-8070-1779476d6db2@tune-it.ru>
In-Reply-To: <20170716233158.53f5d6e3@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> <20170716211441.GA63054@krenn.local> <20170716233158.53f5d6e3@thor.intern.walstatt.dynvpn.de>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Do you receive packets from 192.168.2.0/24 and 192.168.3.0/24 on igb1.2 
and igb1.3 respectively?

Do you really need NAT? As far as I can see, you're looking for static 
inter-VLAN routing.

Could you check the communication between 2.0/24 and 3.0/24 with 
unloaded ipfw module?

I have a lot of installations of such scheme on em(4) and re(4) devices 
-- no problems at all. Even maybe there was igb(4) devices too.

Sergey <KorG> Zhmylove

17.07.2017 0:31, O. Hartmann пишет:
> Am Sun, 16 Jul 2017 23:14:41 +0200
> Frank Steinborn <steinex@nognu.de> schrieb:
>
>> 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?
>>
> Of course I have. As I stated earlier, ICMP pings from on VLAN to another over this
> router works, but any IP (UDP, TCP) is vanishing into thin air.
>
> I don't have a FBSD-11-STABLE reference system at hand, so that I can check with another
> revision/major release of the OS, but I work on that.
>




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?019eb889-ebc1-3c38-8070-1779476d6db2>