Mask:255.255.255.252

^^ Will be a problem.

This mask means you have the ability to use 3 address, of which one is
reserved for the broadcast "IP" Which is not usable by an interface.
192.168.7.0. Which, I'm not a network guru, and I could be remembering
incorrectly. You could try loosing that last field from 252 to 251m and see
if that works.

In an attempt to fix your multiple USB interfaces on the first BBB try to
disable the generic start up service temporarily. This can be done by
issuing the command:

systemctl disable generic-board-startup.service

With elevated commands. reboot the board, and try again. If neither
interface comes up after a reboot, then you can reenable the service by
running:

systemctl enable generic-board-startup.service

On Fri, Jan 20, 2017 at 5:12 PM, Bert Beckmann <[email protected]> wrote:

> so close!
>
> without any kernel changes - I am now seeing usb0 and usb1 in ifconfig on
> BBB1 when I connect the 2nd BBB to the first (mini to full).
> I assign IP's - I gave 192.168.7.1 to the 2nd BBB.
> Maybe netmask / ip #'s are causing problems - will try using .2 and .3
> with mask of 255.255.255.0
>
> what happens now --- if I ssh to 192.168.7.1 expecting to see my 2nd BBB,
> I get connected to the BBB I am running on.
> so so close!
>
> ah - however - now on the 2nd BBB - no usb0 device shows up. That explains
> a little. When the cable is connected, the 2nd BBB drops it's usb0
> definition. The 1st BBB get's usb1 added though.
>
> Maybe Robert's mod is needed.
>
> Here are the ifconfigs:
>
> BBB1:
>
> root@rib2bbb-08977:~# ifconfig -a
>
> eth0      Link encap:Ethernet  HWaddr 80:30:dc:91:16:b5
>
>           inet addr:172.28.0.120  Bcast:172.28.0.255  Mask:255.255.255.0
>
>           inet6 addr: fe80::8230:dcff:fe91:16b5/64 Scope:Link
>
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>
>           RX packets:7500 errors:0 dropped:0 overruns:0 frame:0
>
>           TX packets:1464 errors:0 dropped:0 overruns:0 carrier:0
>
>           collisions:0 txqueuelen:1000
>
>           RX bytes:806150 (787.2 KiB)  TX bytes:163855 (160.0 KiB)
>
>           Interrupt:175
>
>
> lo        Link encap:Local Loopback
>
>           inet addr:127.0.0.1  Mask:255.0.0.0
>
>           inet6 addr: ::1/128 Scope:Host
>
>           UP LOOPBACK RUNNING  MTU:65536  Metric:1
>
>           RX packets:415 errors:0 dropped:0 overruns:0 frame:0
>
>           TX packets:415 errors:0 dropped:0 overruns:0 carrier:0
>
>           collisions:0 txqueuelen:1
>
>           RX bytes:41928 (40.9 KiB)  TX bytes:41928 (40.9 KiB)
>
>
> usb0      Link encap:Ethernet  HWaddr 3a:a6:6d:9c:15:2d
>
>           inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>
>           inet6 addr: fe80::38a6:6dff:fe9c:152d/64 Scope:Link
>
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>
>           TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
>
>           collisions:0 txqueuelen:1000
>
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
>
> usb1      Link encap:Ethernet  HWaddr 9a:2a:76:42:c0:87
>
>           inet addr:192.168.7.1  Bcast:192.168.7.3  Mask:255.255.255.252
>
>           inet6 addr: fe80::982a:76ff:fe42:c087/64 Scope:Link
>
>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>
>           TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
>
>           collisions:0 txqueuelen:1000
>
>           RX bytes:0 (0.0 B)  TX bytes:90 (90.0 B)
> BBB2:
> root@rib2bbb-11111:~# ifconfig
> eth0      Link encap:Ethernet  HWaddr 68:c9:0b:ee:66:c4
>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>           Interrupt:175
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:65536  Metric:1
>           RX packets:452 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:452 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1
>           RX bytes:36528 (35.6 KiB)  TX bytes:36528 (35.6 KiB)
>
>
> On Friday, January 20, 2017 at 4:04:38 PM UTC-7, Bert Beckmann wrote:
>>
>> Is this possible? I see that RP zero and RP 3 can do this. I have tried
>> with no luck so far (mini/otg port on one to full USB on the other) and
>> have searched the internet for an example. I see that the mini ports come
>> up as usb/ethernet/device ports - can they be connect together? Or how to
>> we get the full USB port to act as a host and also act as ethernet device?
>> This would be very useful.
>>
> --
> 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].
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/11dc57f3-12c5-4579-b678-b481cf3f8bdc%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/11dc57f3-12c5-4579-b678-b481cf3f8bdc%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> 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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORo-Q4cvPwJbZQP%2BXjW9weWGq98NZR9WgfOv9t0j8AfsLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to