a sdcpe package 'feed' request
Francis Dupont
fdupont at isc.org
Tue Mar 13 22:12:24 UTC 2012
> the server I've repurposed to use for this effort is: io.lab.bufferbloat.net
=> I got it in IPv4, not in IPv6 but one minute after it worked in IPv6
too. strange... BTW it seems to be connected to some ISC lab networks
so should *not* be a priori reachable from outside.
> It has two network cards and a wireless card in it. It is on
> native ipv6 on the inside and outside, although I need to assign
> at least a /63 out of my existing (and used up) /60 allocation
> for it to manage, and get rid of the 2002 it is also on....
=> if it is an ISC lab machine it should get ISC lab IPv6.
I don't understand its usage, not why it has 3 networks.
> (it's up now, but not integrated into kerberos, so please send
> me an ssh authorized_keys file)
=> I'll wait it gets kerberos: I really want to limit the number
of passwords I use (so I have to remember).
> The kernel I built for it is from the 3.3rc7. It does not have your
> suggested tunneling patch, nor any other patches.
=> my tunneling patch is useful (but not required) for an IPv4
over IPv6 encapsulating box.
> The kernel
> is at ~d/git/linux-2.6 and after other patches are added and
> committed, can be built and installed 'the ubuntu way' via the
> supplied buildit.sh script in that dir.
=> this detail is useless if I am not supposed to become root on it (:-).
> Why is 6rd needed, btw? (it's in there, but...)
=> it is not (or more exactly not yet).
> I have not installed any of the sdcpe related sources or binaries on it,
> being A) clueless, and B) only got this puppy running last night
> (I do have them on the laptop at: 2001:4f8:3:aa0c:227:13ff:fe64:896)
=> I have no idea about your testbed infrastructure...
Regards
Francis Dupont <fdupont at isc.org>
More information about the sdcpe-devel
mailing list