James, didn't we have an avahi workaround for this kinda thing before in the olden days, where having a simultaneous USB Ethernet and wireless connection caused self-assigned addresses to mess up the buddy visibility? I may be mis-remembering, or it may have been an unrelated issue, but forgive me, for I did live a full life in the seventies. :-) Cheers, KG Sent from my currently functioning gadget
James, Gonzalo, Regarding the IBSS/Ad-hoc scenario, if I set the address manually, collaborations work just fine. So this must be related to network discovery. My test goes like this: * I use one XO with fc18+S0.100 to create an ad-hoc network network. * From another XO, with fc20+S0.102, I connect to that ad-hoc network. The second XO ip address does not match the first one's network. But when I manually configure it, then buddy icons appears and collaboration works... On Tue, Sep 16, 2014 at 11:01 AM, Martin Abente <martin.abente.lah...@gmail.com> wrote:
|
_______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
_______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel