It seems inconsistent that the lan interface gets a physical interface through ifname, but Guest gets one indirectly through an entry in a wifi interface definition.
Can someone explain why?
That's right, no ethernet for Guest.
Your question does reveal I don't actually understand where would Guest get internet from.
My internet actually comes from a wireless AP:
I think I get it now. I had assumed that bridging is necessary to get the internet from my wan to my lan.
But now I think bridging two interfaces together identically mirrors the traffic on each. So a wan/wwan + lan bridge is undesirable because then my local traffic gets blasted out.
Instead, it seems that when my router gets a packet on lan that's destined for some external public IP it actually just routes it there. Why? Because there's a default route that will match it, and because there's no firewall rule forbidding it.
The left column called "Zone => Forwardings" indicates that Guest -> wan routing is allowed. That's the key.
I know you understand all this already, I'm mostly writing this up to help myself understand and maybe get corrected if I say something wrong.
Bridging is a bit like routing/forwarding, in that packets from one interface end up going to another, but this happens indiscriminately.
OT: This is all pretty cool, and I wish I knew of a way to learn all this systematically but at a light/moderate level of depth.
I don't want a PhD in networking, I first want a high school level course. @lleachii, could you perhaps suggest something?