24 replies to this topic

[spock]

Some offtopic here that maybe you can answer,

As you have bumped busybox (+PRINC = "13") to get this fix in, I'm assuming that would trigger it to rebuild and stb's seeing it as a new update. How can one identify if this "bump" is the version that's currently installed? I get the impression my busybox never got updated, and I'm not really sure how to verify it, other then the "1.19.4-r17" that opkg reports, which I assume signals some other revisioning technique (the -r17 that is)?

Edited by spock, 19 July 2012 - 16:06.

[Erik Slagter]

It looks the fix has made it into the image now.

Still left is the wpa_supplicant-script-fix, which will follow.

[spock]

It's working perfectly on both my stb's now, many thanks.

You said earlier you're using your own scripts for ipv6, so just out of curiosity, do you use ipv6 for dns too? If so, how did you approach that? Is there any tools in the feed that can grab dns servers from radvd and put them in resolv.conf? And how to stop udhcpc from removing them from there?

[spock]

It seems rdnssd would be needed, which has been merged to ndisc6 (both of these are not available in the feeds). It also looks as busybox can include ndisc6.

I'll try to figure out how to either enable it in busybox build or make a bitbake recipe for ndisc6. Not sure how it will interact with udhcpc and bootup scripts though..

Edited by spock, 26 July 2012 - 15:47.

[Erik Slagter]

I have a script that set everyting statically. I have no rdnssd running on my network. Some hosts get their ip using dhcp6 and some have it configured statically. I am not using radvd, I think it really sucks to have eight bytes of host part in the address while one would suffice.