[Ndr] Winding down first rev

Tue Nov 21 21:07:55 EST 2017

Jason,

Sorry for the delay in response. I have a new job and I have been traveling
just a little bit.

Everything is done on my end. I have the configurations done and I've been
able to simplify the logic substantially. Everything has been upgraded and
set up. The equipment that Coresite data centers donated turned out to be
quite flexible with what wasn't limited by the lack of cisco proprietary
controller. There are some functionality problems that don't make them
perfect, but they are fine.

However. I have come to the conclusion that shipping cost is a major
factor. The equipment weighs a lot. This is the primary reason why I
haven't shipped anything yet. Dominica suggested that we instead provide
them with wireless bridging equipment that they could distribute signals
across the neighborhood. This is a more cost effective approach including
being lighter. The ubiquiti solution tht Nick used in St. John seems to be
the right one in my mind.

I am ready to send gear. The question is which? To be honest, I'd rather
donate enough equipment to give Craig and team the wireless distribution
they seek. It would be lighter and easy to handle. That option would take
me another week to two. Then shipped. Option 1, the cisco gear would take
the same, but do to the cost constraints I'd be concerned with how much
equipment would be sent.

I also have configured a bunch of Raspberry Pi's to provide different low
pressure functionality. They are perfectly find in the current environment
as caching name servers. I can send those immediately as they are extremely
light.

The only outstanding question I have is about power. If CW can provide an
ethernet connection that will allow for DHCP to work, we are in business.
That leaves power and the question there is if it is adequate enough?

What would you like me to do at this point? If you want to talk live, let's
put some time aside tomorrow afternoon. You are aware that Thursday is a
major US holiday? I could speak with you on Friday if that is better.

I have to tell you that I have learned quite a bit from this experience. I
am going to document it and hopefully if this happens again, the enthusiasm
can be turned into action much quicker. The shipping and access piece seems
to the the major blocker, and not only cost. I hope that whatever we send
gets stored for future emergencies and can be replicated for others to do
the same.

Thanks for all your help!!!

Best,

Martin

On Fri, Nov 17, 2017 at 10:29 AM, Jason Hynds <jason.hynds at partsinc.biz>
wrote:

> Dear Martin and Group,
>
> Thanks so much for this great job that you are doing!
>
>
> In Barbados we are willing and eager to receive the kit for Dominica for
> further transshipment it via our military's relief shipments channel.
>
>    1. We have already managed to use to same channel to get essential
>    supplies directly to our ISOC Dominica counterparts. Thus, it is a tested
>    and working channel. Our Dominican counterparts are looking forward to
>    receiving the kit. They still have IP communications challenges that it may
>    help them improve upon.
>    2. We are concerned that the relief shipment window is not necessarily
>    indefinite, so we would like to use it whilst we can.
>
>
> Is there a way that we may assist more from Barbados?
>
>    1. I think we are nearly in a state where we can perform some systems
>    administration and distribution of some of these kits as well, if they were
>    in Barbados.
>    2. If everything is preceding normally we also wanted to reach out to
>    Tortola to find persons we could deploy a kit. We need to know what is
>    possible before we attempt cold contact with the persons from Tortola.
>
> ----
>
> I've cc'ed my ISOC Barbados working group which is assisting with this
> project on the local end and helping to keep me organised.
>
>
>
> *Have a great day! *
>
>
> *CC:* ISOC BB - Disaster Management Working Group
>
>
> Regards,
>
> Jason Hynds
>
> On 10/15/2017 11:46 AM, Martin Hannigan wrote:
>
>
>
> I also built a RPi with a recursive name server and piggybacking a RIPE
> atlas probe. That gives us a remote access platform and
> measurements/up/down. We can lock the name server to the local ISP
> allocations I suppose.
>
> The last question I have is: Does CW have a working port with DHCP
> anywhere in Dominica?
>
>
>
> On Sun, Oct 15, 2017 at 11:43 AM, Martin Hannigan <hannigan at gmail.com>
> wrote:
>
>>
>> Chris,
>>
>> Here's the config. I'm working on buttoning down the edge router now. I
>> have the everything running from an ethernet port on my home internest
>> service with a DHCP address from my provider.
>>
>> I have all three radios connected and reachable. Looks like the lack of
>> server disable some functionality, but the rest is there. I couldn't figure
>> out manual channel seperation. Of note, the AP's themselves will QoS
>> connections. Maybe simpler to limit their and replace the edgemax with
>> something much dumber and cheaper.
>>
>> I think we leave it "open" on shipping. This is not fancy by any means,
>> and I'm wondering how much more we really need.
>>
>> !
>> !
>> username Cisco password 7 062506324F41
>> !
>> !
>> bridge irb
>> !
>> !
>> !
>> interface Dot11Radio0
>>  no ip address
>>  !
>>  ssid LIFELINE
>>  !
>>  antenna gain 0
>>  station-role root
>>  bridge-group 1
>>  bridge-group 1 subscriber-loop-control
>>  bridge-group 1 spanning-disabled
>>  bridge-group 1 block-unknown-source
>>  no bridge-group 1 source-learning
>>  no bridge-group 1 unicast-flooding
>> !
>> interface GigabitEthernet0
>>  no ip address
>>  duplex auto
>>  speed auto
>>  bridge-group 1
>>  bridge-group 1 spanning-disabled
>>  no bridge-group 1 source-learning
>> !
>> interface BVI1
>>  mac-address 649e.f38e.f718
>>  ip address dhcp client-id GigabitEthernet0
>>  ipv6 address dhcp
>>  ipv6 address autoconfig
>>  ipv6 enable
>> !
>> ip forward-protocol nd
>> ip http server
>> no ip http secure-server
>> ip http help-path http://www.cisco.com/warp/publ
>> ic/779/smbiz/prodconfig/help/eag
>> !
>> !
>> bridge 1 route ip
>> !
>> !
>> !
>> line con 0
>> line vty 0 4
>>  login local
>>  transport input all
>> !
>> end
>>
>>
>>
>>
>>
>>
>>
> _______________________________________________
> ndr mailing listndr at puck.nether.nethttps://puck.nether.net/mailman/listinfo/ndr
>
> --
>
> _______________________________________________
> ndr mailing list
> ndr at puck.nether.net
> https://puck.nether.net/mailman/listinfo/ndr
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/ndr/attachments/20171121/86d37659/attachment.html>