On Thu, 30 Jul 2015 12:02:06 -0400, Keith Stokes
wrote:
1. Is it really accurate that the customer’s address is tied to the
modem/router?
To the 802.1x identity of the device, yes. That's the unit serial number,
which (partial) contains the MAC.
2. For my curiosity, is this done through
“Forever” is a long time. We’re shooting for not having to change people’s
address multiple times per week while still trying to help them save costs by
not paying extra for “official" static IPs.
Changing every 6 months as some have pointed out as their experience is
perfectly acceptable to us
I have AT&T u-verse small business connection at my office with a
static IP setup, and my experience matches with the AT&T tech said.
We have a separate router behind the AT&T router. The AT&T router is
an Arris (former Motorola) NVG595. Our router has a static IP out of
our subnet and d
On Thu, Jul 30, 2015 at 12:14 PM, Ca By wrote:
> On Thu, Jul 30, 2015 at 9:02 AM, Keith Stokes wrote:
>
>> I’m wondering if some can share their experiences or maybe there’s an AT&T
>> person here who can confirm policy.
>>
>> I work for SaaS provider who requires a source IP to access our system
I've had AT&T UVerse for 3 years now and it has changed at least twice
since I got it. The DHCP address has an expiration of ~7 days and it
usually keeps the same address upon renewal but a few times I have noticed
that it's changed. I wouldn't trust it to be static forever.
--
James Hartig
On Thu, 30 Jul 2015, Keith Stokes wrote:
1. Is it really accurate that the customer’s address is tied to the
modem/router?
AT&T calls it "Sticky IP address." A U-Verse Residential Gateway tends
to get the same IP address from DHCP, for months or years, but its not
guaranteed. An subnet may c
Access is not the only reason we ask for non-changing source IP addresses.
I’m not arguing the long-term sensibility of the approach. It’s arguably a
legacy app and has 5000 endpoints that we have to still support until different
solutions on our side are complete. That process is outside of my
People need to really stop using Source IP as an ACL mechanism
whereever possible. Have you considered using SSL certs or SSH keys
or some other sort of API key instead? I'm mean, do you really want
to have to know how the technology of every ISP that every possible
SaaS customer may use to acces
On Thu, Jul 30, 2015 at 9:02 AM, Keith Stokes wrote:
> I’m wondering if some can share their experiences or maybe there’s an AT&T
> person here who can confirm policy.
>
> I work for SaaS provider who requires a source IP to access our system to
> businesses.
>
>
That is probably a problematic pr
I’m wondering if some can share their experiences or maybe there’s an AT&T
person here who can confirm policy.
I work for SaaS provider who requires a source IP to access our system to
businesses.
Normally we tell the customer to request a “Static IP” from their provider.
That term makes sense
10 matches
Mail list logo
