Privacy concerns on IPV4 implementation on Mobile networks.

Privacy concerns on IPV4 implementation on Mobile networks. - Networking

Edit:
I have figured out that you can have logging softwares within the system however the logging system will log all details from NAT to the client but what it cant log is the Transversing of Port numbers at the gateway...so my question is do mobile operators keep log of these tables after the expired session. So here is the scenario, to backtrace. you would need the website host to give you the ip address, source and destination port, timestamp etc to start the process, the ISP will then look at its Logs to find out the traffic requests but map each of these requests, the ISP will need to know the table which was used for transversing but according to my knowledge the table gets deleted or releases the port number and ip address information after its timed out idle.
Anyone who can let me know if network operators keep a copy of this table?
Thanks
Gents,
I was looking for some information regarding IPV4 implementation on mobile networks. I have read in detail the IPV4 implementation on mobile networks and also IPV6 theoretical implementation on mobile networks. So here is my analysis so far – For IPV4 on mobile networks.
Mobile networks use NAT for giving dynamic IP addresses to its mobile device users who connect to the internet. On the outside the mobile network operator might have a few external static or dynamic IP addresses. You can get a static external ip address for your mobile device or group of devices but you will have to pay for it. GPRS runs on the back of GSM or UTMS (3G) but looking at GPRS implementation, you have GSGN, SGSN and mobile node all working in harmony in a triangular modulation however where I am lost is with CDRs (call detail record) which are sent by CGF (charging gateway function). Do these records keep a record of internal IP assigned to the mobile device for which the packet was transmitted or not? So far what I have found looking at the format of a CDR is it records the ip of GSGN but not the mobile device. What I am trying to understand is if the mobile users can be traced back from external ip all the way back like reverse lookup? Please note this question is in regards to IPV4 on mobile networks not IPV6.
Can someone please shed some light on this?
Many thanks in advance
V

Related

Salvaging the hours and euros sunk

Since I'm having a couple of problems lately that will ultimately require me to hard-reset my TyTN in the near future, I figured I could document the steps I take to salvage the configuration as I go and learn this stuff.
My primary tool will be the Windows Mobile 5.0 Pocket PC SDK, especially the rapiconfig tool, that allows to process and query configuration information in the form of provisioning xml files.
RapiConfig sends the provisioning file to the device, processes it and saves the answer to RapiConfigOut.xml.
Lesson #1:
How to retrieve Messaging account settings, even if they appear to have vanished, using the EMAIL2 configuration service provider:
<!-- query-email2.xml -->
<wap-provisioningdoc>
<characteristic-query type="EMAIL2" recursive="TRUE" />
</wap-provisioningdoc>
C:\>RapiConfig.exe /p query-email2.xml
The result will be a list of manually configured messaging accounts, plus Hotmail and MMS.
The result will not include passwords (parm name="AUTHSECRET). To be later able and use the output file for restore, these params should be added for those accounts with (parm name="AUTHREQUIRED" value = "1") and the file should be saved under a meaningful name. Since MMS will be commonly setup by the ExtRom setup, it should be removed.
Next time we'll look at wireless connection setup.

Lesson #2:
How to enable RAPI access with manager privileges and retrieve WLAN settings.
The attempt to retrieve WLAN settings using the "Wi-Fi" characteristic will fail with "Access denied", because the Wi-Fi configuration provider requires manager level access, which is like Administrator on a PC.
By default, RAPI only uses user access level, and users can obviously not be allowed to manage WLAN settings using RAPI.
The SDK provides a way around this. Allowing RAPI access to manager-level features can be enabled by a security policy. This policy must be set using a signed configuration file.
The SDK contains a file "RapiAllowed.cpf" in the rapisecurity folder that can be used for this purpose.
However, first the certificate used to sign this file must be installed on the device.
For this, the SDKCerts.cab must be run on the device. This step might fail however, if the network provider chose to prevent the user from using unknown certificates.
The the RapiAllowed.cpf can be copied and run as well. There will be no feedback other than a SMS confirming the installation.
RAPI is a powerful interface, so the inverse, RapiRestricted.cpf, must be run before the device is brought into possible hostile enviroments (e.g. where some people might run Bluetooth scanners, USB ports on public computers, etc).
There is also a tool available from Microsoft called "Security Configuration Manager" that allows reviewing and resetting device security.
With RAPI security disabled, querying Wi-Fi is a piece of cake:

<wap-provisioningdoc>
<characteristic-query type="Wi-Fi" recursive="TRUE"/>
</wap-provisioningdoc>
C:\>rapiconfig /p query.xml
The RapiConfigOut.xml will show all configured WLANs grouped into access-point-based and ad-hoc networks, with a characteristic for each network.
The network key is included as dummy string "****************" that needs to be replaced by the real passphrase.
I guess the next thing is to take a look into the network settings provided by CM_Networks and CM_GPRS_Entries.

HB_TyTN, very interesting stuff in your lessons, thanks for your effort
Also you may like to check rapi unlocker here:
http://forum.xda-developers.com/showthread.php?t=252356

Excellent thread! Will definitely keep mentioining it in my forthcoming, related articles!

About networks
The network thing in Windows Mobile seems pretty messed up. In an attempt to make things easier, safer and more automated, I think, Microsoft left anybody on the way.
Here is what I understand and (warning), I may be totally off.
There are four pre-defined networks Internet, Corp, WAP and Secure WAP.
Although those may have different names based on OS language and HTC, provider or user choosing, the IDs of these networks are fixed and can be looked up in the SDK/include/connmgr.h file. E.g. Internet, is identified by 436EF144-B4FB-4863-A041-8F905A62C572.
These networks describe different setups in terms of routing, security or proxy settings or are used from different applications (e.g. WAP/MMS).
Of all networks, one is selected as Internet (public) and another can be chosen as private under Select Networks in Advanced Connections.
Internet will provide TCP/IP only. Private will provide access to Windows shares, and may connect to the internet, usually thru a proxy.
The Connection Manager separates the world into Internet and private, based on the URL of the server.
Non local server names, e.g. www.xda-developers.com will be connected with the network specfied as Internet.
Yes, this includes any directly entered IP address, as the detection is based on the occurrence of a "." dot in the server name. The only way around this is to specify the URL in Settings, Connections, Advanced, Exceptions (using * as a wildcard if necessary).
Sole server names and except URLs will be connected thru the network designated as private.
With each network, connections, network cards and wireless networks can be associated, so that, finally, the connection manager uses or dials one of those connections based on the network it chose to use.
That's a long intro into lesson #3: Querying network information
I'll start resetting RAPI security to restricted, by copying RapiRestricted.cpf to the device, running it and checking the SMS message for success. This should prevent any actual messing up something.
Now to querying networks using the CM_Networks configuration provider.

<wap-provisioningdoc>
<characteristic-query type="CM_Networks" recursive="TRUE"/>
</wap-provisioningdoc>
C:\>rapiconfig /p query.xml
C:\>notepad RapiConfigOut.xml
The introduction above is to explain why this query does not reveal anything useful, other than a list network names, their ID and an obscure "Secure" value, which is 0 for all my connections.
I find it more interesting to query the CM_PPPEntries or the CM_GPRSEntries providers. They use a similar, yet somewhat convoluted schema.
Here are the notable parts:
DestID associates the entry with one of the networks I talked about and queried above.
Phone is the number to dial for the connection. For GPRS, this entry is set to "~GPRS!". I wonder who came up with that string.
Username and Password are obvious and so is RequirePw.
DnsAddr, AltDnsAddr are not out of the ordinary, and if SpecificIpAddr is "1", the ip address is in IpAddr, although I'd assume it is assigned dynamically in most cases.
DeviceType and DeviceName are set to "modem" and "Cellular Line" for the connections that use the phone network.
DeviceSpecificRAW is the most dangerous entry here, since it contains the parameters for the phone device in binary form. I wonder if there is any point in looking into those other than to inflict pain.
Some of the device parameters are set verbosely, so let's rather look at those. However, your provider may not like it if you modify these vigorously.
If BearerInfoValid is 1, BearerInfoService and BearerInfoSpeed are supposed to specify the type of modem and it's speed. Values in my case are 1 -Async Modem and 15 - 9600 v32, which goes to show that the latter value is rather useless, because I know I get more than that with both UMTS and GPRS. So better not tamper with these.
CompressionInfoValid and RadioLinkInfoValid are set to 0 in my case, so one can easily do without.
GRPSInfoValid is set to 1, but the only real interesting parameter is GPRSInfoAccessPointName, which must be set for the GPRS connection to know whom to talk to.
GPRSInfoQOSSettingsValid and GPRSInfoMinQOSSettingsValid are 0, which is sad, because I'm really not happy with my GPRS Quality of Service and would have loved to improve it.
Now, that was a joke. QoS is a way of classifying network traffic for bandwidth and latency and I doubt any provider supports it for Joe Average.
For all the parameters documentation is in the Smartphone SDK about the Telephony and TSP API structures.
Finally, a list of default URL mappings, as found in the CM_Mapping provider documentation.
*://*.*/* The Internet
*://*/* My Corporate Network
wsp://*/* WAP Network
wsps://*/* Secure WAP Network
To query my personalization settings, next time I'll dive into the registry and see what I can do with RAPI configuration queries.

Is WAP still in use?

Hello everyone,
First off, I apologize if this is the wrong type of question, but you are the only community I know that has the knowledge of the technical details am I looking for. I have asked this in several communities but failed to deliver a proper question and get a proper response. In any case, if you are about to delete this post, please direct me to a more appropriate community.
Here is my train of thought, I hope you can follow:
So, I have this presentation about the Wireless Application Protocol (WAP) which I am having a hard time finding any recent news. All I can find is old articles about WML 2.1 and new phones that support WAP.
The more I search the more I start thinking that WAP is a thing of the past. But the problem is that I am not sure if this is correct. If it is dying, what is replacing it?
The WAP is a stack of 5 protocols. The top one is the application layer which includes the WML language. Under WAP are the various wireless interfaces (CDMA, EDGE, etc). WAP browsers send requests to WAP gateways in order to view a website which is written in (or translated to) WML. So far, so good.
What about Opera Mini??? This a browser designed for mobile phones that is capable of reading HTML (to a degree). How does Opera Mini access the internet? My guess is that it is not using WAP, but the standard TCP/IP stack. Can a cell phone (not a smart phone) use the TCP/IP stack? Is it powerful enough? What about Mobile IP? Is it TCP/Mobile IP?
I know that WAP is still in use. Motorola recently announced a series of low budget cell phones that are WAP-enabled. But doesn't the speed of 3G and the average phone with WiFi support renders WAP useless?
So, I guess my question is: if a mobile phone today (both cell phones and smart phones) access a website using a HTML-capable web browser, does it use the standard TCP/IP stack, a mobile version of it, or each phone has a proprietary model?
Am I even making sense??? :S
Thank you for your patience.

there are still wap pages out there but doubt that will inc
if your network operator support it wap pages will work in any browser
just as ugly www pages

Parts of WAP are still in use, however the majority of it has been replaced.
As I understand it the first version of WAP required special gateways and didn't use HTTP as the application layer. WAP 2.0 however dropped all this rubbish, and just went with HTTP.
In regards to the wireless protocols, the GSM protocols GPRS and EDGE are still used when there is no 3G signal available, however 3G is the preferred method. I don't believe there are any operators who only provide a 3G service without GSM fallback. 3G networks typically use a packet-switched network design for data services, similar to the internet.
The format of the pages themselves is another interesting one. The majority of 'mobile sites' nowadays just use regular HTML, or a subset of it. There are a few different XHTML standards targeted at mobile devices. The level of support varies greatly between handsets, however practically all phones made in the last five years will support some sort of CSS. WML is a markup language designed for WAP usage, however AFAIK it is basically not used now. I don't believe smart phones (Android at least) even support rendering WML pages. WML is an even stricter subset of HTML, and to be honest I don't really think is worth bothering with
Hope this helps, if you want some clarification of anything let me know!

thelucster said:
Parts of WAP are still in use, however the majority of it has been replaced.
As I understand it the first version of WAP required special gateways and didn't use HTTP as the application layer. WAP 2.0 however dropped all this rubbish, and just went with HTTP.
Click to expand...
Click to collapse
That was exactly what I wanted to find out. Thank you very much.
So, if I understand this correctly, when a mobile application wants to access a website with standard HTTP, it still uses the WAP 2.0 Stack; correct? If this is true, then Android or iPhone, or WinMo, or the rest, all have the WAP 2.0 stack embedded in their OS? Or is the WAP stack old and it has been replaced by proprietary TCP/IP implementations?
I think I am a little confused :S
thelucster said:
WML is a markup language designed for WAP usage, however AFAIK it is basically not used now. I don't believe smart phones (Android at least) even support rendering WML pages. WML is an even stricter subset of HTML, and to be honest I don't really think is worth bothering with
Click to expand...
Click to collapse
Well, WML was for WAP 1.0. WAP 2.0 supports XHTML Mobile Profile. So since there is no WAP 1.0 there is probably no WML also.
thelucster said:
Hope this helps, if you want some clarification of anything let me know!
Click to expand...
Click to collapse
It indeed helped. Thank you very much.

Hi, this thread has some factual errors, so figured it may be valuable for someone who looks for information and ends up here, to have a set of good information available in the thread.
kimolias said:
So, if I understand this correctly, when a mobile application wants to access a website with standard HTTP, it still uses the WAP 2.0 Stack; correct? If this is true, then Android or iPhone, or WinMo, or the rest, all have the WAP 2.0 stack embedded in their OS? Or is the WAP stack old and it has been replaced by proprietary TCP/IP implementations?
Click to expand...
Click to collapse
I am not sure what "mobile applications" that want to access websites you are talking about. The typical apps available on a device from the factory that need to connect somewhere are Browser, MMS and Email applications. Of these, the Browser is the one that wants to access a website and the browser has built-in the protocols it needs.
And also to clarify lets make it clear that WAP specs includes both specs for markup language (how to display the content) as well as transport protocols (how to send/get the data). But, for this post I will only comment on the data transport protocols and completely ignore the markup languages (WML, xHTML-MP and HTML) and how or where they are used.
BROWSER
Let's split the Browser into two types of browser first, to make things a little more clear.
1) WEB Browser
2) WAP Browser
The WEB Browser uses the "regular" HTTP protocol to connect directly to webserver (on top of TCP/IP provided by the operating system) to get content.
The WAP Browser can use WAP 1.2 (Wireless Session Protocol/Wireless Transaction Layer) to connect to a WAP Gateway, and the WAP Gateway in turn uses regular HTTP to get the content from the webserver.
The WAP Browser can use WAP 2.0 (Mobile Profile HTTP) to connect to a WAP Proxy, and the WAP Proxy uses regular HTTP to get the content from the webserver.
I do not want to make this confusing by even mentioning the secured versions of the above, cause it's messy.

MMS (a.k.a picture messaging)
Multimedia Messaging also uses WAP. When a MMS Message is sent to a cellphone recipient, the cellphone actually only receives a SMS message (a.k.a. text message) which includes a Notification that a new MMS message exists. Then, the cellphone must open a data connection (GPRS,3G, CDMA or whatever the device/carrier uses) and then use WAP 1.2 or WAP 2.0 to connect to a WAP Proxy or WAP Gateway and then use that connection to download the actual MMS Message. When sending messages the cellphone also uses WAP 1.2 or WAP 2.0 and WAP Gateway/Proxy to deliver the message to the carriers MMSC (Multimedia messaging center).
EMAIL
Email has it's own set of data transport protocols. Depending on the users account it could use protocols like POP3 or IMAP to receive and manage the arriving emails. To send, it could use the SMTP protocol. Unless, it's a Microsoft Exchange email client and uses MS proprietary protocols.
Conclusion so far: As you can see, "mobile apps" can use a variety of protocols to get or send data over wireless connections. Generally the only thing they have in common is that they all ride on top of TCP/IP and the operating system creates that TCP/IP layer on top of the wireless technology (GSM/CDMA/3G/4G/WiFI etc) connection.
To return to the original question of whether WAP still is in use (in 2010), the answer is that WAP in use in almost every handset on the market and doing well. However, it is the WAP protocol stack that today is the important part of the technology. WAP 2.0 pages (xHTML-MP formatted) are also very common and ringtone delivery pages etc all use this over WAP connections as this way the carriers can charge for the content with your monthly bill. Without it, they can't control the payments and credit cards or other means must be use.
Further, if you buy a ringtone or similar by sending a text somewhere, you get a WAP Push message in return with a link for downloading the content. This link would not work over regular HTTP as then the carrier can't track if you downloaded the content you paid for or not.
For Android or Meego or other "new" popular platforms, the OEM maufacturers of devices can buy the WAP Stack's for WAP connectivity or MMS from companies like Winwap Technologies (winwap.com) that specifically provide such technolgy for the manfuacturer.
In the end, the consumer does not need to know if HTTP, WAP or something else is used as long as they get what they paid for and want.
Hope this helps somebody?
Cheers,
Aaron (a developer of mobile that's been around too long...)

TEXT, MMS, and Email formats
I may not be using the proper verbage however I am hoping the process/question is clear.
Are the different protocols used for the three above needed for actual transport of the specific message types etc?
I am assuming the phone / computer / ??? has the protocol to play/view. Could they all be sent via sms text type format. Message plus attachment sent via wifi? once reaching destination program opens them ?
I am sure you woule need applet and servlet but is there a protocol that can do that without using a cellconnection plus data connection?

t_galownia said:
TEXT, MMS, and Email formats
Are the different protocols used for the three above needed for actual transport of the specific message types etc?
I am assuming the phone / computer / ??? has the protocol to play/view. Could they all be sent via sms text type format. Message plus attachment sent via wifi? once reaching destination program opens them ?
I am sure you woule need applet and servlet but is there a protocol that can do that without using a cellconnection plus data connection?
Click to expand...
Click to collapse
Generally anything is possible if you have access to the infrastructure. But, if you are not a telecom carrier or big enough OEM manufacturer - your only choice is to use what is available.
EMAIL: WiFi is fine for email, but you still need to run SMTP on top of WiFi to send the actual email to some SMTP server.
MMS: WiFi is not fine for MMS, unless you have MM7 or other special access to the telecom operators MMS Center.
TEXT: WiFi can not be used. TEXT (correctly called SMS or Short Message Service) uses it's own protocol that's built into the GSM/CDMA protocols. Impossible to send over WiFi unless you use WiFi to send to your own server where you have an actual wireless modem that sends out the TEXT (or again; you can probably pay your telecom carrier and spend money to build a system that let's you send your TEXT over WiFi to some server that handles the rest for you).
hope this helps...

Excellent feedback
abbe-dev said:
Hi, this thread has some factual errors, so figured it may be valuable for someone who looks for information and ends up here, to have a set of good information available in the thread.
I am not sure what "mobile applications" that want to access websites you are talking about. The typical apps available on a device from the factory that need to connect somewhere are Browser, MMS and Email applications. Of these, the Browser is the one that wants to access a website and the browser has built-in the protocols it needs.
And also to clarify lets make it clear that WAP specs includes both specs for markup language (how to display the content) as well as transport protocols (how to send/get the data). But, for this post I will only comment on the data transport protocols and completely ignore the markup languages (WML, xHTML-MP and HTML) and how or where they are used.
BROWSER
Let's split the Browser into two types of browser first, to make things a little more clear.
1) WEB Browser
2) WAP Browser
The WEB Browser uses the "regular" HTTP protocol to connect directly to webserver (on top of TCP/IP provided by the operating system) to get content.
The WAP Browser can use WAP 1.2 (Wireless Session Protocol/Wireless Transaction Layer) to connect to a WAP Gateway, and the WAP Gateway in turn uses regular HTTP to get the content from the webserver.
The WAP Browser can use WAP 2.0 (Mobile Profile HTTP) to connect to a WAP Proxy, and the WAP Proxy uses regular HTTP to get the content from the webserver.
I do not want to make this confusing by even mentioning the secured versions of the above, cause it's messy.

Authentication type bug detected in TF101G

Hi all.
I have detected a bug in authentication type option when configuring a new APN for 3G connection.
In my company, mobile devices connect via 3G connection to corporate network resources. The authentication is provided by our corporate RADIUS server. For reasons not related to this issue, the RADIUS server only provides PAP authentication.
So I have set in TF101G's APN configuration username and password and entered PAP authentication type, but I cannot access to my network resources behind APN.
I have obtained some log and sniffer traces from our corporate RADIUS server where I can observe that TF101G always tries to authenticate using CHAP. So that's the reason why authentication fails.
I've also tested it with samsung smartphones and tablets and it works Ok!!
So I would be pleased if you could verify this same behavior in TF101G. But you would need to obtain sniffer traces from authentication process to verify.
Please, could you confirm this behavior?
Many thanks in advance and best regards,
Ernesto.

sometimes my lips get CHAPPED

Don't worry about that. Wikipedia is up again:
en[dot]wikipedia[dot]org[slash]wiki[slash]Chapped_lips
Best regards,
Ernesto.

[Q] Has Anyone Got a DNS Service Working Yet?

Hello,
I'm trying to set up USAccess on my Nexus Player. As there are no existing guides, I've just been using standard Android guides. So far, I am unable to connect to the internet after changing my DNS settings. I've been searching endlessly and have only found questions regarding this topic before the Nexus Player was released.

I
I tested on my NP both by changing the DNS settings on the device and at the router level and did not have any luck connecting to Netflix on either. With the DNS set on the device, the internet connection wouldn't work on any app but when I changed it on the router, apps worked (Play store for example) but Netflix wouldn't connect.
I wonder if it is similar to the Chromecast where the DNS settings are hardcoded and you need to set up some modifications on your router (or have root access to make the necessary changes).
My suggestion would be to open a ticket with USAccess and they may be able to assist/verify that everything is configured correctly.

Setting DNS on my router works for me for accessing Australian content from the states. So this seems to be a netflix specific thing.
Sent from my Nexus 5

I'm in Canada and Netflix usa works fine for me (go to settings in Netflix and under member if it says US then it should be working) I use unblockus I have my dns settings changed on the router. Now just need a way for the nexus player to load the usa play store, this has always been tricky on Android. Worst case I will sideload Hulu for the time being.

I'm also up in Canada, and I was able to use unotelly's DNS to access Netflix US. I did notice that after changing the DNS settings on the player itself, I couldn't connect to anything until I changed the language setting in the settings app to us English (instead of Canadian), and although everything is connecting now, I've lost the recommendations bar (it just says recommendations are not available right now)

So far USAccess.ca is not working here either. Going to need to do more digging and see what the device is actually trying to do!

I am also up in Canada and I use AdFreeTime DNS service, however I cannot get Netflix to work. When I change the DNS addresses on my router to AdFreeTime, Netflix throws an -100 connection error, but everything else connects fine. I am re-routing google's dns services 8.8.8.8 and 8.8.4.4 to AdFreeTime DNS servers through iptables on my Asus router. Maybe that's an issue?
Can someone from Canada who has Netflix US working post exactly how they got Netflix to connect properly? Thank you.

I just got usaccess.ca working... It turns out I think my version of DD-WRT had some dnsmasq issues (even with strict-order enabled). I flashed a newer release of DD-WRT so i could get tcpdump working and when i finally went to capture the traffic, low and behold netflix was working with the US DNS servers set in dnsmasq. I could even watch US content
Now i just need to find that Hulu Plus .apk!!!

Elrondolio said:
I am also up in Canada and I use AdFreeTime DNS service, however I cannot get Netflix to work. When I change the DNS addresses on my router to AdFreeTime, Netflix throws an -100 connection error, but everything else connects fine. I am re-routing google's dns services 8.8.8.8 and 8.8.4.4 to AdFreeTime DNS servers through iptables on my Asus router. Maybe that's an issue?
Can someone from Canada who has Netflix US working post exactly how they got Netflix to connect properly? Thank you.
Click to expand...
Click to collapse
As a followup: I got Netflix US content working properly on the NP by setting my router to my US dsn services, but I had to disable routing the google dns servers to my AdFreeTime dns servers (which I was doing through an iptables script on my custom Asus AC68U router.) This kind of blows as routing google dns to US dns services such as AdFreeTime, Unblock US, etc was the only way to make the Chromecast work with US Netflix and other services from Canada.
There has to be a way to keep those pesky google dns services built in to Chromecast and the Nexus Player routed to unblocked US dns services without messing up Netflix on the NP.
Any ideas would be greatly welcomed.

The Nexus Player doesn't have hard coded DNS servers. I was able to change my WIFI connection from DNS to STATIC; enter in static, gateway, and DNS (USAccess) IPs and a day later, the settings took and my Netflix region change to US EN.

BlackVariant said:
Hello,
I'm trying to set up USAccess on my Nexus Player. As there are no existing guides, I've just been using standard Android guides. So far, I am unable to connect to the internet after changing my DNS settings. I've been searching endlessly and have only found questions regarding this topic before the Nexus Player was released.
Click to expand...
Click to collapse
+1 for this problem, I get the error -100, using USAccess. Have tried setting a static profile with USAccess DNS and with the IP's on my router. Works fine on my Amazon Fire TV but not the Nexus Player.

I had the same problem with usaccess, so I used the trial of unotelly to compare. unotelly works perfectly including displaying the US play store. Could be worth the extra expense, i have 7 days left to decide .

So following this:
http://forum.xda-developers.com/nexus-player/general/how-to-change-dns-ip-t2953282
USAccess is still not working for you?
I'm using 107.20.195.51 not their new region switching DNS IP.

habskilla said:
So following this:
http://forum.xda-developers.com/nexus-player/general/how-to-change-dns-ip-t2953282
USAccess is still not working for you?
I'm using 107.20.195.51 not their new region switching DNS IP.
Click to expand...
Click to collapse
I do all that and it says ip address not valid. Could you give a better description on what exactly ip addresses and gateways ishould use. Id really appreciate it

OathYvne said:
I do all that and it says ip address not valid. Could you give a better description on what exactly ip addresses and gateways ishould use. Id really appreciate it
Click to expand...
Click to collapse
Everyone has a different home network setup. So, I'll try to help you out.
Go to:
Settings
Network
Wi-Fi Connected
Pick your current Wi-Fi connection
Status info
Write down the IP address
e.g 192.168.2.23
When you go back to your Advanced settings, use the following:
IP address = IP address you wrote down from above (e.g. 192.168.2.23)
Gateway = You will have to figure out. It is usually the first three sets of numbers from your IP address and .1
So, from my example, Gateway = 192.168.2.1
Network prefix length = 24
DNS 1 = Enter in your DNS IP
DNS 2 = Use your secondary DNS IP
I use USAccess so my numbers are
Primary DNS: 107.20.195.51 Secondary DNS: 107.20.190.171
Hit next and you should see settings saved message.

habskilla said:
Everyone has a different home network setup. So, I'll try to help you out.
Go to:
Settings
Network
Wi-Fi Connected
Pick your current Wi-Fi connection
Status info
Write down the IP address
e.g 192.168.2.23
When you go back to your Advanced settings, use the following:
IP address = IP address you wrote down from above (e.g. 192.168.2.23)
Gateway = You will have to figure out. It is usually the first three sets of numbers from your IP address and .1
So, from my example, Gateway = 192.168.2.1
Network prefix length = 24
DNS 1 = Enter in your DNS IP
DNS 2 = Use your secondary DNS IP
I use USAccess so my numbers are
Primary DNS: 107.20.195.51 Secondary DNS: 107.20.190.171
Hit next and you should see settings saved message.
Click to expand...
Click to collapse
Thanks alot man. Did you have to change your date and time to american? cause when i open netflix i get a -201 error and it says make sure your date and time are correct and youre connected to the internet. I changed it to american date and time but still has same error.

Never had that error.

habskilla said:
Everyone has a different home network setup. So, I'll try to help you out.
Go to:
Settings
Network
Wi-Fi Connected
Pick your current Wi-Fi connection
Status info
Write down the IP address
e.g 192.168.2.23
When you go back to your Advanced settings, use the following:
IP address = IP address you wrote down from above (e.g. 192.168.2.23)
Gateway = You will have to figure out. It is usually the first three sets of numbers from your IP address and .1
So, from my example, Gateway = 192.168.2.1
Network prefix length = 24
DNS 1 = Enter in your DNS IP
DNS 2 = Use your secondary DNS IP
I use USAccess so my numbers are
Primary DNS: 107.20.195.51 Secondary DNS: 107.20.190.171
Hit next and you should see settings saved message.
Click to expand...
Click to collapse
I have done this, tried three different wifi networks, both with and without USAccess. I'm starting to think there is something with Netflix that it just won't work in Sweden.

Hasn't anyone who previously had the -100 error been able to resolve it?

Does anyone know what the netflix app is trying to do when we get the -100 error? I would like to find this out so I can tell my ISP about it as they offer their own DNS redirection service so we can get access to things like netflix in the USA.
I have 8.8.4.4 and 8.8.8.8 redirected to a fake IP so that those addresses timeout at the router, but netflix will still not load unless I put unotelly's DNS directly on the NP. My roku on the other hand works without putting unotelly's DNS settings.

own hosting and ip address

I'm installed termux 118 and installed nginx server on my android 9,
I made a domain name ddns service - duckdns site,
connected my ip address, started the server,
and my site is up and running, but after a while,
I can't connect to the my site,
and see this error in windows network diagnostic:
"resource (myDomainName) is online but isn't responding to connection attempts."
Me interested, what is mean? Problem in my phone, server?
or something is blocking my requests to the host IP address of my home internet provider.
Or is it because the free domain name on duckdns is unstable?
I found only approximate answer to this error on the Internet:
-Reset TCP/IP and DNS Cache
-Turn Off Proxy Settings
-Reset Network Settings
-Disable Extensions/Add-ons On The Browser

Database Users

welcome