Re: [homenet] How many people have installed the homenet code?

[Tore Anderson <[e-mail]>]

Hello,

* Tim Coote

> > Even if you're just testing plain babeld, even without hnetd, you
> > must kill network manager.  If you don't, thinkgs may appear to
> > work at first, but NM will take revenge later.  

> I hated NM. But I think that it’s getting better. It does provide an
> initial overall visualisation of what’s going on. Something will be
> required to show the overall picture across all digital entities
> involved in a system, including ‘phones with both wifi and LTE
> connections. For the consumer there needs to be at least a green/red
> light (cf a CD pipeline status), but finer granularity would also
> have value.  I would hope to encourage the NM community to at least
> take cognisance of the Homenet protocols.

NM is being very actively developed, and in my experience its
developers are generally very receptive to bug reports and other
requests. So I'd encourage anyone who have issues with NM to join the
IRC channel and/or reports bugs - chances are they get fixed quickly.

As it happens, NM version 1.2 vas released yesterday. One of the things
that has been improved is NM's ability to stay away from interfaces
that's being managed by something else, so maybe an upgrade would be
enough to fix Juliusz's problems. If not, try adding the following to
NetworkManager.conf:

[main]
no-auto-default=*

Another thing IPv6 folks might be interested in knowing is that it now
defaults to using RFC7217 IID generation instead of EUI-64.

> Maybe I need to create a separate openwrt vm if I cannot run the
> hnetd stack on a more complete distro.

An quicker and more lightweight solution is to isolate hnet inside a
network namespace:

ip netns add hnet-playground
ip link set dev eth1 netns hnet-playground
ip netns exec hnet-playground shncpd --start --if eth1 # or whatever
ip netns exec hnet-playground /bin/bash
# [...do stuff inside the hnet playground here...]

Tore