On Jul 26 13:30:01, Christiano F. Haesbaert wrote: > On 26 July 2012 13:01, Jan Stary <h...@stare.cz> wrote: > > On Jul 23 21:07:09, Stuart Henderson wrote: > >> On 2012-07-23, Jan Stary <h...@stare.cz> wrote: > >> >> On Jul 21, 2012 4:02 PM, "Jan Stary" <h...@stare.cz> wrote: > >> >> > >> >> > Is there any support present or planned for Ethernet over USB? > >> >> > > >> >> > http://en.wikipedia.org/wiki/Ethernet_over_USB#Treat_USB_as_an_Ethernet_network > >> >> > > >> >> > The motivation is to conenct my smartphone via USB to my workstation, > >> >> > thus having the phone connected to the net without either a wifi AP > >> >> > or using the operator's network data tarif. > >> > > >> > > >> > On Jul 21 16:32:31, Christiano F. Haesbaert wrote: > >> >> Yes see urndis > >> > > >> > My phone is Samsung GT-I5510, which is a Samsung Galaxy, > >> > which urndis(4) mentiones as supprted. Does someone use it > >> > as a urndis device? Should it report as a urndis device > >> > once connected via USB? I only get > >> > > >> > umass1 at uhub0 port 3 configuration 1 interface 0 "SAMSUNG Electronics > >> > Co., Ltd. Samsung Android USB Device" rev 2.00/4.00 addr 3 > >> > umass1: using SCSI over Bulk-Only scsibus4 at umass1: 2 targets, > >> > initiator 0 > >> > sd3 at scsibus4 targ 1 lun 0: <SAMSUNG, GT-I5510 Card, 0000> SCSI2 > >> > 0/direct removable serial.04e8681d551065d6a9ce > >> > > >> > i.e. it only exposes itself as a umass device. > >> > >> urndis(4) should connect to this phone in -current, > > > > Today's current/amd64 doesn't: > > > > umass1 at uhub0 port 3 configuration 1 interface 0 "SAMSUNG Electronics > > Co., Ltd. Samsung Android USB Device" rev 2.00/4.00 addr 3 > > umass1: using SCSI over Bulk-Only > > scsibus4 at umass1: 2 targets, initiator 0 > > sd3 at scsibus4 targ 1 lun 0: <SAMSUNG, GT-I5510 Card, 0000> SCSI2 0/direct > > removable serial.04e8681d551065d6a9ce > > > > Is someone is using a Samsung Galaxy as a urndis device, > > would you please share the dmesg? > > > > Note: "SAMSUNG GT-I5510" is probably not entirely the same as > > Samsung Galaxy S / S2" which the urndis manpage mentions. > > > > > > Did you go into your phone settings and enabled "USB Tethering ?"
No I didn't. Thanks. umass1 at uhub0 port 3 configuration 1 interface 0 "SAMSUNG Electronics Co., Ltd. Samsung Android USB Device" rev 2.00/4.00 addr 3 umass1: using SCSI over Bulk-Only scsibus4 at umass1: 2 targets, initiator 0 sd3 at scsibus4 targ 1 lun 0: <SAMSUNG, GT-I5510 Card, 0000> SCSI2 0/direct removable serial.04e8681d551065d6a9ce sd3 detached scsibus4 detached umass1 detached urndis0 at uhub0 port 3 configuration 1 interface 0 "SAMSUNG Electronics Co., Ltd. Samsung Android USB Device" rev 2.00/4.00 addr 3 urndis0: address 5a:88:2a:39:c9:e2 The umass detaching and urndis0 attaching is when I 'cancel' the mass storage offer from the phone and turn on tethering instead. > >> it presents an > >> ethernet-like interface, # ifconfig urndis0 urndis0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 lladdr 5a:88:2a:39:c9:e2 priority: 0 inet6 fe80::5888:2aff:fe39:c9e2%urndis0 prefixlen 64 scopeid 0x5 > >> normally you would run dhclient on a > >> computer to connect via the phone - the computer will then use the > >> phone for internet access via whichever method it's connected, > >> wifi/3g/gprs/etc). # dhclient urndis0 DHCPDISCOVER on urndis0 to 255.255.255.255 port 67 interval 3 DHCPOFFER from 192.168.42.129 (0e:5e:9f:f4:05:70) DHCPREQUEST on urndis0 to 255.255.255.255 port 67 DHCPREQUEST on urndis0 to 255.255.255.255 port 67 DHCPACK from 192.168.42.129 (0e:5e:9f:f4:05:70) bound to 192.168.42.164 -- renewal in 1800 seconds. DHCPACK from 192.168.42.129 (0e:5e:9f:f4:05:70) # arp -a ? (192.168.42.129) at 0e:5e:9f:f4:05:70 on urndis0 gw.stare.cz (192.168.111.1) at 00:0d:b9:12:9f:2d on re0 So yes, the urndis0 is now an ethernet device of my computer and I can run dhclient on it, and the phone will make me a DHCPOFFER. Anyway, the other way a round is what I am after ... > >> However....it's just a network interface, so I imagine that if you > >> have access to change the phone's routing table (which will probably > >> require the phone to be rooted) then I don't see why you couldn't > >> change the default route on the phone... Rooting the phone is what I was trying to avoid, A quick search for "android routing table" suggests it is not entirely impossible ...