[mesh-dev] May be late for sunday mesh stuff

[max b]

Awesome thanks a bunch Marc! I'm gonna pick up Martin a little after noon
and then we'll swing by sudo. If anyone else is out there and wants to
pitch in, come by or give us an email/ring!

On Sun, May 24, 2015 at 5:04 AM, Marc Juul <juul at labitat.dk> wrote:

> It's 5 am and I'm just about to sleep
>
> I've been tweaking sudowrt-firmware and makenode and I now have a working
> setup with a tp-link wdr3500 running the home node firmware and a bullet m2
> running the extender node firmware that are talking to each other with
> notdhcp correctly without any manual configration after flashing.
>
>
> I took the liberty of adding max's ssh pub key (same one as sudoroom.org)
> to the extender node firmware since there's really no other way to get into
> it during development. Alex feel free to add your own as well.
>
> The home nodes have a "for development only" IP of 172.22.0.1 and the
> extender nodes have 172.22.0.2
>
> SO! Just some notdhcp hook script wrangling left and then I'll get the new
> web gui finalized enough that it can replace the luci gui, and maybe
> someone can package it into sudowrt-packages? Then that's it! Ready to go
> for a usable 0.2.
>
> Oh btw, I was wondering how we should parcel up the eternet port. Here's
> one option:
>
> Port 0: The mesh
> Port 1: The private network
> Port 2: An extender node
> Port 3: An extender node
>
> Or we could do port 0 and 1 on the mesh both? Whaddaya think? We can make
> them dymanically switchable from the web gui in next version.
>
> --
> marc/juul
>
>
>
> _______________________________________________
> mesh-dev mailing list
> mesh-dev at lists.sudoroom.org
> https://sudoroom.org/lists/listinfo/mesh-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://sudoroom.org/lists/private/mesh-dev/attachments/20150524/8d978603/attachment.html>