Exactly, so, it seems necessary to get a list of those packages.
Also, your responses didn't address the IPv6 issue, I really need some assistance in identify the missing package for that too. I would assume this should be considered a Firmware Selector bug.
I'm sure you can understand how this will cause an issue with users.
Should I just opkg list-installed and compare?
The ipv6 problem might be related to the luci-proto-ipv6 package. But it might also need another missing package, I suggest comparing manifest files between the default and custom build and finding something ipv6 related.
You can find the .manifest file in the same dir as the builds, for example: https://downloads.openwrt.org/releases/23.05.0-rc1/targets/ipq40xx/generic/openwrt-23.05.0-rc1-ipq40xx-generic.manifest
I guess you're missing me. as you're still focused on LuCI packages. I have no IPv6 connectivity with images from the firmware selector, period. This is regardless of if I install LuCI or not.
Thanks!!!
Is there a manifest for this?
https://downloads.openwrt.org/releases/23.05.0-rc1/targets/ramips/mt7621/
Look at the bottom of the page.
the manifest file is the same for all builds on the same target,
I am using a slightly different config, will this be subject to the same bug?
Your config as listed in the defect report is to have one bridge with VLAN filtering.
I have set up my system with separate bridges for each VLAN (since that's what I had to do pre-DSA, I didn't even think to try the VLAN filtering with one bridge).
my config is like this:
config device
option type 'bridge'
option name 'br-iot'
option bridge_empty '1'
list ports 'lan1.3'
list ports 'lan4.3'
list ports 'wan.3'
config device
option name 'br-lan'
option type 'bridge'
option bridge_empty '1'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
list ports 'wan'
config device
option type 'bridge'
option name 'br-guest'
option bridge_empty '1'
list ports 'lan1.5'
list ports 'lan4.5'
list ports 'wan.5'
(LAN uses untagged traffic via the trunk to the network switch; other networks use VLAN tags on the trunk)
I thought GPIOs would run 5v on most boards
I've tried various different configs and there's been only one that kinda works (with the bugs), all others aren't working at all. You'll most likely lose the config and need to re-setup, it could even be mandatory to re-setup, so expect spending some time there aswell.
Indeed...I ran an experiment to force a roam from another AP to the MR8300-based AP, and it goes half-deaf for about 5 minutes, even with my (weird) separate bridge per VLAN configuration
Any reported issues from anyone updating a WRT3200ACM on OpenWrt 22.03.2 to 23.05.0-rc1 - I've not noticed anything in the forum after doing a search of this post. But thought i would ask just to be safe, encase i overlooked something.
Using RC1 on an Omega2S+. So far so good! Thanks everyone.
config dnsmasq
option domainneeded '1'
option localise_queries '1'
option local '/lan/'
option domain 'lan'
option expandhosts '1'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option localservice '1'
option ednspacket_max '1232'
list server '127.0.0.1#5053'
option cachesize '500'
option port '53'
option doh_backup_noresolv '-1'
option noresolv '1'
list doh_backup_server '127.0.0.1#5053'
option rebind_protection '1'
option rebind_localhost '1'
list rebind_domain 'some.domain'
option nonwildcard '0'
config dhcp 'lan'
option interface 'lan'
option start '98'
option limit '150'
option leasetime '24h'
option dhcpv4 'server'
option dhcpv6 'server'
option ra 'server'
list ra_flags 'managed-config'
option dns_service '0'
config dhcp 'wan'
option interface 'wan'
option ignore '1'
config odhcpd 'odhcpd'
option maindhcp '0'
option leasefile '/tmp/hosts/odhcpd'
option leasetrigger '/usr/sbin/odhcpd-update'
option loglevel '4'
config srvhost
option srv '_vlmcs._tcp'
option target 'OpenWrt'
option port '1688'
option class '0'
option weight '100'
config dhcp 'Modem'
option interface 'Modem'
option ignore '1'
option start '100'
option limit '150'
option leasetime '12h'
list ra_flags 'none'
config dhcp 'Guest'
option interface 'Guest'
option start '100'
option limit '150'
option leasetime '12h'
config dhcp 'LANex'
option interface 'LANex'
option start '100'
option limit '150'
option leasetime '12h'
I have several static host config in dhcp, omitted as I do not think they are related.
command -v awk
/usr/bin/awk
No individual awk package installed, it is a link to busybox.
Btw, I used dnsmaq-full, encountered this issue and recompiled with standard dnsmasq in menuconfig, result was the same. dnsmasq failed to start, no dhcp, no dns.
OK, you were calculating GPIO @ 5V - gotcha. I was referencing the whole power consumption as seen on the meter (the router is hence 12 V device - thers no way to measure amperage from the GPIOs without destroying the LEDs). Cool beans.
I used the manifest list to make an image, but I still had no IPv6. The DHCP screen also still had issues. So I just did a factory reset and re-configured my entire device from scratch.
Despite me copying/pasting nearly every config file, I cannot see where the problem config could have been located.
Anyways thanks, I'm now up and running here now.
1 observation:
option ra_slaac '1' to be deleted from an interface.Here's an example, editing 192.168.1.1 to 192.168.1.2:
Workaround: I made those configs thru SSH
ra_slacc should default to 1, if so then that's not a problem
Odd, I wonder why the developers added it to the default DHCP config then - just for it to be removed on the first interface edit.
Cool beans!
it's one of those inconsistencies between Openwrt core and the luci repository that are the lowest priority to fix haha
I always just add luci to the firmware selector. I've checked and I have all of the packages you listed (apart from luci-ssl that I don't need as luci also comes with SSL). As a relative OpenWrt newbie I must be missing something (it doesn't seem to be packages though 
)
I don't understand, I've read your previous posts, you don't seem to have a problem beyond what already has been explained.
I just wanted to confirm for everyone if only adding luci to the firmware selector is correct and there's no need to add those packages like it was suggested on your previous post, otherwise people who are not that familiar with it (myself included) may start to routinely add them unnecessarily. It may be different for luci-ssl, I've never tried it.
Thanks. How about the lan section from /etc/config/network?
uci show network.lan
ifstatus lan