On Fri, Jan 13, 2017 at 4:08 AM, L. D. Pinney <ldpin...@yahoo.com> wrote:
> DAVE :
> WILL YOU PLEASE STOP YOUR FSCKin' CROSS POSTING ???
I did not start the cross-post in this case.
> This is UNRELATED to the OpenWrt / LEDE DEV mailing list...as the change has
> been merged.
Interop with routing protocols... and networking in general... does
exist outside of the openwrt universe. In my case I am deeply
concerned about what happens against older, deployed versions of
Linuxes (and other OSes) with the new multicast-unicast bridge
conversion code in lede. Babel tends to use it, and I am also testing
(in lede!), as per the below, the dhcpv6-pd code, interop-ing with
> F O
I'm really sorry that you hate cross posting so much. It must be
terrible to have to elide additional responses or deal with bounce
messages on every 20th email from me. And it must be wonderful to be
living in a world where all you have is openwrt/lede devices on the
network and modern kernels everywhere.
> On Friday, January 13, 2017 5:20 AM, Dave Taht <dave.t...@gmail.com> wrote:
> On Thu, Jan 12, 2017 at 1:01 PM, Baptiste Jonglez
> <bapti...@bitsofnetworks.org> wrote:
>> Here is yet another OpenWRT-related change for babeld: I just merged procd
>> support for babeld , after more than two years of lingering .
>> The only user-visible changes should be:
>> - babeld now logs to the system log (visible with "logread") instead of a
>> file in /var/log. This is nice for embedded devices, where you don't
>> want to write too much to the filesystem. It is still possible to
>> explicitly configure babeld to use a log file;
>> - babeld is now restarted automatically whenever it crashes;
>> - the usual procd niceties: calling "/etc/init.d/babeld reload" will
>> restart babeld only if the configuration has changed.
>> Please test babeld 1.8.0-2 and report any resulting breakage. I would
>> like this change (and the other compatibility change) to make it into the
>> upcoming LEDE release, which is due to happen quite soon.
> lede can dynamically insert/delete routes into tables from netifd
> babeld can pull routes from "protos" but not tables.
> I spoke with hedecker (? can't remember his email) about somehow
> having a field to export routes into kernel protos in the lede network
> file, he indicated he'd look at it in a few weeks.
> (I wanted to get away from ever having to revise the conf file
> dynamically, but it looks like not this release. Not having to restart
> babeld as per the above is a nice improvement though and I'll get on
> testing it this weekend. At the moment I'm going through some mild
> hell with dhcpv6-pd on comcast and adding "sonic" fiber (with a HE
> ipv6 tunnel. Will hopefully have 4 source specific gateways to play
> with here)
> In other other news the "rabeld" backport of the gentler route switch
> change loses kernel routes on the vyatta (3.10 based) OS in the
> edgerouter. :(. That said, haven't tested mainline babeld there yet.
> It seems to work on debian.
> For those fiddling with edgerouter's default 1.9.x OS, backports of
> cake, iproute, and rabeld are presently here:
>>  https://github.com/openwrt-routing/packages/pull/55
>>  https://github.com/openwrt-routing/packages/pull/250
>> Babel-users mailing list
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> Lede-dev mailing list
Let's go make home routers and wifi faster! With better software!
Lede-dev mailing list