Guest Wi-Fi using LuCI

Please note: Guest Wi-Fi using LuCI
Tutorial is dated Last modified: 2023/03/05 17:00 by openwrt
However
The tutorial is based off OpenWRT "Breaker" (2017?) so not at all applicable to any recent OpenWRT/LuCI releases.

To avoid confusion/wasting time of new users,
May want to edit so that the page is just blank.

Cheers

1 Like

The screenshots are certainly old, but can you point out where there are inconsistencies that are more than just cosmetic? That will help speed up the corrections.

1 Like

I would add my support for @anon72830772 's post for those of us who are not well versed in OpenWRT.
Maybe it was just the screenshots compared to latest Luci but I found the whole thing confusing and from memory ended up using more this "tutorial" https://openwrt.org/docs/guide-user/network/wifi/guestwifi/guestwifi_dumbap which I had used a few weeks before in my first foray into using OpenWRT.

By comparison I found those directions very easy to follow although it may well be likely that I now have some misconfiguration in my more recent main router guest wifi config.........

Certainly confusing and needs a facelift, but FWIW, it’s still accurate IMO.

You will end up with same result using https://openwrt.org/docs/guide-user/network/wifi/guestwifi/configuration_command_line_interface script.

Why not update the page. Might as well be you.

That would be the blind leading the blind.
The idea is to encourage new users not discourage them! :smile:

Other than updating the screenshots so a new user isn't confused with trying to translate UI changes I don't see an issue.

Usually I manually create a bridge for my guest wifi if I'm not also doing the single bridge multiple vlans method? At least I've run into troubles if I don't create the bridge manually first?

Maybe there needs to be some changes on how the netmask is discussed when creating an interface.

Anyway. It should be relatively straightforward to fix. I might just copy the screenshots/additional instructions from how I said to make a separate SSID on separate bridge. Only addition is to make sure forwarding works as that didn't matter in the below example.

1 Like

At least come forward with luci skin "new users" are using.
Can you explin in deep detail what changed in lstvyear that invalidates that wiki page. Something more than your invented qpi.

Then heed your words.

An open wiki is a collaborative effort towards constant content improvement, not something that should be assigned to others, nor to suggest viable content be removed simply because it fails to suit your cosmetic sensibilities. If you’re not willing to expend the effort, don’t blame the messenger.

1 Like

I wish I had found that or realised it was just copy and paste :slightly_smiling_face:

However even there in Step 2 what does this mean ?

twhich should typically match @wifi-iface[0] or @wifi-iface[1]

I can only guess this is shorthand for wireless interface?

Have a look at

uci show wireless

on your device?

Depends on what it's called?
You're indexing the first wifi-iface and then getting the device from that..

root@OpenWrt-RT3200:~# WIFI_DEV="$(uci -q get wireless.@wifi-iface[0].device)"
root@OpenWrt-RT3200:~# echo $WIFI_DEV
radio0
root@OpenWrt-RT3200:~# 

Note mine are now called "default_radio0" and "default_radio1"

For example on my RT3200:

root@OpenWrt-RT3200:~# uci show wireless
wireless.radio0=wifi-device
wireless.radio0.type='mac80211'
wireless.radio0.path='platform/18000000.wmac'
wireless.radio0.channel='auto'
wireless.radio0.channels='1,5,9,13'
wireless.radio0.band='2g'
wireless.radio0.htmode='HT20'
wireless.radio0.country='AU'
wireless.radio0.cell_density='0'
wireless.default_radio0=wifi-iface
wireless.default_radio0.device='radio0'
wireless.default_radio0.network='leglan'
wireless.default_radio0.mode='ap'
wireless.default_radio0.ssid='ssid'
wireless.default_radio0.encryption='psk2'
wireless.default_radio0.key='key'
wireless.default_radio0.ieee80211r='1'
wireless.default_radio0.ft_over_ds='0'
wireless.default_radio0.ft_psk_generate_local='1'
wireless.default_radio0.ieee80211k='1'
wireless.default_radio0.bss_transition='1'
wireless.radio1=wifi-device
wireless.radio1.type='mac80211'
wireless.radio1.path='1a143000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0'
wireless.radio1.channel='60'
wireless.radio1.channels='36, 44, 52, 60, 100, 108, 132, 140, 149, 157'
wireless.radio1.band='5g'
wireless.radio1.htmode='HE40'
wireless.radio1.country='AU'
wireless.radio1.cell_density='1'
wireless.radio1.txpower='14'
wireless.default_radio1=wifi-iface
wireless.default_radio1.device='radio1'
wireless.default_radio1.network='leglan'
wireless.default_radio1.mode='ap'
wireless.default_radio1.ssid='ssid'
wireless.default_radio1.encryption='psk2'
wireless.default_radio1.key='key'
wireless.default_radio1.ieee80211r='1'
wireless.default_radio1.ft_over_ds='0'
wireless.default_radio1.ft_psk_generate_local='1'
wireless.default_radio1.ieee80211k='1'
wireless.default_radio1.bss_transition='1'
root@OpenWrt-RT3200:~# 

This is not mentioned in the original tutorial mentioned by @anon72830772 which was one point of confusion for me - as it is in the guest wifi for dumb ap and after reviewing @RuralRoots post above appears to be in the CLI script.

@psherman not sure if this is what you call an inconsistency. As it is in the CLI script (unless I read it incorrectly) is it considered preferential to do it that way if not adding other complexities?

Yes as are mine - on 3 different devices but I am guessing it is more based on OpenWRT version than the hardware as one of those was a 6 year old router but with version 23.x on.

I forget what it's like on the earlier openwrt versions.....

But the indexing just means select the first or "zeroeth" as we're counting from zero of all the wifi-iface. So the names don't matter.

You're ASSuming that I already have familiarity of the procedure via LuCI. :roll_eyes:

Not assuming anything other than what I see in your profile which to my eyes is as a respected and viable contributor to the cause that I felt could contribute to this topic.

1 Like

The guide was updated. It should be clear enough now.

4 Likes

Thanks. This is now much clearer to me and hopefully others in the future.

It also seems to answer my question about creating the bridge. :+1:

A post was split to a new topic: Setting up a bridged ap with multiple networks