View Single Post
Posts: 252 | Thanked: 221 times | Joined on Jul 2010
#19
Ok, issue a) will hopefully be resolved with the new device. Note it has the same chipset as Trendnet's.

Issue b) was caused by the local network not having a DHCP server, so who knows where I was getting the DHCP packets from, and what was in them. I tried on a third LAN then, and it worked, except again I had issues a) and b).

Issue c) remains elusive. It seems here that Maemo applications dislike usb ethernet, so I am thinking of installing a dummy network as suggested there. Indeed, it seems like that would completely convince Maemo that I am connected to a network. Never done that, though. Tips, please?

@biketool, yeah, I don't really need need it, but there is a coolness/nerdiness factor involved. Also, once you do need it, it will be too late to try to make it work.

Originally Posted by chill View Post
I got this one:
http://trendnet.com/products/proddet...=280_TU2-ET100

It works "out of the box" (note my N900 setup in my signature, though). However:

a) on one network, I got the same "bogus packet" messages with udhcpc.

b) on another network, it works fine at first, but it seems that after a while the web browsers (microb and Opera) "forget" that they are connected, and never download the requested page; ping and wget from XTerminal still work. Also, turning on the online accounts in My Availability causes the N900 to connect to the default network (3G); this is even before the web browser problem sets in.

c) power consumption: the dongle runs pretty warm (though it can still be held) and will drain a full N900 battery in roughly an hour. The declared consumption is 178 mA.
__________________
21.2011.38-1Smaemo7 (CSSU Stable)
2.6.28.10power53 (not overclocked)
Yes, I search before posting.
 

The Following 2 Users Say Thank You to chill For This Useful Post: