Bridges on VLAN-tagged interfaces.

[Eric Bautsch]

Hi Patrick.


I get that point, but then I have two options only: I somehow convince the BIOS 
to do a network boot over a VLAN for installation - not a capability this BIOS 
appears to have, or I end up creating a whole new VLAN that's either routed or 
has YP, DNS, time and installation servers on it. That's a massive headache....

It'd be much neater if FreeBSD could handle the tagged/untagged traffic. It just 
works (TM) on Solaris and Linux, so I expected it to do the same on FreeBSD... :-(

Surely, there must be a way....

Eric




On 19/03/2019 07:59, Patrick M. Hausen wrote:
> Hi!
>
>> Am 18.03.2019 um 22:12 schrieb Eric Bautsch <eric.bautsch at pobox.com>:
>> I now have a bridge0 on re0.33 which works, great.
>> I now configure a bridge1 which contains re0 and put an IP on that bridge, and hey presto, that IP pings, but the IP on bridge0 on VLAN 33 stops pinging.
> IMHO you should not be mixing VLAN tagged and untagged
> traffic on the same interface. A port is a trunk port carrying
> tagged traffic or an access port carrying untagged traffic
> only.
>
> So you should - again, my opinion - create a VLAN, say 1 on
> re0 and put re0.1 into bridge1. I know this works from
> experience.
>
> We have some rare performance issues when combining
> this with VNET but first things first … still investigating and I’ll keep
> the list informed.
>
> Kind regards,
> Patrick

-- 
  
       ____
      /          .                           Eric A. Bautsch
     /--   __       ___                ______________________________________
    /     /    /   /                  /
   (_____/____(___(__________________/       email: eric.bautsch at pobox.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4127 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.freebsd.org/pipermail/freebsd-net/attachments/20190319/537fd319/attachment.bin>