On Tuesday, March 8, 2016 at 2:01:36 PM UTC-8, RobertCNelson wrote: > > PS, i'm also switched to 'git' on the build: > > > https://github.com/rcn-ee/repos/commit/dd480e6dac1317eac1cc15b2a60740e7ba53128e > > > It's currently building, so i'll retest in a bit.. > > > Did you unplug/replug the USB cable from the desktop? When first > enabling > > this with the cable plugged in, it seems to require a re-plug to get > DHCP to > > issue an IP. But I suppose your dhclient request from the desktop side > > should have triggered this. > > That's actually going to be a problem. On the BeagleBone Green, power > comes thru usb0... (and i've run out of BeagleBone Black's at > work...) >
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've tried, restarting connman.service, that didn't help... We might > have to fake a hotplug event? > Sounds like the right thing, but I haven't done that before. I suppose a hotplug event on boot iff a usb cable is plugged in? > > >> (systemd: 215 debian jessie) > >> > >> dnsmasq/create_ap removed > >> > >> $(dirname $0)/autoconfigure_usb0.sh disabled... > >> > >> bone: > >> > >> usb0 Link encap:Ethernet HWaddr ec:24:b8:d2:06:a0 > >> inet6 addr: fe80::ee24:b8ff:fed2:6a0/64 Scope:Link > >> UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1 > >> RX packets:6 errors:0 dropped:0 overruns:0 frame:0 > >> TX packets:20 errors:0 dropped:0 overruns:0 carrier:0 > >> collisions:0 txqueuelen:1000 > >> RX bytes:1968 (1.9 KiB) TX bytes:6180 (6.0 KiB) > > > > > > Do you see a tether interface (ip addr)? Attached log has output from > ip on > > bone. And of course, if you have rebooted, you need to enable the > tether > > again unless you have setup things for persistent tethering...some > connman > > config parameter. > > Nope, no tether, and i've enabled: > > PersistentTetheringMode=true > > err.. > > that seems like it was it!! > > mkdir /etc/connman/ > mv /etc/connman.conf /etc/connman/main.conf > > reboot... > > Mar 08 21:57:44 beaglebone connmand[307]: usb0 {RX} 0 packets 0 bytes > Mar 08 21:57:44 beaglebone connmand[307]: usb0 {TX} 3 packets 390 bytes > Mar 08 21:57:44 beaglebone connmand[307]: usb0 {newlink} index 3 > address EC:24:B8:D2:06:A0 mtu 1500 > Mar 08 21:57:44 beaglebone connmand[307]: usb0 {newlink} index 3 > operstate 6 <UP> > Mar 08 21:57:45 beaglebone connmand[307]: usb0 {RX} 0 packets 0 bytes > Mar 08 21:57:45 beaglebone connmand[307]: usb0 {TX} 3 packets 390 bytes > Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 > address EC:24:B8:D2:06:A0 mtu 1500 > Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 > operstate 6 <UP> > Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 > address EC:24:B8:D2:06:A0 mtu 1500 > Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 > operstate 6 <UP> > Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 > address EC:24:B8:D2:06:A0 mtu 1500 > Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 > operstate 6 <UP> > Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 > address EC:24:B8:D2:06:A0 mtu 1500 > Mar 08 21:57:45 beaglebone connmand[307]: usb0 {newlink} index 3 > operstate 6 <UP> > Mar 08 21:57:45 beaglebone kernel: device usb0 entered promiscuous mode > Mar 08 21:57:45 beaglebone kernel: tether: port 1(usb0) entered forwarding > state > Mar 08 21:57:45 beaglebone kernel: tether: port 1(usb0) entered forwarding > state > > bone: > > tether Link encap:Ethernet HWaddr ec:24:b8:d2:06:a0 > inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 > inet6 addr: fe80::38b0:4eff:feb4:9211/64 Scope:Link > UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1 > RX packets:684 errors:0 dropped:0 overruns:0 frame:0 > TX packets:360 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:66369 (64.8 KiB) TX bytes:38011 (37.1 KiB) > > usb0 Link encap:Ethernet HWaddr ec:24:b8:d2:06:a0 > inet6 addr: fe80::ee24:b8ff:fed2:6a0/64 Scope:Link > UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1 > RX packets:684 errors:0 dropped:0 overruns:0 frame:0 > TX packets:380 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:66369 (64.8 KiB) TX bytes:60067 (58.6 KiB) > > desktop: > > enxec24b8d206af: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255 > inet6 fe80::ee24:b8ff:fed2:6af prefixlen 64 scopeid 0x20<link> > ether ec:24:b8:d2:06:af txqueuelen 1000 (Ethernet) > RX packets 180 bytes 24507 (23.9 KiB) > RX errors 3 dropped 0 overruns 0 frame 3 > TX packets 183 bytes 24716 (24.1 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > 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". 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. ba ba -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.