John Dyson - did you ever get this to work? I have had the same problem and can't get it to work...
On Friday, October 16, 2020 at 3:18:40 AM UTC-4 jonn...@gmail.com wrote: > Typically, Windows disables the response to ping. I would leave it that > way. > > To get the Beaglebone to talk to the Internet through the Windows internet > connection you should not have to change anything with the firewall; I did > not have to do this. > I would go back through the steps and see what is missing. > > Jon > > On Thu, Oct 15, 2020 at 11:57 PM John Dyson <dysona...@gmail.com> wrote: > >> Hi, >> >> You are right disabling the windows firewall allowed the beaglebone to >> ping the windows PC. I disabled the PC wifi in order that there were no >> issues. Any idea how I can configure the firewall in order that the >> beaglebone over the usb cable is allowed through? >> >> Thanks >> >> On Wednesday, 14 October 2020 at 16:16:49 UTC+1 Dennis Bieber wrote: >> >>> On Wed, 14 Oct 2020 01:01:42 -0700 (PDT), in >>> gmane.comp.hardware.beagleboard.user John Dyson >>> <dysonator619-re5j...@public.gmane.org> wrote: >>> >>> >Hi, >>> > >>> >Following these instructions: >>> > >>> >I have connected the USB Cable and nothing else from the beaglebone to >>> the >>> >PC. All of thwe windows 64 bit drivers have been successfully >>> installed. >>> > >>> >>> Just to follow along on this part, I've pulled the CAT-5 from my BBB. >>> >>> debian@beaglebone:~$ ifconfig >>> eth0: flags=-28669<UP,BROADCAST,MULTICAST,DYNAMIC> mtu 1500 >>> ether d0:39:72:18:3e:e5 txqueuelen 1000 (Ethernet) >>> RX packets 164 bytes 13701 (13.3 KiB) >>> RX errors 0 dropped 0 overruns 0 frame 0 >>> TX packets 95 bytes 15719 (15.3 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 153 bytes 11380 (11.1 KiB) >>> RX errors 0 dropped 0 overruns 0 frame 0 >>> TX packets 153 bytes 11380 (11.1 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 193 bytes 35656 (34.8 KiB) >>> RX errors 0 dropped 4 overruns 0 frame 0 >>> TX packets 84 bytes 18613 (18.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 >>> >>> No IP address on eth0, expected address on usb0. >>> >>> > >>> >The initial ping to the gateway 192.168.7.1 fails when I SSH into the >>> >beaglebone (Figure 3) >>> > >>> WHY a screen grab? You are using a text console, aren't you -- just >>> select/copy/paste the TEXT... >>> >>> debian@beaglebone:~$ route >>> Kernel IP routing table >>> Destination Gateway Genmask Flags Metric Ref Use >>> Iface >>> 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 >>> debian@beaglebone:~$ ping 192.168.7.1 >>> PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data. >>> 64 bytes from 192.168.7.1: icmp_seq=1 ttl=128 time=0.368 ms >>> 64 bytes from 192.168.7.1: icmp_seq=2 ttl=128 time=0.475 ms >>> 64 bytes from 192.168.7.1: icmp_seq=3 ttl=128 time=0.501 ms >>> 64 bytes from 192.168.7.1: icmp_seq=4 ttl=128 time=0.491 ms >>> ^C >>> --- 192.168.7.1 ping statistics --- >>> 4 packets transmitted, 4 received, 0% packet loss, time 9ms >>> rtt min/avg/max/mdev = 0.368/0.458/0.501/0.059 ms >>> debian@beaglebone:~$ >>> >>> Pinging the host computer works, even without a gateway setting (since >>> 192.168.7.1 and 192.168.7.2 are the same network, and likely it is >>> presumed >>> that all hosts on that network can be reached using the adapter [usb0] >>> that >>> is itself on the network). >>> >>> >>> >>> If that simple step is failing, you might have to check whatever >>> firewall you have running on Windows. >>> >>> >>> >>> NEXT action I tried was opening the Windows "Network Connections" >>> control panel. BRIDGING "Ethernet" (remember -- My systems are normally >>> cable connection) and "Ethernet 2" (the RNDIS gadget) is not the correct >>> action, as it kills the Internet access on "Ethernet" (and there is an >>> advisory that one cannot bridge an ICS adapter). >>> >>> So... remove bridge, open "Ethernet" and enable Sharing, specifying >>> "Ethernet 2" as the private network side. >>> >>> With ICS active, Windows assigned 192.168.137.1 to the RNDIS adapter! I >>> just edited that to use a manual IP address 192.168.7.1, length 24, and >>> gateway is set to my router (192.168.1.1). (I used the "WiFi" section as >>> that was the control panel type I had open) >>> https://pureinfotech.com/set-static-ip-address-windows-10/ >>> >>> SSH back into the BBB at 192.168.7.2. >>> >>> Lastly, I added a gateway on the BBB... >>> >>> debian@beaglebone:~$ route >>> Kernel IP routing table >>> Destination Gateway Genmask Flags Metric Ref Use >>> Iface >>> 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 >>> debian@beaglebone:~$ sudo route add default gw 192.168.7.1 usb0 >>> [sudo] password for debian: >>> debian@beaglebone:~$ route >>> Kernel IP routing table >>> Destination Gateway Genmask Flags Metric Ref Use >>> Iface >>> default 192.168.7.1 0.0.0.0 UG 0 0 0 >>> usb0 >>> 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 >>> debian@beaglebone:~$ ping 192.168.7.1 >>> PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data. >>> 64 bytes from 192.168.7.1: icmp_seq=1 ttl=128 time=0.432 ms >>> 64 bytes from 192.168.7.1: icmp_seq=2 ttl=128 time=0.491 ms >>> 64 bytes from 192.168.7.1: icmp_seq=3 ttl=128 time=0.460 ms >>> ^C >>> --- 192.168.7.1 ping statistics --- >>> 3 packets transmitted, 3 received, 0% packet loss, time 5ms >>> rtt min/avg/max/mdev = 0.432/0.461/0.491/0.024 ms >>> >>> Okay, I didn't expect that layer to change, as that is just BBB to host >>> level. >>> >>> debian@beaglebone:~$ ping 8.8.8.8 >>> PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. >>> 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=23.4 ms >>> 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=22.7 ms >>> 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=23.7 ms >>> 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=23.5 ms >>> 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=23.1 ms >>> ^C >>> --- 8.8.8.8 ping statistics --- >>> 5 packets transmitted, 5 received, 0% packet loss, time 12ms >>> rtt min/avg/max/mdev = 22.723/23.281/23.677/0.362 ms >>> >>> ... but that shows the routing went from BBB through my host computer to >>> my >>> router... >>> >>> {Now to see how difficult it is to undo all this} >>> >>> >>> >>> -- >>> 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 beagleboard...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/a59b278a-3339-4378-8f55-d5073307f7c0n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/beagleboard/a59b278a-3339-4378-8f55-d5073307f7c0n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/0d68f229-4e0a-423a-a403-375dcf6e995bn%40googlegroups.com.
