Re: [OpenWrt-Devel] batman-adv ipv6

2014-12-21 Thread Steven Barth
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

Re: [OpenWrt-Devel] batman-adv ipv6

2014-12-20 Thread Lars Boegild Thomsen
On Saturday, December 20, 2014 11:46:47 Alexander Couzens wrote: > maybe this is related to #17625 https://dev.openwrt.org/ticket/17625 ? > (destination mac address of IPv6 neighbour solicitation changed from multi- > to unicast (IPv6 partly broken)) I thought so for a while but apparently not.

Re: [OpenWrt-Devel] batman-adv ipv6

2014-12-20 Thread Alexander Couzens
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, maybe this is related to #17625 https://dev.openwrt.org/ticket/17625 ? (destination mac address of IPv6 neighbour solicitation changed from multi- to unicast (IPv6 partly broken)) Best, lynxis - -- Alexander Couzens mail: lyn...@fe80.eu jab

[OpenWrt-Devel] batman-adv ipv6

2014-12-19 Thread Lars Boegild Thomsen
For a while I have been running a batman-adv mesh as my "backbone". Configuration is pretty straight forward - my "lan" interface is simply an ethernet interface, a wifi access point and the bat0 interface bridged together. This was working flawlessly until about a month ago when IPv6 auto co