Re: [OpenWrt-Devel] batman-adv ipv6
There were no firewall changes for quite a while really and IPv6 configuration hasn't been touched for quite a while either and if you have ruled out the igmp_snooping as a source of error then thats a bit confusing. OpenWrt switched from using kernel-mode IPv6 RA handling (SLAAC) to handling RAs in userspace some time after the AA release that means you need to have a proto=dhcpv6 interface section in /etc/config/network for using IPv6 SLAAC (in forwarding mode) as is done in the default configuration of OpenWrt. Alternatively you might set the sysctl value to accept RAs in forwarding mode but this is greatly discouraged and might cause some issues with other parts of OpenWrt. Cheers, Steven ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] dnsmasq: Makefile fixes and cleanups
NAK, unless you deal with all the dnsmasq-dhcpv6 and dnsmasq-full missing in opkg tickets afterwards ;) On a more serious note, some people depend on the precompiled stuff and they would probably not welcome that change all too much. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] dnsmasq: Makefile fixes and cleanups
Am 21.12.2014 um 14:21 schrieb Steven Barth: NAK, unless you deal with all the dnsmasq-dhcpv6 and dnsmasq-full missing in opkg tickets afterwards ;) Following this argumentation, you can never change anything. I'm confused. Can we please come to a clear decision which way to go !? Package variants or configurable package ? My initial suggestion aimed at the first direction. But then commit a2558749e8 has been accepted which goes the other direction. Again, I'm fine with both approaches (I just don't think we should mix them). In any case, trunk needs to be fixed. Regards, Frank ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] 3.18 kernel timing? (Was Re: Moving to 3.17.x kernel?)
On December 20, 2014 at 1:04:05 PM, Rafał Miłecki (zaj...@gmail.com) wrote:
Don't top post.
On 20 December 2014 at 18:58, Marc Nicholas m...@wimoto.com wrote:
Well, there-in lies the problem: AR71xx doesn’t have any patches for 3.14
kernel right now.
I’m trying to build it, though.
You can be the one to add them.
cp -R patches-3.14 patches-3.18
make target/linux/{clean,prepare} V=s QUILT=1
http://wiki.openwrt.org/doc/devel/patches#adding_or_editing_kernel_patches
Okay, spent a couple of hours working through patching a 3.18 kernel. Went
reasonably well ;)
Aside from quite a few particular router support patches (which I’m not overly
concerned about), there were some failures in Flash, PHY, SPI and USB support
for the AR71xx platform.
Before I dig in and analyse some more, any pointers on why the following might
fail, or how to triage? Is there a possibility some now exist in the mainline
kernel?
Thx.
-m
406-mtd-m25p80-allow-to-specify-max-read-size.patch
407-mtd-m25p80-allow-to-pass-probe-types-via-platform-data.patch
425-net-phy-at803x-allow-to-configure-via-pdata.patch
430-drivers-link-spi-before-mtd.patch
432-spi-rb4xx-spi-driver.patch
433-spi-rb4xx-cpld-driver.patch
462-mtd-m25p80-set-spi-transfer-type.patch
464-spi-ath79-fix-fast-flash-read.patch
490-usb-ehci-add-quirks-for-qca-socs.patch
605-MIPS-ath79-db120-fixes.patch
610-MIPS-ath79-openwrt-machines.patch
616-MIPS-ath79-ubnt-xw.patch
902-unaligned_access_hacks.patch
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
