Can not connect via USB

[KenUnix]

Got my BBB in today. Nice.

I am able to connect to it via the serial port header but can not connect via USB?

I tried installing the BONE_D64.exe drivers but all came back with red X's. I rebooted

the P.C. and tried again. Same results.

The serial connection is via Putty. and that works. I tried using putty

via SSH to 192.168.7.2 but all I get is a blank screen which eventually

times out..

Someone asked me today why am I fooling around with a BBB when

I can get the "real" thing on a P.C. or VM. I told him there are things

a BBB can do like add on capes, peripheral I/O that you can't really

do with a VM which if you could do it you would have to leave on 24/7

where as the BBB is a cute thing that once setup can run headless

at very little current. I just like it.

So, any help would be appreciated. Thanks.

[David Dyck]

What computer /os are you using to ssh from?

  ( if windows - did you check firewall settings? )

Also try hooking up a display/keyboard/mouse to enable networking 

--
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/e02dffbf-f374-4e6d-aff5-61b367d4c4ca%40googlegroups.com.

[Dennis Lee Bieber]

On Thu, 13 Feb 2020 17:51:44 -0800 (PST), in
gmane.comp.hardware.beagleboard.user KenUnix
<ken.unix.guy-Re5J...@public.gmane.org> wrote:


>
>*I tried installing the BONE_D64.exe drivers but all came back with red
>X's. I rebooted*
>

What came back "red X's"?

I'd suggest opening the device manager (admin privileges needed),
looking for any entry with an alert icon, and maybe deleting those devices.

I'm pretty certain the BONE_D64.exe drivers don't need to be explicitly
loaded -- I think Win10 can find a compatible driver online, automatically.
At least, I don't recall running that installer on my system when I had to
rebuild it for Win10.

With a BBB booted, I show a "Linux File-Stor Gadget USB Device" under
Disk Drives. Under Network Adapters I have a "Linux USB Ethernet/RNDIS
Gadget". I do have a "CDC ECM" item under "other devices" with a !-triangle
which says no driver is available for it. I suspect the "CDC ECM" device is
associated with the 192.168.6.2 address used on Mac connections.


https://en.wikipedia.org/wiki/RNDIS
"""
The USB Implementers Forum (USB-IF) defines at least three non-proprietary
USB communications device class (USB CDC) protocols with comparable
"virtual Ethernet" functionality; one of them (CDC-ECM) predates RNDIS and
is widely used for interoperability with non-Microsoft operating systems,
but does not work with Windows.
"""


Personally -- I don't use the USB network connection; I prefer a CAT-5
(or better) cable to a high-speed switch connected to my Uverse "modem".
Otherwise the BBB can't get to the outside world unless one configures
"internet connection sharing" and any needed openings in the Windows
firewall. I'm only using the USB to provide power as I have too many
wall-warts in use already -- I have one, if not two, power strips plugged
into my rather large UPS just to get room for wall warts.




--
Dennis L Bieber

[Kenneth Martin]

Dennis,

My laptop has an Ethernet port on it. What would be involved

in using that?  I don't mean to be stupid. Using the USB for

simply power, as you say.

I'm running Windows 10 64-bit 19.09 with all patches.

Thanks

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/bp4c4fhjrq6uvscp2nup0va1ah8ctftemg%404ax.com.

[Mark Lazarewicz]

You use this and a cable

10/100 Mbps 8 Port Fast Ethernet LAN Desktop RJ45 Network Switch Hub Adapter, Plug-and-Play - Walmart.com

10/100 Mbps 8 Port Fast Ethernet LAN Desktop RJ45 Network Switch Hub Adapter, Plug-and-Play - Walmart.com Free 2-day shipping. Buy 10/100 Mbps 8 Port Fast Ethernet LAN Desktop RJ45 Network Switch Hub Adapter, Plug-and-Play at Walmart.com

Sent from Yahoo Mail on Android

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/CAJXSPs8HbeFJHVpJ_48HNKW%2Bn1J9hKGu-a-h7HSv8r%3D8oCjN1g%40mail.gmail.com

.

[Kenneth Martin]

Mark,

Thanks for the EtherSwitch idea. I got rid of those along with a NAS server and 2 towers

some time ago when I was forced to re-locate.

There should be a way to get the USB port working??

Where I am now I am very limited on space. I would

think some body has got a BBB working with USB.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/435407280.2571493.1581662676293%40mail.yahoo.com.

[Mark Lazarewicz]

I remember year's ago seeing troubles this smells like a windows driver issue follow Dennis suggestions remove driver's in control panel. I always reboot after removing one item it might take multiple reboots all I have is a bb black and white I can't try it and I'm retired 🤪 As much as I miss pulling hair's out I have not dug all my stuff out you really need all the toys like serial cable's Routers, switches and for me JTAG if you want to be serious it doesn't take up much space. Start with quick start guide and keep your focus on one problem your juggling approaches and reply with details to those offering help like previous responder. Best of luck

Sent from Yahoo Mail on Android

On Fri, Feb 14, 2020 at 4:19 PM, Kenneth Martin

<ken.un...@gmail.com> wrote:

https://groups.google.com/d/msgid/beagleboard/CAJXSPs-dKNkSsOrcvmbE%3D13a79qti-o6Ee2%2BLwTBj%2B2oXtRv-g%40mail.gmail.com

.

[KenUnix]

Update

Trying to share Internet on Win-10 with BBB over USB. SSH 192.168.7.2 &

Serial to JTAG & Firefox to 192.168.7.2 to it ok???

Need to do "sudo apt install xxxx", etc.

Can not ping from BBB to external address. I.E 8.8.8.8, or 23.194.117.73

Route shows

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.252 U     0      0        0 usb1
192.168.7.0     0.0.0.0         255.255.255.252 U     0      0        0 usb0

I think I have everything in Win-10 net connections OK. If they are

wrong I could not Firefox or SSH to it correct.

[Robert Heller]

Is the Win-10 set up to forward packets? On a *Linux* desktop it would be

sysctl -w net.ipv4.ip_forward=1

What the mess-windows equivalent of this is I have no clue. But without it,
all the beagle can do is talk to the mess-windows box and not the internet.


>
>
> >
> >
>

--
Robert Heller -- 978-544-6933 Cell: 413-658-7953
Deepwoods Software -- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services
hel...@deepsoft.com -- Webhosting Services

[Kenneth Martin]

Robert,

===> Is the Win-10 set up to forward packets?

That's where I'm stuck and need a little help/

--
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...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/20200215201409.94D6E26C0173%40sharky3.deepsoft.com.

[Dennis Lee Bieber]

On Sat, 15 Feb 2020 15:18:28 -0500, in gmane.comp.hardware.beagleboard.user
Kenneth Martin <ken.unix.guy-Re5J...@public.gmane.org>
wrote:

>Robert,
>
>===> Is the Win-10 set up to forward packets?
>
>That's where I'm stuck and need a little help/
>

Google:
Win10 Internet Connection Sharing

as a starting point.


--
Dennis L Bieber

[KenUnix]

Bob,

In my efforts I have gone and screwed up routing on the BBB.

I now can only access via the JTAG serial port.

The BBB can't ping 192.168.7.1 the Win-10 address and the

P.C. can't ping 192.168.7.2 either

This is what's in /etc/network/interfaces

iface usb0 inet static
    address 192.168.7.2
    netmask 255.255.255.252
    network 192.168.7.0
    gateway 192.168.7.1
    dns-nameservers 8.8.8.8
    post-up route add default gw 192.168.7.1

Then to add default

sudo /sbin/route add default gw 192.168.7.2

It did work, but now not. Any help is appreciated. Sorry to bother.

On Saturday, February 15, 2020 at 9:34:49 PM UTC-5, Dennis Bieber wrote:

On Sat, 15 Feb 2020 15:18:28 -0500, in gmane.comp.hardware.beagleboard.user

[Dennis Lee Bieber]

On Sat, 15 Feb 2020 20:12:31 -0800 (PST), in
gmane.comp.hardware.beagleboard.user KenUnix

<ken.unix.guy-Re5J...@public.gmane.org> wrote:

>Bob,
>
>In my efforts I have gone and screwed up routing on the BBB.
>
>I now can only access via the JTAG serial port.
>
>The BBB can't ping 192.168.7.1 the Win-10 address and the
>P.C. can't ping 192.168.7.2 either
>
>This is what's in /etc/network/interfaces
>iface usb0 inet static
> address 192.168.7.2
> netmask 255.255.255.252
> network 192.168.7.0
> gateway 192.168.7.1
> dns-nameservers 8.8.8.8
> post-up route add default gw 192.168.7.1
>
>Then to add default
>sudo /sbin/route add default gw 192.168.7.2
>
>It did work, but now not. Any help is appreciated. Sorry to bother.
>

You keep fiddling with the BBB configuration, when it is the WINDOWS
configuration you need to change.

debian@beaglebone:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

<SNIP COMMENTED LINES>

# Ethernet/RNDIS gadget (g_ether)
# Used by: /opt/scripts/boot/autoconfigure_usb0.sh

iface usb0 inet static
address 192.168.7.2
netmask 255.255.255.252
network 192.168.7.0
gateway 192.168.7.1

debian@beaglebone:~$


Pulling the CAT-5 cable from my BBB and rebooting... Then connecting
via PuTTY...

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.252 U 0 0 0
usb1
192.168.7.0 0.0.0.0 255.255.255.252 U 0 0 0
usb0

debian@beaglebone:~$

I do NOT have Internet Connection Sharing configured on Windows, so am
unable to ping anything outside of 192.168.7.1. If I plug in the CAT-5
cable, I show...

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.252 U 0 0 0
usb1
192.168.7.0 0.0.0.0 255.255.255.252 U 0 0 0
usb0

debian@beaglebone:~$



--
Dennis L Bieber

[KenUnix]

Actually what I had to do follows for Internet access. Took some trial and error.

Out of the box the IP addresses 192.168.7.x are only good between two devices.

Example a Laptop and the BBB.

If you want Internet access to do updates or whatever do the following

In /etc/network/interfaces make the following changes

iface usb0 inet static

    address 192.168.137.2    <=== 137 was used because Windows insisted on it to do WiFi sharing 7 no go

    netmask 255.255.0.0

    network 192.168.137.0    <=== 137 was 7 originally

    gateway 192.168.137.1    <=== What Windows assigned to the adapter in Windows-10 19.09 64-bit home

    dns-nameservers 8.8.8.8  <=== Point to nameserver

    post-up route add default gw 192.168.137.1  <== Add default gateway. Auto up.

debian@beaglebone:~$ route

Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

default         192.168.137.1   0.0.0.0         UG    0      0        0 usb0  <== Updated automatic entry

192.168.0.0     0.0.0.0         255.255.0.0     U     0      0        0 usb0

192.168.6.0     0.0.0.0         255.255.255.252 U     0      0        0 usb1

debian@beaglebone:~$

On the Windows side make sure the Network connection for the BBB or Ethernet 2

that the TCP/IP V4 setting is set to the 137 address from above. Save it then bring

up the WiFi  settings / Properties / Sharing and allow sharing and choose either BBB

or Ethernet 2. Whichever is the new one added. Save it and exit.

Do a clean startup of the P.C. and the BBB.

It should work fine.

[Chris Green]

KenUnix <ken.un...@gmail.com> wrote:
> [-- multipart/alternative, encoding 7bit, 196 lines --]

>
>
> Actually what I had to do follows for Internet access. Took some trial and
> error.
>
>
> Out of the box the IP addresses 192.168.7.x are only good between two
> devices.
>
> Example a Laptop and the BBB.
>

True enough, the USB link is handy but can cause lots of confusion.

>
> If you want Internet access to do updates or whatever do the following
>

[skip complicated way of doing it]

Simply connect an ethernet (UTP Cat5 or Cat6) cable from the RJ45
socket on the BBB to your router, the BBB will have then internet
access (assuming your router is set up to provide internet access of
course).

The router (if as is usually the way) runs as a DHCP server and will
assign an IP address to the BBB. If you want to access the BBB from
another computer on your router's LAN then you need to find out what
this address is.

--
Chris Green
·

[KenUnix]

Chris,

If you don't have a router or Ethernet switch and only have access

via your computers WiFi then what I did was make a change to

one file on the BBB and one change to your P.C.'s network

connection for the BBB.

sudo nano /etc/network/interfaces

iface usb0 inet static
    address 192.168.137.2

    netmask 255.255.0.0
    network 192.168.137.0
    gateway 192.168.137.1

    dns-nameservers 8.8.8.8

    post-up route add default gw 192.168.137.1

Change entry on P.C. Reboot BBB. Now access

BBB using 192.168.137.2

ssh to 192.168.137.2

Firefox to 192.168.137.2

Putty ssh to 192.168.137.2

This change is persistent any only needs to be

done once. Not complicated and works great.

After changes are made you can now get the

date / time automatically. Simply install ntpdate.

sudo apt update

sudo apt install ntpdate

Then one time

sudo cp -f /usr/share/zoneinfo/America/New_York /etc/localtime

Another example

sudo cp -f /usr/share/zoneinfo/Europe/Berlin /etc/localtime

Then at boot time

sudo /usr/sbin/ntpdate -b -s -u 0.north-america.pool.ntp.org

The above can be put in a shell script. Check for correct

timezone and date using

date

If wrong see zoneinfo directory to find YOUR time zone.

If you are not in North America change

0.north-america.pool.ntp.org

To see YOUR country. See

https://www.pool.ntp.org/zone/@

The above works, works great and is not over complicated.

And only needs to be done once then your BBB will have

the correct date / time and Internet access.

I also added a small program that's been around for years

in Linux / Unix called 'ed' a line editor. It's small and fast

supports 'here' input and redirection. To get it

sudo apt install ed

See https://www.computerhope.com/unix/ued.htm

And https://www.gnu.org/software/ed/manual/ed_manual.html

[Rajesh Kulkarni]

Hi Ken,

I followed steps given by Drew Fustini. And was able to connect to the internet temporarily , but as soon as I rebooted I could not. You seem to have figured out the way to make BBB connect via Beaglebone. I am using Ubuntu as my host PC to connect to BBB.

So if I understand correctly all I need to do is add the following lines in my network/interfaces file ?

iface usb0 inet static
    address 192.168.137.2
    netmask 255.255.0.0
    network 192.168.137.0
    gateway 192.168.137.1

    dns-nameservers 8.8.8.8
    post-up route add default gw 192.168.137.1

And this is what my netstat -rn looks like

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

1. I can successfully ping 192.168.7.1 . But whenever I ping 8.8.8.8 (once I reboot) , all I see in response is "From 192.168.7.1 icmp_seq=1 Destination Host unreachable".

So my gateway is set correctly and ping to it, but for some reason it can not ping through it to 8.8.8.8.  Doesn't make sense.

2. How did you get the number 137 ?

3. According to Drew Fustinis post (https://gist.github.com/pdp7/d2711b5ff1fbb000240bd8337b859412 )  entering the following command "debian@beaglebone:~$ cat /etc/resolv.conf"


 should get my the response "nameserver 8.8.8.8".

 But the response I get is  "nameserver 127.0.0.1"  which is locat host , and I don't why I get this response. And I tried to edit that file manually but it gets overwritten after every reboot.

Any help is appreciated. Thank you for your time . :)

And you said the 137 is the

[KenUnix]

So if I understand correctly all I need to do is add the following lines in my network/interfaces file ?

iface usb0 inet static
    address 192.168.137.2
    netmask 255.255.0.0
    network 192.168.137.0
    gateway 192.168.137.1

    dns-nameservers 8.8.8.8
    post-up route add default gw 192.168.137.1

 Make 2 changes so it reads

iface usb0 inet static
    address 192.168.137.2
    netmask 255.255.0.0
    network 192.168.137.0

    nameservers 8.8.8.8
    gateway 192.168.137.1

The 192.168.137 is based on the address supplied by the host.

Also this assumes you are NOT using connmanctl. That does its own thing.

Let me know if this helps.

The entire /etc/network/interfaces looks like (in my case)

# The loopback network interface
auto lo
iface lo inet loopback

iface usb0 inet static
    address 192.168.137.2
    netmask 255.255.0.0
    network 192.168.137.0

    nameservers 8.8.8.8
    gateway 192.168.137.1

 

[Robert Nelson]

HEADS up!! Starting with 2020.04.06 image's this ^ will no longer
work.. With having too many random config location for usb0 having to
coordinate with dnsmasq/softap/etc.. This was re-written to use one
location:

/etc/default/bb-boot

Specifically this section:

USB_CONFIGURATION=enable
#Its assumed usb0 is always enabled, usb1 can be disabled...
USB0_SUBNET=192.168.7
USB0_ADDRESS=192.168.7.2
USB0_NETMASK=255.255.255.0

USB1_ENABLE=enable
USB1_SUBNET=192.168.6
USB1_ADDRESS=192.168.6.2
USB1_NETMASK=255.255.255.0

DNS_NAMESERVER=8.8.8.8

These values are then used by these 4 scripts on all board variants
(Classic, with WiFi, etc..)

https://github.com/beagleboard/customizations/tree/master/usr/bin

Regards,

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

[KenUnix]

 Robert,

The proper (official) point to setup Ethernet now?  And the steps involved to make that your default method of transport..

In other words use USB for P.C. <> BBB but use Eth0 for Internet access.

I assume connmanctl is still for WiFi if one has WiFi.

Thanks

[Robert Nelson]

No, my email was in reference for usb0/usb1/SoftAp0 as
dnsmasq/hostapd/etc are involved..

[Rajesh Kulkarni]

I have installed the latest debian image on my BBB. And I don't know how to proceed with getting the internet to work via USB .

Does making the following changes in /etc/default/bb-boot get you a  internet connection ? (I mean via Wifi as a gateway BBB via USB<-->UBUNTU<-> Wifi  )

Best

Rajesh
On Tuesday, May 5, 2020 at 8:42:45 AM UTC-7, RobertCNelson wrote:

[Robert Nelson]

On Tue, May 12, 2020, 10:58 PM Rajesh Kulkarni <rajkul...@gmail.com> wrote:

I have installed the latest debian image on my BBB. And I don't know how to proceed with getting the internet to work via USB .

Does making the following changes in /etc/default/bb-boot get you a  internet connection ? (I mean via Wifi as a gateway BBB via USB<-->UBUNTU<-> Wifi  )

Just use iptables on your Ubuntu host:

https://github.com/RobertCNelson/boot-scripts/blob/master/network/doc-debian-setup.md

And run this script on the beagle

sudo /opt/scripts/network/usb_linux_usb0_ics.sh

Regards,

[Rajesh Kulkarni]

Hi Robert,

I tried the script on my PC Ubunutu host .

All commands went through except for the last two, for which the error message was something like : 

update-alternatives: error: alternative /usr/sbin/arptables-legacy for arptables not registered; not setting

update-alternatives: error: alternative /usr/sbin/ebtables-legacy for ebtables not registered; not setting

 

And after that when I ran the script on my BBB all I got was :

debian@beaglebone:~$ sudo /opt/scripts/network/usb_linux_usb0_ics.sh            

SIOCADDRT: File exists                                                          

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.                                    

From 192.168.7.1 icmp_seq=1 Destination Host Unreachable    

And the IP was unreachable. Is it something which is trivial and I am doing wrong ?.

One more question in the following command :

sudo iptables --table nat --append POSTROUTING --out-interface eth0 -j MASQUERADE
sudo iptables --append FORWARD --in-interface eth1 -j ACCEPT

I would want to use my wifi id instead of eth0 if I want the internet to go through PC Host wifi , right ?And my eth0 is 192.168.7.1 & eth1 is 192.168.6.1. Is it encouraged to use eth1 for BBB on Linux instead of 192.168.7.1 ?

[jonnymo]

You may need to install the missing arptables and ebtables if they are not already installed:

  sudo apt-get install -y iptables arptables ebtables

Cheers,

Jon

--

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/68dfb039-f96d-4a87-b1db-d107c8dd5939%40googlegroups.com.

[Robert Nelson]

On Wed, May 13, 2020 at 1:20 AM jonnymo <jonn...@gmail.com> wrote:
>
> You may need to install the missing arptables and ebtables if they are not already installed:
>
> sudo apt-get install -y iptables arptables ebtables

Side note, now that Debian 10.x Buster and Ubuntu 20.04 are shipping
nftables by default

anyone want to dive and try getting nftables to do the same thing as:

sudo iptables --table nat --append POSTROUTING --out-interface eth0 -j
MASQUERADE
sudo iptables --append FORWARD --in-interface eth1 -j ACCEPT

[Rajesh Kulkarni]

I reinstalled the latest debian on BBB. 

I was able to install arptables ebtables on my host side.Everything went well .

 But still I am not able to ping 8.8.8.8 or any DNS name for that matter.

And still get the same output :

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.                                    

From 192.168.7.1 icmp_seq=1 Destination Host Unreachable  

1. Is it because of connmanctl(on the host or BBB) by any chance ?

2. My "netstat -rn"  of BBB looks fine 

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

3. The BBB website https://beagleboard.org/upgrade has these instructions which did work, but after restart didn't last 

    In your host operating system, you'll need to share your Internet connection back to the board. With an Ubuntu host, use the utility "nm-connection-editor".

sudo ip addr flush dev usb0
sudo dhclient usb0

I am really confused  .

[KenUnix]

Looks to me that all you need is;

sudo route add default gw 192.168.7.1

 

[Robert Heller]

At Thu, 14 May 2020 19:19:47 -0700 (PDT) beagl...@googlegroups.com wrote:

>
>
>
> I reinstalled the latest debian on BBB.

> I was able to install *arptables ebtables on my host side.*Everything went

> well .
> But still I am not able to ping 8.8.8.8 or any DNS name for that matter.
>

> *And still get the same output :*
> *PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
> *
> *From 192.168.7.1 icmp_seq=1 Destination Host Unreachable *

>
> 1. Is it because of connmanctl(on the host or BBB) by any chance ?
>

> 2. My "*netstat -rn*" of BBB looks fine

> 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
>
> 3. The BBB website https://beagleboard.org/upgrade has these instructions
> which did work, but after restart didn't last
> In your host operating system, you'll need to share your Internet
> connection back to the board. With an Ubuntu host, use the utility
> "nm-connection-editor".
>
> sudo ip addr flush dev usb0
> sudo dhclient usb0
>
>
> I am really confused .

One thing that is needed is that the upstream host (your PC?) needs to be
doing IP forwarding. I don't know what that is for either Mess-Windows or
MacOSX, but for Linux, you need something like:

sysctl -w net.ipv4.ip_forward=1

somewhere in the host's startup. Where and how depends on the distro, kernel
version, distro vintage, type of init (sysV, upstart, systemd, etc.).

>
> On Wednesday, May 13, 2020 at 8:29:45 AM UTC-7, RobertCNelson wrote:
> >

> > On Wed, May 13, 2020 at 1:20 AM jonnymo <jonn...@gmail.com <javascript:>>

> > wrote:
> > >
> > > You may need to install the missing arptables and ebtables if they are
> > not already installed:
> > >
> > > sudo apt-get install -y iptables arptables ebtables
> >
> > Side note, now that Debian 10.x Buster and Ubuntu 20.04 are shipping
> > nftables by default
> >
> > anyone want to dive and try getting nftables to do the same thing as:
> >
> > sudo iptables --table nat --append POSTROUTING --out-interface eth0 -j
> > MASQUERADE
> > sudo iptables --append FORWARD --in-interface eth1 -j ACCEPT
> >
> > Regards,
> >
> > --
> > Robert Nelson
> > https://rcn-ee.com/
> >
>

--
Robert Heller -- 978-544-6933 Cell: 413-658-7953 GV: 978-633-5364

[Rajesh Kulkarni]

@Ken Yep, I already did add the default gateway and the response I get is "already exists" .

@Robert, yep I un-commented that part.

root@sp3:~# grep forward /etc/sysctl.conf
# Uncomment the next line to enable packet forwarding for IPv4
net.ipv4.ip_forward=1
# Uncomment the next line to enable packet forwarding for IPv6 

net.ipv6.conf.all.forwarding=1

followed by this command "sysctl -a |fgrep .forwarding |grep ^net |grep ipv4"

But nothing seems to be helping, 

Also should I try using usb1 i.e. 192.68.6.2 ?? As of now the way I am trying is to get my 192.168.7.2 requests to forward to my PC wifi connection.

sudo iptables --table nat --append POSTROUTING --out-interface wlp8s0 -j MASQUERADE (wlp8s0 is my PC Wifi )
sudo iptables --append FORWARD --in-interface eth0 -j ACCEPT (eth0 is 192.168.7.2)

 

On Thu, May 14, 2020 at 7:33 PM KenUnix <ken.un...@gmail.com> wrote:

Looks to me that all you need is;

sudo route add default gw 192.168.7.1

 

--

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/0d0b9b06-7a32-42af-8c11-27735b28c869%40googlegroups.com.

[Kenneth Martin]

I don't know what you are doing with

root@sp3:~# grep forward /etc/sysctl.conf
# Uncomment the next line to enable packet forwarding for IPv4
net.ipv4.ip_forward=1
# Uncomment the next line to enable packet forwarding for IPv6 

net.ipv6.conf.all.forwarding=1

followed by this command "sysctl -a |fgrep .forwarding |grep ^net |grep ipv4"

Can you upload a copy of the script?

All I can say about the route add default is your route printout shows a default route on the BBB

but it's 0.0.0.0 in the left column.  Try   sudo route delete default gw 192.168.7.1  then re-enter it as

sudo route add default gw 192.168.7.1   then do the route list again and see if the 0.0.0.0 in

the first column is replaced by the word default. And if it is try ping 8.8.8.8 again.

Let me know.

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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAFZwMK%2BiR%2BET9Hoj2_HXiSetURWXm6XU%3D0s1RdU_QUV%3Dwpig_g%40mail.gmail.com.

[Rajesh Kulkarni]

Hi Ken,

I used the grep forward /etc/sysctl.conf after following drew's post about setting up a USB connection.

https://docs.google.com/viewer?a=v&pid=forums&srcid=MTczNzY5MjQ0Njg2MjQ5NDgzODcBMDAwNDQ0MDU5Mzk5ODM4OTQwMTcBSkFWYVlKS3BBZ0FKATAuMQEBdjI

I did delete the default gw and set i back to 192.168.7.2 But it doesn't help. I still see 0.0.0.0 on the left column. All I get is :

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. From 192.168.7.1 icmp_seq=1 Destination Host Unreachable From 192.168.7.1 icmp_seq=2 Destination Host Unreachable From 192.168.7.1 icmp_seq=3 Destination Host Unreachable From 192.168.7.1 icmp_seq=4 Destination Host Unreachable From 192.168.7.1 icmp_seq=5 Destination Host Unreachable

Also my /etc/network/interfaces contains following lines :

#auto lo

#iface lo inet loopback

Should I uncomment these lines and save ?Will it make a difference ?

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

So I used 

sudo iptables --table nat --append POSTROUTING --out-interface wlp8s0 -j MASQUERADE (wlp8s0 is my PC Wifi )

sudo iptables --append FORWARD --in-interface eth0 -j ACCEPT (eth0 is 192.168.7.2)

Any help is appreciated !

Best Raj

root@rajeshpc:/home/rajesh# ifconfig

To unsubscribe from this group and stop receiving emails from it, send an email to beagl...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/0d0b9b06-7a32-42af-8c11-27735b28c869%40googlegroups.com.

--
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 beagl...@googlegroups.com.

[KenUnix]

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.

[jonnymo]

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 table

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

192.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: 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: 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: 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

--
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/21cc8527-1fd9-4f9f-bd7d-7d6f46f25f58%40googlegroups.com.

[Kenneth Martin]

On the Beaglebone can you ping 192.168.7.1 ?

On my Beaglebone here is what I get

debian@beaglebone:~$ netstat -rn

Kernel IP routing table
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.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.

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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAG99bkr7RGpa_wmvtjbw1JFkHe381xE%3Dn9-pJ0EmuD4W2itMDQ%40mail.gmail.com.

[jonnymo]

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

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAJXSPs83vAiDHARKiEQ-i-UhvL7Rx3odCLf4BYjUzP5tA1pmAw%40mail.gmail.com.

[Kenneth Martin]

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?

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAG99bkoJwoGQjpHGdybUojycZpAyNifKP3HHwgdZq4UNFfMJ1w%40mail.gmail.com.

[Robert Heller]

At Sat, 16 May 2020 13:32:03 -0400 beagl...@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 <jonn...@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.un...@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 <jonn...@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)*

> >>>> <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...@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...@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...@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>
> > .

[jonnymo]

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: icmp_seq=1 ttl=103 time=17.9 ms

64 bytes from 8.8.8.8: icmp_seq=2 ttl=103 time=15.8 ms

64 bytes from 8.8.8.8: icmp_seq=3 ttl=103 time=15.3 ms

64 bytes from 8.8.8.8: icmp_seq=4 ttl=103 time=15.7 m

Cheers,

Jon

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/20200516192904.5AE44223E69%40sharky4.deepsoft.com.

[Rajesh Kulkarni]

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 

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAG99bkqk0pq63Bud1ave3D5u15cmPmXaaPvn9pC8Mj-HRHAaLA%40mail.gmail.com.

[Rajesh Kulkarni]

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

[Kenneth Martin]

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

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAFZwMKJ%3DqAGFrxssxs9QxWu-dqQ%2BK9FagDDiQhWvvo3LvVm5OQ%40mail.gmail.com.

[Rajesh Kulkarni]

Hi Kenneth,

I am using Debian Buster IoT Image 2020-04-06 .

Regards,

Rajesh

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAJXSPs8_1Xsg4rNjBiJ8zQFa3ipNrU2y5i9yuwBLq3db_9RMNA%40mail.gmail.com.

[Kenneth Martin]

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

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAFZwMKK5K2EyUQa8CynrzmOLUVkkrmV6H8EzmWzigfGbb-8_XA%40mail.gmail.com.

[Rajesh Kulkarni]

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           

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAJXSPs8nLrfCthjdmWErQg%3DUrufjG_WZfWEtMC%2B90tcWxO34yA%40mail.gmail.com.

[Kenneth Martin]

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

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAFZwMK%2B2VgTm%3DG3VZFd0%3DD1Hv7k%2BwF99n7fcdL_OgJgGS3iUtw%40mail.gmail.com.

[Rajesh Kulkarni]

Again , Thank you so much Kenneth !

I was wondering were you able to see all the boxes set to green when you visit the webserver of the beaglebone i.e. the getting started guide .?

Attached is a screenshot which shows only my Power and Boot to be successful, but requirements for other steps seemed not to be met yet. 

Did any one else experience this ?(and yes I am connected to the internet)

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAJXSPs_m29EohBSBiEiv4VRPhAFUZeT_SRXAJ9zvWG%3DZPtkf2g%40mail.gmail.com.

[Kenneth Martin]

Rajesh,

Yes, in my case from a P.C running Windows  file:///F:/START.htm  I can see and click on all the options.

What do you get if using your browser  enter  192.168.7.2 ?

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAFZwMK%2BcknbiSR7Zp8tgdQFS1CPFZFdgJ02DQfso0GeETVFESQ%40mail.gmail.com.

[Rajesh Kulkarni]

When I open the 192.168.7.2 page in my browser(chrome and Firefox ) It takes me to a cloud9 IDE  ,inside which a introduction.md file is shown which tells me to update my OS on my BBB(although it has the latest Debian) . 

And if I do go on to the “getting started” page via the cloud9 IDE NONE of the steps are highlighted in green.

Again I am able to successfully ping my PC host and BBB successfully. As a matter of fact I was able to run the program to blink LED which worked . But just the fact that I don’t see the same stuff that people do makes me think of there’s something wrong 

Rajesh

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAJXSPs-9svE2D_znEh01OeK2uw8TOyNEa8kYg05WLjaXyvW6dg%40mail.gmail.com.

[Kenneth Martin]

Rajesh, I am sorry I can not duplicate this problem.  I do know changes were made to default port numbers I.E. 80,8080,3000,etc.and one package was retired. Um, You mention Firefox which is what I use .  Do you have 'No Script' loaded? If so make sure Beaglebone (192.168.7.2) is set to trusted. Beyond this I would suggest opening a new report and stop adding to USB problem. Ken

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAFZwMKJQUOFYrt6veUNUTfueU_7QDpVqzWc5dRfY-WsV%2BjEGZg%40mail.gmail.com.