Rajesh Kulkarni,

Glad its finally fixed. Save that file postboot.sh. It may be needed in
later releases.

Ken


On Mon, May 18, 2020 at 10:10 PM Rajesh Kulkarni <rajkulkarn...@gmail.com>
wrote:

> Ken
> Thank you so much ! It looks it helped.I was able to successfully ping dns
> server names with no issues !
>
> * So I copied the postboot.sh as you suggested.
> * did "sudo crontab -e"
> * Added the following in the file"  @reboot sh
> /home/debian/cronjobs/postboot.sh 1>/home/debian/cronjobs/log
> 2>/home/debian/cronjobs/log  "
> * Did a reboot.
> * The following is the log file :
>
> === Boot ===
> Set Nameserver and Gateway
> Nameserver 8.8.8.8, GW 192.168.7.1
> Set route with gw 192.168.7.1
> Display 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
> Set timezone
>                Local time: Mon 2020-05-18 18:44:27 PDT
>            Universal time: Tue 2020-05-19 01:44:27 UTC
>
>                  RTC time: Tue 2020-05-19 01:44:27
>
>                 Time zone: America/Los_Angeles (PDT, -0700)
>
> System clock synchronized: no
>
>               NTP service: active
>
>           RTC in local TZ: no
>
> Finished at  Mon 18 May 2020 06:44:27 PM PDT
>
> On Mon, May 18, 2020 at 7:08 AM Kenneth Martin <ken.unix....@gmail.com>
> wrote:
>
>> Rajesh Kulkarni
>> A lot has changed with the 4-6 release. Don't fool around with
>> /etc/network/interfaces or /etc/resolv.conf.
>>
>> As debian user in the home directory.  cd ~/
>>
>> mkdir cronjobs
>>
>> copy the attached file into cronjobs
>>
>> cd cronjobs
>>
>> Read the top of the file postboot.sh
>>
>> The following must be done as sudo because the user level will not have
>> permission.
>> .
>> sudo crontab -e
>>
>> Make entry as explained in postboot.sh
>>
>> This entry will execute at boot time and sleep 20 seconds to allow the
>> system to be up.
>>
>> This may seem complicated. The reason for this setup is you can later if
>> needed make other cronjobs
>> as you or as sudo. Remember full pathnames and any executed commands
>> requiring sudo access
>> will need to be added as  sudo crontab -e. If you want a user level
>> cronjob just do  crontab -e
>>
>> When this script runs at boot time it will create a file called log. You
>> can cat log to see the results of
>> the current boot. postboot.sh also updates the system date/time. Please
>> nano or vi postboot.sh and
>> verify your Country / Time Zone.
>>
>> So, backup original  cp /etc/network/interfaces  ~/. Then clean up using
>> sudo nano /etc/network/interfaces
>> The only two active entries should be:
>>
>> auto lo
>> iface lo inet loopback
>>
>> Reboot  sudo reboot  then cat log in cronjobs
>>
>> Let me know how it works out.
>>
>> Ken
>>
>> On Mon, May 18, 2020 at 2:01 AM Rajesh Kulkarni <rajkulkarn...@gmail.com>
>> wrote:
>>
>>> Hi Kenneth,
>>> I am using Debian Buster IoT Image 2020-04-06 .
>>>
>>> Regards,
>>> Rajesh
>>>
>>> On Sun, May 17, 2020 at 7:59 PM Kenneth Martin <ken.unix....@gmail.com>
>>> wrote:
>>>
>>>> Rajesh Kulkarni
>>>> Send another message tomorrow. I have a fix for that and it uses
>>>> crontab as sudo. I
>>>> will send you examples of it all and it works. I use it.
>>>>
>>>> What version of Debian are you running?  cat /etc/dogtag
>>>>
>>>>
>>>> On Sun, May 17, 2020 at 9:21 PM Rajesh Kulkarni <
>>>> rajkulkarn...@gmail.com> wrote:
>>>>
>>>>> So I added  in my /etc/network/interfaces
>>>>>
>>>>> iface usb0 inet static
>>>>>     address 192.168.7.2
>>>>>     netmask 255.255.255.0
>>>>>     network 192.168.7.0
>>>>>     nameservers 8.8.8.8
>>>>>     gateway 192.168.7.1
>>>>>
>>>>> This *takes care of ping 8.8.8.8*. after a reboot
>>>>>
>>>>> But
>>>>> still unable to ping www.google.com : *Temporary failure in name
>>>>> resolution*
>>>>>
>>>>>
>>>>> On Sun, May 17, 2020 at 5:30 PM Rajesh Kulkarni <
>>>>> rajkulkarn...@gmail.com> wrote:
>>>>>
>>>>>> I was finally able to connect to the internet via USB(still dont know
>>>>>> what the problem was, I just reinstalled my Host Ubuntu)
>>>>>>
>>>>>> I followed the instructions given by Robert and ran the script on my
>>>>>> Host PC
>>>>>> https://github.com/RobertCNelson/boot-scripts/blob/master/network/doc-debian-setup.md
>>>>>> .
>>>>>> And this on the BBB " sudo /opt/scripts/network/usb_linux_usb0_ics.sh
>>>>>> "
>>>>>>
>>>>>> *But ,the above instructions apparently doesn't save the
>>>>>> configuration* , and the default gateway disappears after the BBB is
>>>>>> rebooted.
>>>>>> So I have to execute this command sudo
>>>>>> /opt/scripts/network/usb_linux_usb0_ics.sh every reboot.
>>>>>>
>>>>>> Do I still need to save the config in /etc/network/interfaces
>>>>>> something like :
>>>>>> iface usb0 inet static
>>>>>>     address 192.168.7.2
>>>>>>     netmask 255.255.0.0
>>>>>>     network 192.168.7.0
>>>>>>     gateway 192.168.7.1
>>>>>>
>>>>>> OR
>>>>>> does it have to be through a bash script which runs has to be set to
>>>>>> autorun mode after boot ?
>>>>>>
>>>>>> Thanks
>>>>>> Rajesh
>>>>>>
>>>>>> On Sat, May 16, 2020 at 2:02 PM jonnymo <jonnym...@gmail.com> wrote:
>>>>>>
>>>>>>> Okay, I solved my issue by adding an iptable entry for the
>>>>>>> return from wlan0 to eth1 (BB).
>>>>>>>
>>>>>>> * sudo iptables -A FORWARD -i wlan0 -o eth1 -j ACCEPT*
>>>>>>>
>>>>>>>
>>>>>>> Now pinging '8.8.8.8' from the BB works as expected.
>>>>>>>
>>>>>>> *root@beaglebone:~# ping -I usb0 8.8.8.8*
>>>>>>> *PING 8.8.8.8 (8.8.8.8) from 192.168.7.2 usb0: 56(84) bytes of data.*
>>>>>>> *64 bytes from 8.8.8.8 <http://8.8.8.8>: icmp_seq=1 ttl=103
>>>>>>> time=17.9 ms*
>>>>>>> *64 bytes from 8.8.8.8 <http://8.8.8.8>: icmp_seq=2 ttl=103
>>>>>>> time=15.8 ms*
>>>>>>> *64 bytes from 8.8.8.8 <http://8.8.8.8>: icmp_seq=3 ttl=103
>>>>>>> time=15.3 ms*
>>>>>>> *64 bytes from 8.8.8.8 <http://8.8.8.8>: icmp_seq=4 ttl=103
>>>>>>> time=15.7 m*
>>>>>>>
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Jon
>>>>>>>
>>>>>>> On Sat, May 16, 2020 at 12:29 PM Robert Heller <hel...@deepsoft.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> At Sat, 16 May 2020 13:32:03 -0400 beagleboard@googlegroups.com
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> >
>>>>>>>> > Jon,
>>>>>>>> >
>>>>>>>> > So you can ssh from the PC to the BB and ssh to the PC from the
>>>>>>>> BB...
>>>>>>>> >
>>>>>>>> > So the two are talking. Hum.
>>>>>>>> >
>>>>>>>> > Have you checked the firewall on the PC side to make sure it is
>>>>>>>> allowing
>>>>>>>> > traffic from 192.168.7 out?
>>>>>>>>
>>>>>>>> And is it set to forward IP packets?  You might need to have the PC
>>>>>>>> implement
>>>>>>>> NAT and/or Masquading.  And yes, check the firewall.
>>>>>>>>
>>>>>>>> >
>>>>>>>> >
>>>>>>>> > On Sat, May 16, 2020 at 12:53 PM jonnymo <jonnym...@gmail.com>
>>>>>>>> wrote:
>>>>>>>> >
>>>>>>>> > > I can ssh between the PC and the BB via 192.168.7.x and back
>>>>>>>> without
>>>>>>>> > > issue.
>>>>>>>> > > However, no traffic is sent out passed the wireless connection.
>>>>>>>> > >
>>>>>>>> > > Jon
>>>>>>>> > >
>>>>>>>> > >
>>>>>>>> > > On Sat, May 16, 2020 at 9:44 AM Kenneth Martin <
>>>>>>>> ken.unix....@gmail.com>
>>>>>>>> > > wrote:
>>>>>>>> > >
>>>>>>>> > >>
>>>>>>>> > >> *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 <jonnym...@gmail.com>
>>>>>>>> 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 <
>>>>>>>> ken.unix....@gmail.com> 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 beagleboard+unsubscr...@googlegroups.com.
>>>>>>>> > >>>> 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
>>>>>>>> > >>> beagleboard+unsubscr...@googlegroups.com.
>>>>>>>> > >>> 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 beagleboard+unsubscr...@googlegroups.com.
>>>>>>>> > >> To view this discussion on the web visit
>>>>>>>> > >>
>>>>>>>> https://groups.google.com/d/msgid/beagleboard/CAJXSPs83vAiDHARKiEQ-i-UhvL7Rx3odCLf4BYjUzP5tA1pmAw%40mail.gmail.com
>>>>>>>> > >> <
>>>>>>>> https://groups.google.com/d/msgid/beagleboard/CAJXSPs83vAiDHARKiEQ-i-UhvL7Rx3odCLf4BYjUzP5tA1pmAw%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 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
>>>>>>>> > > beagleboard+unsubscr...@googlegroups.com.
>>>>>>>> > > To view this discussion on the web visit
>>>>>>>> > >
>>>>>>>> https://groups.google.com/d/msgid/beagleboard/CAG99bkoJwoGQjpHGdybUojycZpAyNifKP3HHwgdZq4UNFfMJ1w%40mail.gmail.com
>>>>>>>> > > <
>>>>>>>> https://groups.google.com/d/msgid/beagleboard/CAG99bkoJwoGQjpHGdybUojycZpAyNifKP3HHwgdZq4UNFfMJ1w%40mail.gmail.com?utm_medium=email&utm_source=footer
>>>>>>>> >
>>>>>>>> > > .
>>>>>>>> > >
>>>>>>>> >
>>>>>>>>
>>>>>>>> --
>>>>>>>> Robert Heller             -- 978-544-6933 Cell: 413-658-7953 GV:
>>>>>>>> 978-633-5364
>>>>>>>> Deepwoods Software        -- Custom Software Services
>>>>>>>> http://www.deepsoft.com/  -- Linux Administration Services
>>>>>>>> hel...@deepsoft.com       -- Webhosting Services
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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/20200516192904.5AE44223E69%40sharky4.deepsoft.com
>>>>>>>> .
>>>>>>>>
>>>>>>> --
>>>>>>> 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/CAG99bkqk0pq63Bud1ave3D5u15cmPmXaaPvn9pC8Mj-HRHAaLA%40mail.gmail.com
>>>>>>> <https://groups.google.com/d/msgid/beagleboard/CAG99bkqk0pq63Bud1ave3D5u15cmPmXaaPvn9pC8Mj-HRHAaLA%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 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
>>>>> beagleboard+unsubscr...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/beagleboard/CAFZwMKJ%3DqAGFrxssxs9QxWu-dqQ%2BK9FagDDiQhWvvo3LvVm5OQ%40mail.gmail.com
>>>>> <https://groups.google.com/d/msgid/beagleboard/CAFZwMKJ%3DqAGFrxssxs9QxWu-dqQ%2BK9FagDDiQhWvvo3LvVm5OQ%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 beagleboard+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/beagleboard/CAJXSPs8_1Xsg4rNjBiJ8zQFa3ipNrU2y5i9yuwBLq3db_9RMNA%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/beagleboard/CAJXSPs8_1Xsg4rNjBiJ8zQFa3ipNrU2y5i9yuwBLq3db_9RMNA%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 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
>>> beagleboard+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beagleboard/CAFZwMKK5K2EyUQa8CynrzmOLUVkkrmV6H8EzmWzigfGbb-8_XA%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/beagleboard/CAFZwMKK5K2EyUQa8CynrzmOLUVkkrmV6H8EzmWzigfGbb-8_XA%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 beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/CAJXSPs8nLrfCthjdmWErQg%3DUrufjG_WZfWEtMC%2B90tcWxO34yA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/beagleboard/CAJXSPs8nLrfCthjdmWErQg%3DUrufjG_WZfWEtMC%2B90tcWxO34yA%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 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
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAFZwMK%2B2VgTm%3DG3VZFd0%3DD1Hv7k%2BwF99n7fcdL_OgJgGS3iUtw%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CAFZwMK%2B2VgTm%3DG3VZFd0%3DD1Hv7k%2BwF99n7fcdL_OgJgGS3iUtw%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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAJXSPs_m29EohBSBiEiv4VRPhAFUZeT_SRXAJ9zvWG%3DZPtkf2g%40mail.gmail.com.

Reply via email to