next steps

Dave Taht dave.taht at gmail.com
Mon Mar 19 20:14:15 UTC 2012


On Mon, Mar 19, 2012 at 1:48 AM, Francis Dupont <fdupont at isc.org> wrote:
>> (in other words: hit reload on
>> http://huchra.bufferbloat.net/~d/sdcpe-demo-doc/shownet.png
>> )
>
> => it works but it doesn't provide cut&paste so is far less useful
> than a text.
>
>> > - we don't know what is the hardware used for the SD-AFTRs
>>
>> The laptops
>
> => good but as far as I can know there are not yet ready so
> for instance the Ethernet addresses are not good.

Will be ready this afternoon.

>> > - we need the Ethernet (and IPv6 and IPv4) addresses of the 2 SD-AFTRs
>>
>> Noted.
>
> => we need the addresses on both side of SD-AFTR1 so we can copy them
> on SD-AFTR2 for the failover (using hwaddress clauses in
> /etc/network/interfaces)

Assuming the ethernet cards actually support that. I'm going to make
the failover interfaces be the hardware internet rather than the usbs,
and use the usb for the external to-the-internet


>
>> > - we need one IPv6 address for the SD-AFTR service (and the IPv4
>> > address too but we don't know it yet)
>>
>> We need to simulate using my ipv6 allocation in the lab, which is a
>> 2001:4f8:fff8:/48
>
> => No, it should be in 2001:db8::/32.

How am I supposed to get DNS?

>
>> > - I'd like to get the IPv4 addresses for the 2 SD-B4s (the usage
>> > is to give the address and the prefix length)
>>
>> We need those routable and from isc's it dept, at this point?
>
> => I thought about the internal address (done with 176.28.1.1/24
> but not with 176.28.0.0/24 ?)

So we can go double nat?

>
> Some comments:
>  - there is no need to give any details about SD-AFTR2 has it will
>  be a copy of SD-AFTR1

>From my perspective I'd like to keep it on the diagram.

>
>  - there is no IPv4 prefix for the internal Ethernet (the one with
>  the switch)

It's there to get to the switch.

>
>  - I don't know what will be the switch but I recommend a small dumb
>  switch without management and port replication

Netgear Prosafe GS105E, and it has management and port replication,
because I thought that was what we'd agreed on.

>
>  - please drop the wireshark box (wireshark will be run on SD-AFTRs
>  and/or SD-B4 if we have a laptop based SD-B4)

While this makes sense, I thought the plan was to have wireshark
listening on a mirrored port.

I have no problems dropping it.

>
>  - please drop wireless

Dropped.

>
>  - the DNS will be over IPv6 with a caching server on SD-AFTRs.
>  Looking at the saved conf/testbeds/hw/aftr-named.conf
>  there is nothing special.

The problem here (to me) was that the caching server on the AFTRs
needs to listen on an ipv6 address. The failover process assuming it's
switching ivp6 addresses (or adding them)
needs to update the ipv6 address, and/or restart the name server to
quickly pickup the new interface/ip

I'm under the impression that bind scans for new interfaces periodically.

>
> Regards
>
> Francis Dupont <fdupont at isc.org>



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net


More information about the sdcpe-devel mailing list