Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] hacking on babel 1.8.3
Date: Thu, 4 Oct 2018 16:27:45 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1810041625350.4550@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw5-0YSsj-dxU_jbxFPJW6hG4d7n7M_Hk=KXnNjSv93oyw@mail.gmail.com>

On Wed, 3 Oct 2018, Dave Taht wrote:

> I've been trying to deploy the latest openwrt to all ~40 routers I
> have. (I did get a reprieve on having to close the lab, but I have to
> update the whole campus as part of it).

I managed to get Homenet working on 18.06.1. There is a conflict with some 
files so you have to do "opkg remove" on the dhcpv6 server, but after that 
it installs cleanly and seems to work. I installed it on two machines and 
they did all the homenet+hncp+babel things.

One thing I discovered is that I would like DHCPv6-PD lifetime capping, so 
I can control the source address selection of hosts. I had two different 
upstreams with PDs and one had much longer lifetime compared to the 
other. So hosts chose the one with the highest lifetime, which wasn't what 
I wanted.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

  parent reply	other threads:[~2018-10-04 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03 22:57 Dave Taht
2018-10-04  3:40 ` Dave Taht
2018-10-04 14:27 ` Mikael Abrahamsson [this message]
2018-10-04 14:33   ` Dave Taht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1810041625350.4550@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox