On Sun, 11 Oct 2020 02:46:28 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user John Dyson
<[email protected]> wrote:
>Hi,
>
>I think the problem is with the network adapter not working correctly in
>windows. The network adapter shown is "Remote NDIS compatible Device".
>
That adapter is the norm for the BBB USB "ethernet" emulation.
How are you powering the BBB? Using USB from the host computer? If so,
you also have the USB ethernet gadget active.
In either case, you need the BBB configured to /route/ packets to the
next node in your network. Normally that would be an internet router --
even though I've powered this BBB using the USB (and hence have the
192.168.7.x IPs active) it is also connected to my router over a CAT-5
cable. Note that the router issued the BBB 192.168.1.69, and also that the
default destination for packets is the router (ATT U-Verse service).
debian@beaglebone:~$ ifconfig
eth0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500
inet 192.168.1.69 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 2600:1700:e630:890:d239:72ff:fe18:3ee5 prefixlen 64 scopeid
0x0<global>
inet6 fe80::d239:72ff:fe18:3ee5 prefixlen 64 scopeid 0x20<link>
inet6 2600:1700:e630:890::31 prefixlen 64 scopeid 0x0<global>
ether d0:39:72:18:3e:e5 txqueuelen 1000 (Ethernet)
RX packets 111 bytes 13355 (13.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 139 bytes 23120 (22.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 81 bytes 6556 (6.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 81 bytes 6556 (6.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.7.2 netmask 255.255.255.0 broadcast 192.168.7.255
inet6 fe80::d239:72ff:fe18:3ee7 prefixlen 64 scopeid 0x20<link>
ether d0:39:72:18:3e:e7 txqueuelen 1000 (Ethernet)
RX packets 118 bytes 27503 (26.8 KiB)
RX errors 0 dropped 4 overruns 0 frame 0
TX packets 46 bytes 10444 (10.1 KiB)
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.0 broadcast 192.168.6.255
ether d0:39:72:18:3e:eb 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
debian@beaglebone:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
default dsldevice.attlo 0.0.0.0 UG 0 0 0
eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
dsldevice.attlo 0.0.0.0 255.255.255.255 UH 0 0 0
eth0
192.168.6.0 0.0.0.0 255.255.255.0 U 0 0 0
usb1
192.168.7.0 0.0.0.0 255.255.255.0 U 0 0 0
usb0
If you are connecting to an ethernet port on your computer, your host
computer has to also be configured to act as a router -- that is, it has to
accept packets from the BBB, and pass them on to whatever node the host has
defined as a gateway.
THIS ACTION is not automatic for Windows! In some versions it is known
as Internet Connection Sharing (ICS), and requires configuration to "link"
the (to-be-shared) network with the devices connected to the host computer.
cf:
https://answers.microsoft.com/en-us/windows/forum/windows_10-networking-winpc/internet-connection-sharing-in-windows-10/f6dcac4b-5203-4c98-8cf2-dcac86d98fb9
I have never done this, and have no desire to experiment with it
debian@beaglebone:~$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 dsldevice.attlocal.net (192.168.1.254) 0.741 ms 0.966 ms 0.868 ms
2 76-255-152-1.lightspeed.gdrpmi.sbcglobal.net (76.255.152.1) 26.304 ms
26.519 ms 27.412 ms
3 71.152.176.29 (71.152.176.29) 21.155 ms 21.087 ms 21.230 ms
4 cr2.cgcil.ip.att.net (12.123.7.142) 32.936 ms 32.997 ms 33.044 ms
5 gar10.cgcil.ip.att.net (12.122.133.45) 28.911 ms 29.198 ms 30.100 ms
6 12.255.10.54 (12.255.10.54) 30.498 ms 22.241 ms 23.598 ms
7 10.252.38.62 (10.252.38.62) 24.052 ms 10.252.49.190 (10.252.49.190)
23.670 ms 10.252.38.30 (10.252.38.30) 24.364 ms
8 dns.google (8.8.8.8) 25.134 ms 22.236 ms 23.141 ms
debian@beaglebone:~$ traceroute 192.168.1.66
traceroute to 192.168.1.66 (192.168.1.66), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 *^C
debian@beaglebone:~$
Appears my host computer is blocking traceroute, but ping is okay
debian@beaglebone:~$ ping 192.168.1.66
PING 192.168.1.66 (192.168.1.66) 56(84) bytes of data.
64 bytes from 192.168.1.66: icmp_seq=1 ttl=128 time=0.440 ms
64 bytes from 192.168.1.66: icmp_seq=2 ttl=128 time=0.473 ms
64 bytes from 192.168.1.66: icmp_seq=3 ttl=128 time=0.454 ms
64 bytes from 192.168.1.66: icmp_seq=4 ttl=128 time=0.424 ms
64 bytes from 192.168.1.66: icmp_seq=5 ttl=128 time=0.433 ms
64 bytes from 192.168.1.66: icmp_seq=6 ttl=128 time=0.424 ms
^C
--- 192.168.1.66 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 13ms
rtt min/avg/max/mdev = 0.424/0.441/0.473/0.024 ms
debian@beaglebone:~$
--
Dennis L Bieber
--
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/5649of1ecp9huj7aelhc91epfch5vv3mit%404ax.com.
