At home now, but don't recall USB settings of any sort there, just the
wired Ethernet adapter of my machine. I set that to the same subnet but
that's irrelevant. ifconfig on the Linux machine didn't show a USB
adapter, from memory.
I'll have to hunt around for USB adapter settings - they're probably
there somewhere!! Or Linux is not detecting the RNDIS adapter connection
perhaps. Is there an RNDIS equivalent of "msconn"?
My Linux abilities are on a par with my NuttX abilities...very very bad!
Which is the lesson I'm learning the very hard way...NuttX is extremely
hard if you don't know Linux :(
On 20/01/2022 18:08, Alan Carvalho de Assis wrote:
Hi Tim,
You we welcome!
Are your Linux usb interface on this 10.0.0.x range as well? Is they
are not in the same network class it will not work.
BR,
Alan
On 1/20/22, Tim<t...@jti.uk.com> wrote:
Following suggestions relating to FAT/MSD/USB I have been playing with
RNDIS
following the NuttX Channel video by Alan C. de Assis (thank you Alan -
only just found all of your videos!!).
It all builds OK and ifconfig suggests all is good:
nsh> ifconfig
lo Link encap:Local Loopback at UP
inet addr:127.0.0.1 DRaddr:127.0.0.1 Mask:255.0.0.0
eth0 Link encap:Ethernet HWaddr e0:de:00:ad:be:ef at UP
inet addr:10.0.0.2 DRaddr:10.0.0.1 Mask:255.255.255.0
But Linux (Ubuntu 20.04) doesn't "see" it and I can't ping it.
Connecting to Windows just results in loads of error messages in nsh to do
with unrecognised rndis messages. Leave that for another day.
If I try and do a local ping it suggests there's an error with sockets, or
ping?
nsh> ping 127.0.0.1
psock_socket: ERROR: socket address family unsupported: 2
socket: ERROR: psock_socket() failed: -106
ERROR: socket() failed: 106
nsh>
106 is endpoint already connected; it's the same whether the USB is
connected to the Linux machine or not.
As usual, any suggestions welcomed!!
