I have an original AFTV gen 1 running the latest (end of Aug) software.
I have it connected via an ethernet cable, but need to change the DNS sever settings.
If I go under Settings/Network it shows the ethernet connection and it lets me go through the settings and I can enter the changes (new DNS settings) that I want. At the end it lets you press the "play" button to save and it looks like it works.
But when you go back to look at the connection the changes are not saved or applied - I have tried this repeated times - but no luck.
There is an option to 'forget' the connection. However it doesnt appear you can remove the ethernet connection.
I disconnected the ethernet cable and the device switches to wifi - I managed to set up a wifi connection and specify my custom DNS entries, but would really prefer it to be using the ethernet connection because its usually more responsive.
I had thought about doing a full factory restore, but dont really want to have to set all my apps up again - and there is no guarantee that it will let me change the DNS settings anyway.
Anyone got any good ideas or suggestions?
Related
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.
Stuck at choose network screen,not connecting to my network-my network is working on all other devices ,OUYA keeps on saying"please check your internet connection and try again"
Wifi or wired? Can you try the other way, or change locations, jacks, etc. If that doesn't work try changing the wifi network to a new broadcast SID name, maybe without security for testing.
Anything unusual about your network?
If using wireless go into settings and turn off ethernet...
First time connecting? The OUYA had wifi problems out of the box that have been...improved (not fixed), the best way to set it up is just use ethernet, after the initial updates you should be fine to use wifi
I have installed cwm recovery and is on ouya plus rom
its fault of ouya launcher,I managed to sideload nova launcher,am using nova as default launcher,now i can download from playstore:good:didnt checkout ouya store thoough
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...
Hello everyone. I'm going to share a way for you to control your CWM install over WiFi, sort-of. Do not ask for a pure WiFi implementation, I am more interested in other projects here that may or may not happen with the release of 5.0 sources and rbox's partial unlock.
Next, here is a list of things you'll need:
A WiFi router
A laptop or WiFi device
patience
time
Now that we have all of this, you will connect your gateway into your wireless router, in order to provide an internet connection. If you do not have a way to plug in your gateway, you may want to explore using DD-WRT and the router as a client-bridge (this will connect to your home's network, then turn the router into a switch). With this completed, reboot your Fire TV to the recovery. You will see that it has an IP on your sub-net (just like your laptop and phone). This is because the router is doing all of the work and connecting the devices, much like if the WiFi inside of the Fire TV was utilized.
All you must do now is type the following:
Code:
adb connect X.X.X.X
where the X's are replaced with the IP shown on the Fire TV's screen.
Now do as you please, you have your WiFi control. If you desire to donate, do so to @rbox He was the one who allowed you to do this stuff in the first place.
i'm running 13.2 on a fire tv. it's connected to my home network through ethernet.
i can access it through any browser on my windows 8 computer connected to the same network (IP address:8080).
however, i can't seem to connect to it through the Yatse app on my phone. neither auto detection nor by entering in the IP and port manually work. the phone is connected through wifi on the same network. (Nexus 5, 4.4.4).
i've followed all the directions on this page to setup the fire tv: http://yatse.leetzone.org/redmine/p...#XBMC-Gotham-Version-13-Kodi-Helix-Version-14
i've also tried port forwarding through my router (2Wire 3600HGV)
i chose the IP address of the fire tv and forwarded the port 8080
tcp: 8080
udp: 8080
i wasn't sure of the application type so i left it blank. do i need to change it to one of the ones listed? did i miss something else?
i've also tried other ports (8111, 8181). still won't connect
1lazysheep said:
i'm running 13.2 on a fire tv. it's connected to my home network through ethernet.
i can access it through any browser on my windows 8 computer connected to the same network (IP address:8080).
however, i can't seem to connect to it through the Yatse app on my phone. neither auto detection nor by entering in the IP and port manually work. the phone is connected through wifi on the same network. (Nexus 5, 4.4.4).
i've followed all the directions on this page to setup the fire tv: http://yatse.leetzone.org/redmine/p...#XBMC-Gotham-Version-13-Kodi-Helix-Version-14
i've also tried port forwarding through my router (2Wire 3600HGV)
i chose the IP address of the fire tv and forwarded the port 8080
tcp: 8080
udp: 8080
i wasn't sure of the application type so i left it blank. do i need to change it to one of the ones listed? did i miss something else?
i've also tried other ports (8111, 8181). still won't connect
Click to expand...
Click to collapse
I forget the exact name, but in settings on XBMC are you sure you've allowed 'controlling device over webserver' and whatever other options there are. Basically enabling to allow to control the xbmc from external devices. As my Yatse picked up my AFTV as soon as i had it installed and running.
swiss_lis said:
I forget the exact name, but in settings on XBMC are you sure you've allowed 'controlling device over webserver' and whatever other options there are. Basically enabling to allow to control the xbmc from external devices. As my Yatse picked up my AFTV as soon as i had it installed and running.
Click to expand...
Click to collapse
yes, i followed every step on the link i posted
Enabled: Allow control of XBMC via HTTP (in Webserver menu)
Enabled: Allow programs on this system to control XBMC (in Remote control menu)
Enabled: Allow programs on other systems to control XBMC (in Remote control menu)
1lazysheep said:
yes, i followed every step on the link i posted
Enabled: Allow control of XBMC via HTTP (in Webserver menu)
Enabled: Allow programs on this system to control XBMC (in Remote control menu)
Enabled: Allow programs on other systems to control XBMC (in Remote control menu)
Click to expand...
Click to collapse
Ok, it seems you got ATT and the dread ATT router/modem combo. This thing is notorious for setting up network. Here is a few things you can do. First, ping the FireTV. I see that you set a static IP for the FireTV. Check if that is the actual IP of the FireTV.
Go to System->System Info->Network. Check if the address is the same as the one that you set for static IP, then ping it. In Window, open command center and type ping <ip address of fire tv>
About port opening, you don't really need it. If this is intra-network within the same subnet domain (same WIFI for layman term), then opening port is not necessary.
Once you can ping the FireTV, you can test that the Webserver is working by open any browser. Type this in:
http://<ip address>:<port>
For example: mine is
http://192.168.1.55:8080
If you can access the webserver interface, then it means the network and firetv works like it supposed to be and the problem is with your phone.
Make sure that the phone is in the same WIFI, don't try to use mobile network to control the Fire TV. The port openning is too complicate and represent a security risk. Turns it off.
Also, I just want to note, sometimes the ATT router won't allow communication with static IP. This rarely happens, and it is a bug. What you want to do is to just let the router gives the FireTV its own IP address then use that address to set up.
vi6s said:
Ok, it seems you got ATT and the dread ATT router/modem combo. This thing is notorious for setting up network. Here is a few things you can do. First, ping the FireTV. I see that you set a static IP for the FireTV. Check if that is the actual IP of the FireTV.
Go to System->System Info->Network. Check if the address is the same as the one that you set for static IP, then ping it. In Window, open command center and type ping <ip address of fire tv>
About port opening, you don't really need it. If this is intra-network within the same subnet domain (same WIFI for layman term), then opening port is not necessary.
Once you can ping the FireTV, you can test that the Webserver is working by open any browser. Type this in:
http://<ip address>:<port>
For example: mine is
http://192.168.1.55:8080
If you can access the webserver interface, then it means the network and firetv works like it supposed to be and the problem is with your phone.
Make sure that the phone is in the same WIFI, don't try to use mobile network to control the Fire TV. The port openning is too complicate and represent a security risk. Turns it off.
Also, I just want to note, sometimes the ATT router won't allow communication with static IP. This rarely happens, and it is a bug. What you want to do is to just let the router gives the FireTV its own IP address then use that address to set up.
Click to expand...
Click to collapse
thank you for the detailed reply.
you're right about the craptastic 2wire modem/router. i've had a ton of trouble setting up my network in the past
with that in mind, i decided to plug an old linksys directly (ethernet) to the 2wire. then i connected my phone's wifi to the linksys. i was able to connect yatse with the first try!
thanks again for the suggestions. :good: