Walter Schilling <schill...@msoe.edu> wrote: > [-- text/plain, encoding 7bit, charset: UTF-8, 16 lines --] > > I have students working on the Beaglebone using the current Debian image. > They are working in pairs. Student one has bone A and laptop a. Student > two has bone B and laptop b. If b connects to B and then a connects to A, > they receive an ssh failure with a broken pipe. If b connects to both A > and B, then it works fine. It makes no sense to me at all. Any ideas? > The "write failed, broken pipe" message usually indicates a disconnection after ssh has successfully logged in.
>From what you're saying though it sounds to me as if there is some problem with clashing IP addresses. Are both the laptops on the same LAN? More specifically are they on the same subnet? If you are connecting the BBBs to the laptops using the ethernet over USB then confusing things might happen. Tell us more about how you're connecting the BBBs and also try with no other (ethernet/LAN) connections to the Laptops. If all is OK with no other network connections then add things back until it goes wrong. Remember also that ethernet/LAN connections can be WiFi, maybe both Laptops are connecting by WiFi to the local LAN without you even knowing (try turning WiFi off). -- Chris Green ยท -- 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.
