Hello,
I have followed the guides for [DEV] Native Ubuntu and [HowTo] Native Ubuntu as well as searching google and these forums to get ubuntu running on the Asus Eee Pad Transformer. It works brilliantly except for one issue. All of the suggestions I have seen about getting wireless working don't seem to work for me. I feel I'm missing something simple and just need to be pointed in the correct direction. I have a UK version of the Eee Pad.
1. I have made the /etc/wpa_supplicant/wpa_supplicant.conf file as suggested by the forums.
2. sudo ifconfig eth0 down gives "eth0: ERROR while getting interface flags: No such device"
3. /etc/init.d/start-networking doesn't seem to exist on my system.
4. ifconfig only lists lo and usb0. usb0 has an ip address oddly enough.
The list of possible network devices ubuntu says I have are as follows:lo, dummy0, usb0, tunl0, sit0, and ip6tnl0. I have followed various suggestions about bringing down the usb0 interface before working with eth0, but it didn't seem to help.
It makes me think that the wireless drivers are missing in my rootfs.ext2 file, but I'd rather not try to download it again to see due to bandwidth limits. I would appreciate any thoughts or places to go that would help get this working. Thank you for your help.
I've been trying to work through the wireless problem, and I've found a little more info:
Code:
dmesg |grep bcm
device: 'bcm4329_wlan.1': device_add
device: 'bcm4329_rfkill': device_add
bcm4329_rfkill_probe : can't find reset gpio
I think this indicates a problem loading the driver, but I am purely speculating here. I've checked and the chipset's firmware is loaded in /lib/firmware/brcm so the driver is present.
I'll keep playing around to see if I can get it working. Any suggestions that could help point me in the right direction would be appreciated.
Hi XDA community!
I've been working on my first real Android application for a few weeks now, and I just released in on the Google Play Store.
I'm posting here because some developers around here could be interested
It's a front-end to dropbear, a minimalist SSH server.
It allows you to SSH on to your Android phone and also to use SCP.
It is highly configurable and accepts a master password and/or public keys.
Feel free to give feedback / reports / anything.
https://play.google.com/store/apps/details?id=me.shkschneider.dropbearserver
Source is up on github and many thanks to the people listed in my README file.
Well, I installed it on a rooted Samsung Galaxy 2 with NeatRom kernel (Android 4.0.3). Installation is ok but when I start the server the applications remains blocked on the
window Starting server Please wait ...
0% ... 0/100
I waited several minutes but it does not move
Does this app have any advantages over SSHDroid? (Other than lack of ads)
It is just another alternative.
Free
No ads
Open-Source (github)
Start/Stop/Started/Stopped intents for broadcasts
Configurable
Root/non-root access
...
Sadly I can't get this to run on my Evo3d gsm. Everytime I try to connect I get "Error connecting: Connection refused" even on the adb shell:
Code:
1|[email protected]:/ # ssh -p 1022 [email protected]
ssh -p 1022 [email protected]
ssh: exited: Error connecting: Connection refused
ssh on the adb shell works with other computers in the local network.
I tried port 22 and 1022 with the same result, and tried almost every combination of the options. Certificates did not help either. One strange thing is, that i get two ips one is the usual unknown.external.ip.adress and the other is not my normal class c (192.168.0.xxx) ip i get over wlan but some 10.156.xx.xx ip. After some digging i found out, that thats the ip of the rmnet0 interface.
If you need any more information I am happy to provide you these as best as I can.
ls /sys/class/net returns:
Code:
dummy0
gannet0
ip6tnl0
lo
rmnet0
rmnet1
rmnet2
rmnet3
rmnet4
rmnet5
rmnet6
rmnet7
sit0
wlan0
I couldn't get dropbear to start on my GNex, but OK on the N7. Dropbear starts OK if I run it in a terminal. GUI just stuck at 'server stopped'.
Sent from my Nexus 7 using Tapatalk 2
Just updated, and now force closes on both
Sent from my Nexus 7 using Tapatalk 2
Latest update works great, thanks again
Sent from my Nexus 7 using Tapatalk 2
Not working for me on Moto XT910 with MIUI ICS. Even though I allowed it root, it forever says "Root privileges KO, Dropbear Status KO, Server status error"
I know the thread is a bit old and there is already a second release of this app, but I couldn't find any thread about it.
I have been running the server successfully and managed to make a connection over the local network. However, I get timed out when trying to connect over the mobile network. This should be possible, right? Or am I missing something here?
Thanks,
HolySid
where should I place my .ssh hosts file?
What I wanted was a simple, secure way to access my home computer remotely from my android phone. I know there are vpn options but I’ve seen that cause battery drain issues if in constant use, and also is more than I wanted/needed to setup. I know I could just setup a ssh server but leaving port 22 open on the remote computer for anyone to scan and hack the password seemed too insecure for me. So I came up with this solution and have been using it for about 2 years now without any problems. I thought maybe I should share this method since it may be of use to someone else and I don’t know of anyone else putting all these together for use with android.
What this does:
By running a small script on your android phone in terminal (only 2 commands), your phone knocks 3 specific ports, in a specific order (like a combination lock), your remote computer recognizes this order and opens port 22 for 10 sec. Your script then ssh’s the remote computer on port 22 and you log in. The port 22 on the remote computer closes so no one else can see it, but the keep-alive feature keeps your ssh session open so you can do whatever you need, for as long as your like, without worrying about someone port sweeping the remote computer and seeing the port open, or brut forcing a ssh password on it. You with me so far?
Now the ssh session also uses port forwarding to forward port 5900 from the remote computer to port 5900 on the localhost of the android phone. Now you can open your vnc client and connect to the remote computer through your ssh tunnel and see your x11 desktop. So you know also have a secure VNC connection! All this is done securely and only runs ondemand.
While this may look like a lot to setup, it’s actually quite easy and should only take about 15min tops. This tutorial should be complete but if I’ve forgotten anything, let me know and I’ll be sure to update this page.
In other words, run two simple commands within a script and you have secure access to your remote computer from your phone! Enjoy!
Pros:
- Secure
- Works on 3G and wifi
- Runs on all android versions
- Works on all x11 GUI’s (gnome, kde, etc). Assuming a VNC session is also desired.
- Fun!
Problems:
- This only works on linux computers, although I’m sure there is a way to setup port knocking on windows. I have no use for this, but if people are interesting, I can add a way to my tutorial as well.
Howto:
Setup Remote Computer:
First we need to setup the remote computer. This is geared towards Debian/Ubuntu but small adjustments should have it working on all distros (I’m using Debian Squeeze personally). Let’s begin:
First we need to install a few packages if not already there:
Code:
apt-get install openssh-server x11vnc knockd
Now lets configure your ssh daemon. Using nano or another text editor, edit /etc/ssh/sshd_config:
Change the following line to read as follows:
Code:
PermitRootLogin no
This will disable root login, so you will login in as a user and then su to root (You can leave root login if desired, it’s just less secure and not recommended).
Next we need to edit our iptables, so open /etc/network/if-pre-up.d/iptables and add the following:
MAKE A BACKUP FIRST OF THIS FILE
Code:
# Accepts all established inbound connections
iptables -A INPUT -i eth0 -m state --state ESTABLISHED,RELATED -j ACCEPT
# Allows all outbound traffic
iptables -A OUTPUT -j ACCEPT
# Allow ping
iptables -A INPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
# log iptables denied calls (access via 'dmesg' command)
iptables -A INPUT -m limit --limit 5/min -j LOG --log-prefix "iptables denied: " --log-level 7
# Reject all other inbound - default deny unless explicitly allowed policy:
iptables -A INPUT -j REJECT
iptables -A FORWARD -j REJECT
Now we setup our port knocking. Edit /etc/knockd.conf:
Code:
[options]
UseSyslog
[openSSH]
sequence = port1,port2,port3
seq_timeout = 5
command = /sbin/iptables -I INPUT -p tcp -m state --state NEW --dport 22 -j ACCEPT
cmd_timeout = 10
stop_command = iptables -I INPUT -p tcp -m state --state NEW --dport 22 -j DROP
tcpflags = syn
[closeSSH]
sequence = port1,port2,port3
seq_timeout = 5
command = /etc/init.d/ssh stop
tcpflags = syn
The section [openSSH] is what opens the port for 10 sec by running the iptables command and then drops the packets after the time expires, running the stop_command. The section [closeSSH] is not needed. It was a failsafe I use in case I want to disable ssh if I thought I was getting hacked and could not login. This is also left to show how you can use the knocking to run different commands using another sequence of ports (for ftp, etc.)
Now lets restart the network interface and restart the knock daemon:
Code:
ifconfig eth0 down #adjust to whatever interface you use normally
ifconfig eth0 up
dhclient
/etc/init.d/knockd restart
/etc/init.d/sshd restart
Test your internet and make sure it works. To make sure you have it setup to run on boot, first determine your runlevel:
Code:
runlevel
Make sure knockd, ssh are in the /etc/rcX.d (where X equals your runlevel). If not, add it
Code:
ln -s /etc/init.d/knockd /etc/rcX.d/S02knockd
And so on for shh if needed, (again, adjust X to equal your runlevel)
Setup X11VNC password:
Code:
x11vnc --store password
create a script for ~/bin/x11vncserver
add this to the script
Code:
#!/bin/bash
x11vnc -safer -forever -usepw -noxdamage
The “-noxdamage” fixes a display problem of the desktop not updating in the android vnc client. Now if using gnome and you only care about vnc login for one user then, goto System → Preferences → Startup Applications → Add →
Name = VNC Server
Command = x11vncserver &
Or add to GDM for access to any user, add to /etc/gdm3/Init/Default:
Code:
x11vnc -safer -forever -usepw -noxdamage
DONE! (KDE will be similar but slightly different to load on login, post if help is needed)
Setup android phone:
create script called knockh in /system/xbin. Then add this:
Code:
nc -z [ipaddress] port1 port2 port3
ssh -L 5990:localhost:5900 [email protected][ipaddress]
Replaces the ipaddress with your own (google “what is my ip” if you don’t know your external ip). Replace the ports with the ones used in the config file above for knockd. Change the user to whatever user has ssh rights. Then
Code:
chmod 755 /system/xbin/knockh
Now run knockh in the terminal and you should see a login for ssh on your remote computer.
Next download “android-vnc-viewer” from the market (it’s free). Create a new connection by selecting “new” from the dropdown box.
Create a nickname, enter your x11vnc pasword, address is “localhost” and port is “5900”. For 3G connections, I recommend 8 colors, for wifi 256. I also check the “Local mouse pointer” in the checkbox. Now click connect and see your desktop!
(If you are on your local wifi network be sure to create another connection for your local ip address)
Fixes:
Keep in mind this is for remote networks, if you are on your local lan, this won’t work without changing the ip address.
If using a router or modem, setup port forwarding to your remote computer for TCP ports 5900, 22, port1, port2, port3 (your port knocking ports). Also make sure to setup a static dhcp for the remote computer so your router/modem doesn’t change it’s ip address and you can’t connect.
If you are using an ISP that doesn’t give you a static ip address for your router, you will not be able to login whenever they change it, you’ll have to update the script first with the new IP. A solution is to setup a dynamic dns, using dyndns.org or something similar. Free options are out there, just google it.
I hope this helps, please post if you have any questions, comments, etc. Enjoy!
-Mike
On some roms, the busybox version of "nc" does not allow the -z command for knocking the proper ports. I've pulled the version of it from CM 7.2 and put in my /system/xbin and full functionality has been retained. I've included both "nc" and "ssh" here and they should work fine if you are missing them. (Tested on my EVO LTE running mostly stock Sense ICS, but this is fine for other android versions)
nc
ssh
Hope this helps!
-Mike
Hi,
Over the past few days I've tried getting my USB Ethernet cable to work with my Tab 2 10.1 running stock ICS 4.0.4
And now I got it up to the point where my PC and my Tab can ping eachother, but that's about it. Get ready for a long and technical read
Now I know Samsung has neglected to include drivers for commonly used USB to Ethernet cables, so I built my own modules to load into the stock kernel (3.0.8-1060237):
drivers/net/mii.ko - Generic Media Independent Interface device support
drivers/net/usb/usbnet.ko - support for usb network
drivers/net/usb/mcs7830.ko - driver for this specific ethernet cable (moschip 7830 based)
Driver depends on support for USB network, USB network depends on support for media independent interface.
So loading these into the kernel using insmod works. After I plug in the cable the kernel tells me:
Code:
[ 3754.987335] MOSCHIP usb-ethernet driver 1-1:1.0: eth0: register 'MOSCHIP usb-ethernet driver' at usb-musb-hdrc-1, MOSCHIP 7830/7832/7730 usb-NET adapter, 00:60:6e:42:32:8f
And even netcfg agrees eth0 exists:
Code:
[email protected]:/ # netcfg
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
ifb0 DOWN 0.0.0.0/0 0x00000082 26:d8:ae:9d:18:30
ifb1 DOWN 0.0.0.0/0 0x00000082 3e:2c:67:48:bd:92
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
eth0 DOWN 0.0.0.0/0 0x00001002 00:60:6e:42:32:8f
wlan0 UP 130.161.censored/26 0x00001043 1c:66:aa:50:39:ee
[email protected]:/ #
So for testing I put the device on a simple switch with just my PC.
I gave my PC 192.168.1.253 and the tablet 192.168.1.200 (both netmask 255.255.255.0).
Code:
[email protected]:/ # ifconfig eth0 192.168.1.200 netmask 255.255.255.0
And there was much rejoicing:
Code:
Windows:
Reply from 192.168.1.200: bytes=32 time<1ms TTL=64
Android:
64 bytes from 192.168.1.253: seq=32 ttl=128 time=0.733 ms
Now here is the problem: Half the apps trip over this new eth0 network interface.
For instance:
"kWS - android web server" works great, immediately recognizes eth0 and uses it without any problems.
Android Browser crashes the network driver.
SSHDroid starts up thinking it is an ipv6 interface and crashes the network driver on any incoming connections.
Also when I turn off WiFi (regardless if it is connected to a network or not), eth0 is killed too.
Couple of questions:
What am I missing to make Android treat this as a good, normal network interface?
How can I make the modules load when the tablet boots?
How can set the IP adres so I don't have to use ifconfig eth0 192...etc every time I connect the device?
How can I add the eth0 to the settings GUI of Android?
Can installing a different kernel or something like CyanogenMod fix the problem alltogether?
Many thanks in advance for any answers!
If anyone is interested in the modules I compiled please reply, but note they only work on rooted tablets that have stock ICS kernel version 3.0.8-1060237 because of what Linux calls "version magic".
Kind Regards,
Android has Incomplete Eth0 Support...
baggush said:
Hi,
Couple of questions:
What am I missing to make Android treat this as a good, normal network interface?
How can I make the modules load when the tablet boots?
How can set the IP adres so I don't have to use ifconfig eth0 192...etc every time I connect the device?
How can I add the eth0 to the settings GUI of Android?
Can installing a different kernel or something like CyanogenMod fix the problem alltogether?
Many thanks in advance for any answers!
Click to expand...
Click to collapse
Well, he first thing to know is that Android has incomplete Eth0 support!
As you've seen, it's implemented and correct at the Linux level. Which means programs that are written in C++ and either work at the native linux level or bypass the Android framework will work.
However, the Java implementation is busted. It's incomplete.
I'd highly recommend Ben Zores presentation, "Dive Into Android Networking: Adding Ethernet Connectivity" if you want to understand the issues.
(You'll have to google it, I can't post links yet!)
Basically all the Android API gets you is the ability to see that Eth0 exists. You can't talk to it, set it, get notifications on it, etc. because the Service Manager and the Connection Manager framework components are incomplete.
Some implementations, like Android-IA and Cynogen and Linaro have been patched to work, some better than others.
I ran into this the hard way, because I'm implementing a machine control system using Android as a UI and Control Computer. It's a fixed app, not a mobile/tablet thing. And I'm linking to a WAGO Modbus-based fieldbus system for digital and analog I/O and motion control.
Trust me, it's a real headache. I've gotten around it, but there's no official news or support yet.
Regards,
David Schofield, Hotspot Office LLC, Pittsburgh, PA
Galaxy tab 2 eth0 needed
I need to connect an USB to Ethernet to my Galaxy tab 2 7.0 (GT-P3100) or Galaxy tab 3 7.0 (GT-P3200), is there is a way to add the driver without rebuild the rom (like a patch or update) or if there is a custom ROM that supports Ethernet ? Please help me doing this
Ethernet support for Galaxy tab 2.7.0
MJBLACKEND said:
I need to connect an USB to Ethernet to my Galaxy tab 2 7.0 (GT-P3100) or Galaxy tab 3 7.0 (GT-P3200), is there is a way to add the driver without rebuild the rom (like a patch or update) or if there is a custom ROM that supports Ethernet ? Please help me doing this
Click to expand...
Click to collapse
How to say this gently... umm-m-m,
No.
Each manufacturer has configured Android to their liking, and apparently Samsung DOESN'T like Ethernet.
.
I'm doing just as you did, using a Radio Shack Belkin USB interface to connect to industrial equipment (Modbus/TCP PLC's and fieldbus I/O systems.) I've evaluated a number of tablets, including all Samsung tablets (and Nexus, Lenovo, Curtis, and many, many others.) If they don't fully support wired Ethernet, you can't back-fill it without rooting and flashing the ROMs.
(I wish Toshiba would unroot my original Thrive, which they've orphaned.)
In the end, I've bought cheap tablets like some Proscan's (at BigLots, $80USD ) and the 7" Zeki TBDG773B (K-Mart, $119USD) and in testing them, discovered they supported wired Ethernet. (Note that exact models are important, because I've found ROM differences between almost identical models that make the difference between success and failure. Polaroid-branded tablets are infamous for this.)
To test, go to Settings, Wireless & Networks -> Ethernet, (or sometimes, More...-> Ethernet) then switch Ethernet ON, and click Advanced Configuration or sometimes, Configure Ethernet Device. (Polaroids usually fail at this point, they never included the rest of the module.)
My Zeki gives the choice of DHCP vs. Static IP, .IP Address, Netmask, DNS Address and Gateway Address. Proscan gives you DNS1 and DNS2.
I have tested over 80 Android tablets now... Many are tested, few are worthy.
Check out my video on Android-->Ethernet connectivity on YouTube, search for Hotspot Office modbus, or watch video JCMkvHkeNzw, as in /watch?v=JCMkvHkeNzw
I've got specifics and talk about models and equipment and demonstrate stepper motor control using a WAGO fieldbus system.
Thanks
Hotspot Office said:
How to say this gently... umm-m-m,
No.
Each manufacturer has configured Android to their liking, and apparently Samsung DOESN'T like Ethernet.
.
I'm doing just as you did, using a Radio Shack Belkin USB interface to connect to industrial equipment (Modbus/TCP PLC's and fieldbus I/O systems.) I've evaluated a number of tablets, including all Samsung tablets (and Nexus, Lenovo, Curtis, and many, many others.) If they don't fully support wired Ethernet, you can't back-fill it without rooting and flashing the ROMs.
(I wish Toshiba would unroot my original Thrive, which they've orphaned.)
In the end, I've bought cheap tablets like some Proscan's (at BigLots, $80USD ) and the 7" Zeki TBDG773B (K-Mart, $119USD) and in testing them, discovered they supported wired Ethernet. (Note that exact models are important, because I've found ROM differences between almost identical models that make the difference between success and failure. Polaroid-branded tablets are infamous for this.)
To test, go to Settings, Wireless & Networks -> Ethernet, (or sometimes, More...-> Ethernet) then switch Ethernet ON, and click Advanced Configuration or sometimes, Configure Ethernet Device. (Polaroids usually fail at this point, they never included the rest of the module.)
My Zeki gives the choice of DHCP vs. Static IP, .IP Address, Netmask, DNS Address and Gateway Address. Proscan gives you DNS1 and DNS2.
I have tested over 80 Android tablets now... Many are tested, few are worthy.
Check out my video on Android-->Ethernet connectivity on YouTube, search for Hotspot Office modbus, or watch video JCMkvHkeNzw, as in /watch?v=JCMkvHkeNzw
I've got specifics and talk about models and equipment and demonstrate stepper motor control using a WAGO fieldbus system.
Click to expand...
Click to collapse
Thank you for your reply. As you mentioned, there is a way by rooting and flashing, so Where can we find a ready ROM which we can flash to enable Ethernet on Galaxy tab 2 [P3113]?
Also, is there a way to recompile the kernel of Galaxy tab 2 with enabling the Ethernet module from my side? if there is can you advise me how?
Thanks and regards,
Flashing the Galaxy...
MJBLACKEND said:
Thank you for your reply. As you mentioned, there is a way by rooting and flashing, so Where can we find a ready ROM which we can flash to enable Ethernet on Galaxy tab 2 [P3113]?
Also, is there a way to recompile the kernel of Galaxy tab 2 with enabling the Ethernet module from my side? if there is can you advise me how?
Thanks and regards,
Click to expand...
Click to collapse
There are sources on the internet, if you google for "reflash galaxy 2 ROM" but I don't know if they support wired ethernet.
You'll find sites like galaxys2root.com, etc. Biftor is apparently a popular ROM, and ODIN is a popular facility.
It's an involved process, but not impossible. Strict attention to the right instructions will win you success!
Good Providence!
-d
Bump!
Dear Forum,
has there been any development on this topic?
@Hotspot Office -- kudos for the link!
Like Hotspot Office, We have to build a machine GUI based on the P5110. My application will be bypassing the incomplete Android eth0 support
so most probable baggush's approach could work for us but we ar running Cyanogenmod 11 and the Dhollmen kernel.
I still have to get my legs about this whole issue. So any hints and thoughts will be greatly appreciated.
Martin
Functional Eth0, check out my project vid on youtube!
Well, I got things straight, but it wasn't easy.
Check out my project vid featuring a WAGO fieldbus controlling a stepper motor via a functional Eth0 on youtube
You can google for "youtube android modbus" or search youtube for video JCMkvHkeNzw
Or you can plug it into the youtube url, as in /watch?v=JCMkvHkeNzw
The actual title is "Android Tablet Modbus/TCP Stepper-Motor/Robot Exerciser"
If you like it, be sure to thumbs-up it, and leave a comment!
david schofield
dub-dub-dub dot hotspot office dot net
I'm running 4.2.2 so maybe this won't apply, but did you have to do anything in terms of the Ethernet UI in Settings? I've installed the drivers and it looks like the tablet is detecting it, but the Ethernet settings never show up
diimentio said:
I'm running 4.2.2 so maybe this won't apply, but did you have to do anything in terms of the Ethernet UI in Settings? I've installed the drivers and it looks like the tablet is detecting it, but the Ethernet settings never show up
Click to expand...
Click to collapse
Are you running a full 4.2.2, or a stripped down version? What's its pedigree?
Hotspot Office said:
Are you running a full 4.2.2, or a stripped down version? What's its pedigree?
Click to expand...
Click to collapse
I'm not sure, how can you tell?
diimentio said:
I'm not sure, how can you tell?
Click to expand...
Click to collapse
What kind of device is it? Or try Settings, About?
The thing is, if it isn't under "Settings->Wireless and Networks" or whatever, then you don't have it.
-d
Hotspot Office said:
What kind of device is it? Or try Settings, About?
The thing is, if it isn't under "Settings->Wireless and Networks" or whatever, then you don't have it.
-d
Click to expand...
Click to collapse
Well it definitely says 4.2.2 under Settings, About. I have a Samsung Galaxy Tab 2 GT-P5113 model. I don't know what a "stripped down" version is.
I don't have it under Wireless and Networks but in this video (https://www.youtube.com/watch?v=J-RQwQTjraM) the Ethernet option pops up when it detects a valid Ethernet connection. Obviously it's not the same model but I'm wondering whether I need a UI patch or if it should just work out of the box assuming I have all the correct drivers installed.
diimentio said:
Well it definitely says 4.2.2 under Settings, About. I have a Samsung Galaxy Tab 2 GT-P5113 model. I don't know what a "stripped down" version is.
I don't have it under Wireless and Networks but in this video (https://www.youtube.com/watch?v=J-RQwQTjraM) the Ethernet option pops up when it detects a valid Ethernet connection. Obviously it's not the same model but I'm wondering whether I need a UI patch or if it should just work out of the box assuming I have all the correct drivers installed.
Click to expand...
Click to collapse
In my experience, I've found you'd need the *EXACT* same model. I've checked probably a hundred tablets, and found that the specific model and software version, matters. That's why in my video I detail the exact model number. You need to realize that an Android version, say 4.2.2 isn't the same the whole world over. Like Windows XP Embedded, it's a kit of parts. I can burn a version of 4.2.2 with Ethernet support, and I can burn a version of 4.2.2 WITHOUT Ethernet support apps at the Android level. As the developer, I pick and choose what features and applications I include, and which I leave out--which I customize, and which I leave alone.
Sorry, unless you root your device with a version of 4.2.2. that supports the wired Ethernet applications in the settings, you're at the mercy of the Samsung folks.