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 googled IPv6 and WP7 and found that mango is suppose to offer this to WP7.
My Nokia Lumia 800 however is blissfully ignorant when it comes to IPv6, it simply doesn't get an address and is therefore unable to connect to any IPv6 host.
Now I don't have any other handsets, so I cannot determine if this is a Nokia special, or that Mango doesn't offer any IPv6 support, contrary to the articles that claim it does offer IPv6 support.
Can anyone chime in here ?
Does your Lumia receive an IPv6 assigned by your carrier? I guess if your carrier dosn't assign IPv6 adresses you can do nothing about this...
I have IPv6 configured on my local network and I can confirm that Lumia actually gets an IPv6 address (public, routable one, not only link-local) and I can also ping it over IPv6.
It doesn't, however, seem to open any IPv6 web pages and all the pages with both v4 and v6 fallback to v4.
Hmm, how did you find out it got an IPv6 address ? Whireshark ?
As far as I know, there is no way of checking on the device itself, in any case, sites like test-ipv6 com report that the Lumia doesn't have any IPv6 address.
It is strange, as I have a dhcpv6 server for statefull configuration (mainly pc's) and I also have two IPv6 routers that advertise RA's to devices. My Nokia N82 and E72 and the IPAD2 all get global addresses and are happily surfing to IPv6 sites.
I presume you are on Mango or 7740 ?
I've first checked ARP table on my computer, found IPv4 of my phone and matched its MAC with a list of IPv6 neighbors (netsh -> interface ipv6 -> show neighbors).
And yes, it is Mango.
ChrisKringel said:
Does your Lumia receive an IPv6 assigned by your carrier? I guess if your carrier dosn't assign IPv6 adresses you can do nothing about this...
Click to expand...
Click to collapse
Sorry should have mentioned, my home network is fully IPv6 enabled for about two years now. I run one native IPv6 connection, where I get a :/48 prefix. My main line (in speed) is a tunnel connection over Ipv4 with a different :/48 prefix from the tunnelbroker.
The setup is such, that my Servers all get a fixed IPv6 address in the first available :/64 and are routed over the tunnel. My Windows PC's get routed over the same tunnel using a DHCPv6 server, all other devices either go over one or the other, depending on which RA (route advertisement) gets to them first, as both IPv6 routers also advertise their routes (pc's are setup not to listen to ra's in any case).
This works fine for my two Symbian powered Nokia's, as well as for the IPAD2, they only device in my house who seems to be unaware of IPv6 is the Lumia.
sjaak327 said:
Hmm, how did you find out it got an IPv6 address ? Whireshark ?
As far as I know, there is no way of checking on the device itself, in any case, sites like test-ipv6 com report that the Lumia doesn't have any IPv6 address.
It is strange, as I have a dhcpv6 server for statefull configuration (mainly pc's) and I also have two IPv6 routers that advertise RA's to devices. My Nokia N82 and E72 and the IPAD2 all get global addresses and are happily surfing to IPv6 sites.
I presume you are on Mango or 7740 ?
Click to expand...
Click to collapse
Are there websites that you use that are only accessible through IPv6?
http://test-ipv6.com tells me that I don't have access to IPv6 from work.
Your IPv4 address on the public Internet appears to be xxx.xxx.xxx.xxx
No IPv6 address detected [more info]
You appear to be able to browse the IPv4 Internet only. You will not be able to reach IPv6-only sites.
Your DNS server (possibly run by your ISP) appears to have IPv6 Internet access
My iPhone through 3G on AT&T gives the same result, expect the last one, which says:
Your DNS server (possibly run by your ISP) appears to have no access to the IPv6 Internet, or is not configured to use it. This may in the future restrict your ability to reach IPv6-only sites.
This is not even using Wi-Fi. So, major carriers aren't even supporting IPv6 browsing yet. It's not iPhone specific. Just being on AT&T 3G in Minnesota means no IPv6.
I'd like to know of even 1 real site that this prevents you from accessing.
----
Just read your post above.
What problem are you experiencing on your network by the device not having an IPv6 address?
Why not also support IPv4 in your internal network?
It's pretty unlikely that you would need that many addresses internally.
Yes, IPv6 on 3G (cellular network in general) support is really limited and it is much harder for both operators and mobile phones to support it.
It would be, however, about time, that WP starts supporting IPv6 over wifi.
N37-L0RD said:
I've first checked ARP table on my computer, found IPv4 of my phone and matched its MAC with a list of IPv6 neighbors (netsh -> interface ipv6 -> show neighbors).
And yes, it is Mango.
Click to expand...
Click to collapse
Hmm, Using Netsh int ipv6 show neighbors, I see my server, a few other clients, the Ipad, but not the Lumia. If you go to test-ipv6.com, does it show the global unicast IPv6 address ?
If it matters:
OS: 7.10.7740.16
FW: 1600.2479.7740.11451
HW: 112.1402.2.3
JVH3 said:
Are there websites that you use that are only accessible through IPv6?
http://test-ipv6.com tells me that I don't have access to IPv6 from work.
Your IPv4 address on the public Internet appears to be xxx.xxx.xxx.xxx
No IPv6 address detected [more info]
You appear to be able to browse the IPv4 Internet only. You will not be able to reach IPv6-only sites.
Your DNS server (possibly run by your ISP) appears to have IPv6 Internet access
My iPhone through 3G on AT&T gives the same result, expect the last one, which says:
Your DNS server (possibly run by your ISP) appears to have no access to the IPv6 Internet, or is not configured to use it. This may in the future restrict your ability to reach IPv6-only sites.
This is not even using Wi-Fi. So, major carriers aren't even supporting IPv6 browsing yet. It's not iPhone specific. Just being on AT&T 3G in Minnesota means no IPv6.
I'd like to know of even 1 real site that this prevents you from accessing.
----
Just read your post above.
What problem are you experiencing on your network by the device not having an IPv6 address?
Why not also support IPv4 in your internal network?
It's pretty unlikely that you would need that many addresses internally.
Click to expand...
Click to collapse
I do support IPv4 on my internal network as well, that is not the point. It is 2012, all my devices run dual stack, and I think it is time that a Nokia released in November 2011 should also be able to handle dual stack and connect using either IPv4 or IPv6, I mean come on, even a Nokia N82 which is over three years old can do it !
And yes, if I go with a pc, or the ipad or the N82 to that Ipv6 test site, they all report a global IPv6 address and pass with flying colors, the Lumia only has a IPv4 address.
Oh and to make myself clear, (if it isn't obvious from previous posts) I am not talking about 3g, I am talking about my home network over wifi.
sjaak327 said:
I do support IPv4 on my internal network as well, that is not the point. It is 2012, all my devices run dual stack, and I think it is time that a Nokia released in November 2011 should also be able to handle dual stack and connect using either IPv4 or IPv6, I mean come on, even a Nokia N82 which is over three years old can do it !
And yes, if I go with a pc, or the ipad or the N82 to that Ipv6 test site, they all report a global IPv6 address and pass with flying colors, the Lumia only has a IPv4 address.
Oh and to make myself clear, (if it isn't obvious from previous posts) I am not talking about 3g, I am talking about my home network over wifi.
Click to expand...
Click to collapse
I understood that you were talking about your local network with WiFi. I only mentioned the 3G, to show that the carriers are not yet even giving access to IPv6 only Internet sites.
Is the reason you need this to get to IPv6 only internet sites from home?
Or do you restrict access to some machines on your network to machines with IPv6 addresses for the security advantages?
Or is the reason strictly because the number of IP address under IPv4 is running out and at some point new sites will be forced into being IPv6 only? At that point the phone will not be able to access the new sites.
I don't see a reason for Nokia not supporting IPv6. It's been around for a long time. We've know it was needed for a long time.
The only thing I can think is that most phones are only used for about 2 years and you aren't going to see alot, if any, major sites switching to IPv6 only in that period of time. Realistically all major sites will support IPv4 for at least 5 years or longer.
Yes, Nokia should support it. But, phones not supporting it today are not going to cause typical users any problems.
JVH3 said:
I understood that you were talking about your local network with WiFi. I only mentioned the 3G, to show that the carriers are not yet even giving access to IPv6 only Internet sites.
Is the reason you need this to get to IPv6 only internet sites from home?
Or do you restrict access to some machines on your network to machines with IPv6 addresses for the security advantages?
Or is the reason strictly because the number of IP address under IPv4 is running out and at some point new sites will be forced into being IPv6 only? At that point the phone will not be able to access the new sites.
I don't see a reason for Nokia not supporting IPv6. It's been around for a long time. We've know it was needed for a long time.
The only thing I can think is that most phones are only used for about 2 years and you aren't going to see alot, if any, major sites switching to IPv6 only in that period of time. Realistically all major sites will support IPv4 for at least 5 years or longer.
Yes, Nokia should support it. But, phones not supporting it today are not going to cause typical users any problems.
Click to expand...
Click to collapse
All you say is true, yes there is no problem now, the phone supports IPv4 just fine, however, since it is 2012, and since IPv6 is around for > 10 years, I am utterly disappointed by either WP or Nokia not fully supporting IPv6, and this should really be rectified asap,regardless of all the things you said. Not to mention the fact that in Asia things are quickly going to IPv6, simply because they did already run out of IPv4 addresses.
The sooner we get rid of IPv4 the better, the stack has run it course and is redundant.
sjaak327 said:
Hmm, Using Netsh int ipv6 show neighbors, I see my server, a few other clients, the Ipad, but not the Lumia. If you go to test-ipv6.com, does it show the global unicast IPv6 address ?
If it matters:
OS: 7.10.7740.16
FW: 1600.2479.7740.11451
HW: 112.1402.2.3
Click to expand...
Click to collapse
Sorry, I made a big mistake by making false assumptions. It appears that the IPv6 enabled Nokia was actually Nokia E52 (I've only checked MAC vendor and forgot about the other phone having wireless enabled).
It seems Lumia doesn't get IPv6 after all.
Hello!
I'm having issues getting wifi/hotspot tethering to work when pointing the Note II toward a non-standard APN.
Current environment:
Note II devices on T-Mobile US. Provisioning on the T-Mobile side allows access to the B2B APN, as opposed to the standard fast/epc APN the device normally comes configured to access. Turning B2B APN provisioning on actually disables access to the standard fast.t-mobile.com APN for native data, and the PCWEB APN for tethered connections. On the B2B APN, data originating on the device itself works just fine, but devices tethered to the Note II are not able to access the internet.
Wi-Fi connected PC receives an IP address of 192.168.43.16 (standard setup from Samsung), so the device is firing up the hotspot and handing out DHCP addresses. Network trace from T-Mobile shows 192.168.43.16 as the source address of the session, rather than showing the carrier address being handed to the phone. In short, it looks like the native tethering application is failing to NAT the session when pointed at the b2b.tmobile.com APN.
This is a rooted device with a custom ROM, so I side-loaded the WiFi Tether application. After some tweaks, I got tethering to work using the following options:
Device Profile: Generic ICS/JB (wlan0)
Setup Method: Netd-Ndc (master)
Set Netd Max Client Cmd (checked)
Wireless driver reload (checked)
Wireless driver reload 2 (checked)
Enable routing-fix (checked)
So, is there a way to tweak the settings in the native tethering function on the device to get the NAT to behave properly? Customer does not want to push the .apk for WiFi tether out to the devices in the field as the application requires root access and configuration. Entire install base of devices is custom ROM, and SOTI managed. If there is a way to easily push the app and config out to the devices, and have a push button wifi tethering experience for the end users, I might be able to convince them to go that route.
Your thoughts are appreciated!
Hi rob,
There's a dedicated T-Mobile(US) Note 2 Thread. This is the international forum.
I want to prevent my carrier from knowing that I am using CM11's native Hotspot or Tethering features. I know that they can look at the TTL of packets or analyze the traffic (Windows Update, Steam) to detect this. I have a subscription to a VPN service, Private Internet Access, which has an app on Android. If I enable the VPN mode of this app, will all the Hotspot traffic be routed through it, completely invisible to the carrier?
Searching showed me some conflicting answers on this, with some people saying to run it on the tethered device, and others saying to run it on the phone. I am thinking running VPN on phone, as the packets should appear to originate from the phone, rather than something 1 hop behind it.
kcattakcaz said:
I want to prevent my carrier from knowing that I am using CM11's native Hotspot or Tethering features. I know that they can look at the TTL of packets or analyze the traffic (Windows Update, Steam) to detect this. I have a subscription to a VPN service, Private Internet Access, which has an app on Android. If I enable the VPN mode of this app, will all the Hotspot traffic be routed through it, completely invisible to the carrier?
Searching showed me some conflicting answers on this, with some people saying to run it on the tethered device, and others saying to run it on the phone. I am thinking running VPN on phone, as the packets should appear to originate from the phone, rather than something 1 hop behind it.
Click to expand...
Click to collapse
To the best of my knowledge, they could easily know that you are connecting to the VPN tunnel as it utilizes a certain ports. However if it's correctly set up and utilize a secure protocol, all your traffic will get through the VPN and your ISP won't be able to decipher your online activities and your connection type or make sense of your internet traffic.
In other words, you may be using the VPN to connect to websites A, B, and C and send all sorts of interesting information to those websites; or send email; or whatever. Your ISP can see none of that. All they can see is encrypted data that they can't decrypt. So they know you're using a VPN, but they don't know what you're using it for.
Hope it could help.
Update: This is resolvable by setting the firewall to blacklist mode and inverting the selection. While I prefer whitelist mode, this will work until I can find a better solution.
Note, when inverting, make sure that "All Applications" isn't checked. It isn't obvious, because it should also be left unchecked in whitelist mode, but this will block everything in blacklist mode.
First off, this is on the Dev Edition (Sense) Lollipop release. Phone is S-off/bootloader unlocked, but I doubt that matters. I am using AFWall+ to manipulate the firewall (iptables) configuration.
The problem is USB tethering. DNS requests aren't getting through to the tethered device no matter what I do if iptables is configured. I checked the logs and they showed that process -11 (kernel) was blocked from sending UDP (DNS) to the tethered IP address. However, I specifically enabled the kernel, -12 (tethering DHCP & DNS), and root apps for good measure. Nothing.
However, it is JUST DNS. If I use an onboard terminal to nslookup the name, I can use the IP address from the tethered machine just fine. It appears that TCP isn't being blocked, just UDP. Further, local apps have no problem access the network in any way - it's just the USB tethered PC that is having trouble. I have not tried WiFi tethering yet.
I have tried my usual app, DroidWall, and now AFWall+, but neither can get it done. Something seems to have changed in Lollipop, because this used to work in KitKat.
Any ideas?