[Q] Tethering issues Note II custom APN T-Mobile - Galaxy Note II Q&A, Help & Troubleshooting

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.

Related

How to force the use of proxy ?

I want to connect to internet via a wifi proxy running on another computer. I have configured the network as 'Work'. Also configured the proxy at Start->Settings->Connections->Proxy . Also did PIE->Menu->Tool->Options->Connections Select (i.e check) "Automatically Detect Settings".
But PIE keeps connecting directly to internet via wifi. The direct connection also alows the internet access but I want to go via proxy. The setting in PIE "Automatically Detect Setting" uses proxy if there is no direct access to inetrnet.
Any idea how I can force PIE to use proxy instead of direct Wifi access.
Thanks
I do not think it is possible by the sounding of it, it does not seems possible but I could be wrong.
It seems that the use of proxy is dependent on the application implementation. Some application do use proxy and some do not. e.g. PIE uses it but messaging do not.
The behavior is similar to desktop applications. There also each application has its own proxy setting. In WM, apps do not have individual proxy setting, but they chose whether to use proxy or not.
http://msdn.microsoft.com/en-us/library/bb840031.aspx#EstablishingaConnection
Look into function ConnMgrEstablishConnection and dwflags (flags to request proxy)
Now to answer my own question. How to force apps to not to use proxy. There are three ways.
1. Delete all proxy.
2. All set up connection as "work" connection but set up work URL exceptions as */* or *
3. Set up connection as "internet".
Now to force the connection to use proxy. I do not think there is any way to do this. And this is what I wanted to do.

USB Tethering on Mac OS X

I read in the manual under the tethering chapter that USB tethering works out of the box on Windows, Mac OS X, or latest Linux distros.
Spend all day yesterday trying to get it to work on my 15" MBP running Lion 10.7.2 with no luck.
Is there anyone that can point me to the right direction to get this to work. I do not want to use third party tethering apps.
Thank you!
Not going to work ; where did you read it works on Lion?
ICS is still using NDIS based USB tether and Mac OS X (Snow Leopard thru to Lion) does not support this.
I just tested this - plugged GN to my Mac while USB tethering is on, if it was a non NDIS Mac compatible network adapter via USB it would have showed up in System Preferences, Network - it didn't
If I redirect the USB to my Windows VM on Fusion right away an NDIS adapter showed up and the Windows VM worked with tethering.
It's in the manual under the tethering. Clearly states Mac as one of the options.
"Share your phone's data connection via USB
If your computer is running Windows 7, Mac OS X, or a recent distribution of some flavors of Linux (such as Ubuntu), you can follow these instructions without any special preparation.
If you're running a version of Windows that precedes Windows 7, or some other operating system, you may need to prepare your computer to establish a network connection via USB.
1 Connect your phone to your computer with a USB cable.
A USB icon appears at the top of the screen, and the notification Connected as a media device or Connected as a camera appears briefly at the top of the screen. For the purposes of tethering, the type of connection doesn't matter.
2 Go to Settings > Wireless & networks > More > Tethering & portable hotspot.
3 Check USB tethering.
Your computer is now sharing your device's data connection.
4 To stop sharing your data connection, uncheck USB tethering or disconnect the USB cable."
Have you tried something like PdaNet?
oilfighter said:
Have you tried something like PdaNet?
Click to expand...
Click to collapse
I'd like to get it to work natively without the third party apps.
Sent from my Galaxy Nexus using Tapatalk
Getting USB tethering working seemed like a huge hassle on my MBP, just use Bluetooth tether or hotspot is your best option
Sent from my Galaxy Nexus using xda premium
Its a big hassle to set up USB tether on OSX. It requires creating a new network config in system preferences and setting it up properly. Super annoying I ended up just WiFi tethering.
martonikaj said:
Its a big hassle to set up USB tether on OSX. It requires creating a new network config in system preferences and setting it up properly. Super annoying I ended up just WiFi tethering.
Click to expand...
Click to collapse
So have you seen an NDIS 10.7 driver stack - I haven't.. I don't think it's at all possible with a standard AOSP ICS device
milan03 said:
I'd like to get it to work natively without the third party apps.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
There are a few benefits though.
- I'm on T-Mobile, so for me, I don't have to fork over another payment just for tethering.
- They've already bundled all the software you need in one neat package, so it takes most of the guess work out, especially on mac
martonikaj said:
Its a big hassle to set up USB tether on OSX. It requires creating a new network config in system preferences and setting it up properly. Super annoying I ended up just WiFi tethering.
Click to expand...
Click to collapse
That new config settings config is what I need. Do you mind sharing the parameters? Thanks.
Sent from my Galaxy Nexus using Tapatalk
Wait so nobody knows?
Just use wifi. You can still keep the phone charged over USB while doing that.
Sent from my Galaxy Nexus using Tapatalk
[hfm] said:
Just use wifi. You can still keep the phone charged over USB while doing that.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
That's given and its not the point. I wanna know how to USB tether since the tutorial states that is possible on a mac os x...
Sent from my Galaxy Nexus using Tapatalk
The earlier poster is in error.. USB Tethering is RNDIS only = NO SUPPORT ON MAC OS X.
Unless you are planning on writing an RNDIS driver you are out of luck with the built in ICS tethering. You will need to use a 3rd party app like EasyTether or just use WiFi tethering.
NPS_CA said:
The earlier poster is in error.. USB Tethering is RNDIS only = NO SUPPORT ON MAC OS X.
Unless you are planning on writing an RNDIS driver you are out of luck with the built in ICS tethering. You will need to use a 3rd party app like EasyTether or just use WiFi tethering.
Click to expand...
Click to collapse
I just don't understand why did Google talk about USB tethering support out of the box in International GN manual as well as in Verizon's manual. WTF?!
milan03 said:
I just don't understand why did Google talk about USB tethering support out of the box in International GN manual as well as in Verizon's manual. WTF?!
Click to expand...
Click to collapse
I have the same question.
I am not on Verizon (living in Germany), and have a GSM native GN. In the (online) manual it is clearly stated that it works with Mac and cable. But as the others have written and as I experienced, it simply does not work :-(
Please do not tell me that I should use Wifi ;-) Yes, this works, but it consumes much more battery compared to cable.
i got it easy by using HTC sensation XL it has two options windows or MAC OS tethering ,, but i cant do it here on GN there is an app can do that .ClockworkMod Tether ...
Oddly enough, if you plug a Nexus S into a Mac and do USB tethering, it works fine using RNDIS or some other witchcraft.
If anyone is still looking for the T-Mobile US settings for tethering, try this:
When you enable tethering, have an active ADB connection, and you receive a pop-up in OS X that says you have a new unconfigured network device, then you're good to enter these settings and connect:
Telephone Number: *99***1#
Username: GPRS
Password: GPRS
I got the above credentials from the T-Mobile WebConnect Manager for OS X using one of my Tablet Internet Device SIM Cards in a Rocket 3.0 USB stick. So, if Authentication fails using the above credentials, meaning that OS X dials the connection, says "Authenticating. . .", then disconnects without ever saying "Connected", then try these credentials:
Username: none
Password: none
If that still doesn't work, leave the Username and passwords blank.
Click the Advanced Button:
Modem Tab:
Notes About Which Vendor to select:
If you don't have a Samsung, Motorola or Sony Ericson Android Device, and the modem does not supply a .ccl script or nothing comes up in the Model drop down list after select other, then try choosing Generic. My LG p999 (G2x), LG v909, Dell Streak 7, HTC One X and HTC Amaze 4G, and Nexus One displayed a Model corresponding to the device that was connected when I selected Other as the Vendor.
I can verify that this works on all of my Samsung devices, when choosing Samsung as the Vendor. IK verified it on my Galaxy Nexus (GSM i9250), Nexus S, Galaxy S3, Galaxy S2, Galaxy S 4G, and Galaxy S Vibrant.
Model: GPRS (GSM/3G)
APN*: epc.tmobile.com
CID**: 1 (This is the Country ID for the US, I am not sure what countries are represented by the other CID integers).
*APN is the acronym for Access Point Name.
**CID: This should only appear when selecting Generic as the Vendor.
DNS Tab:
Leave these blank, they should fill dynamically, if they don't, try using 8.8.8.8, 8.8.4.4 for DNS servers and tmobile.com as the search domain.
WINS Tab:
Leave blank
Proxies Tab:
Leave all unchecked, except for Use PASV FTP.
PPP Tab:
Make sure the following are not selected:
Send PPP echo packets
Make sure the following items are checked/selected:
Use TCP header compression
Use Verbose Logging (once you have gotten connected, you can probably disable this)
Redial 5 times if busy, waiting 10 seconds before redialing
Make sure Terminal script is set to None.
For resolving issues make sure to select Use verbose logging, connect using a terminal window, and Send PPP echo packets (only if the modem commands are not being displayed in the terminal window).
All the rest of the PPP options, e.g. Automatic connections and disconnecting are set to your personal preferences and security concerns.
I got it working by turning data off (on the phone)
Also works when the phone is connected to wifi
After connecting on the Mac, you can turn data on and it will stay connected
JBDynamics said:
If anyone is still looking for the T-Mobile US settings for tethering, try this:
When you enable tethering, have an active ADB connection, and you receive a pop-up in OS X that says you have a new unconfigured network device, then you're good to enter these settings and connect:
Telephone Number: *99***1#
Username: GPRS
Password: GPRS
I got the above credentials from the T-Mobile WebConnect Manager for OS X using one of my Tablet Internet Device SIM Cards in a Rocket 3.0 USB stick. So, if Authentication fails using the above credentials, meaning that OS X dials the connection, says "Authenticating. . .", then disconnects without ever saying "Connected", then try these credentials:
Username: none
Password: none
If that still doesn't work, leave the Username and passwords blank.
Click the Advanced Button:
Modem Tab:
Notes About Which Vendor to select:
If you don't have a Samsung, Motorola or Sony Ericson Android Device, and the modem does not supply a .ccl script or nothing comes up in the Model drop down list after select other, then try choosing Generic. My LG p999 (G2x), LG v909, Dell Streak 7, HTC One X and HTC Amaze 4G, and Nexus One displayed a Model corresponding to the device that was connected when I selected Other as the Vendor.
I can verify that this works on all of my Samsung devices, when choosing Samsung as the Vendor. IK verified it on my Galaxy Nexus (GSM i9250), Nexus S, Galaxy S3, Galaxy S2, Galaxy S 4G, and Galaxy S Vibrant.
Model: GPRS (GSM/3G)
APN*: epc.tmobile.com
CID**: 1 (This is the Country ID for the US, I am not sure what countries are represented by the other CID integers).
*APN is the acronym for Access Point Name.
**CID: This should only appear when selecting Generic as the Vendor.
DNS Tab:
Leave these blank, they should fill dynamically, if they don't, try using 8.8.8.8, 8.8.4.4 for DNS servers and tmobile.com as the search domain.
WINS Tab:
Leave blank
Proxies Tab:
Leave all unchecked, except for Use PASV FTP.
PPP Tab:
Make sure the following are not selected:
Send PPP echo packets
Make sure the following items are checked/selected:
Use TCP header compression
Use Verbose Logging (once you have gotten connected, you can probably disable this)
Redial 5 times if busy, waiting 10 seconds before redialing
Make sure Terminal script is set to None.
For resolving issues make sure to select Use verbose logging, connect using a terminal window, and Send PPP echo packets (only if the modem commands are not being displayed in the terminal window).
All the rest of the PPP options, e.g. Automatic connections and disconnecting are set to your personal preferences and security concerns.
Click to expand...
Click to collapse

AT&T Note 2 Global Proxy issues

Hello all,
I am new to the Android family and have just bought my first Android phone the AT&T Note 2. At home and about town in the states the phone is phenomenal, so far I am loving Android, except for the minor flaw of it not having global proxy permissions for all apps.
I am on a corporate network which uses a proxy with authentication, and also has some sites blocked of course, facebook, pandora, etc. I know that you probably tire of the endless comparisons of iphone to Android, but by setting up my iphone and hitting a proxy app I could use the facebook app, magic jack, pandora, or whatever.
I have rooted the Note 2 running JB 4.1.2, and have installed ProxyDroid and BusyBox. I assumed by putting in the settings of the proxy into ProxyDroid would connect it automatically. I have had some success some apps would work intermittently like skype and whatsapp, but the playstore and most of the other apps will not connect, and I have be changing settings without properly recording the working settings so much for good troubleshooting..... I can surf the web, under restrictions of course, with Opera Mobile because I entered the proxy info directly into the app.
Now to the meat of things:
The WiFi settings are as follows:
EAP: PEAP
PHASE 2: MSCHAPV2
No Certificates
Correct Identity
No Anonymous Identity
Correct Password
Proxy settings Manual
blahblahproxy800.corp.company.com
Proxy Port: 80
No Bypass
IP: DHCP
the security is 802.1x EAP
ProxyDroid Settings:
Host: blahblahproxy800.corp.company.com
Port: 80
Proxy type: HTTPS
Auto Connect ON
BOUND to network SSID
Authentication on
Correct User
Correct PW
NTLM Authentication ON
Domain: corp.company.com
Global Proxy ON
DNS Proxy ON
I know that rubbish up there is a lot of information, but I am a complete noob in the world of Android. I can give the settings that I have in the Iphone to connect if you need them, but if you have any experience with it you know that it is extremely easy to set up. Any help will be greatly appreciated. Is there something missing in my setup? Do I need to add anything else, app or settings wise? Or do I just have to accept it and leave my shiny new note as a paper weight until I go on days off, and use the Iphone while I am here?
Thank you all in advance for you help on this and the help that you unknowingly gave me while I was stalking / searching the boards getting info on how to root.
Cheers

[GUIDE] SSH Proxy with ConnectBot and ProxyDroid

For anyone interested in data security the ability to encrypt network traffic is obviously important-- especially in light of the myriad of recent well publicized reports of private and government electronic snooping. It is also relevant to mention that to date no one has come close to cracking "TwoFish" encryption which can be used by SSH. With this in mind, consider the following tutorial which describes a method for encrypting all 3g, 4g, and Wi-Fi data, thus beefing up phone and personal data security.
Setting up a global SSH Tunnel on Android phones
This tutorial assumes the reader possesses a fully configured SSH server and rooted phone. In lieu of a server, (eg., the reader only has only a Windows-based operating system), research into CYGWIN is recommended. I use CYGWIN to run my SSH server and I have found that it is the most robust option for Windows users; however, setting this up on Windows can be a daunting task.
Setting up global SSH Tunnel on Android
1. Download 2 apps from the Google Playstore: ConnectBot and ProxyDroid
2. Install ConnectBot and ProxyDroid on your phone.
3. In ConnectBot set up Port forwards for your SSH connection. For "Type" field use "Dynamic (SOCKS)." For “Source Port” use 56001 or any local port not being used. The reasoning behind using port 56001 is this: System Ports (0-1023), User Ports (1024-49151), and the Dynamic and/or Private Ports (49152-65535)
4. Open ProxyDroid and configure as follows:
Host: 127.0.0.1
Port: 56001 (or the port you chose to use in step 3)
Proxy Type: SOCKS5
Global Proxy: Check the box
The above procedure accomplishes several things. First, ConnectBot remotely connects to your SSH server. Next, the ConnectBot connection forwards to the local port 56001. ProxyDroid then redirects all network traffic through the localhost on port 56001. Once you are connected through ConnectBot and ProxyDroid is activated all of your data will be tunneled through the encrypted ConnectBot session. This is an excellent way to set up a global proxy because it does not require manual configuration of any applications to connect through the proxy. You can test the functionality of the connection by opening up your phone browser and performing the Google search: What is my IP. If the proxy is functional you will see the WAN IP of the network of your SSH server. Additional and more thorough testing can be done with packet sniffers such as WireShark.
An application called "SSH Tunnel" is an alternative to accomplishing the above. However, I find ConnectBot and ProxyDroid is more elegant and gives better control-- not to mention being more sophisticated/chic. When correctly performed the ConnectBot and ProxyDroid method encrypts all 3g, 4g and Wi-Fi data on your phone. This is obviously useful for phone access of sensitive materials especially using unfamiliar or alien network connections. With the current proliferation of identity theft via electronic snooping on mobile devices I do not advocate using cellular phones for any banking or electronic transactions without setting up a robust and reliable encrypted connection.
I would also add that you need to run connectbot first then run ProxyDroid. If you do it in reverse Connectbot will have problems connecting.
Dr.Tautology said:
For anyone interested in data security the ability to encrypt network traffic is obviously important-- especially in light of the myriad of recent well publicized reports of private and government electronic snooping. It is also relevant to mention that to date no one has come close to cracking "TwoFish" encryption which can be used by SSH. With this in mind, consider the following tutorial which describes a method for encrypting all 3g, 4g, and Wi-Fi data, thus beefing up phone and personal data security.
Setting up a global SSH Tunnel on Android phones
This tutorial assumes the reader possesses a fully configured SSH server and rooted phone. In lieu of a server, (eg., the reader only has only a Windows-based operating system), research into CYGWIN is recommended. I use CYGWIN to run my SSH server and I have found that it is the most robust option for Windows users; however, setting this up on Windows can be a daunting task.
Setting up global SSH Tunnel on Android
1. Download 2 apps from the Google Playstore: ConnectBot and ProxyDroid
2. Install ConnectBot and ProxyDroid on your phone.
3. In ConnectBot set up Port forwards for your SSH connection. For "Type" field use "Dynamic (SOCKS)." For “Source Port” use 56001 or any local port not being used. The reasoning behind using port 56001 is this: System Ports (0-1023), User Ports (1024-49151), and the Dynamic and/or Private Ports (49152-65535)
4. Open ProxyDroid and configure as follows:
Host: 127.0.0.1
Port: 56001 (or the port you chose to use in step 3)
Proxy Type: SOCKS5
Global Proxy: Check the box
The above procedure accomplishes several things. First, ConnectBot remotely connects to your SSH server. Next, the ConnectBot connection forwards to the local port 56001. ProxyDroid then redirects all network traffic through the localhost on port 56001. Once you are connected through ConnectBot and ProxyDroid is activated all of your data will be tunneled through the encrypted ConnectBot session. This is an excellent way to set up a global proxy because it does not require manual configuration of any applications to connect through the proxy. You can test the functionality of the connection by opening up your phone browser and performing the Google search: What is my IP. If the proxy is functional you will see the WAN IP of the network of your SSH server. Additional and more thorough testing can be done with packet sniffers such as WireShark.
An application called "SSH Tunnel" is an alternative to accomplishing the above. However, I find ConnectBot and ProxyDroid is more elegant and gives better control-- not to mention being more sophisticated/chic. When correctly performed the ConnectBot and ProxyDroid method encrypts all 3g, 4g and Wi-Fi data on your phone. This is obviously useful for phone access of sensitive materials especially using unfamiliar or alien network connections. With the current proliferation of identity theft via electronic snooping on mobile devices I do not advocate using cellular phones for any banking or electronic transactions without setting up a robust and reliable encrypted connection.
Click to expand...
Click to collapse
I know that this is an old thread but is there any way to ssh-tunnel wifi traffic only ? Especially "untrusted wifi" traffic only?
Thanks
how to set up connect bot? please can you provide the information in detail?
Okay so I was using this setup of connect-bot and proxy-droid on kit kat. It was working great. I upgraded my phone to lollipop and connectbot would not port forward (the port data would be crossed out after connecting)
I decided to replace connectbot with ssh tunnel in this config
https://play.google.com/store/apps/details?id=org.sshtunnel
it did not work with global proxy in ssh-tunnel so I used proxy-droid like the OP did and it worked.
so basically substituting connect-bot with ssh-tunnel from the OP
setup:
root required
instead of connect-bot configure ssh-tunnel
host= ip address of ssh server
port= 22
user=ssh username
password=ssh passworrd
check use socks proxy box
set proxy port to 56001
do not check global proxy
now configure Proxy droid same as mentioned by OP
Open ProxyDroid and configure as follows:
Host: 127.0.0.1
Port: 56001
Proxy Type: SOCKS5
Global Proxy: Check the box
this should work great for devices absent of vpn files but have root access
launch and connect ssh-tunnel the proxy-droid. then use a browser to connect to local lan.
I have tested using a rasberry pi running ssh and in sshd_config allowed root access and maybe also tcp forwarding.
I have also tested on dd-wrt 3.0beta with tcp forwarding checked. (ssh is mostly broken/disabled in v2.4)
is there any other option instead of proxy droid ...because proxydroid is not working on Youwave..
Could an app like SSH Tunnel be used without ProxyDroid? I noticed that with ProxyDroid I was able to cloak my IP address at an IP reveal website, but couldn't do so without it. Unfortunately ProxyDroid requires root, which my current phone does not have. What good would SSH Tunnel be without ProxyDroid?
Not solve the problem, when ConnectBot connects first, and I enable SocksDroid second. ConnectBot will drop the SSH connection.
It's tool late, but the problem solved:
On SocksDroid, need select: Per-App proxy and select BypassMode, and add org.connectbot (NOT only ConnectBot) to the App List. With this settings, ConnectBot ALWAYS bypass the proxy.
Tesetd, working satble.

Can't run some network services on my G3

I'm trying to run some network services (servers listening for incoming connections) on my LG G3 phone. Its rooted, though all the services that I want to run do not require root to function (they use unpriviliged ports).
Some network services work, while others do not. For example, Ice Cold Apps SSH server does not work, while droid VNC server does.
From what I'm able to see, services that bind to "0.0.0.0" as the listen IP address work fine and are accessible from everywhere (NAT not withstanding), while services that bind to ":::" (IPv6) are only available from the phone itself (I test using ConnectBot's "telnet" mode). Such a service will respond to the phone's IPv4 address - when called from a local app - but will not respond to incoming connections from other devices on the network.
I don't have an IPv6 network that I can access, so I'm not sure if the problem is only for IPv4 devices or for all access.
I didn't have this problem with my previous phone - a Galaxy S2 running TouchWiz 4.1.2 or Cyanogenmod 11.
From looking at the output of iptables, I see there are many firewall rules, but I didn't see anything that should actually block content. I can paste the output of iptables if you guys want to take a look.
Any help will be much appreciated.
guss77 said:
I'm trying to run some network services (servers listening for incoming connections) on my LG G3 phone. Its rooted, though all the services that I want to run do not require root to function (they use unpriviliged ports).
Some network services work, while others do not. For example, Ice Cold Apps SSH server does not work, while droid VNC server does.
From what I'm able to see, services that bind to "0.0.0.0" as the listen IP address work fine and are accessible from everywhere (NAT not withstanding), while services that bind to ":::" (IPv6) are only available from the phone itself (I test using ConnectBot's "telnet" mode). Such a service will respond to the phone's IPv4 address - when called from a local app - but will not respond to incoming connections from other devices on the network.
I don't have an IPv6 network that I can access, so I'm not sure if the problem is only for IPv4 devices or for all access.
I didn't have this problem with my previous phone - a Galaxy S2 running TouchWiz 4.1.2 or Cyanogenmod 11.
From looking at the output of iptables, I see there are many firewall rules, but I didn't see anything that should actually block content. I can paste the output of iptables if you guys want to take a look.
Any help will be much appreciated.
Click to expand...
Click to collapse
Which G3 do you have? I have a T-Mobile version and have noticed that the phones do not have IPV4 support on mobile networks, they instead do 6to4 to get IPV4 for apps. This does not happen on WiFi though. I'm trying to figure out if the G3 defaults to IPV6 only and even WiFi IPV4 services might be secondary to IPV6, so any app on the phone that is IPV6 ready will bind to the IPV6 interface and not listen on IPV4 for incoming connections.
You could try disabling IPV6 globally to see if this solves your problem. Not sure how to do it though.
I have the international G3 (LG-D855). I don't think my mobile network is using IPv6 (not that advanced - the IPv6 for rmnet0 is a zeroconf address).
Also, the situation is only interesting on WiFi, and I don't have an IPv6 wifi - so all traffic coming in should be IPv4 by definition.

Categories

Resources