Hello everyone!
I successfully manged to get a USB-Ethernet Dongle working on my note 2.
However I am experiencing a strange issue:
When I had first set up the ethernet functionality, everything was working fine.
(Most apps could Not access the internet though, but some such as browser or vlc-player could).
Some days passed by during which I did not use the ethernet functionality but accessed several wifi networks
Now the issue:
if I want to use ethernet at my home network again everything seems fine first.
I can connect via ethernet, retrieve an ip adress using "dhcpcd eth0" and even issue commands like "traceroute www .google. de"
The output of "ip addr show" and "ip route show" also indicates that eth0 interface was assigned a ip-adress and also the correct default gateway has been defined
however if I want to use the browser to browse the web no connection can be established...
same with VLC-Player.
so network commands via terminal work but there's no internet connection within apps.
The strange thing is:
if I now access my home network via wifi first, turn wifi off and use ethernet again everything works as expected (especially the browser is working again..?!)
I'm wondering what I'm missing here:
Do I miss something during setting up the ethernet interface?
note that I also set the "net.dns1" and "net.dns2" property for primary and secondary DNS Server...
But why is ethernet only working if I firstly connect to the same network via wifi?
I assume that while connecting to the network via wifi some additional properties are set.
I'd very appreciate any explanation/suggestion on this matter.
thanks in advance!
Regards!
BennyKay said:
Hello everyone!
I successfully manged to get a USB-Ethernet Dongle working on my note 2.
However I am experiencing a strange issue:
When I had first set up the ethernet functionality, everything was working fine.
(Most apps could Not access the internet though, but some such as browser or vlc-player could).
Some days passed by during which I did not use the ethernet functionality but accessed several wifi networks
Now the issue:
if I want to use ethernet at my home network again everything seems fine first.
I can connect via ethernet, retrieve an ip adress using "dhcpcd eth0" and even issue commands like "traceroute www .google. de"
The output of "ip addr show" and "ip route show" also indicates that eth0 interface was assigned a ip-adress and also the correct default gateway has been defined
however if I want to use the browser to browse the web no connection can be established...
same with VLC-Player.
so network commands via terminal work but there's no internet connection within apps.
The strange thing is:
if I now access my home network via wifi first, turn wifi off and use ethernet again everything works as expected (especially the browser is working again..?!)
I'm wondering what I'm missing here:
Do I miss something during setting up the ethernet interface?
note that I also set the "net.dns1" and "net.dns2" property for primary and secondary DNS Server...
But why is ethernet only working if I firstly connect to the same network via wifi?
I assume that while connecting to the network via wifi some additional properties are set.
I'd very appreciate any explanation/suggestion on this matter.
thanks in advance!
Regards!
Click to expand...
Click to collapse
There is something on these forums called "reverse tether" look it up, it has something that can fix this with IP tables and force the phone to think that it is connected to Wifi
Great, thank you!
I did not know about this possibility!
Especially the xposed module looks promising.
It might help to get more apps to reconize the active internet connection.
I'll give it a try!
however I still have no clue why the ethernet interface only seems to work correctly if I first connect the phone via wifi to the network.
The browser will recognize the connection when I do the following:
1.1>turn wifi on and connect to my network
1.2>turn wifi off again
2.1>connect the ethernet USB Dongle
2.2>set up eth0 interface
3>web browser works
Note that I only turn wifi on for step 1.1 and 1.2. When using the ethernet connection wifi is already turned off and the browser still works.
I read that the browser uses some low-level functionality and bypasses the Android framework which is why it can use network connections even though android "thinks" no network is available.
But if I skip the first 2 steps even the web browser won't work.
I think it's quite strange behavior which I cannot explain. Maybe a configuration problem which is solved when setting up a wifi connection prior?
Maybe I'll have to dig a bit deeper into how networking in android works.
Hi, can you share your settings and how did you managed to connect through ethernet? Which rom and kernel you used?
Sent from my GT-N7100 using Tapatalk
chandoliasnikos said:
Hi, can you share your settings and how did you managed to connect through ethernet? Which rom and kernel you used?
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hello!
I am using PhoeniX ROM v16.7 along with the AGNI PureStock Kernel v.3.9.3.
It is the kernel that enables the ethernet functionality.
However ethernet support depends on the chipset of the ethernet adapter you are going to use.
Mine has an ASIX AX88772 chipset. I am not sure what kind of chipsets are supported by this kernel.
If the kernel does not support your chipset you will have to compile the driver yourself and insert it as a kernel-module.
I cannot post any links (due to restrictions for new members) but you will find a lot about this topic if you search for: note 2 ethernet kernel module
I do not really understand what you mean by settings:
If you have ethernet up and running you can type in terminal:
Code:
netcfg
You will then see a list of all network interfaces along with the eth0 interface.
To set up the eth0 interface using dhcp you can issue:
Code:
dhcpcd eth0
For manual configuration you will need:
Code:
ifconfig eth0 IP_ADDRESS_YOU_WANT_TO_ASSINGN netmask YOUR_SUBNETMASK
route add default gateway IP_ADDRESS_OF_YOUR_GW dev eth0
setprop net.dns1 IP_OF_YOUR_DNS_SERVER
I am not sure if I do something wrong during configuration, because eth0 interface will only work in apps like the browser if I connect to my network via wifi first (see the my first posts for detailed explanation).
I can turn my wifi off afterwards and use ethernet instead but for configuration I need to start wifi first.
I am not sure why - I still could not figure out the problem...
Related
im trying to get an internet connection through my wifi connection. i have done search's and lots of people seem to be asking the same question but nobody has the answer.
at the moment i can access my c: using an application called Resco explorer. but i can not connect to the internet. im not sure what setting i should have on the wifi manger and on my pc. im also using AOL as my isp.
PLS PLS help :lol:
Edit:
also i can not connect to activesync (version 3.8.0) via wifi. maybe if i was able to connect to this the internet would work as it does when its docked??????
looks like a no then
I got mine working but setting my wireless network adapter to connect to "Work".
Under Settings>Connections>Tasks>Manage existing connections>Proxy Settings> check the "This network connects to the internet" box
then
Under Settings>Connections>Advanced>Select Networks> "Programs that automatically connect to the internet should connect using:" to "My Work Network" (and the same with one for private network)
Also in your active sync settings, make sure your connection settings allow network (Ethernet) and RAS connections.
From previous research around this, i'm pretty sure you can only use the internet pass through under "WORK" settings only.
*thought i'd better register and contribute as i've gained a fair bit from this forum.
no good anyother ideas. i have searched through hundreds of threads and still no go
help pls
Make sure you have "Enable Netbios over TCP/IP" checked in your TCP/IP Advanced settings.
i have done this on both my wifi network and my isp network.
still not working
Have you checked if you're getting an IP address from your Wireless Router's DHCP server? Also DNS settings and Gateway address should be there.
You can check this easily by using vxUtil (free )
these are my settings:
tiacxwln1 - tiacxwln compatible wireless
Ip address 192.168.0.2
subnet mask 255.255.255.0
default gateway 192.168.0.1
primary DNS 192.168.0.1
secondary dns
primary wins
seconfdary wins
DHCPs server 192.168.0.1
under serial usb
IP address 192.168.55.101
subnet mask 255.255.255.0
default gateway 192.168.55.100
primary DNS 127.0.0.1
Getting this error when I tried to allow my broadband connection to share with my wifi connection. If I unplug the wifi connection and try and share with another network I don’t get any errors.
Internet connection sharing (ics) cannot be enabled due to IP address conflict on the network. ICS requires the host be configured to use 192.168.0.1 please ensure that no other client on the network is configured to use 192.168.0.1
hmmm ... ever had the same problem. all devices are able to connect to the same router except mine sx66.
then i change the router's channel to '1' .. tada .. now everyone is connected. it might sounds silly, but it worked for me.
try changing your ap wireless channel.
Re: does NE1 have the answer to wifi not connecting to the n
robboy said:
Edit:
also i can not connect to activesync (version 3.8.0) via wifi. maybe if i was able to connect to this the internet would work as it does when its docked??????
Click to expand...
Click to collapse
i found the problem with activesync 3.8 and 4.0 somehow, so i reverted back to 3.7, now wifi can sync.
afaik, connecting to internet has nothing to do with activesync. its a direct connection to wifi router. use work location and check the proxy settings if u hv any? (at home i use connect to internet without proxy, at work i use connect to internet with proxy).
Also, for Activsync with wifi, make sure that the WINS server address is that of yr PC u want to sync with.
Hi,
I'm experiencing a weird problem and please let me know if it's only my problem or there is some work around for it.
My phone is SX66 upgraded to 1.40 ROM + 1.13 Radio stack
I can connect Wifi fine whenever I have some phone signal (at work). Whenever I go home where the phone signal is weak then the WIFI couldn't get connected (I believe I set up my home network correctly as I've been using it for so long and configure it for several computer/laptop in house). The network could detect the AP with the SSID but I just couldn't connect to it even I'm sitting right next to the AP.
ROM 1.40
Radio: 1.13
MDD
Are you sure it isn't connecting? What has led you to this conclusion?
Is it possible that it is connecting, but that you just can't browse the internet, in which case check your connection proxy settings. If your work uses a proxy server and you've enabled the pass-through setting in ActiveSync, your network connection may be configured with your work proxy server.
If you're sure you're just not connecting however, things to check are;
WEP/WPA Encryption - If you're using it and have other wireless devices on your network, you no doubt know what to do. If not, say so & I can help you.
DHCP - Does your router/AP support Auto-IP Addressing? Is it enabled? If not, you'll have to configure the WiFi card with a static IP within the same subnet as your router. Ask if you need help.
MAC Filtering - Are you blocking unauthorised MAC Addresses (on your router/ap)?
Interference - Wireless A/V Senders and digital cordless phones are common culprits for RFI. 802.11x APs support multiple channels (most default to channel 11), and you can change these in case of interference. Once again, if you have other WiFi gear already connected with good, strong signals, you can probably discount this one.
Sorry if this is all elementary to you - I don't know how technical you are.
Thanks for your reply.
> Are you sure it isn't connecting? What has led you to this conclusion?
Yes, I've check wireless status on the phone. "Connected to the network", and the AP with DHCP on showed the status of an IP has been allocate to the SX66 mac address. However I dont' really believe it then I check the "Adater", it said network available, and the WIFI icon just didnot show any traffic.
> Is it possible that it is connecting, but that you just can't browse the internet, in which case check your connection proxy settings. If your work uses a proxy server and you've enabled the pass-through setting in ActiveSync, your network connection may be configured with your work proxy server.
I've experience once with the internet connection via Active Sync so I disable the passthrough. Both home and work doesn't have proxy server so I selected not to have any on the phone.
> WEP/WPA Encryption - If you're using it and have other wireless devices on your network, you no doubt know what to do. If not, say so & I can help you.
At work, I have 128 WEP and the connection works fine with the key. At home, I open my network but using MAC filtering to protect it. I have problem with the open network one at home. Perhaps, I will try to setup WEP at home and see if it can work.
The only thing I'm not really clear is the difference between setting "WPA" and "WPA-PSK" from the phone.
> DHCP - Does your router/AP support Auto-IP Addressing? Is it enabled? If not, you'll have to configure the WiFi card with a static IP within the same subnet as your router. Ask if you need help.
Yes, DHCP enable as I don't want to change it back and forth when traveling.
> MAC Filtering - Are you blocking unauthorised MAC Addresses (on your router/ap)?
I do it and I already opened the network and then captured the MAC address into the AP memory. (that's why I think it's connected but will check).
> Interference -
Not really, I'm 6' away from the AP and I don't have any cordless device in my computer room.
> Sorry if this is all elementary to you - I don't know how technical you
are.
No problem, I'd like to learn more about this PDA. The concept is about the same with PC, but the tools to debug is not there. I can't use tracert/traceroute, ifconfig or ping broadcast to really know if I'm the network.
Once again, thanks a lot.
Okay, well it sounds like you're on the right track & know what you're doing.
A useful troubleshooting tool, which gives you tracert, ping, whios, ipconfig and a host of other tools is "vxUtil", which is freeware. I'd give you a URL for downloading it, but I'm on my iMate now (sipping coffee by the Yarra in a Melbourne Cafe - oh what a techno-wanker am I!), but search these forums or Google it and you'll find it.
Now, regarding the proxy thing... These PPCs are a little tricky with their internet settings, and I had to create a different 'connect using...' connection profile, if that makes sense. The important setting within the profile, which is under the Proxy tab, from memory, is "This network connects to the internet".
Now for some reason, if you don't enter in a proxy server here, that check-box doesn't stay checked when you ok your way out. So what I've had to do is go into the advanced area & enter anything in the "wap" proxy, then ok out.
Strange, but it seems to work. Although I always leave my "Private network" on "My Work Network", I can now browse the 'Net through the WiFi AP/Router.
Download vxUtil & see if you can ping your AP, then go from there.
I've worked around the problem by using static IP address instead of depending on DHCP. Thanks to Hitchhiker software. I noticed that it was trying to obtain IP address from DHCP but failed. (The very same DHCP work wells for the rest of my network). Anyway, I will use Hitchhiker to switch IP back and forth if necessary.
Thanks a lot!
MDD
Great to hear you found the problem - well done.
I've got an EVO running CM6 stable with android-wireless-tether (pre7). I am able to pair/connect to my home PC by setting up a bluetooth PAN in Windows 7. I right click on my device, choose "Connect > Access Point" and it says "Connection Successful". The only thing I get now is "Identifying..." until I am stuck with the good ol' 169.xx... IP address.
I checked the log for the wireless tether app, and it shows:
Enabling NAT rules... done
Enabling IP forwarding... done
Tethering now running... done
error: SIOCSIFFLAGS (Cannot assign requested address)
I've done a little research on the error and tried a few suggestions (rebuild binary/config files, changing the default LAN IP in awt settings) to no avail.
I also tried disabling WiFi and just attempting to share the 3G connection which still isn't working out (same error). Can anyone help me out with this one? I've also tried awt pre8 with the same results.
I had same setup and problem. Started the supper user app and quit app. Powered down phone restarted phone. After restart WiFi tether worked fine. Don't know why .
Sent from my PC36100 using XDA App
Just turn on wireless teather and the go to access conections fine androidap and connect to that. Why do you have to use blue tooth am I missing something? Wireless teather is in the settings with CM6 so you dont need an extra app for teather?
Thanks for the suggestions. I tried opening/closing SU app and rebooting, got the same result.
The reason why I am doing it this way is because I have a PC with only a network card (not WiFi). It's about 30/40 ft. from my router. Rather than buying a wireless card or some cable, I'm connecting via bluetooth and sharing my phones WiFi connection.
I understand if I had a WiFi adapter I could just use the built in Hotspot feature, but if I had WiFi, I would rather connect directly to the router.
I'm definitely interested in this too. At work, we have a no-wireless router policy, and I don't really feel like firing it up and have a guy holding a Fluke wireless network analyzer come and find me.
Bluetooth is alright for what I need. Seems to almost be a kernel issue or something. Worked *perfectly* with my N1, even with pre8. The EVO with CM6 stable isnt working. Just as a note, the wifi portion works correctly.
Actually let me rephrase : The bluetooth section does work, I believe there might be an issue related to the dnsmasq dhcp server not being able to serve IPs. The 'Upload' section of the information panel changes, the Green Download section stays 0.00. The client never receives an IP address, and thats about it.
Logcat didnt really show me much of anything critical error-wise, I'm really hoping that I can downgrade/upgrade a kernel in order to support whatever hardware changes there were between the N1 and the EVO.
I checked the wireless router wifi mode, and it no longer works either. 'Started with errors' is what I get now when in the wifi mode. The built-android wireless tether works fine, but I either wish I could hide the ESSID or have a bluetooth option available.
It *seems* related to the kernel, but logcat doesnt mention anything about not being able to load a module, and the wifi-tether app doesnt have a txt log, or does it?
I have a question regarding tethering via wifi on my T989D.
I am using the Juggernaut v5.0 on my Telus T989D. It has wifi-sharing app built in. When I use this application to share my mobile internet with my PC, I get two different ip addresses. For example, use my PC's browser, I find my PC's ip address is 123.123.123.57, however my phone's IP address is 123.123.123.101. So my phone and my pc have different ip addresses.
Strange enough, my Samsung Vibrant (T959 from TMobile), is different. I use wifi tethering for root user app, and I find my PC and my phone (T959) share the same ip address.
Why they are different on my T989D?
The problem I am having right now is, tethering via T989D's built-in function is slow. Sometimes connection drops. However the tethering via my T959 is very reliable and fast.
Is there a way to disable built-in tethering on T989D and use the tethering for root user app on my T989D? I have tried to freeze the tether manager, but tethering for root user still has error in log and I cannot connect to it at all.
Please help, I want to fix my tethering problem with T989D.
thanks
think about it...
when you are WiFi tethering, your phone is acting as the router, and it provides its own IP to you
you don't get the Mobilicity IP on your laptop or whatever it's hooking up to your phone on WiFi
Sorry I don't get it.
Why my T989D and T959 act differently?
Basically there are two ways of tethering your phone to your PC, (to allow the PC to access the internet through your phone's data connection). The first way is connect PC to the phone, and then to configure your PC to see the phone as the network adapter. This is the method used when you configure USB tethering and you connect the PC to the phone with a USB cable. In that case there will only be 1 IP address assigned, because the PC is using the phone as the network adapter. (Imagine the phone is just an ethernet adapter for the PC)
The second way is to connect your phone to your PC and then to configure the PC to access the phone as if it were a Wireless Access Point (WAP). This is the method used when you use Wi-Fi sharing, (called Portable Hotspot). It's called sharing because the phone can share access to its data connection through its Wi-Fi hardware, for up to 8 different PCs simultaneously. In order to do this the phone has to route data requests correctly between the connected computers. It does this by assigning itself 1 IP address, and then assigning each PC that's connected to it, a different IP address. This is similar to setting up a wireless router at home to share a single internet connection between multiple PCs.
Usually USB tethering results in 1 IP address for both phone (network adapter) and PC, and Wi-Fi sharing/tethering results in 1 IP address for the phone and another IP address for each connected PC. However, I suppose it's possible to use different Wi-Fi tethering software that connects the PC to the phone via Wi-Fi, using only 1 IP address for both phone and PC, like the USB tether method. This would mean you couldn't share the connection, but it may work faster, since the phone wouldn't need to do any routing.
If the android-wifi-tether app is what you refer to as "wifi tethering for root user app", it's worth it to see if it works on the T989. (I'd be curious if it works too). However, if you're using Juggernaut 5.0, you should be able to install android-wifi-tether, and it should work. You shouldn't actually have a Tethering manager app in your list of apps, I don't and I'm using 5.0. If you do, and freezing Tethering manager doesn't allow this app to work, then I would try freezing both the Wi-Fi sharing app and the Wi-Fi sharing manager app as well. If it still doesn't work I'd be tempted to reflash the Juggernaut 5.0 ROM, and then install the android-wifi-tether app again, and see if it works.
Good Luck..
Thanks Jasnn, this really helped and I am now clear.
Yes, the application I am referring to was android-wifi-tether. It works flawlessly
on T959D. it is very slow on my T989D with Juggernaut 5.0/Telus modem.
If I reboot the phone and start tethering using android-wifi-tether, the application starts, but there is one error in log:
Setting ad-hoc mode: failed.
IP address are still different. My pc and phone has two different ipaddress.
I'd like to have the same ipaddress, also one thing bugs me is, the internet connection is not stable, the internet goes on and off. Lots of t989/D users have experienced this problem, there is no cure yet.
thanks
jasnn said:
Basically there are two ways of tethering your phone to your PC, (to allow the PC to access the internet through your phone's data connection). The first way is connect PC to the phone, and then to configure your PC to see the phone as the network adapter. This is the method used when you configure USB tethering and you connect the PC to the phone with a USB cable. In that case there will only be 1 IP address assigned, because the PC is using the phone as the network adapter. (Imagine the phone is just an ethernet adapter for the PC)
The second way is to connect your phone to your PC and then to configure the PC to access the phone as if it were a Wireless Access Point (WAP). This is the method used when you use Wi-Fi sharing, (called Portable Hotspot). It's called sharing because the phone can share access to its data connection through its Wi-Fi hardware, for up to 8 different PCs simultaneously. In order to do this the phone has to route data requests correctly between the connected computers. It does this by assigning itself 1 IP address, and then assigning each PC that's connected to it, a different IP address. This is similar to setting up a wireless router at home to share a single internet connection between multiple PCs.
Usually USB tethering results in 1 IP address for both phone (network adapter) and PC, and Wi-Fi sharing/tethering results in 1 IP address for the phone and another IP address for each connected PC. However, I suppose it's possible to use different Wi-Fi tethering software that connects the PC to the phone via Wi-Fi, using only 1 IP address for both phone and PC, like the USB tether method. This would mean you couldn't share the connection, but it may work faster, since the phone wouldn't need to do any routing.
If the android-wifi-tether app is what you refer to as "wifi tethering for root user app", it's worth it to see if it works on the T989. (I'd be curious if it works too). However, if you're using Juggernaut 5.0, you should be able to install android-wifi-tether, and it should work. You shouldn't actually have a Tethering manager app in your list of apps, I don't and I'm using 5.0. If you do, and freezing Tethering manager doesn't allow this app to work, then I would try freezing both the Wi-Fi sharing app and the Wi-Fi sharing manager app as well. If it still doesn't work I'd be tempted to reflash the Juggernaut 5.0 ROM, and then install the android-wifi-tether app again, and see if it works.
Good Luck..
Click to expand...
Click to collapse
What does it take to configure an ethernet eth0 device on my S9 (Andorid 10)? Under what conditions does it recognize a network interface to be connected and worthy to configure permanently? Does it test for certain internet hosts? Does it test if DNS requests being answered?
I have an usb ethernet adapter which is recognized by my S9. Now I want to give the ethernet interface a static IP address in order to be able to receive UDP packages from an other ethernet device. These two devices are the only ones on the network. I will use it out in the wild where there is no full featured network or other infrastructure, and the devices would just communicate using their hard coded IP addresses.
However the S9 refuses to accept my manual configuration and does not bring the interface up (after a brief (2s?) periode of trying). In the past, with lineageOS and an S5 i was able to install a special file in the system partition preconfiguring the device. i didnt root the S9, so this option is not available.
What are the prerequisits for android to accept the ethernet configuration and setting the interface to UP? How can I fake those prerequisits to be able to configure my eth0 and receive packages on my IP address?
Update: switching the phone into airplane mode seemed to have made it "try harder" to bring eth0 up. however, it was not up continously but went down for a second every now and then. I am still looking for a robust solution.