*On the Beaglebone can you ping* * 192.168.7.1 ?* *On my Beaglebone here is what I get*
*debian@beaglebone:~$ netstat -rnKernel IP routing tableDestination Gateway Genmask Flags MSS Window irtt Iface0.0.0.0 192.168.7.1 0.0.0.0 UG 0 0 0 usb0192.168.6.0 0.0.0.0 255.255.255.0 U 0 0 0 usb1192.168.147.0 0.0.0.0 255.255.255.0 U 0 0 0 usb0* *Looking at your setup I would say the ping will fail* *$ sudo netstat -rn* *Kernel IP routing table* *Destination Gateway Genmask Flags MSS Window irtt Iface* *0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 wlan0* *169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan0* *172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0* *192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0* *192.168.6.0 0.0.0.0 255.255.255.0 U 0 0 0 usb0* *192.168.7.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1* *Unfortunately my only Linux hosts are on VM's.* On Sat, May 16, 2020 at 12:11 PM jonnymo <[email protected]> wrote: > I'm seeing a similar issue with a BBAI. > However, on my host Ubuntu 18 system, I am seeing the network ports from > the BB in the routing table. > > *$ sudo netstat -rn* > *Kernel IP routing table* > *Destination Gateway Genmask Flags MSS Window irtt > Iface* > *0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 > wlan0* > *169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 > wlan0* > *172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 > docker0* > *192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 > wlan0* > *192.168.6.0 0.0.0.0 255.255.255.0 U 0 0 0 > usb0* > *192.168.7.0 0.0.0.0 255.255.255.0 U 0 0 0 > eth1* > > > On the BB: > * # netstat -rn* > > > > > > > > *Kernel IP routing tableDestination Gateway Genmask > Flags MSS Window irtt Iface0.0.0.0 192.168.7.1 0.0.0.0 > UG 0 0 0 usb0192.168.6.0 0.0.0.0 > 255.255.255.0 U 0 0 0 usb1192.168.7.0 0.0.0.0 > 255.255.255.0 U 0 0 0 usb0192.168.8.0 0.0.0.0 > 255.255.255.0 U 0 0 0 SoftAp0* > > Running tcpdump on my Ubuntu system, I can see where the incoming traffic > from the BB is reaching the correct IP on the host but does not seem to be > getting routed out. > > On BB: > > *# ping -I usb0 8.8.8.8* > > On Host: > > *$ sudo tcpdump -nvvi wlan0 'icmp[icmptype] == icmp-echo or icmp[icmptype] > == icmp-echoreply'* > *tcpdump: listening on wlan0, link-type EN10MB (Ethernet), capture size > 262144 bytes* > *08:55:34.027628 IP (tos 0x0, ttl 115, id 44071, offset 0, flags [DF], > proto ICMP (1), length 84)* > * 192.168.2.216 > 8.8.8.8 <http://8.8.8.8>: ICMP echo request, id 1402, > seq 1, length 64* > *08:55:34.049037 IP (tos 0x20, ttl 52, id 0, offset 0, flags [none], proto > ICMP (1), length 84)* > * 8.8.8.8 > 192.168.2.216 <http://192.168.2.216>: ICMP echo reply, id > 1402, seq 1, length 64* > *08:55:35.049654 IP (tos 0x0, ttl 115, id 44297, offset 0, flags [DF], > proto ICMP (1), length 84)* > * 192.168.2.216 > 8.8.8.8 <http://8.8.8.8>: ICMP echo request, id 1402, > seq 2, length 64* > *08:55:35.067301 IP (tos 0x20, ttl 52, id 0, offset 0, flags [none], proto > ICMP (1), length 84)* > > It seems that something either on the Ubuntu side or in the network is > blocking the traffic. > > Cheers, > > Jon > > On Sat, May 16, 2020 at 7:07 AM KenUnix <[email protected]> wrote: > >> >> I too am having problems today. In your regard >> >> The following is my netstat -rn for my Ubuntu Linux host PC: >> >> Kernel IP routing table >> |||--- >> Destination Gateway Genmask Flags MSS Window irtt >> Iface >> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 >> wlp8s0 >> 10.42.0.0 0.0.0.0 255.255.255.0 U 0 0 0 >> eth0 >> 10.42.1.0 0.0.0.0 255.255.255.0 U 0 0 0 >> eth1 >> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 >> eth0 >> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 >> wlp8s0 (wlp8s0 is my wifi) >> >> And my BBB routing table looks like >> |||--- >> Destination Gateway Genmask Flags MSS Window irtt >> Iface >> 0.0.0.0 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 >> >> The gateway address on BOTH sides of the connection should match >> with one side being .....1 and the other side being ....2 If they do not >> line up each side will not see the other side. >> >> -- >> 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/21cc8527-1fd9-4f9f-bd7d-7d6f46f25f58%40googlegroups.com >> <https://groups.google.com/d/msgid/beagleboard/21cc8527-1fd9-4f9f-bd7d-7d6f46f25f58%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 a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/QBTe4BoyF1c/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/CAG99bkr7RGpa_wmvtjbw1JFkHe381xE%3Dn9-pJ0EmuD4W2itMDQ%40mail.gmail.com > <https://groups.google.com/d/msgid/beagleboard/CAG99bkr7RGpa_wmvtjbw1JFkHe381xE%3Dn9-pJ0EmuD4W2itMDQ%40mail.gmail.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAJXSPs83vAiDHARKiEQ-i-UhvL7Rx3odCLf4BYjUzP5tA1pmAw%40mail.gmail.com.
