status

Dave Taht dave.taht at gmail.com
Mon Mar 12 17:32:08 UTC 2012


Me:

began code freeze for cerowrt project (anticipated 'ship' date would
be around may 1)

got to where I could actually get and build the sdcpe related from the right
branches pulled via kerberos, etc, on x86.

reviewed the code to some extent

Three issues:

1) My build system and packaging system is entirely public. I don't
know to what extent I am allowed to make these added packages public,
or if I should establish an entirely private fork of my own stuff
specific for this project. I would prefer the former...

2) The isc upnp code is based on several 'dumps' of the release
tarballs and patches around it. The mainline code is maintained in
git, publically, and it strikes me as sane to be branching and
patching around that instead. https://github.com/miniupnp/miniupnp

3) I have been totally unable to get routed multicast to work on
anything using pimd and mrd6.

4) My cvs skillz are rusty and what I'd wanted to come up with was a
patch for dhcp from this branch that applied against the mainline...

Some more comments below.

On Mon, Mar 12, 2012 at 3:30 PM, Francis Dupont <fdupont at isc.org> wrote:
> AFTR: tested the pseudo SD-AFTR code, including the ICMP (which requires
> a default private clause to raise the expected error in natin()),
> saved the config files. Copied and updated the echo match extension
> for netfilter from the old netfilter-based AFTR branch, including
> the ping which comes with it, so one can route on the ICMP echo ID.

This is what is in one of the repos I know about?

> PCP: nothing new (but just received an announce about a new upnp ietf I-D)

I see pcpd and various other binaries here, not a lot of
documentation. Which of these binaries
is required on the server and which on the client.

> DHCP: nothing new (and nothing to do too)
> Multicast: read the mB4 code (shan't comment the code quality to stay
> polite)

I shan't comment either.

> CPE: tested the sdctld stuff, move the build to autoreconf --install
> (i.e., same than bind10): should be easier to package for OpenWRT?

preferred packaging method is from a release tarball + patches, using autotools.

> Demo: still have no idea (at the exception it is CPE, not PCP demo)
> about what we'll be supposed to do...

I thought we were going with server -> cpe -> one or more clients

>
> TODO:
>  - more docs
>  - OpenWRT packaging (Dave?)
>  - ICMP stuff on the CPE (Dave?)
>  - conntrack stuff (today the recovery is simply a reboot)
>  - install VLC on my Windows 7 VM
>  - understand how to install Fedora 16 on an EFI box and everything,
>  including /boot, in a LVM2 volume (i.e., using Boot Camp on a Mac
>  without hack)

TODO: Getting to where I have running code, on hardware, in 'the demo setup'

> Regards
>
> Francis Dupont <fdupont at isc.org>
> _______________________________________________
> sdcpe-devel mailing list
> sdcpe-devel at lists.isc.org
> https://lists.isc.org/mailman/listinfo/sdcpe-devel



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


More information about the sdcpe-devel mailing list