Date: Mon, 03 Jun 2019 10:54:20 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 238198] Traffic through a vm -> bridge(4) -> vlan -> ix(4) does not return Message-ID: <bug-238198-7501-eVN351IZm6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238198-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-238198-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238198 --- Comment #15 from dgilbert@eicat.ca --- (In reply to punkt.de Hosting Team from comment #14) [ on configuring my switch to avoid the problem ] That's fine on a Cisco. But for the dozens of other brands, not-so-much. = In this case, it's a ubiquity (or unifi ?) ... and aggressively positioned swi= tch as part of an ecosystem of WiFi and WISP gear. AFAICT, changing the access vlan removes communication with the management = lan alltogether. As I said, so far I'm using another ethernet card to talk to this. It's not an uncommon setup, I believe. FreeBSD should be that swiss army k= nife that just works in all situations, not the OS that prays to one particular = god of configuration or the other. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238198-7501-eVN351IZm6>