On Wed, 27 Apr 2016, Baptiste Jonglez wrote:
So, if this is basically DNS64/NAT64, these IP addresses should not be
seen as source or destination address outside of T-Mobile's network, and
are not attached to the interface of any device.
Based on http://dan.drown.org/android/clat/, it looks
On Wed, 27 Apr 2016, Baptiste Jonglez wrote:
While doing statistics on the participants of a public DHT, I was
surprised to see some IP addresses that are not present in the DFZ:
I believe those are used by T-mobile's 464XLAT (RFC 6877) implementation.
Recent Android on T-mobile is IPv6-only
On Sun, 18 Oct 2015, Clayton Zekelman wrote:
I didn't think Asterisk had modem DSP and RAS code?! Huh?
I was surprised to find IAXmodem (http://iaxmodem.sourceforge.net/), which
is "a software modem written in C that uses an IAX channel (commonly
provided by an Asterisk PBX system) instead
Is it normal to bill for IPv6 service as a separate product? I was
surprised to hear from from my Akamai rep they they do:
Hi Aaron, We can add the IPV6 service to the contract at an additional
cost of $XXX/month. Please let me know if you would like to go ahead with
the service and I can
On Mon, 18 Aug 2014, Mehmet Akcin wrote:
What did they say when you asked them(Akamai)?
I quoted their response in my mail; sorry if that wasn't clear. They
offered to enable IPv6 service for a non-trivial monthly recurring fee,
which they offered to send me a revised contract to include.
On Mon, 18 Aug 2014, Noam Freedman wrote:
I'll make sure someone follows up on your ticket. To help accelerate
overall IPv6 adoption, we stopped charging for new conversions to IPv6
over a year ago. Probably just some misinformation in the sales force
from the old policy...
Oh, I hadn't
On Sat, 18 Aug 2012, Patrick W. Gilmore wrote:
IMHO, if Google losses a datacenter and all users are stuck waiting for a
long TTL to run out, that is Very Bad. In fact, I would call even 2.5
minutes (average of 5 min TTL) Very Bad. I'm impressed they are
comfortable with a 300 second TTL.
On Thu, 21 Apr 2011, Dan White wrote:
We're experiencing very poor quality with You Tube, and it appears we're
subject to a bad entry within a geolocation database somewhere.
I'm not sure about Youtube, but Google seems to do some some clever but
annoying things with correlating requests
On Tue, 10 Nov 2009, Drew Weaver wrote:
If you have several transit providers connected to your network and much
of your traffic is generally directed by the BGP tiebreaker (i.e. lowest
IP address) is there a way, without specifying on a per-prefix basis to
prefer the tie breaker winner
On Wed, 21 Jan 2009, Phil Rosenthal wrote:
This attack has been ongoing on 66.230.128.15/66.230.160.1 for about 24 hours
now, and we are receiving roughly 5Gbit of attack packets from roughly
750,000 hosts.
I'm only receiving NS queries for . from spoofed 66.230.128.15 and
66.230.160.1 via
10 matches
Mail list logo
