pmelange
pmelange
Please re-open this issue (i don't have permission). It is still a problem with the latest snapshot. The device I am using is an Arch C7 V4. Snapshot image r11037-1979af10ca...
aside from the command-line iptables/ip6tables, do we also need to keep an eye open for all packages which depend on kmod-ipt.*?
I ran into this problem today on a Linksys WRT1900ACS which has an uptime of 248 days running ``` ~# cat /etc/openwrt_release DISTRIB_ID='OpenWrt' DISTRIB_RELEASE='21.02.0' DISTRIB_REVISION='r16279-5cc0535800' DISTRIB_TARGET='mvebu/cortexa9' DISTRIB_ARCH='arm_cortex-a9_vfpv3-d16' DISTRIB_DESCRIPTION='OpenWrt 21.02.0 r16279-5cc0535800'...
It also depends on what type of broker selection is being used. I use 'usage' based. With 'usage' and 'random' , I think it would make more sense to balance...
The wikipedia link for "SRV record" is https://en.wikipedia.org/wiki/SRV_record
I have recently modified the Freifunk tunneldigger init and hotplug scripts to be able to use SRV records. The changes can be seen here https://github.com/Freifunk-Spalter/packages/commit/29943b0d10ac3e04322dbe222e0c6453a37b49e3 Instead of having tunneldigger itself...
I have gone ahead with option 2. You can see how we are doing this at freifunk-berlin https://github.com/freifunk-berlin/firmware-packages/pull/154/commits/405a58245d9091eefb627ebf2b20edfdc16e18c2
I meant changing it from an error to a warning. But if you think error is better, than keep it that way. It seems to be working fine with the...
https://github.com/freifunk-berlin/firmware-packages/blob/5e5e75f82a9c0f389a55b4446bfc8c252a752bba/addons/freifunk-berlin-bbbdigger/files/postinst.sh#L65 changing the line to ```uci -q add ...``` doesn't change the output. I think it would be a bad idea to redirect the output to null just in case...