Tags:
create new tag
, view all tags
iRulu 10.1" Model AX105 with Android 4.2

Networking

<Starting a rewrite>

There are a variety of reasons to connect your iRulu to your home network (LAN):

  • you might share one Internet connection among several computers on your home network
  • you might share files with other computers on your home network
  • you might print to a printer on your home network

<Arrgh! I fat fingered something and lost about 3 half decent paragraphs--trying to at least remember them, with cryptic notes--ok, got some cryptic notes back, but not written nearly as well as the first time...didn't even attempt, was just trying to recollect my thoughts>

I can also use an Ethernet connection not being shared on my LAN:

  • WiFi (like at a WiFi hotspot)
  • Wired Ethernet (I used to do this when I traveled on business before WiFi existed--might still happen occasionally, might find an RJ-45 jack in a hotel room, library, business, or ...)
  • 3G/4G cellphone connection--well, I could do this with the right type of dongle and SIM card--but usually more expensive than the other options

I can connect to my LAN either by WiFi or by a wired Ethernet connection, but I've found that some apps work with either WiFi or hard wired Ethernet (as they should) but some work only with one or the other. (In some cases I've contacted the developer and some of those have acknowledged it as a bug, at least one (Videoder) promising to fix it in the next release.)

The frustrating thing is that some things almost seemed like they required magical incantations--I'd try them one way and they wouldn't work, and I'd try them another way (with insignificant differences) and they did work. Examples:

  • When I tried to set up various forms of secure WiFi, they would not work if I reused the static IP that I had used for the unsecured WiFi. If I let the iRulu get a dynamic IP assigned via DHCP (even if it usually happened to be the same as the one used for non-secure WiFi), or if I assigned a new (previously unused) static IP it worked.

  • (I need to remember (or look up) the details--I wrote about this on another page--) When I first powered up the iRulu, the first thing I did was connect the USB / Ethernet adapter and connected hard-wired to the Ethernet, and that worked fine. Then I tried to plug in my USB keyboard and had a terrible time getting it to work (iirc, I got it to work very occasionally, but not consistently). At some point I decided to wipe the iRulu to its factory fresh state (that is, both clearing all user installed apps and data and doing a hardware reset). Then I plugged in the USB keyboard first--it worked fine, then (afterwards) plugged in the USB / Ethernet adapter--both have worked fine ever since. (Well, with the exception of some apps that work only via WiFi and some others that work only via hard wired Ethernet (alluded to above).) The details I forget at the moment include which port I plugged the keyboard into after the factory reset, and whether I used the OTG cable or the "ordinary" USB cable. (Since then, I've been using the OTG cable plugged into the Host port, but I've tried all four combinations and all work fine since the factory reset.) This is discussed in (slightly) more detail on [[][]].

  • When I first installed FTP server, it worked fine over the hardwired Ethernet link to my LAN. When I tried it over WiFi, it would not work. I don't remember (and don't think I made good notes) of the steps I took which eventually got it to work over WiFi (and I'm not 100% sure I've tried it again over the hardwired Ethernet link). I think that one of the things I did was to (completely) uninstall it, and then reinstall it while connected via WiFi--that might have been the key.

  • Perhaps related to that (and perhaps not), when I first tried pinging to / from the iRulu from / to another computer on my LAN, neither worked. Then I found some instructions that involved adding the IP of the iRulu to the ARP table of that other computer. At that point I could ping the iRulu from that other computer, but not vice versa. I could not add the IP of the other computer to the ARP table of the iRulu because (despite conflicting indications--see [[][]]) I apparently don't have (full?) root privileges on the iRulu. All of the above was done with the hardwired Ethernet connection. When I switched to WiFi, I could no longer ping from the other computer to the iRulu. (I need to try this again, but have to modify the ARP table again as I've since changed the IP of the iRulu--there is a slight chance that, the first time I tried this on WiFi that the iRulu got a dynamic IP address rather than the static IP address I had previously assigned and had put in the ARP table of the other computer.)

< older stuff>

I run a LAN at home. Computers are connected to the LAN to share an Earthlink DSL connection to the Internet. In addition, computers on the LAN can exchange files among themselves.

I had little or no problem connecting the iRulu to the LAN to get access to the Internet. (I used a hardwired connection instead of WiFi or 3G--see Hardwired Ethernet.) But, so far, I have not been able to exchange files with other computers on the LAN.

Achieving that ability is the subject of this page.

Older stuff:

Just starting this page, moved some notes here from Downloading Videos:

UPDATE: on a preliminary try, the iRulu would not respond to a ping from my desktop--I should try the reverse direction.

UPDATE: on a first try pinging from the iRulu to my desktop, I got a message something like "ICMP open socket: operation not permitted. Maybe I have to be root?

Later I found an article that gave me some arp commands to try (to load the arp table or whatever it is called). The arp commands that I could enter in my desktop seemed to work and after entering them I could ping the iRulu from the desktop.

The arp commands that the article suggested I use in the iRulu did not work (so far, anyway) and I still have not been able to ping the desktop from the iRulu.

Two applications that I loaded on the iRulu to help me enter those commands are:

  • Terminal Emulator
  • Bash <something>

It seems like the Terminal Emulator by itself lets me run a very few Linux type commands (ls for one). I assume (I know) that installing the Bash <something> will let me use more Linux type commands, but, so far, I'm not sure which.

See:

Contents

FTP Server

UPDATE: When I wrote the below, I was connected to my LAN "hard-wired" via the USB / Ethernet adapter I bought separately from the iRulu. When I switched to using WiFi, FTP Server stopped working, nor did any other ftp server that I tried work. At this point I have got FTP Server to work if I run an "open" WiFi system (that is, with no security). For a more thorough discussion of the problems I ran into and those that I've solved so far, see Networking Anomalies.

Installed Ftp server (by The Olive Tree): works--when it first came up, it wanted me to press the button to start the ftp server, but then it didn't start. I looked at its settings, apparently, by default, it was looking for a WiFi connection. I switched it to use an Ethernet connection--success--I can connect to the iRulu from my desktop using Konqueror with address ftp://192.168.1.30:2221/.

I should remember that, earlier, I had added 192.168.1.30 to the ARP table (see below) of my desktop. Possibly, if I hadn't done that, the ftp client on my desktop might not have found the iRulu (at 192.168.1.3).

FTP Client

Installed AndFTP but so far it hasn't worked--I don't think I'm currently running an FTP server on my LAN--I'd have to do that before the client working. It might still not work because I couldn't add anything to the ARP table on the iRulu, because I don't have root.

Pinging to the iRulu

The following shows the arp command I used that made it possible to ping the iRulu from another machine on my network. The IP and MAC addresses in the command are those of the iRulu.

s17:~# arp -i eth0 -s 192.168.1.30 00:E0:4C:53:44:58
s17:~# arp -av
? (192.168.1.30) at 00:e0:4c:53:44:58 [ether] PERM on eth0
? (192.168.1.2) at 00:0f:66:ab:33:3b [ether] on eth0
Entries: 2      Skipped: 0      Found: 2
s17:~#
s17:~# ping 192.168.1.30
PING 192.168.1.30 (192.168.1.30) 56(84) bytes of data.
64 bytes from 192.168.1.30: icmp_seq=1 ttl=64 time=1.35 ms
64 bytes from 192.168.1.30: icmp_seq=2 ttl=64 time=1.23 ms
64 bytes from 192.168.1.30: icmp_seq=3 ttl=64 time=1.20 ms
64 bytes from 192.168.1.30: icmp_seq=4 ttl=64 time=1.23 ms
64 bytes from 192.168.1.30: icmp_seq=5 ttl=64 time=1.39 ms
^C
--- 192.168.1.30 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4015ms
rtt min/avg/max/mdev = 1.203/1.284/1.393/0.080 ms
s17:~#
s17:~# arp
Address                  HWtype  HWaddress           Flags Mask            Iface
192.168.1.30             ether   00:e0:4c:53:44:58   CM                    eth0
192.168.1.2              ether   00:0f:66:ab:33:3b   C                     eth0

Pinging from the iRulu

I tried running an arp command on the iRulu similar to the above (but using the IP and MAC addresses of the PC I wanted to ping). It failed with a message something like "ICMP open socket: operation not permitted". I was not root (I was root when I issued the arp command from my PC)--I strongly suspect I have to have root privileges on the iRulu to do this, but, so far, I have not done the necessary things to get root privileges.

Rant

<rant> Hmm: why should Android (or iRulu) make me jump through hoops to get root privileges--I mean, it is my device. I've read a little about the procedures to get root privileges on the iRulu--they typically involve installing the Android SDK on another computer--I mean, already that is crazy--just one small example, suppose I don't have another computer. Amplifying, who is Android (or iRulu) trying to protect me from, and why should they have that ability. <rant>

Resources

 This is how we did:
 1. Open the terminal on your notebook and type in:
 
Code:
sudo arp -i eth1 -s THE.IP.ADDRESS.OF.YOUR.ANDROID THE:MAC:ADDRESS:OF:YOUR:ANDROID
2. Typing in 
Code:
arp -av
 now finally recognizes the Android device.
 
 3. Open a terminal emulator on your Android device and type in:
 
Code:
sudo arp -i wlan0 -s THE.IP.ADDRESS.OF.YOUR.NOTEBOOK THE:MAC:ADDRESS:OF:YOUR:NOTEBOOK
4. Typing in the terminal emulator 
Code:
arp -av
 now finally recognizes the notebook.
 

Contributors

  • () RandyKramer - 2014-03-08
  • If you edit this page: add your name here; move this to the next line; and if you've used a comment marker (your initials in parenthesis), include it before your WikiName.

Revision Comment

%SECTION{last_revision}%
  • %DATE% —

Page Ratings

Edit | Attach | Watch | Print version | History: r11 < r10 < r9 < r8 < r7 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r11 - 2014-04-20 - RandyKramer
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by PerlCopyright 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding WikiLearn? WebBottomBar">Send feedback
See TWiki's New Look