Internet for the router itself is missing
and therefore Opkg not working. So even though I have the guide to regenerate a certificate, I cannot proceed as it needs additional packages. I have a feeling I am close to figuring this out and only one elusive setting remains. Take note clients that connect to the dumb AP have internet. It's only the Internet for the routers needs are not working
By default the uhttpd listens to all addresses (0.0.0.0/0). Also https is not enabled by default and there are no certificates.
It is mentioned in a couple of places in the guide that you need to configure the gateway and dns.
Step 3 says "Set DNS and gateway to point into your main router to enable internet access for the dumb AP itself "
Apparently it doesn't listen to all. Co'z when I added 192.168.1.2 in the uhttpd config it became accessible. Though I know that the 0.0.0.0 is supposed to signify that is should listen to all addresses.
The only thing not working is https and found in the guide in cert regeneration that it needs IP address.
I have read the Dumb AP guide. I know that you need to do stuff related DNS and DHCP.
Don't get me wrong, I mean I may have misunderstood the guide but definitely I have read it.
I actually decided to make a case here in the forum since there are more than a couple of unresolved cases with similar problem like this:
There are options "commonname" and "realm" in UHTTPD config file. "Commonname" is currently commented out in my config file out of the box. At any rate noted on the hostnames in LuCI will check if that will work.
Sorry if you were lost ... I meant In LuCI->Interfaces -> LAN there is "ignore interface" when there is a need to disable to service itself.
Anyway, I have a much bigger issue now. The Dumb AP guide mentions to disable Firewall, dnsmasq and DHCP services in Dumb router as options available for lazy guys like me. I re-enabled dnsmasq and DHCP and just disabled certain components as per the DumbAP guide. I am assuming that option was listed as because some parts of dnsmasq and DHCP will be needed if you plan to setup guest wifi in your DumbAP as per guide https://openwrt.org/docs/guide-user/network/wifi/guestwifi/guestwifi_dumbap.
I learnt this the hard way when I connected to my guest wifi it didn't get an IP address.
Now I have IP address expected 10.0.1.x but I don't have Internet. I have a feeling this is a firewall issue. I have two concerns about the firewall config. In the DumbAP guide requested to simply disabling of firewall and no other limited disabling listed. So i'm puzzled how the firewall rules as described in the guestwifi_dumbap guide will run if the FW is disabled.
The dumbAP and the guestwifi_dumbAP follow different approaches and you cannot combine them.
One is disabling the firewall, the other depends on the firewall.
One doesn't use dhcp, the other is using it.
So if you need a guest wifi on a dumbAP, you need to start configuring from defaults using the guest wifi guide, not trying to combine them.
I have one follow up question. Since the router in question is dumb and have Guest wifi set up. My main router also has Guest wifi. Both had SQM configured 5 mbps down and 2 mbps up. My question is, given this set up does this mean the guests can gobble up up to 10 mbps of my internet bandwidth if they use both wifis? Or it will only access 5 mbps?
The commands you gave in your last reply is to be done on the dumbAP?
you should add your hostname into hosts in order to be available to resolutions
if you add it using luci will be like doing:
uci add dhcp domain
uci set dhcp.@domain[-1].name='openwrt'
uci set dhcp.@domain[-1].ip='192.168.1.1'
you could try also:
uci set dhcp.@domain[-1].name='openwrt.lan'
but I think that expandhosts adds .lan , if I remember it well its, so you should check:
uci show dhcp | grep dnsmasq
those are the defaults I think, check it out on: https://openwrt.org/docs/guide-user/base-system/dhcp
Also in your first reply (see below) to me you gave me a link to a scripts you have shared is this still applicable? If yes, the dumb-ap-wired-link.sh is for the dumbAPs then the wireless-link-wds.sh is commands for the main router?