{"id":917,"date":"2026-11-22T10:58:00","date_gmt":"2026-11-22T18:58:00","guid":{"rendered":"https:\/\/blog.canutethegreat.com\/?p=917"},"modified":"2026-11-22T10:47:20","modified_gmt":"2026-11-22T18:47:20","slug":"patronus-i-switched-on-the-guest-network-and-tried-to-get-out-of-it","status":"publish","type":"post","link":"https:\/\/blog.canutethegreat.com\/index.php\/2026\/11\/22\/patronus-i-switched-on-the-guest-network-and-tried-to-get-out-of-it\/","title":{"rendered":"Patronus: I switched on the guest network and tried to get out of it"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Full disclosure: I make Patronus, a router and firewall OS built on Gentoo. The guest network page is the newest thing I&#8217;ve added to it. It went into main on November 17 and isn&#8217;t in a tagged release yet.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Every router says guests can&#8217;t reach your LAN. I wanted to check that claim, so on November 22 I switched the guest network on in a lab and tried to reach the NAS, the router&#8217;s admin page, the modem and the other guest.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The lab<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This was a lab, not my house. One container with a handful of network namespaces: the router (the real <code>patronus-web<\/code> plus the apply step, built from main at commit 02e0a2c7, 5 minutes 11 seconds cold in a capped container), one LAN device, two &#8220;visitor&#8221; devices on two spare router ports, a fake ISP and a fake internet. The NAS is a tiny web server on the LAN that answers &#8220;192.168.50.13 sees 192.168.50.10&#8221;. The ISP modem&#8217;s admin page is another one at 10.77.7.7, behind the WAN. Everything is curl and a DHCP client. I drove the admin page with a real browser, from the LAN device&#8217;s namespace.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Things that are fake or missing. There is no radio, so this is the wired half only: visitors are plugged into ports and the Wi-Fi switch stayed off. The visitors run busybox&#8217;s <code>udhcpc<\/code>, not a phone. The lab router has no resolver of its own, so I filled in the &#8220;Router DNS forwards to&#8221; box with the fake internet&#8217;s DNS server. The page still carries a &#8220;This router has not been set up yet&#8221; banner because I never ran the setup wizard in this lab.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Turning it on<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The guest network is off until you switch it on, and everything lives on one page: <code>\/svc\/guest<\/code>. It&#8217;s one long form. I ticked the box, set the VLAN id to 0 (no VLAN, use ports only), listed the two spare ports, left the address at its default of 192.168.30.1\/24, and set a per-guest download cap of 4000 kbit\/s.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blog.canutethegreat.com\/wp-content\/uploads\/2026\/11\/patronus-guest-04-settings-filled.png\" alt=\"The guest network settings form with the network switched on, extra ports gst-a and gst-b, address 192.168.30.1\/24 and a per-guest download cap of 4000\" loading=\"lazy\"\/><figcaption class=\"wp-element-caption\">The settings form as I filled it in. The DNS forwarder box is only filled because my lab router has no resolver.<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Before the real save I tried to break it. I typed the LAN&#8217;s own subnet, 192.168.50.5\/24, as the guest address. The page refused with &#8220;Invalid guest subnet 192.168.50.0\/24 (overlaps 192.168.50.0\/24 on rtr-lan; pick another address)&#8221;, and when I asked the API afterwards the address was still 192.168.30.1\/24. The red box shows up at the top of the page though, above the part you&#8217;re looking at when you click Save, so on a laptop it looks like nothing happened until you scroll up.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blog.canutethegreat.com\/wp-content\/uploads\/2026\/11\/patronus-guest-03-refused-overlap.png\" alt=\"A red message reading Not applied: Configuration error: Invalid guest subnet 192.168.50.0\/24 overlaps 192.168.50.0\/24 on rtr-lan, above the settings card with the address field filled with 192.168.50.5\/24\" loading=\"lazy\"\/><figcaption class=\"wp-element-caption\">The refusal. The stored address did not change.<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The real save took between 0.7 and 0.8 seconds in four runs, measured from the click to the status card saying the bridge is up. Then I plugged in the two visitors.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blog.canutethegreat.com\/wp-content\/uploads\/2026\/11\/patronus-guest-10-status-two-guests.png\" alt=\"The live status card showing bridge up yes, DHCP and DNS running yes, and two clients listed by address and MAC\" loading=\"lazy\"\/><figcaption class=\"wp-element-caption\">Status card with two guests. Clients are an address, a MAC and a star where a name would go.<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Being a visitor<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Both visitors got a lease from 192.168.30.1 with a 7200 second lease time (the default of 120 minutes), the router as gateway and DNS, and could fetch a page from the fake internet. The site saw the router&#8217;s WAN address, so the traffic is masqueraded. A ping to the router answers, which is a setting that defaults to on.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blog.canutethegreat.com\/wp-content\/uploads\/2026\/11\/patronus-guest-06-term-visitor-joins.png\" alt=\"Terminal output: a visitor runs udhcpc and gets 192.168.30.193 from 192.168.30.1, fetches www.example.test and sees the router&#x27;s WAN address, and pings the router\" loading=\"lazy\"\/><figcaption class=\"wp-element-caption\">A visitor joins. Lab names and documentation addresses throughout.<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">From the visitor I tried the NAS, the router&#8217;s admin page on its guest address, on its LAN address and on its WAN address, the modem&#8217;s page behind the WAN, and the other visitor. All six timed out. As a control, the LAN device fetched the NAS fine, and a LAN device trying to open a connection to a visitor also timed out, which is what the docs promise (nothing starts a connection into the guest network).<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blog.canutethegreat.com\/wp-content\/uploads\/2026\/11\/patronus-guest-07-term-blocked.png\" alt=\"Terminal output: the LAN device reaches the NAS, while the visitor&#x27;s curl to the NAS, the router admin page on three addresses, the modem page and the other guest all end with exit 28, and a LAN device curling a guest also times out\" loading=\"lazy\"\/><figcaption class=\"wp-element-caption\">The LAN control fetch, then the six visitor probes. Exit 28 is curl giving up after 3 seconds.<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">These are drops, so a visitor just waits for the timeout. I looked at the firewall to see why. The guest rules are their own nft table at priority -15, ahead of the main firewall, and its input chain ends with a drop commented &#8220;guests reach nothing else on the router&#8221;. The forward chain drops private ranges beyond the WAN, drops a source address that isn&#8217;t in the guest subnet, and the way back into the guest network only allows established flows.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blog.canutethegreat.com\/wp-content\/uploads\/2026\/11\/patronus-guest-09-term-nft.png\" alt=\"Output of nft list table inet patronus_guest: input chain allowing DHCP, DNS and ping then dropping, forward chains guest_out and to_guest, a per-guest download cap set, and a masquerade rule\" loading=\"lazy\"\/><figcaption class=\"wp-element-caption\">The kernel&#8217;s view of the guest network. I removed one line of live meter entries, nothing else.<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">The speed cap<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">I set 4000 kbit\/s per guest, which is 500 kilobytes a second. Each visitor downloaded for 8 seconds from a bulk server and curl reported 576,369 and 580,724 bytes a second. Across four runs the figures stayed between 576,000 and 581,000, about 15 percent over the setting. The docs say per-guest caps are policed with nft meters, that packets over the rate are dropped and that TCP settles somewhere near it, and they estimate the error at &#8220;within about 20 percent&#8221;. The LAN device on the same server got about 8.3 gigabytes a second through the lab&#8217;s virtual links, so the cap is the only thing slowing the visitors. I only tested the per-guest download cap, not the network-wide caps or either upload cap.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blog.canutethegreat.com\/wp-content\/uploads\/2026\/11\/patronus-guest-08-term-cap.png\" alt=\"Terminal output: two visitors measured at about 576 and 581 kilobytes per second, and the LAN device at over 8 gigabytes per second\" loading=\"lazy\"\/><figcaption class=\"wp-element-caption\">Measured with curl over 8 seconds. The LAN device number is the lab&#8217;s virtual link, not a real speed.<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Closing it, and the clip<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The page has buttons: new Wi-Fi password, new voucher, open for a while, close now, and show the password with a QR code. I pressed close now. The visitor&#8217;s internet request timed out, and a DHCP renew still worked, so the device keeps its address. DNS and ping to the router were refused. The docs say that&#8217;s intended: while closed, DHCP still answers and nothing else does.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blog.canutethegreat.com\/wp-content\/uploads\/2026\/11\/patronus-guest-14-term-closed.png\" alt=\"Terminal output after pressing Close now: the visitor&#x27;s curl times out, udhcpc renews a lease, ping to the router gets 100 percent loss, and a name lookup fails\" loading=\"lazy\"\/><figcaption class=\"wp-element-caption\">After Close now. The lease renews, nothing else works.<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The clip is a different run on the same lab, 37 seconds, real time. The router page is on top and a terminal is underneath: I switch it on from the form, a visitor joins, tries the NAS, the router page and the other visitor, I press close now, then open for a while, and the internet comes back. The two panes were recorded at the same time but separately, so don&#8217;t read anything into sub-second timing.<\/p>\n\n\n\n<figure class=\"wp-block-video\"><video controls preload=\"none\" poster=\"https:\/\/blog.canutethegreat.com\/wp-content\/uploads\/2026\/11\/patronus-guest-network-poster.jpg\" src=\"https:\/\/blog.canutethegreat.com\/wp-content\/uploads\/2026\/11\/patronus-guest-network.mp4\"><\/video><figcaption class=\"wp-element-caption\">Switch on, join, probe, close now, open for 120 minutes. Router page on top, terminal below. Lab clocks are real.<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The share card is the other button I used. It generates a 16 character password and shows it with the standard Wi-Fi join text and a QR code. It&#8217;s the demo password from my lab, and I didn&#8217;t scan the QR or join anything with it, because there is no radio in this lab.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blog.canutethegreat.com\/wp-content\/uploads\/2026\/11\/patronus-guest-11-share-card.png\" alt=\"The Actions card with five buttons and, below them, the guest SSID, a WIFI join string with a password, and a QR code\" loading=\"lazy\"\/><figcaption class=\"wp-element-caption\">The share card. Password is from the throwaway lab.<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">What the docs say about the design<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Several choices are written down in <code>docs\/GUEST-NETWORK.md<\/code>. The guest network is one bridge. VLAN sub-interfaces, spare ports and the guest SSID all join it, the ports are isolated from each other, and the SSID runs client isolation. The doc says plainly that a guest VLAN that continues onto an unmanaged switch can&#8217;t be isolated by the router, because the trunk is one bridge port. Guests get their own dnsmasq bound to the guest address only. Schedules and timed windows are nft rules, written that way &#8220;so they close by themselves, with no daemon&#8221; and survive a reboot. Vouchers are WPA2-only because stock hostapd reads SAE passwords only at start. The intro says it follows the way pfSense and OPNsense guest VLANs, OpenWrt guest networks and UniFi and Firewalla guest networks work. I haven&#8217;t done a feature-by-feature comparison against any of them.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The docs don&#8217;t say why the default is 192.168.30.0\/24 on VLAN 30, or why leases are 120 minutes, or why it ships switched off. They also don&#8217;t say why guest IPv6 is dropped, only that it isn&#8217;t supported yet. I don&#8217;t know why.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What doesn&#8217;t work (yet)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Worst bug: the status card shows the wrong state for schedules. I set the access mode to a daily schedule of 03:00 to 04:00 and looked at the card at 18:25 and again at 18:37 on the lab clock. The card said &#8220;schedule 03:00-04:00&#8221; and &#8220;access now: open&#8221;. The visitor&#8217;s request timed out both times, because the firewall rules were doing their job. When I changed the window to 00:00 to 23:59 the visitor got through. The rules are right and the label is wrong. I read the status function in <code>guest.rs<\/code> and it never checks the clock for a schedule, it just reports open.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blog.canutethegreat.com\/wp-content\/uploads\/2026\/11\/patronus-guest-16-status-outside-schedule.png\" alt=\"The live status card showing ACCESS DETAIL schedule 03:00-04:00 and ACCESS NOW open\" loading=\"lazy\"\/><figcaption class=\"wp-element-caption\">The page says open. The visitor&#8217;s internet was closed when this was taken.<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Close now and Open for a while change the access mode to timed and leave it there. After &#8220;open for 120 minutes&#8221; the network closes by itself when the time runs out and stays shut until somebody opens it again, which the docs say. I didn&#8217;t wait it out. Switching back to always open is a separate step on the form.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Smaller things. The header says &#8220;Home \/ Svc-guest&#8221;; a commit this morning fixed names like DHCP and DNS in the breadcrumb and this page didn&#8217;t get the same treatment. The form has &#8220;Open until (epoch seconds)&#8221; as a raw number. The minutes for open-for-a-while and for a voucher come from the browser&#8217;s own popup boxes. The clients list is an address and a MAC with a star where a hostname would be, and there is no way to kick one, which the docs list under &#8220;not yet&#8221;. On a 390 pixel wide phone the Guest network checkbox floats awkwardly next to its label. The status card looks fine there, but I only skimmed the long settings form.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/blog.canutethegreat.com\/wp-content\/uploads\/2026\/11\/patronus-guest-17-phone-status.png\" alt=\"The live status card on a 390 pixel wide phone, listing ACCESS DETAIL schedule 00:00-23:59, bridge up yes, two clients, DHCP and DNS running\" loading=\"lazy\"\/><figcaption class=\"wp-element-caption\">Status card on a phone. This was taken at the end of the session, after I&#8217;d set an all day schedule.<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">What I didn&#8217;t test: Wi-Fi at all, VLAN mode, a reboot, IPv6 (guests are supposed to get none), a real phone or a real DHCP client, lease expiry, the network-wide caps, the upload caps, a voucher actually being used to join, and anything that ran longer than an hour. I created one voucher through the page (name weekend-visitor, 2880 minutes) and it showed up in the list, and that&#8217;s all I know about vouchers. The unit tests I ran pass: 22 in the network crate&#8217;s guest module, 2 in the web crate&#8217;s guest tests and 6 in the firewall rule tests. There is also a netlab lane for the guest network (the docs count 66 checks), a Wi-Fi lane on simulated radios and a Firefox test of the page. I didn&#8217;t run them.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Where it stands<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">It works in the lab: guests get internet and can&#8217;t reach anything else. The cap lands a little high. The page needs work, starting with the schedule status.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Next: a phone joining by QR on real hardware, and a schedule left running for a full day. The status card gets fixed first.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Patronus lives at <a href=\"https:\/\/patronus.errant.solutions\/\">patronus.errant.solutions<\/a>.<\/p>\n\n\n","protected":false},"excerpt":{"rendered":"<p>Full disclosure: I make Patronus, a router and firewall OS built on Gentoo. The guest network page is the newest thing I&#8217;ve added to it. It went into main on November 17 and isn&#8217;t in a tagged release yet. Every router says guests can&#8217;t reach your LAN. I wanted to check that claim, so on [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":932,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22,26],"tags":[374,423,174,207,375,386],"class_list":["post-917","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux","category-software-engineering","tag-firewall","tag-guest-network","tag-networking","tag-network-security","tag-nftables","tag-patronus"],"_links":{"self":[{"href":"https:\/\/blog.canutethegreat.com\/index.php\/wp-json\/wp\/v2\/posts\/917","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.canutethegreat.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.canutethegreat.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.canutethegreat.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.canutethegreat.com\/index.php\/wp-json\/wp\/v2\/comments?post=917"}],"version-history":[{"count":1,"href":"https:\/\/blog.canutethegreat.com\/index.php\/wp-json\/wp\/v2\/posts\/917\/revisions"}],"predecessor-version":[{"id":931,"href":"https:\/\/blog.canutethegreat.com\/index.php\/wp-json\/wp\/v2\/posts\/917\/revisions\/931"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.canutethegreat.com\/index.php\/wp-json\/wp\/v2\/media\/932"}],"wp:attachment":[{"href":"https:\/\/blog.canutethegreat.com\/index.php\/wp-json\/wp\/v2\/media?parent=917"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.canutethegreat.com\/index.php\/wp-json\/wp\/v2\/categories?post=917"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.canutethegreat.com\/index.php\/wp-json\/wp\/v2\/tags?post=917"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}