Has anyone had any luck getting a wired ethernet connection working on their device? I feel like I'm missing some minor piece of configuration that prevents me from getting it working. Here's what I've got so far.
1) compiled asix.ko, usbnet.ko and mii.ko for P5113
2) insmod above modules
3) connect usb ethernet adapter
As soon as I complete this, the following happens:
a) lights start flashing as soon as I connect ethernet cable
b) eth0 becomes a recognized interface
The problem is that I can't get the device to get an ip address. Neither a statically assigned ip address works, nor is one retrieved using dhcpcd. The strange thing is that when I run wireshark and do some port-mirroring on my switch, I see that the DHCP server is offering an ip address to the device, but the device doesn't seem to want to accept it. Traceroutes and pings to my gateway all show "host unreachable" messages.
Usb to Ethernet
Did you solve this? I am a network engineer that would love to see this fixed I have tried a couple of different ones and none of them have worked yet.
Related
been messing with it all day, i'm sure i am doing something wrong googled the hell out of it though.
ok here is what i am trying to do, I just bought a Acer Nettop running XP i installed the HTC drivers on it MNS is working great. i would like to hook up my wireless router to the Ethernet port to share the internet connection with the rest of my gadgets.
any help would be appreciated.
smittycg said:
been messing with it all day, i'm sure i am doing something wrong googled the hell out of it though.
ok here is what i am trying to do, I just bought a Acer Nettop running XP i installed the HTC drivers on it MNS is working great. i would like to hook up my wireless router to the Ethernet port to share the internet connection with the rest of my gadgets.
any help would be appreciated.
Click to expand...
Click to collapse
Why don't use Wireless Tether and everything can pull internet from the phone without the need of a router?
Bridge the connections in network connections or use ICS
morbidpete said:
Bridge the connections in network connections or use ICS
Click to expand...
Click to collapse
tried both of those, the bridge would connect, but no internet, ics didn't work either, i am pretty tired though probably missing something simple.
WIFI tether is cool and all but i want to use it full time with a dedicated phone and be able to use my wireless printer
I've never been able to get to work if you do post Back with what you did. I think the issue is up addresses, you may have to setup the router gateway address as the pcs ip or even the phones ip... Im not a networking guru though
Kcarpenter said:
I've never been able to get to work if you do post Back with what you did. I think the issue is up addresses, you may have to setup the router gateway address as the pcs ip or even the phones ip... Im not a networking guru though
Click to expand...
Click to collapse
to be honest i was hoping someone had done it and could tell me how easy it was. while trying to get it to work today i was just clicking around, tomorrow i'll go about if more scientifically and post all the stuff i'm doing wrong.
I can't see any reason off the top of my head why ICS wouldn't work.
So, let me see if I have this straight. Your phone is connected to your PC via USB. Your access point is connected to the PC via ethernet. And you want other devices to connect over wifi and have Internet access. That about right?
Try this... Assign the ethernet port on your PC a static IP address of 192.168.1.1. Connect that to the "Internet" port on your access point, and assign that port an IP address of 192.168.1.2. In the wireless setup on your access point, assign the wireless side the static ip address 192.168.2.1 and tell it to act as a dhcp server, and hand out addresses from 192.168.2.100 to 192.168.2.200. Netmask in all cases will be 255.255.255.0. For dns go ahead and use 208.67.222.222 unless you have another dns service that you prefer.
The router should be configured to use 192.168.1.1 as its default gateway. The wireless devices should be set to use 192.168.2.1 as their default gateway.
This *should* work. Different accesss points can be finicky in various ways, but I really don't see why the setup I've outlined wouldn't work....
I am not sure if its the right forum to ask this question, but knowing the smart ppl we have here i hope i am wrong!
I just downloaded Remote RDP Enterprise 3.2 and i am trying to setup so i can connect to my home pc. I am using a router model WGT624 netgear router. I tried the port forwarding (had to setup custom PF, because it wouldnt let me add 3389 as a port on the services which offers through the router) as it was suggested but i think i might be doing something wrong because it just wont connect at all.
my PF on my router looks something like this:
# Service Name Start Port End Port Server IP Address
1 RDP 3389 3389 192.168.X.X
And when i goto whatismyip.com i have a different IP address: 67.234.x.x
on the app on my phone which IP address do i connect through?
Anyone use the same app and has a netgear router and knows how to set it up? or any documentation on how to get this thing working and can share it would be extremely helpful, its for my work!
Thanx so much in advance
Hi iknight8. I don't have that app but I'll try and help.
You need to connect to the external IP address (67.234.x.x) when you are on the internet and the internal IP (192.168.X.X) when you are on your internal network.
A good troubleshooting step would be to try connecting to you PC on the internal address when you are connected to your wifi. This should work with any of the port forwarding you have setup so if it doesn't then then you know it is a proble with the setting on the pc itself. Remote desktop has to be enabled in the computer settings and allowed on any firewalls you are using.
i tried connecting both but i get a Socket is not connected message!
if u can use it and let me know of the setting to make it work would be nice
Thanx again
p.s. wen i am on internal wifi network, same as pc and i put that PF ip addess, i get a mesage "no route to host"...
Do you have allowed RDP connection on PC?
I downloaded the app and the first time I tried it on my wifi I got the same error as you, no route to host. The problem was that I didn't enable remote desktop on my PC. Once I set it to allow connections from computers running any version of remote desktop it worked straight away.
This is what I did.
1. In the app, press the menu button and add.
2. I put in the IP address of my pc and port 3389.
3. On my PC I disabled the windows firewall.
4. Also on my PC (I'm using windows 7), I enabled remote desktop by going to start, right click computer, click properties, click remote settings and check the allow connections from computers running any version of resmote desktop radio button.
5. finally I connected my phone to my wifi and tapped on the connection I created in the app. It gave me my logon screen.
If you can get this working hopefully your port forwarding settings are corect and that will work too. Hope this helps.
I'm attempting to connect my Asus TF300T in an Asus Connect Dock to a linux box using an ethernet crossover cable. The TF300T is running CM 10.2. After Googling a bit, I tried setting up new wired connections on the linux box using both the link-local method and the manual method and assigning an IP address. Unfortunately I havent been able to ping the linux box from the tablet using either method. This is uncharted territory for me and so am unsure how to proceed (or if this is even possible). Does anyone have any pointers they could share about how to accomplish this?
jtdevxda said:
I'm attempting to connect my Asus TF300T in an Asus Connect Dock to a linux box using an ethernet crossover cable. The TF300T is running CM 10.2. After Googling a bit, I tried setting up new wired connections on the linux box using both the link-local method and the manual method and assigning an IP address. Unfortunately I havent been able to ping the linux box from the tablet using either method. This is uncharted territory for me and so am unsure how to proceed (or if this is even possible). Does anyone have any pointers they could share about how to accomplish this?
Click to expand...
Click to collapse
Sorry, no pointers, just a few things to look at.
Make sure on both sides that you have a valid IP address in the same subnet. You can use "ip addr" to list all interfaces and addresses.
On the PC manual assignment is probably best. For the tablet, you could run a DHCP server on your PC or assign it manually too.
If "ip addr" shows different IP addresses in the same subnet, and you still have no ping, the next best guess is to check the firewall rules on both sides.
Sent from my TF300T using Tapatalk
f69m said:
Sorry, no pointers, just a few things to look at.
Make sure on both sides that you have a valid IP address in the same subnet. You can use "ip addr" to list all interfaces and addresses.
On the PC manual assignment is probably best. For the tablet, you could run a DHCP server on your PC or assign it manually too.
If "ip addr" shows different IP addresses in the same subnet, and you still have no ping, the next best guess is to check the firewall rules on both sides.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
I haven't been able to find a way to manually assign the IP for eth0 on the tablet, so I attempted to install a dhcp server on the linux box in hopes that it would then assign the IP address to the tablet. I installed isc-dhcp-server and made sure that the following line in /etc/default/isc-dhcp-server was set: INTERFACES="eth0". After running sudo service isc-dhcp-server restart on the linux box I shut wired connections off, plugged in the cross over cable to both machines, and then turned on the wired connection on the linux box that I created to use a manual IP (10.0.0.1). The tablet doesn't get an IP assigned that I can tell - at least nothing shows up when I run ifconfig or 'ip addr'.
I'm not sure if this has anything to do with it or not, but on the tablet I took a look at /etc/dhcpcd/dhcpcd.conf and it appears that it only contains configuration for the wlan0 interface. Is it possible that I need to provide some additional configuration on the tablet side to get eth0 to work properly since it is being provided by the Asus Connect Dock?
jtdevxda said:
I haven't been able to find a way to manually assign the IP for eth0 on the tablet, so I attempted to install a dhcp server on the linux box in hopes that it would then assign the IP address to the tablet. I installed isc-dhcp-server and made sure that the following line in /etc/default/isc-dhcp-server was set: INTERFACES="eth0". After running sudo service isc-dhcp-server restart on the linux box I shut wired connections off, plugged in the cross over cable to both machines, and then turned on the wired connection on the linux box that I created to use a manual IP (10.0.0.1). The tablet doesn't get an IP assigned that I can tell - at least nothing shows up when I run ifconfig or 'ip addr'.
I'm not sure if this has anything to do with it or not, but on the tablet I took a look at /etc/dhcpcd/dhcpcd.conf and it appears that it only contains configuration for the wlan0 interface. Is it possible that I need to provide some additional configuration on the tablet side to get eth0 to work properly since it is being provided by the Asus Connect Dock?
Click to expand...
Click to collapse
That's a good point, probably you need to tell dhcpc on the tablet to work on eth0 too, never really tried that. Also you probably need to configure dhcpd on your PC for the subnet you use.
But maybe better to get a manually configured ping first, then tackle DHCP.
On your tablet try:
ip addr add 10.0.0.10/16 dev eth0
The /16 is just an example and should match the prefix set on your PC.
If you can get a ping with that, I am happy to assist you setting up DHCP.
Sent from my TF300T using Tapatalk
f69m said:
That's a good point, probably you need to tell dhcpc on the tablet to work on eth0 too, never really tried that. Also you probably need to configure dhcpd on your PC for the subnet you use.
But maybe better to get a manually configured ping first, then tackle DHCP.
On your tablet try:
ip addr add 10.0.0.10/16 dev eth0
The /16 is just an example and should match the prefix set on your PC.
If you can get a ping with that, I am happy to assist you setting up DHCP.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
That worked! Thanks. I was able to ping successfully in both directions. I need to do some further testing but I think I might be able to use the static IPs and avoid having to setup the DHCP server on the laptop. I will do further investigation in the morning and post results.
I am in need of an Ethernet connection which is fully compatible with userspace on the latest version of Android. Plugging in an Ethernet cable through an adapter works fine, it's just apps that require a connection from userspace do not work (such as Telegram, Magisk, etc).
I am able to compile a custom kernel and have compiled a kernel as part of a LineageOS ROM that I had built from the official instructions for my Pixel 3a XL (bonito). I had set the following in the kernel configuration:
CONFIG_MAC80211_HWSIM=m
CONFIG_VIRT_WIFI=m
so that I could build the virt_wifi module.
I ended up making several more modifications to the kernel as the virt_wifi module source code was different to one listed in Android-x86 (which I know definitely works). I was having issues with the virt_wifi module that came with my kernel as it was never connecting, only giving me 'Failed to connect to network' alerts and failing to connect 100% of the time (as opposed to 90% of the time that I get from Android-x86's kernel module). I took the following files from the Android-x86 kernel and placed them into the msm-4.9 kernel for my Pixel 3a XL device:
include/net/virt_wifi.h
kernel/drivers/net/wireless/virt_wifi.c
After recompiling with these files replacing the existing ones, I had more success but things were still unreliable (I dive deeper into the issue later in this post).
I found instructions listed at the bottom of https://groups.google.com/g/android-x86/c/cjzhscvylSw which helped me setup a virtual wireless connection. I have altered them for my particular case.
rmmod wlan # remove internal wifi module to remove existing wlan0 interface
modprobe -d /vendor/lib/modules lib80211 # modprobe lib80211 - seemingly required for virt_wifi
modprobe -d /vendor/lib/modules virt_wifi # modprobe virt_wifi itself
ifconfig eth0 down # bring ethernet interface down temporarily
ip link set eth0 name wifi_eth # change ethernet interface name
ifconfig wifi_eth up # bring ethernet interface back up (under new name)
ip link add link wifi_eth name wlan0 type virt_wifi # add virtual link from wifi_eth interface to wlan0 as type 'virt_wifi'
After this, if I immediately turn on my Wi-Fi and check the Wi-Fi settings, it just says that it is searching for a network.
ifconfig wlan0 up
Before I transferred the virt_wifi related files from Android-x86's kernel source code to the msm-4.9 kernel source code, I was completely unable to get a connection at all (I tried over 25 times to get a connection with no success).
After transferring the files and rebuilding the LineageOS ROM for my Pixel 3a XL, I was able to get a connection after repeating the previous command multiple times and returning back to the Wi-Fi settings screen quickly. I have ended up being able to get a connection five times and I had used the previous command over 50 times in total. Magisk functioned without issues (which requires Wi-Fi to use any downloading functionality - it cannot use Ethernet directly for this) and the Wi-Fi status screen showed everything as connected fully, as it would a standard Wi-Fi connection.
The problem is, it is incredibly tedious to be trying to connect constantly and have to repeat this time consuming process if I disconnect the Ethernet cable. I want to be able to simply tap on VirtWifi and connect to it without issues, at the moment when I tap on it I get 'Failed to connect to network' alerts.
By the way, before anyone asks, it is very unlikely to be related to my Ethernet adapter. I used a dummy Ethernet interface to connect so that I could test to see if it has the same problem of not being able to connect most of the time and it still has the issue where it only connects once in every ten or so times (however it isn't able to connect to the internet so it drops the connection after 30 or so seconds anyway, it just attempts a connection but the real Ethernet interface would do the same thing if it had no internet).
If anyone could help me fix this issue, I will give them $100. Thanks.
May I ask if you have solved the problem
Hi looking to resolve a problem that I can't find an answer to by using Google
I have a tablet running android 11 and have connected a USB c to Ethernet adapter. I have activated wifi and the tablet connects to my local office network. I have activated Ethernet tethering and plugged in a LAN cable to the adapter and the external device (ASIC computer).
The tablet is basically being used to provide wifi connectivity for the device.
I can log into the dashboard and it shows that the ASIC computer is connected and all is working normally BUT I have not found a way to log into the device.... mainly because I have not found a way to locate it's IP address.
I want to be able to configure the firmware on the device from the tablet. It is possible to do this by connecting the device to the router via a lan cable. I then find the IP address on my PC, but I would like to also use the tablet. Thanks
Here is a link to show the set up: https://photos.app.goo.gl/iFsKNWniz2DiDpHD7
Bumped! still trying to get an answer....