Android Device can't connect to network ressources although stays connected to Wifi

---

chris_at wrote:

Ok so actually after a software update I was able to setup the LTE Router in Bridge mode. So no double NAT anymore - guess I should have done that before but who changes something thats working perfectly well - at least it seemed so ;)

 

So lets see if that fixed the problem. Will take 1-2 days to confirm.

---

Good luck! :)

Glad that was a simple fix. 

Please mark your thread as solved so others will know for future reference. 

Enjoy. :smileywink:

---

chris_at wrote:

Ok so actually after a software update I was able to setup the LTE Router in Bridge mode. So no double NAT anymore - guess I should have done that before but who changes something thats working perfectly well - at least it seemed so ;)

 

So lets see if that fixed the problem. Will take 1-2 days to confirm.

---

not fixed :(

Problem is still there ...

So is the modem still in bridge mode? 

It was working. What changed? 

---

chris_at wrote:

not fixed :(

Problem is still there ...

---

yes - still in bridge mode - still all devices but the android tablet working having no issues with the networt / internet connection

Almost sounds like a problem with the Android device. 

Has it's SW/FW been updated recently? 

---

chris_at wrote:

yes - still in bridge mode - still all devices but the android tablet working having no issues with the networt / internet connection

---

Have you tested the tracert command as described above? It will be interesteing to see if you really now have only one NAT router after the latest changes?

trace route gives

Routenverfolgung zu google-public-dns-a.google.com [8.8.8.8]
über maximal 30 Hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 78 ms 27 ms 50 ms 172.16.22.170
3 * * * Zeitüberschreitung der Anforderung.
4 64 ms 37 ms 27 ms 213.94.72.44
5 40 ms 18 ms 46 ms ae9.vienna51.vie.seabone.net [195.22.215.60]
6 96 ms 54 ms 59 ms racc.franco52.fra.seabone.net [195.22.211.207]
7 89 ms 40 ms 44 ms

not sure why there is a timeout on the 3rd hop but as only one internal ip is shown I guess there is no double NAT

software/firmaware of the table has not been updated since its not maintained by sony any more and I saw no need to switch to a alternative rom.
It might be a combination of Orbi and the Device but its defenitly not the device that worked flawlessly for the past 4-5 years in combination with the R7000 and other hotspots when traveling.

---

chris_at wrote:

......

1 1 ms 1 ms 1 ms 192.168.1.1
2 78 ms 27 ms 50 ms 172.16.22.170

......

---

Both 192.168.1.1 and 172.16.22.170 are private addresses so you actually have double NAT, and I believe this is the main source of the issue!

172.xxx is the IP I got assigned from the network provider ... no way to get around this. So basically every customer of Three Austria has double NAT then ;)

---

chris_at wrote:

172.xxx is the IP I got assigned from the network provider ... no way to get around this. So basically every customer of Three Austria has double NAT then ;)

---

So you mean that your ISP provides you with ONE private IP address? Only one IP or a DHCP service? Can you connect multiple devices to the ISP router and get them to work? Which IP address range will you get if you connect multiple devices to the ISP router?

172... is the IP that I get on the WAN port from the provider. 

The LTE Router or now the Orbi have a 192... range. Obviously I don't get a public IP from the provider. I will call them tomorrow morning and see if they can provide a public IP.

I thought they did in the past.

can you go to WHATISMYIP.COM and see what your IP is?  (xxx out the last octal for privacy)

Well the technical support wasn't really helpful.

I do get a public IP (77.x.x.x) assigned to the router - I also see that on WHATISMYIP.COM

But I don't know yet where the 172.x.x.x is coming from. I try to get an answer via the local forum on such topics maybe someone knows more about that.

BUT that setup didn't cause any issues in the past - so I still doubt thats the cause of the issues

---

chris_at wrote:

.........

But I don't know yet where the 172.x.x.x is coming from. I try to get an answer via the local forum on such topics maybe someone knows more about that.
.......

---

This must be the internal network in the 4G router?

---

chris_at wrote:

.......BUT that setup didn't cause any issues in the past - so I still doubt thats the cause of the issues

---

This is the nature of double NAT issues, can appear only for very specific ports and traffic cases.

No replies on the other forum. I think there is no way to get around this 172.x.x.x - likely internal IP of the LTE router.

But regarding double NAT: the traffic cases and ports did not change and it even effects normal browsing not only streaming and access to the webinterface of the local NAS or Orbi itself. I assume for the later there is no NAT involved at all.

I really appriciate but I honestly doubt its a double NAT issue as nothing changed but the router (R7000 -> Orbi).
As I have the feeling I can't be sure Orbi will work with any device (in the future) and it is also lacking a VPN client  I guess the best option for me is to replace the Orbi system again with a DD-WRT based system.
( Yes I know there is a post about VPN client for Orbi but it's been in review by netgear for a long time and the mentioned limitation by the used CPU does make sense. )


So again thanks a lot for trying to help but if there are no other suggestens but double NAT elimination I guess we can close this topic.

Have you configured Orbi for AP mode with the LTE router? 

---

chris_at wrote:

No replies on the other forum. I think there is no way to get around this 172.x.x.x - likely internal IP of the LTE router.

 

But regarding double NAT: the traffic cases and ports did not change and it even effects normal browsing not only streaming and access to the webinterface of the local NAS or Orbi itself. I assume for the later there is no NAT involved at all.

I really appriciate but I honestly doubt its a double NAT issue as nothing changed but the router (R7000 -> Orbi).
As I have the feeling I can't be sure Orbi will work with any device (in the future) and it is also lacking a VPN client  I guess the best option for me is to replace the Orbi system again with a DD-WRT based system.
( Yes I know there is a post about VPN client for Orbi but it's been in review by netgear for a long time and the mentioned limitation by the used CPU does make sense. )


So again thanks a lot for trying to help but if there are no other suggestens but double NAT elimination I guess we can close this topic.

---

No as that is not an option for me. Orbi is way to expensive as AP and the LTE router also lacks functionality I'd like to use.

I would at least give it a try to see if this resolves the Adroid device. If there is a NAT issue, this will be telling if this changes in AP mode with the Android device. You can change The Orbi back.

Does the LTE router have a DMZ or IP Pass thru feature? 

---

chris_at wrote:

No as that is not an option for me. Orbi is way to expensive as AP and the LTE router also lacks functionality I'd like to use.

---