Re: Trying to make usb networking work

Hello,

One more status...

I'm still unable to make the USB device work, through I tried several
high level drivers (g_zero, g_ether, g_file_storage). The GNU/Linux PC
host seems to identify the gadget without any issue (Everything looks
all right... I checked "usbview", amongst others), but I didn't manage
to use the functionality of the drivers.

Tomorrow, I'll try to run USB tests described on
http://linux-usb.sourceforge.net/usbtest/

So, I'm not successful yet, but I'm learning a lot!

Don't hesitate to give me advice that could help, or of course make your
own tests. That's easy:

    * You could use my initrd:
      http://michaelo.free.fr/pda/h2210/starterkit/initrd_minimum_usb_feb26
      . You have to insmod modules through their full paths. All the
      network utils you need should be there: ifconfig, ping... by the
      way, make sure you run ping in background (and use ps / kill to
      stop it later), as Ctrl C doesn't work on my shell!
    * You could use my kernel:
      http://michaelo.free.fr/pda/h2210/starterkit/zImage_minimum_usb_feb26

There could be issues happening only on my side... I'll be glad if
others prove that everything works fine for them! I still wonder what
happened to Koen...

Cheers,

    Michael.

> Thanks Phil!
>
> I checked that the destination MAC address is correct from the host side.
>
> Well, no progress yet today on this topic. However, I still have work
> to do: use the "gadget zero" module for testing USB gadget support.
>
> To be continued. Don't hesitate to make your own experiments!
>
> I copy some of you directly as the mail server seems to be down...
>
> :-)
>
> Michael.
>
>> On Tue, 2004-02-24 at 22:11, Michael Opdenacker wrote:
>>
>>
>>> 22:57:04.101789 arp who-has 192.168.0.201 tell 192.168.0.200
>>> 22:57:05.101226 arp who-has 192.168.0.201 tell 192.168.0.200
>>> 22:57:05.120230 arp reply 192.168.0.201 is-at 3e:3a:93:d7:3b:f0
>>> 22:57:05.121221 arp reply 192.168.0.201 is-at 3e:3a:93:d7:3b:f0
>>> ... (the same sequence starts again).
>>>
>>> It seems that the PC doesn't know where to reply to... I guess there
>>> should be an IP address instead of "3e:3a:93:d7:3b:f0"
>>>
>>
>>
>> No, that looks OK. ARP is the protocol which translates IP addresses
>> into MAC addresses. So, assuming that 3e:3a:93:d7:3b:f0 really is the
>> MAC that your host has picked for its usb0 interface, everything would
>> seem to be in order at that end. You could enable the -e option on
>> tcpdump to check that the destination MAC is also correct.
>>
>> p.
>>
>>
>>
>>
>>
>
>

-- 
Michael Opdenacker
http://opdenacker.org/