Details if you need are in the user manual:
I suggest that you log into the ASKEY interface and check the ALG settings first and see that the FTP and TFTP are allowed. Now when I try to connect with T-Mobile HI, I get the following error message.any thoughts? I have permissions on the remote FTP server.
I used Windows 10 File Explorer in split screen mode (remote on one screen and local files on second) and simply clicked and dragged the files from one screen to the other. However, since I switched from a slow DSL connection to T-Mobile HI (ASKEY), I no longer can move the files. Over the years I have used FTP to easily transfer these files. I am responsible for posting documents/pictures, etc. The APN is not selectable but is it possible that this APN is the source of all the issues and not the 464XLAT?įranklin have been holding off with this observation and thought you might have some insight into the problem. corporate VPN works fine on the Franklin hotspot, the ASKEY gateway etc. The fbb.home appears to be blocking most things (VPN’s, XBOX Party chat, etc) while the does not, i.e. Question: I noticed that the APN on the Nokia gateway is fbb.home while the APN on the Franklin hotspot is. Yes, I recognize you, I’m over there too, different ID. I also posted this issue in DSLreports for those oldtimers like me that remember that site. Xbox One NAT / UPnP results for the Nokia modem for those that asked. Unstable or "hung" SSH sessions when using the Nokia? T-mobile should fix their home internet and remove filtering on IPv6 Netgear LAX20 with ATT SIM card = IPv6 can be pinged and ports forwarded. Here are some of my discussions in r/tmobileisp in:re T-mobile home internet. I’m active there - posted here as I don’t think T-mobile suits care about reddit and I may get someone at actually T-mobile to help raise the awareness of these issues. Lots of people there working on the same issue, appears to be their use of CG-NAT. Would be really great if you post this over in the Reddit r/tmobileisp forum. T-mobile please fix your business model for this new service, starting with adding the ability to request zero network filtering for home internet subscribers and the ability to get IPv6 prefix delegated. Those users who wish to be able to remotely manage their smart home should perhaps stay away for now until T-mobile decides to do the right thing which is for “home internet” service subscribers to have different security network rules than cellphones on the network. On AT&T I can ping and access my device remotely when it is on the AT&T LTE network on the same Netgear LAX20.ĭecided to post here to vent and share some findings, as this is somewhat frustrating that other LTE carriers that do not offer ‘home internet’ service do allow you to control and manage your network as you see fit while the new “home internet” service does not give you any control at all. Most folks out there are blaming the Nokia router firmware which is really locked down by T-mobile, so being the IT engineer I pretend to be I purchased a Netgear LAX20 which is T-mobile and AT&T certified - I swapped SIMs for my Home internet service and tested both.Įven with a router that I fully control, with firewall disabled and allowing WAN icmp/ping responses T-mobile seems to continue to filter traffic (even pings!) incoming towards my service equipment… to make a fair comparison I got an AT&T SIM card and repeated the tests. I’ve spent the majority of my time trying to figure out ways to make this work.
The router being shipped today to customers is missing very important features for power users - it actually broke my ability to remotely access my home via direct-connection using public IPv6 and IPv4 that I used on comcast.Ĭontacting support for help is pretty much useless, although I have raised a few tickets regarding the major issues affecting me since switching ISPs, namely: My background is in IT / networking and I started using Tmo Home Internet for the past 2 weeks.