<html><head></head><body>So you have a manageable switch that does vlans. Ports are assigned to specific vlans ids. To bridge vlans requires either vlan combination at a port or an external device like a multi homed server.<br><br>For small locations like homes with under 20k devices, it's easier to use literal private networks. Guest network is one class C, phones get another, iot another, etc. Use the dhcp server as the bridge/firewall/router between all. Assign fixed IPs by mac in the dhcp for servers, printers, and such, and dynamic for everything else based on which nic port the request arrives on at the dhcp server.<br><br><div class="gmail_quote">On April 16, 2019 11:47:28 PM EDT, Alex Carver via Ale <ale@ale.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">I'm playing around with the idea of splitting a few things at home into<br>VLANs. This would include one VLAN for phones, another for the general<br>computers, a third for IoT devices, a guest network, and one for the<br>video cameras.<br><br>The problem I'm trying to figure out is how to set things up so that the<br>devices with configurable syslogs (in this case phones, computers,<br>cameras) send their logs to my central logging server, allow the devices<br>to pick up their DHCP leases from the central DHCP server, and still<br>have the ability to reach the admin consoles for things like the phones<br>and cameras.<hr>Ale mailing list<br>Ale@ale.org<br><a href="https://mail.ale.org/mailman/listinfo/ale">https://mail.ale.org/mailman/listinfo/ale</a><br>See JOBS, ANNOUNCE and SCHOOLS lists at<br><a href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a><br></pre></blockquote></div><br>-- <br>Sent from my Android device with K-9 Mail. All tyopes are thumb related and reflect authenticity.</body></html>