'eth1' instead of 'usb0'
 

I am working on USB Connectivity between android 2.1 Host and Windows Mobiles 6.1 device...When I connect the windows mobile device to android host through USB (in RNDIS Mode), It is appearing as 'eth1' interface instead of 'usb0' interface.
Why 'eth1' instead of 'usb0' ?
Does behaviour of 'eth1' is same as 'usb0'?

Please provide me some help...
Thanks in advance

Regards,
Ganesh

It is using tcp/ip to access.

It should have an ip address in ifconfig to see also.

Thanks very much for your support.

Sorry...I didn't give much info on what i have to do...

Case 1: I connected my Samsung Galaxy I7500 phone (android phone) to my Host (android) through USB Cable. It was in ECM Mode.It is detecting as 'usb0' device.

Case 2: I connected Windows Mobile to my Host(android) through USB Cable.It was in RNDIS Mode.It is detecting as 'eth1' device.

Being both phones connected through USB Cable, Why windows phone is detecting as 'eth1' device.

As u have said, It is recognising as network device. But 'usb0' is also network device. So why the difference comes?

[ECM and RNDIS are one and the same.]

Please help me...

Regards,
Ganesh

I guess the person who wrote the application/device driver decided it.

dunno exactly about the android. Is it really able to act as a networked device or are you simply seeing it as a usb storage?

yeah, sounds like it is acting as a network interface
post the output of 'ifconfig', i'll bet you eth1 has an ip address of some sort
example:

Re: 'eth1' instead of 'usb0'
 

Jefro and frieza,Thanks for Your Technical Support...

frieza, As you have told, I have posted the result of "ifconfig" when my windows mobiles phone is connected to android host.

Network Interface is appearing as 'eth1' instead of 'usb0'...But when my Samsung Galaxy (Android) phone is connected, Network Interface is 'usb0' only...

eth0 Link encap:Ethernet HWaddr 00:21:85:00:be:9c
inet addr:10.214.133.82 Bcast:10.214.135.255 Mask:255.255.252.0
inet6 addr: fe80::221:85ff:fe00:be9c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5748162 errors:0 dropped:0 overruns:0 frame:0
TX packets:17543 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:862718577 (862.7 MB) TX bytes:3851800 (3.8 MB)
Interrupt:18

eth1 Link encap:Ethernet HWaddr 80:00:60:0f:e8:00
inet addr:169.254.2.2 Bcast:169.254.2.255 Mask:255.255.255.0
inet6 addr: fe80::8200:60ff:fe0f:e800/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14 errors:7 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1264 (1.2 KB) TX bytes:5477 (5.4 KB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:240 (240.0 B) TX bytes:240 (240.0 B)


Jefro, When USB is connected in RNDIS Mode,It is not appearing as USB Mass Storage...It is getting an address 169.254.2.2,as i shown above...

yep, this one is your phone, which is probably acting as an internet access point if your other modem wasn't attached when you booted your computer.

you should look also at the 'lsusb' output
which should look something like
and do a search on the ID of your phone to find out the capabilities
(the ID is the number that looks like 1d6b:0002)
it might not be able to switch into other then a network card mode, and particularly not without proprietary software to do so, but i would at least look into it.

Re:'eth1' instead of 'usb0'
 

frieza, Thanks a lot...

So, You mean to say, I cannot change the interface from 'eth1' to 'usb0'...All these things are proprietary of microsoft corporation...And It is using network card drivers instead of USB Drivers...

Correct or not?

Please reply...
Thanks in advance...


Regards,
Ganesh

you are half right, it isn't proprietary of microsoft per-se, but rather proprietary of the company that built the machine, however if you look hard enough you *might* find a hack that lets you do it, or if you are lucky the company may have written linux drivers for the device, the situation isn't hopeless yet, but yes it is loading as a network card, at least that is wnat it appears. Like i said, run lsusb and do a search for the usb id of the devic, you might find a bit more technical documents on how to get it to work in linux.