Re: Amazon now controls 3.0.0.0/8

2018-11-08 Thread Dan Lowe
Maybe Amazon will do something cool with 3.1.33.7 ...

dan


On Thu, Nov 8, 2018, at 8:30 PM, Todd Underwood wrote:
> google used 4.4.4.4 for DNS in the past (2010, IIRC).
> 
> t
> 
> On Thu, Nov 8, 2018 at 8:21 PM Steve Meuse  wrote:
>> 
>> I think it was the dial modem team that beat us to 4.4.4.0/24? 
>> 
>> -Steve
>> 
>> On Thu, Nov 8, 2018 at 7:44 PM John Orthoefer
>>  wrote:>>> 
>>> I wish we could have used 4.4.4.4. Although at the time I suspect we
>>> would have used 4.4.4.[123].>>> 
>>> Johno 
>>> 
>>> On Nov 8, 2018, at 18:58, Matt Erculiani 
>>> wrote: So it looks like GE will be solvent for a few more years and
 3.3.3.3 DNS is incoming. 
 -Matt
 
 On Thu, Nov 8, 2018, 17:54 Eric Kuhnke >>> wrote:> https://news.ycombinator.com/item?id=18407173
> 
> Quoting from the post:
> 
> "
> 
> Apparently bought in two chunks: 3.0.0.0/9 and 3.128.0.0/9.
> Previous owner was GE.


> Anecdotal reports across the Internet that AWS EIPs are now being
> assigned in that range.> 
> https://whois.arin.net/rest/net/NET-3-0-0-0-1.html


> https://whois.arin.net/rest/net/NET-3-128-0-0-1.html


> "
> 
> 
> 



Re: Oct. 3, 2018 EAS Presidential Alert test

2018-10-04 Thread Dan Lowe
My wife and I, both on AT iPhones in the greater Cleveland area, received 
nothing. A co-worker of mine in Virginia got an alert, another in Texas did 
not. I believe the co-workers are both on AT

I can't speak for the co-workers, but my wife and I do not have wifi calling 
enabled.

Dan


On Wed, Oct 3, 2018, at 2:52 PM, Andy Ringsmuth wrote:
> Did anyone on AT or an iPhone receive the test today? I believe it was 
> supposed to happen at 2:18 EDT, followed by one on broadcast radio at 
> 2:20 EDT.
> 
> I’m in CDT, so 1:18 and 1:20 p.m. CDT.
> 
> Message was heard on my desk radio at 1:21:35 p.m. CDT but as of the 
> sending of this at 1:52 p.m. CDT, nothing on phones. I have an office 
> full of AT iPhones and not a single one of them alerted.
> 
> FEMA says https://www.fema.gov/emergency-alert-test
> 
> "Cell towers will broadcast the WEA test for approximately 30 minutes 
> beginning at 2:18 p.m. EDT. During this time, WEA compatible cell phones 
> that are switched on, within range of an active cell tower, and whose 
> wireless provider participates in WEA should be capable of receiving the 
> test message. Some cell phones will not receive the test message, and 
> cell phones should only receive the message once."
> 
> My wife, with a Sprint iPhone, received the test.
> 
> 
> 
> Andy Ringsmuth
> 5609 Harding Drive
> Lincoln, NE 68521-5831
> (402) 304-0083
> a...@andyring.com
> 


Re: UVerse question

2015-02-08 Thread Dan Lowe
On Sun, Feb 8, 2015, at 05:48 PM, TR Shaw wrote:
 Any suggestions on what to tell ATT to get IPv6 added to a current
 account and upgrade a 2wire router to 4wire with halfway decent
 performance and capability?

I have no advice on the equipment upgrade, but I was able to add IPv6 to
my account by visiting this page

http://www.att.com/esupport/ipv6.jsp

and running the compatibility test. Once it determined that I didn't
have IPv6, it offered to turn it on. A few minutes later, my router had
an IPv6 subnet configured. A co-worker pointed me to this link, and it
worked similarly for him. He's in the Santa Rosa, CA market, and I'm in
the Cleveland, OH market.

Dan


Re: ATT uVerse blocking SIP?

2015-01-27 Thread Dan Lowe


On Mon, Jan 26, 2015, at 10:22 PM, Jared Mauch wrote:
 Yes.  If you move to another port, e.g.: 5061 it works fine.
 
 If you’re running on a Linux based system, you can do this:
 
 /sbin/iptables -A PREROUTING -t nat -i eth1 -p udp --dport 5061 -j
 REDIRECT --to-port 5060
 
 on the host to remap 5061 - 5060 with no application change.
 
 - Jared

In most cases the above has worked fine (we also use a 15060 - 5060
remap), but I have one user for whom nothing seems to work. The problem
has persisted with different models of CPE, different phones, different
server-side ports (5060, 5061, 15060). They even moved and the problem
followed them to a new house (albeit in the same area). I was never able
to work out the issue and have been assuming it's a regional problem in
Uverse (in this case it was near Austin, TX).

IIRC, the user ended up switching to cable.

Dan