On Tue, 22 Sep 2009 16:40:46 +0100 Alan Maguire <Alan.Maguire at Sun.COM> wrote:
> fresh webrev in place, I've retested and > it seems to resolve all the issues described > in 11437, 11092 and 10707. We're seeing > some weirdness with DHCPv6 and autoconf > that John has kindly spent some time investigating, > this likely results from us having to rely on regular > router advertisements rather than sending > solicitations when IPv6 is plumbed. The same > behaviour is observed outside of NWAM so it > doesn't seem to be an NWAM-specific issue. > > One other weird thing we see on John's test machine - > DHCPv4 takes a long time to respond sometimes > (>60sec), despite nwamd doing the right thing in > starting DHCP during the configuration phase. > Webrev is at: > > http://zhadum.east/export/ws/amaguire/nwam1-fixes/webrev/ [...] ncu.c:205 This should be reworded to something like "In our current implementation reinitialization needs to start from scratch in order to make management of NCUs rational." or something like that. ncu.c:251 Why? You could have received a state{less,full} address by now. ncu_ip.c:342 (curiosity) Was setting the flags back to what they were causing a problem? ncu_ip.c:390 the prefix argument can go away since you are getting the whole newaddr message ncu_ip.c:1286,1294,1294,1407 This must never happen in testing since you alloc the address on the first go around and free it every time after that ;)
