Re: [homenet] wifi broadcast domain - Mikael Abrahamsson's comments

2019-04-07 Thread Tore Anderson
* Juliusz Chroboczek >> If there is a more complex HNCP network, then we could probably simulate >> the L2 scenario with VXLAN, configured by HNCP. > > If memory serves, VXLAN requires support for multicast, which HNCP+Babel > doesn't provide. There's a set of IBM (?) extensions to VXLAN that av

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

2016-04-26 Thread Tore Anderson
* Rich Brown > (And I may take Tore up on his offer to push a feed of the newer > packages to Github...) I had some time to kill today, so here you go. Let me know if you find it useful. https://github.com/toreanderson/openwrt-feed You're probably better off taking Markus's advice and staying w

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

2016-04-25 Thread Tore Anderson
* Rich Brown > I'm new to this list, but have been using CeroWrt and OpenWrt for > several years. Welcome! > Earlier in this thread there was a mention about hnetd being well > integrated into the OpenWrt ecosystem. Before I try installing hnetd, > I would like to know: > > 1) What are the curr

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

2016-04-21 Thread Tore Anderson
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 overa

Re: [homenet] New Version Notification for draft-barth-homenet-wifi-roaming-00.txt

2015-11-30 Thread Tore Anderson
* Steven Barth > here is some attempt to formalize a simple WiFi roaming approach > using host routes and a stateless proxy for DAD NDP messages. > > It's a bit theoretical right now but may be useful as a start for a > discussion. We could do a talk on it in Yokohama as well. Hi Steven and tha

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

2015-10-21 Thread Tore Anderson
* Dave Taht > is it up from 8? Depends. Am I one of the 8? In any case, this might be of help to whoever wants to be #9: http://blog.toreanderson.no/2015/10/11/making-a-homenet-router-out-of-openwrt.html Tore ___ homenet mailing list homenet@ietf.o

Re: [homenet] Host naming in Homenet

2015-09-09 Thread Tore Anderson
Hi Steven, * Steven Barth > Am 05.09.2015 um 12:24 schrieb Tore Anderson: > > What I am starting to suspect is that OpenWrt's «IPv6 ULA-Prefix» > > setting is orthogonal to the Homenet handling of the interfaces, and > > that in order to get the full/correct «Ho

Re: [homenet] Host naming in Homenet

2015-09-05 Thread Tore Anderson
* Juliusz Chroboczek > > BTW - this reminded me that I also noticed that after rebooting a > > router, another ULA prefix (*not* the one configured in OpenWrt on > > either router) also showed up and links were numbered using it, but it > > vanished again after a while. No idea where it came from.

Re: [homenet] Host naming in Homenet

2015-08-31 Thread Tore Anderson
* Markus Stenberg > Instead, it sounds like potentially issue with IPv4 + dnsmasq (e.g. > option that prevents RFC1918 replies from being forwarded), I hope > you are not using legacy IP :) I left everything at defaults, so my links were indeed numbered using IPv4 (RFC1918, 10/8), as well as IPv

Re: [homenet] Host naming in Homenet

2015-08-31 Thread Tore Anderson
Hi, Jumping in here with the perpective of a «dumb user» who spent the weekend playing with the Homenet implementation in OpenWrt 15.05... (Note that I don't know whether my comments pertain to the Homenet standards themselves or are specific to the OpenWrt implementation.) * Markus Stenberg >

Re: [homenet] Moving forward.

2015-08-11 Thread Tore Anderson
* Sander Steffann > > Op 10 aug. 2015, om 10:23 heeft Erik Kline het > > volgende geschreven: > > > >> Whilst not wanting to de-rail any effort to standardise Babel > >> (since I firmly believe it should be standardised), I'd like to > >> hear the WG's view on having part of our Homenet stack b

Re: [homenet] HNCP, RA and DHCPv4

2015-08-02 Thread Tore Anderson
* Juliusz Chroboczek > > After that you can also include the PIO with PL=VL=0 in the periodic > > RAs (that you'll presumably be transmitting anyway) > > How many PIOs will fit? Is the 1280 octet minimal MTU the only > limitation? I don't think there's any practical limit, considering that you

Re: [homenet] HNCP, RA and DHCPv4

2015-07-31 Thread Tore Anderson
* Steven Barth > >If a new host is connecting to the network while you're advertising > >the max(old valid lft, 2h) valid lifetime, it will actually > >auto-configure itself with an address from the withdrawn prefix. If > >you set valid lifetime to 0, it won't. > > Sounds good, i don't mind. Just

Re: [homenet] HNCP, RA and DHCPv4

2015-07-31 Thread Tore Anderson
* Steven Barth > In an ungraceful case (flash renumbering) we stop announcing the prefix in > HNCP and the individual routers who have assigned it, MUST deprecate it > according to RFC 7084 (not just stop announcing it in RAs). This deprecation > sets preferred lifetime to 0 and valid lifetime to

Re: [homenet] Moving forward.

2015-07-27 Thread Tore Anderson
* "Hemant Singh (shemant)" > (c) An average home has one wifi link. I think you'll find that an "average" home has more than 1 wifi link. Maybe somewhere between 1 and 2 is the correct number. For example: The concrete between the two floors in my apartment makes an AP located upstairs practica