Also, I'm glad you all are working on getting this working. Truly. But is it or does it really have to be all this work, and all this difficult to get this sort of thing working ? Me, I really *really* hate, yes hate, with a passion -> connman. So of course im sitting on the sidelines here thinking this should be doable with using connman. But again, of course, I've no hands on yet to date.
On Tue, Mar 8, 2016 at 6:05 PM, William Hermans <[email protected]> wrote: > *(so much stuff is hard-coded for 192.168.7.2)* >> > > So, again. I'm wondering why you all *need* to have dhcp on this interface > at all ? I mean with all the hassles I'm hearing about on the forums here, > it would be easier to teach people how to set the interface manually to > *7.1 on the host side. Then of course . . . *7.2 on the beaglebone. I've > been doing this pretty much since day one, give or take a week or two shake > down early on . . .and yeah have had no problems. Definately not the > problems I'm seeing crop up on the forums here all the time . . . > > On Tue, Mar 8, 2016 at 4:25 PM, Robert Nelson <[email protected]> > wrote: > >> > Ya. I have a couple of BBGs and didn't read the fine print close >> enough to >> > see that there is no barrel jack. >> > So, I have an Andice Labs Power Cape at the ready and/or build my own >> power >> > supply as power over USB is obviously such a non-starter for real work. >> >> I have that same power cape, just need to assemble it.. >> >> > >> > Excellent! >> > >> > So one has to wonder if it would be wise to eliminate >> > /etc/network/interfaces (or at least have everthing commented out with >> > warnings) to help prevent the often occurring confusion when Connman >> > overrides definitions in /etc/network/interfaces. And, of course, >> > /etc/network/interfaces is supposed to be "legacy". >> >> I think we will just blank it out, then users can add there own tweaks.. >> >> I think i figured out how to get the usb0 to start at 192.168.7.2 >> >> https://paste.debian.net/413402/ >> >> (so much stuff is hard-coded for 192.168.7.2) >> >> > When this is sorted, it would be cool to work towards an "on-boarding" >> > solution (possibly using something like AllJoyn OnBoarding Service) to >> > provision credentials on boards with on board wifi...sorta like what >> JasonK >> > was pining about. >> >> I'd be up for anything unified.. ;) >> >> Regards, >> >> -- >> Robert Nelson >> https://rcn-ee.com/ >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
