how-to block ads
|reply to MrMazda86 |
Re: [DSL] Static IP Address
said by MrMazda86:Wrong. For the purposes of our discussion, there's just the PPP relay running between two devices, which is a "logical link" not a "virtual link". There's no difference in the PPP link whether you have a static address/subnet or a dynamically-assigned address; PPP doesn't care what is traversing that link, it just encapsulates it. The routing tables are set at either end to route traffic properly for a specific subnet, and the default gateway of the CPE would be the router on the other end of the PPP link. You can set any arbitrary IP addresses you want on either side of the PPP link, but that doesn't mean they'll be routable.
What surprises me is that nobody at TSI has been able to respond with the actual answer. As for there not being a "virtual link", you clearly have never run a static subnet before because... that's got to be the biggest load of rubbish I've ever heard.
Also I'm pretty sure you've heard more outlandish things in your life, so "biggest load of rubbish" may be a slight overstatement.
said by MrMazda86:Neither does IPv4. What you're inquiring about is a policy related to the handling of AAA (specifically the second "A") based on whether or not a customer has a static subnet allocated to them. Obviously, you can't practically assign the same (in this case, static) IP to two separate stub networks, so they're only allowing one PPP relay to be established to prevent this from happening. Again, nothing to do with IPv6 or IPv4! It's all AAA!
As for IPv6, that's a whole separate ball of wax completely from the issue that I'm inquiring on. IPv6 has nothing to do with what I'm inquiring on.
said by MrMazda86:Also wrong. IPv6 logins aren't IPv6-only, and you prove your ignorance by saying so. It's not a "whole separate service with a whole separate purpose", although you are correct that it won't solve the issue you're talking about here.
In fact, an IPv6 login is just that... IPv6 ONLY! It too is a whole separate service with a whole separate purpose, which will not allow for what I'm inquiring about.
I know exactly the "issue" you're talking about, but you're being really belligerent when people are honestly trying to help you out. To get a direct answer from TSI, you should ask one of them either over the phone or in the direct forum as I'm sure they'd be able to help you out there, and let you know whether you can have a separate login with a dynamic IP for testing purposes. Also, let's not forget that test@test/test was designed for, well, testing (not that the credentials imply that or anything ), so I'd imagine that's probably they answer they'll give you.
I decided to call TSI to inquire... It turns out that they're not able to directly issue two static IP addresses to a single PPPoE login, however they can create a second PPPoE login and affix a static IP address to each one of them. That would then allow me to be able to use my DSL service normally with its own static IP, which would then also leave me able to have the troubleshooting login for sticky situations. As for the bill, all it will do is add the $4 charge for a static IP to the bill twice, which is fine.
Apparently, TSI can do pretty well anything... It's just a matter of setting up the configurations to do so.