[SOLVED] USB-Ethernet adapter works only with router

äxl · 07-06-2013, 12:49 PM

Hi all. I'm using a cable modem and trying to connect through a USB-Ethernet adapter. I don't want to use the router because I don't need it with the desktop computer and thus it's a pointless consumer (about 4-5 watts). The adapter is actually only for an Android tablet (4.0.3) but I connected it to the PC (Squeeze) for testing.

The adapter's enclosure says "JP1082 No: 030818", PCB says JP1082-970. There's nothing printed on the chip.

On the included CD (USB LAN-RD9700) are driver for Mac and Win + Win CE and the source code for Win CE and Android. The Windows Logo Verification Report says "Shenzen Lian He An Xin Software Development Co,Ltd". The Win drivers say "Corechip Semiconductor, Inc.". The Android source is named jp1081_android.c and the headers say "JiaPeng NET JP1081 USB2NET" and "JiaPeng NET JP1081 one chip USB 1.1" written by jokeliujl <jokeliu@163.com> in 2010 under GPL v2. The Win CE source says "Davicom Inc."

I guess I could upload this somewhere ... if anyone's interested.

lsusb says "Bus 003 Device 004: ID 0fe6:9700 Kontron (Industrial Computer Source / ICS Advent) DM9601 Fast Ethernet Adapter"
nopaste of # lsusb -vd 0fe6:9700

I tried to compile the Android module but since it's from 2010 I guess I would also need an older kernel. Anyway when connected with my Android tablet through the router it connects with original module qf9700 and dhcpcd_eth0 just fine. I mostly think this is a hardware problem ...

On desktop PC (kernel 2.6.32) I patched the dm9601 like explained here: http://tech.firdooze.com/2011/11/16/...9601-on-linux/
I also tried out qf9700 from here: http://mquin.livejournal.com/178482.html
Both work - but of course only with router. The adapter is directly connected to the PC - no hub.

I'm using wicd with dhcpcd as I've read is recommended.
Also only with the router the LED of the adapter is lid.

Normal LAN
to modem

Code:

$ ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:1a:a0:4X:4X:X8  
          inet addr:37.5.X.X  Bcast:37.5.X.255  Mask:255.255.248.0
          UP BROADCAST RUNNING MULTICAST  MTU:576  Metric:1

Code:

$ netstat -nr
Destination     Gateway       Genmask         Flags   MSS Window  irtt Iface
37.5.X.0        0.0.0.0       255.255.248.0   U         0 0          0 eth0
0.0.0.0         37.5.X.254    0.0.0.0         UG        0 0          0 eth0

to router to modem

Code:

$ ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:1a:a0:4X:4X:X8  
          inet addr:192.168.0.199  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::21a:a0ff:fe4b:4eb8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

Code:

$ netstat -nr
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.0.0     *               255.255.255.0   U     0      0        0 eth0
default         192.168.0.1     0.0.0.0         UG    0      0        0 eth0

With adapter
to modem

Code:

$ ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 00:e0:4c:53:44:58  
          inet6 addr: fe80::2e0:4cff:fe53:4458/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1

Routing table is empty but dhcpcd gives:

Code:

dhcpcd.sh: interface eth1 has been configured with new IP=169.254.102.191
dhcpcd.sh: interface eth1 has been configured with old IP=169.254.102.191

to router to modem

Code:

$ ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 00:e0:4c:53:44:58  
          inet addr:192.168.0.198  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::2e0:4cff:fe53:4458/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

Code:

$ netstat -nr
Destination     Gateway         Genmask         Flags Metric Ref    Use 
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth1
0.0.0.0         192.168.0.1     0.0.0.0         UG    0      0        0 eth1

Output in Android should be similar.
So when I connect with the adapter directly to modem I don't get an IP and can't browse the web. Only when I interpose the router it works ...

On PC should I disable eth0 for eth1 to connect? And how?
Do I need the router because the modem is not giving enough power (->LED)?

273 · 07-06-2013, 07:34 PM

Can you get onto the internet if you plug the normal ethernet port of your PC into the modem? I ask because I think my cable modem is tied to the MAC address of the device used to initialise it. When I connected a router for the first time I had to use the MAC address cloning feature to take on the same MAC address as my PC before it would work and when I bought a new router I had to give that the same MAC address to use it.

äxl · 07-06-2013, 09:02 PM

Yes, connection directly to modem is how I always do it.
Can't say I remember having to adjust the MAC address. I installed the modem under fista years ago. The router came with the modem (from my cable provider) but was only activated for the tablet a year or so ago.

It's a Motorola SBV5121E modem and a D-Link DIR-615 router before someone asks.
The router manual says:
"For Cable users make sure Clone MAC address option is ticked during Wizard installation (or enter the registered MAC) and make sure the service has been enabled/connected and is operational."
Can't remember.

So you're saying I should spoof the MAC address of the adapter cloning the PC's?

273 · 07-06-2013, 09:10 PM

Quote:

Originally Posted by äxl

So you're saying I should spoof the MAC address of the adapter cloning the PC's?

You could try that, yes, though I wouldn't know how to go about it. You could check the router to see whether you did set it to clone the MAC address of your PCs network card though as if you didn't then it probably won't be that which is causing the problem.
If it is the MAC address and you can't find a way to change it for the USB network adaptor you may need to find out how to change the MAC address which is accepted by the modem form your cable provider.

äxl · 07-06-2013, 09:48 PM

This kinda makes sense. Well, it's late here.^^
Well just:

Code:

# ifconfig eth1 hw ether 00:e0:4c:X3:X4:X7

But I don't know if two devices with the same HWaddr are okay ...? Also would this explain that the LED isn't lid ...?

273 · 07-06-2013, 09:56 PM

Yes, having two devices with the same MAC address on the same subnet would be a no-no but since you can only plug one thing into the modem at a time you'll only have one device anyway? I'm not sure what makes the LEDs light on ethernet cards, sorry.

äxl · 07-06-2013, 10:13 PM

Yeah, right.
But sorry, still no connection. dhcpcd still gives a local link ...
Well, thanks so far. Gotta go to bed. Night.

äxl · 07-09-2013, 05:27 AM

I only now found the IP of my modem by pinging the DHCPDISCOVER address:

Code:

$ ping -b -w 3 255.255.255.255
WARNING: pinging broadcast address
PING 255.255.255.255 (255.255.255.255) 56(84) bytes of data.
64 bytes from 10.90.50.79: icmp_req=1 ttl=63 time=10.8 ms
64 bytes from 10.88.49.240: icmp_req=1 ttl=63 time=34.8 ms (DUP!)
64 bytes from 10.90.50.79: icmp_req=2 ttl=63 time=10.2 ms
64 bytes from 10.88.49.240: icmp_req=2 ttl=63 time=24.8 ms (DUP!)
64 bytes from 10.90.50.79: icmp_req=3 ttl=63 time=11.8 ms
64 bytes from 10.88.49.240: icmp_req=3 ttl=63 time=16.1 ms (DUP!)

--- 255.255.255.255 ping statistics ---
3 packets transmitted, 3 received, +3 duplicates, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 10.214/18.120/34.885/8.989 ms

So going to 10.90.50.79 showed me the login screen (which is also 192.168.100.1 duh).
Pinging 10.88.49.240 got me nowhere. Since it's a duplicate is this some kind of loopback?
After finding out the password I can browse through the interface but not set much. Only interesting thing is this:

Code:

# 	Known CPE MAC Address (Max 2) 	Status
1	00 22 10 XX XX XX		Static
2	00 1a a0 XX XX XX		Dynamic
3	00 24 01 XX XX XX		Dynamic

The first is the modem's own MTA MAC Address, second is my PC and third is the router.
Now this "Max 2" made me really nervous. After restarting the modem the router's MAC vanished but still the adapter wouldn't work. No LED, no MAC address. dhcpcd again gave me a local link.

newbeliever · 07-17-2013, 02:52 AM

When I had worked for our local cable company as an internet technician we ran into similar situations where the LED was lit, activity was shown but the system was not given an IP. The "Max 2" is the allotted number of CPE that can be connected to the device at the same time as you may have two IP's allotted on your account/ or based on surfboard standards you are allotted the LAN MAC and CPE MAC allowing only one IP.

Surfboard modems have a built in DHCP server that only activates if the cable modem does not get SYNC with the cable company, try disconnecting the cable from the modem and reboot the modem and see if you get a 192.x.x.x from the cable modem; this will narrow down to a modem or provider issue.

Don't know if this is any info to help but it is a step that we used to reestablish MAC provisioning to the modem. Once this was complete we would disconnect the CPE from the modem hook the modem back to cable company reboot the modem and establish SYNC then connect the CPE and 99/100 get IP from provider. This all stemmed back to a provisioning issue with the cable company as the MAC is bind to the MAC of the MODEM LAN MAC.

äxl · 07-18-2013, 10:05 AM

Thanks for your reply, newbeliever.
Directly connected to the modem the adapter's LED was never lid; the "Link" LED on the modem is also off.

When I disconnect from cable net, there's no difference. When I then connect the ethernet cable to the desktop PC the "Link" LED is on but all I can get is 169.254.x.x ... So this should simply be a modem issue.
I also get IPv4LL with the adapter. The adapter's MAC is not known to the modem's DHCP.

Is it possible to measure the voltage on the ethernet port (maybe through an opened up cable)?
What could I expect? 0.85 Volt, 1 Volt, 2 Volt?
Or maybe someone could just say that this modem is not capable to supply the adapter ...

äxl · 07-18-2013, 12:56 PM

*blush*
On my provider's forum someone asked if I'm using cross-over cables ...
Which I should! I only tried the straight throughs with the adapter - since everything worked with the router.
Seems the adapter doesn't know auto detection (Auto-MDIX) - which is understandable since it was cheap.