RodneyWright wrote:
Jason Tower wrote:
...are you getting a 192.168.1.x ip on the linksys wan port? if you are that means you're double natting which (without getting all technical) is undesirable, what you ideally want is a public ip on the wan port. odds are the at&t cpe can do that but some reconfiguration will probably be required. what you have now works but you may run into a situation in the future which will not due to the double nat, and outside access (port forwarding, something i use every day) is impossible. i've set up uverse for a couple of clients and i always have to call tech support to make this change. just a heads up.
That's good info to have. Installer told me calling the tech desk was a chargable call and I was frustrated at the time. Now that it's working I can explore more. You willing to share your config info? I have access to both modems in regard to configuration.
i was never told of a charge to call tech, although i wasn't the one paying the at&t bill. i doubt it would apply since you're calling about a change to the cpe (customer premise equipment) not your own stuff, and you can argue that it should have been set up this way from the get go. i don't have any configs but what you want is to set it up so that your device gets a public ip, not a private one. sometimes it's called bridge mode, or ip passthrough, or something to that effect. when set up correctly it will disable nat on the cpe so that your device can handle it instead, you'll receive a public ip on your device via dhcp. note that cable modems generally work this way by default, certainly twc does, which is why they're so much nicer to deal with. dsl and other network technologies tend to default to the "we'll do nat on our device even though very few people actually want it that way" mode.
Login
Register
FAQ
Search
