User Profile
teckel
Roaming Rookie
Joined 4 years ago
User Widgets
Contribuciones
Re: Can't use Vanguard 401k's website with T-Mobile Internet
My public IP address does change, but not mid-session in Vanguard. There's never a problem on the main dashboard with Vanguard, it's only when trying to get into any other area of the dashboard. It seems to do a auth check and fails due to something T-Mobile's network is doing differently than say Verizon.6Visto0likes0ComentariosCan't use Vanguard 401k's website with T-Mobile Internet
I can sign into Vanguard's 401k website, but navigating around will log me out with the message "You have been logged out". If I connect to a Verizon hotspot form an iPad, I have zero problems. It's easily reproducible, just sign in, and navigate to activity history, select a report, or update savings rate and you'll be logged out. Not new, this has been happening ever since getting T-Mobile Internet, but I was just able to verify it always fails with T-Mobile Internet and never fails on a Verizon connection. I'm using a home mesh network with an Ethernet connection to the T-Mobile Internet modem (I don't use the T-Mobile Internet WiFi at all for coverage reasons).Re: NAT (Forwarding) in T-Mobile Gateway
inteller wrote: Holy sh* man you are saying exactly what I'm stating! The right thing to do would be instead of trying to work against me, work WITH me to pressure T-Mobile to get this deivce more functional and then we can ALL do whatever we want with it. All T-mobile has to do is enable the device to bridge. That's it. I know this because that's how my cable modem worked and I was able to do everything else I wanted from there. So if you want to sit there and tell me the networking configuration I used for YEARS was 'incorrect' and didn't work, go right ahead…..but you are not helping.You can be an apologist for why they don't enable these things, but this device is for HOME INTERNET. I do not sit at home on my phone and nothing else.If that is T-mobile's position then I'll be returning it and wait until they grow up. Actually, we're not at all saying the same thing. You believe the modem could be updated with a few featureand it would work. I'm saying that's not the case, as you're basically behind T-Mobile's NAT/VPN so enabling features on the model wouldn't solve the problem one bit. How exactly do do believe enabling bridge mode would solve your problem? You're comparing your cable company's network with T-Mobile, which are TOTALLY different. Your cable company didn't hide your connection behind a NAT/VPN. You could identify your home connection with a unique IP address which you could access remotely (with or without a DDNS like NoIP). But T-Mobile's network doesn't work like your cable company. Every connection is like a VPN or NAT, where there's not a unique IP address, but it's shared with many other people. So, lets's say bridge mode is available on your T-Mobile modem. How would you remotely access your home modem? By IP? Via a DDNS like NoIP? Nope! As there's still not a uniqueIP address assigned to your home connection, it's shared with thousands of other people. So you would try to access your home network and it could never route to your home. So I'm sorry, you don't know what you're talking about. You have limited knowledge and basing your assumptions on how your cable company's network is configured, when in reality T-Mobile's network isn't at all setup the same way, and as a result, your assumption that bridge mode will solve everything is totally wrong. Sorry, it's not as simple as that.9Visto1like0ComentariosRe: NAT (Forwarding) in T-Mobile Gateway
inteller wrote: I can't use noip with t-mobile because it doesn't support it, but if it was just bridging I could. I'm not willing to wait around for another device when the speeds I get right now are just fine and the device I have is capable of the functions I need. Sorry, you're incorrect. You can setup NOIP on other devices other than just your modem. I set it up on my local server. But, this doesn't work as T-Mobile doesn't assign you a unique IP address (it's shared with hundreds/thousands of other people). So even if you setup NOIP, that doesn't help one bit. Nor would port forwarding or bridge mode. You're failing to understand the problem. The issue is how the T-Mobile network is setup for a security aspect. It was setup to be a secured network for phones. It's not capable of working with a DDNS service, bridge mode, or port forwarding. That's why they disabled these features on the T-Mobile modem, as they would never work. Keep in mind that Nokia added these features to this modem firmware when they designed it (for other markets). When T-Mobile wanted to use it, they had to disable features as they don't work on their network, not because they wanted to limit the device. The new modem won't resolve the problem either. It may happen along with a T-Mobile network change, but a modem alone can't fix the problem, either a firmware update or new hardware. The only work-around is a service like ZeroTier until T-Mobile changes their network, which very well may never happen.19Visto1like0ComentariosRe: NAT (Forwarding) in T-Mobile Gateway
inteller wrote: The Nokia 5G 3.1 is the newer device. That's why I was very specific in the model I was discussing. I don't want hackery 3rd party services, I need this functionality in the hardware. Noip and dyndns solve this anyways, my current router supports this natively. The Nokia 5Gis the latest released modem. But T-Mobile is releasing a newer 5G modem(which I was referring to) which is not made by Nokia andwill also support the higher higher frequency 5G frequencies which the current Nokia modem doesn't support. ZeroTier isn't a hack, it's method to create a secure link between devices, even through secured networks like T-Mobile. You can't use NOIP or DynDNSwith T-Mobile. It's not that the IP address changes, it's that the connection is like aVPN connection, so even with the IP address you can't route to your in-home modem. There could be thousands of people using the same IP address. You're thinking it's just a port forwarding issue, when that's not really the problem. The reason T-Mobile disabled port forwarding and bridged mode is because it won't work on their network.7Visto0likes0Comentarios- 7Visto0likes0Comentarios
Re: NAT (Forwarding) in T-Mobile Gateway
inteller wrote: I'm fairly confident that this device (Nokia) is able to handle all of these things. I think what has happened here is T-Mobile threw a very locked down firmware on the device to make setup easy. The following things need to happen. Provide settings to place the gateway in bridge mode. This will allow customers to keep their existing setups and NAT fine. Provide settings to turn off the wifi in the gateway COMPLETELY. Turning off broadcast and reducing power to minimal is not sufficient. Make all of these settings accessible only through the web admin page. The average consumer doesn't need this stuff, but the power user who is smart enough to know how to login to the admin web page should be able to modify these settings. Ultimately, I just want "a dumb modem" just like I get with the cable co. I don't want or need T-Mobile helping me by dumbing down the device. But, since they really need a new modem anyway that supports the higher frequencies, it's probably easier to replace the current units with new units that support the higher frequencies as well as adds the lacking features. Also, it's more than just port forwarding and bridged mode. Even with this, you still can't access your home remotely as there's not an ip address assigned to the device. This is why a solution like ZeroTier is needed. It doesn't have anything to do with port forwarding or bridged mode, it's that there isn't even an IP address assigned that you can point to. It's like being behind a VPN, which is what ZeroTier allows you to get around.5Visto0likes0ComentariosRe: NAT (Forwarding) in T-Mobile Gateway
Kevin71246 wrote: I spoke with TMobile Home Internet technical support over the past week. They are working on the port forwarding feature within their 5g modem/router, but it's not available or ready yet. 2 different techs said they have a workaround, however (& it doesn't require 3rd party services). I haven't tested it yet, but what you need to do is, & many of us have this setup already, connect via Ethernet (wire) the garbage can LAN port <-> YOUR own router. Then configure port forwarding on YOUR router. That's it. (Your router needs to support ipv6! Not sure if we need to allow ipv6 passthrough for this.) Now, I was educated a long time ago on IPv4 & they barely touched on IPv6, so I don't know a lot about it, but this would never work this way with IPv6. Ipv6, however can allow passthrough so public "internet" can pass through a router, which is why I'm "buying" this theory. Ie, you can go through T-Mobiles garbage can, and then your router, and you device (call it a PC) could have a public IPv6 IP, which is why port forwarding could work this way. Anyone have time to test & report back? Or comments? I previously had a dynamic public IP (ipv4) that I made work with my domain name via ZoneEdit that allowed my PC to update ZoneEdit with public Ip changes since it was dynamic. With this NEW setup, I'm not exactly sure how that would work, or if my DNS service will play nicely or even support ipv6 or if ZoneEdit will either. And I have numerous services that I need to "hit" MY router & forward internally, such as a VPN, RDP, FTP, website, etc - not sure if all that will play nicely - or if all the services, like VPN client, can point to a domain->ipv6 ip & work. Like will the VPN client config & SW accept this new format? Anyways, lot of testing & messing around needed! Please report back with any updates! This doesn't work because the ports can't route from the T-Mobile gateway to the router. Also, the way T-Mobile's network is setup, it's basically a no-go. I did get some things to work using the ZeroTier software. But, it needs both the ZeroTier server software running on the local device you want to access and the ZeroTier client software running from the device you want to connect from. This works from my phone (running the ZeroTier client) to my NAS (running a ZeroTier server on a Docker container). It's a clunky "solution" that only solves some problems. Really, the T-Mobile internet modem needs to add a few features (DNZ as minimum, but port forwarding and assigning an IP address). I hear there's a new T-Mobile internet modem coming soon that will not only add these features, but also support the higher 5G frequencies for higher speeds. This is great for me as I have a T-Mobile millimeter wave tower on the boulevard right across the street from my house (formally a Sprint tower). But, no word yet on when this will be released.4Visto0likes0ComentariosRe: High-Speed Internet Gateway will not lock to 5G speeds (5G21)
I know this is an old thread, but the issue seems to be ongoing. What I did was get a directional 5g antenna and aim it at the 5g tower (n41 band 2500 MHz) so the 4g (B66 band 1700 MHz) signal wasn't the strongest. What I really wish is that the gateway worked with millimeter wave bands (mmWave) as I have a mmWave tower in the boulevard directly across the street from me. Not even my brand new phone uses it, so I'd guess a new version of this gateway supporting mmWave in the near future.4Visto1like0Comentarios