Can't connect to BBB over Ethernet

[Pavel Yermolenko]

Hello,

Trying to connect to BBB I've tried 2 options for login:

• temppwd
• debian:tempwd

Both failed:

pavel@ALABAMA:~$ sudo ssh ro...@beaglebone.local
Debian GNU/Linux 9

BeagleBoard.org Debian Image 2019-10-01

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

ro...@beaglebone.local's password:
Permission denied, please try again.
ro...@beaglebone.local's password:
Permission denied, please try again.
ro...@beaglebone.local's password:
ro...@beaglebone.local: Permission denied (publickey,password).
pavel@ALABAMA:~$

Any comments ?

Thanks.

[Ray Willis]

That's not how you ssh into a device. You cannot ssh into root.

From your machine (ensure the ip schema for ipv4 is the same, setting the last octet one number aboveor below your BBB ip address), in your terminal: $ ssh deb...@192.168.7.2

If you changed the ip address of your BBB. Use it's ip address.

[NAGABHOOSHANAM VEMULA]

Hi,

My understanding, login to root@ in first go doesn't seems work,  

Initially SSH for debian@.... then we can switch to root just ..by.. sudo su.

I use PockerBeagle and connect internet-over-USB. here are steps commands, which may help you.

=========

root@DESKTOP-S0M2XXX:/home/nvemula# ssh deb...@192.168.7.2

Debian GNU/Linux 10

BeagleBoard.org Debian Buster IoT Image 2020-04-06

Support: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

=========  

deb...@192.168.7.2's password:   [ enter the pwd as temppwd]

The programs included with the Debian GNU/Linux system are free software;

the exact distribution terms for each program are described in the

individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent

permitted by applicable law.

Last login: Tue Aug 18 12:27:01 2020 from 192.168.7.1

debian@beaglebone:~$ sudo su

[sudo] password for debian:

root@beaglebone:/home/debian#  

=========  

[Pavel Yermolenko]

Ok, it works. Thanks

But IP you specified is for connection over USB.

The IP when connected over Ethernet is quite different.

[Ray Willis]

Cool. That ip address is typically the default for both USB and eth0.

Glad I could help.

[Pavel Yermolenko]

That ip address is typically the default for both USB and eth0.

Not in my case:

debian@beaglebone:~$ ifconfig
eth0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC>  mtu 1500
        inet 10.42.0.39  netmask 255.255.255.0  broadcast 10.42.0.255
        inet6 fe80::96e3:6dff:fed4:ae86  prefixlen 64  scopeid 0x20<link>
        ether 94:e3:6d:d4:ae:86  txqueuelen 1000  (Ethernet)
        RX packets 43  bytes 5224 (5.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 75  bytes 11801 (11.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 55 

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 160  bytes 12960 (12.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 160  bytes 12960 (12.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.7.2  netmask 255.255.255.252  broadcast 192.168.7.3
        ether 8a:7c:4a:06:36:ec  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.6.2  netmask 255.255.255.252  broadcast 192.168.6.3
        ether 7e:13:e8:37:42:05  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

BTW why 2 USBs ?

Thanks.

[Pavel Yermolenko]

... I mean two USBs ("big" and "small") can be used for Internet connection.

I thought that "big" is only for pereferals.

[Robert Nelson]

Because, Microsoft (RNDIS) and Apple (USB-NCM) can't agree on what
technology to give access to "without" a signed driver..

With Windows, USB-CDM/NCM needs a 'signed driver'
With Mac, RNDIS needs a 3rd party driver..

So due to that crap..

usb0, is the RNDIS driver for Windows users
usb1, is the CDC-NCM driver for Mac Users..

and on linux we get two 'working' drivers..

Regards,


--
Robert Nelson
https://rcn-ee.com/

[Ray Willis]

That first octet looks like an assigned one by the network. Since eth0 is dhcp by default, it was assigned an ip address by the dhcp server.
usb0 is the virtual ethernet NIC. When you connect via uUSB it acts as a ethernet connection.
usb1 is (I think) the onboard server where you can use the ide and lists the startup stuff (when you click the little beagle icon on your desktop).

[Pavel Yermolenko]

Ok, thanks

[Ray Willis]

Lol.. sounds right. Look at how many different types of micro usb there are. Everyone wants to be the next standard. From Apple to Samsung. Pick one and go with it.

[Dennis Lee Bieber]

On Thu, 20 Aug 2020 06:36:38 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user NAGABHOOSHANAM VEMULA

<nagabhooshanam.v-Re...@public.gmane.org> wrote:

>Hi,
>My understanding, login to root@ in first go doesn't seems work,
>Initially SSH for debian@.... then we can switch to root just ..by.. sudo
>su.

Ideally, you should not NEED to "switch to root". If you encounter some
operation that requires root privilege, you should run JUST that operation
using "sudo <the operation>".


--
Dennis L Bieber

[Dennis Lee Bieber]

On Thu, 20 Aug 2020 07:17:38 -0700 (PDT), in

gmane.comp.hardware.beagleboard.user "'Ray Willis' via BeagleBoard"

usb0 is, I believe, the RNDIS protocol used by Windows -- typically the
192.168.7.x network.

usb1 is, again I believe, CDC protocol used by Mac -- 192.168.6.x
network

(Linux appears to have support for both so either IP could be used)

https://en.wikipedia.org/wiki/Ethernet_over_USB


--
Dennis L Bieber

[Pavel Yermolenko]

Can't connect BBB anymore by ssh:

pavel@ALABAMA:~$ ssh deb...@10.42.0.39
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!

[Steve Lentz]

This has nothing to do with the BBB, it’s your Ubuntu machine protecting you from something it thinks could be dangerous.  If you switch from one board to another, you will get this warning.  If you haven’t connected to a board in a long time (years), you may get it as well.  If you garble up SSH the first time you connect, it will give you this warning.  

Here’s a helpful link:

https://stackabuse.com/how-to-fix-warning-remote-host-identification-has-changed-on-mac-and-linux/

[Pavel Yermolenko]

Hi Steve,

Works fine, thanks.