root@arm:/var/log# 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.7.0 * 255.255.255.252 U 0 0 0 usb0
Thanks for your help group
so maybe your Windows system is blocking ip forwarding.
pinging 8.8.8.8 and google.com say the same thing because 8.8.8.8 is a name server out in the wild wild Internet and google.com is a server out in the same space.
Your route table looks like mine so what’s left is your host computer so I think you’ll find the answer searching for how or why Windows does ip forwarding.
But It was working before I flashed over the Angstrom image with Debian.
I’ll try undoing and redoing the commands on my PC when I get home.
if you changed the OS on the BBB then wouldn’t it look like a different device to your host and possible use different firewall rules? I’ve heard that sometimes Windows tries too hard to help.
I guess I just wanted to make sure that what I was trying to do should work…
it would seem you already did that by getting the Angstrom OS to work. Once you changed out that OS it’s just a matter of persuading the other OS(s) to do the same. Not really BBB related it would seem.
there has to be communication or else how could the route and nameserver be set on the BBB? Surely if this was the case it wouldn’t be an internet over USB issue because well, without the USB ethernet there can not be any Internet access.
I’ve pretty much given up on Windows years ago so what ever it’s called, something is probably not working on the Windows side because what was setup for Angstroms USB ethernet widget is probably not going to be also setup for the widget Debian would setup. I learned the pain of Windows long ago and know you can not assume anything with that platform involved.