| === chris14_ is now known as chris14 | ||
| === bittin__ is now known as luna_curlup | ||
| === TheCaptain89 is now known as TheCaptain8 | ||
| trippeh | I'm not seeing anything on vlan aware bridges in netplan docs - is it not supported? | 20:07 |
|---|---|---|
| trippeh | appears not: https://bugs.launchpad.net/netplan/+bug/1793128 | 20:07 |
| -ubottu:#ubuntu-server- Launchpad bug 1793128 in Netplan "support vlan-aware bridges (vlan-filtering)" [Wishlist, Triaged] | 20:07 | |
| trippeh | figured I'd give netplan a go on a open ethernet type switch, but I guess not :) | 20:08 |
| trippeh | (note: oldskool per-vlan bridges + a metric crapton of vlan devices would work) | 20:24 |
| znf | trippeh, do you want to do filtering? | 21:24 |
| znf | else, is there a reason you want to use vlan-aware? | 21:24 |
| trippeh | znf: this device can do 64 ethernet ports, managing per vlan virtual devices for every port with more than one vlan and adding them to per vlan bridges would be .. a lot | 21:44 |
| znf | Understandable | 21:45 |
| patdk-lap | hmm, I have never had an issue running vlans on bridges | 22:15 |
| patdk-lap | for several releases now | 22:15 |
| patdk-lap | oh wait, I'm thinking bond | 22:15 |
| patdk-lap | I do a bond, then vlan it, then run bridges on those vlans | 22:16 |
| trippeh | that is the traditional way, yes. | 22:17 |
| patdk-lap | not possible using ebtables? | 22:18 |
| trippeh | well the point of vlan aware bridges are to make vlan things less complicated, not more complicated :p | 22:21 |
| trippeh | also dont think ebtables gets pushed down to the switch asic | 22:21 |
| trippeh | switching 64x25Gbps over the x4 pcie gen2 link to the cpu would be pretty terrible (: | 22:23 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!