Jump to content


Member Since 09 May 2014
Online Last Active Today, 02:17 PM

Topics I've Started

Cookie Disclaimer every page load

14 November 2017 - 07:12 PM

I don't know if it's a problem with the new firefox 57 or the new add-on system but I'm getting the cookie disclaimer at the bottom of the page with every page load.  Anybody else seeing this?

recursive routing in pfsense

17 August 2017 - 07:31 PM

Is something wrong with my config that when I try to view the status page for the server to which I'm connected I get warnings of recursive routing in my openvpn log?  pfsense thinks the destination is itself or something, right?  It prevents me from viewing the graphs on the status page for the server. :)

Staff, why the Enzu servers imminent withdrawal?

24 July 2017 - 02:42 PM

Just wondering why.  Also, will there be any replacements?

Can't download linux, windows, mac software

03 April 2017 - 07:59 PM

I first noticed that my linux box erred when updating the Eddie repo.


Then, I looked to see if something had changed in the Linux client section.  That's when I see that the page isn't working to download Eddie for windows, mac, nor linux.


working now

ISP routing craziness

02 April 2017 - 11:14 PM

Starting this topic as a way for me to vent and perhaps see that I'm not the only one to see crazy routing by my ISP.


The topic has come up in other threads, with knowledgeable people confirming my belief that ISPs relegate VPN traffic to very low priority.


Route testing shows that this low priority isn't based on packet inspection but simply the destination of the traffic (and, I assume, the source).  In other words, traffic both directions between us and the server is affected.



Trace to Draco, primary IP address

2  [7922] [COMCAST-22] xe-3-1-3-sur02.east.tx.houston.comcast.net ( 8.8ms
 3  [7922] [COMCAST-22] ae-9-ar01.bisbee.tx.houston.comcast.net ( 7.9ms
 4  [7922] [COMCAST-16] be-33662-cr02.56marietta.ga.ibone.comcast.net ( 30.7ms
 5  [7922] [COMCAST-16] hu-0-12-0-6-pe01.56marietta.ga.ibone.comcast.net ( 24.4ms
 6  [7922] [IBONE-CCCS-2] 30.9ms
 7  [174] [NET-154-54-0-0] be2847.ccr41.atl01.atlas.cogentco.com ( 42.4ms
 8  [174] [NET-154-54-0-0] be2687.ccr41.iah01.atlas.cogentco.com ( 28.8ms
 9  [174] [NET-154-54-0-0] be2441.ccr21.dfw01.atlas.cogentco.com ( 30.1ms
10  [174] [NET-154-54-0-0] te0-0-0-0.agr12.dfw01.atlas.cogentco.com ( 41.1ms
11  [174] [NET-154-24-0-0] te0-0-2-3.nr11.b000821-1.dfw01.atlas.cogentco.com ( 37.1ms
12  [174] [COGENT-A] 35.6ms
13  [15003] [NETBLK-NOBIS-TECHNOLOGY-GROUP-06] [target] 32.1ms

Note it goes all the way to Atlanta, then back to Dallas through Houston on Cogent.  Why on earth do they send it to Atlanta to get on Cogent's network?  Dallas is only 4 hours drive from Houston and as you'll see from the next trace, Comcast has a connection to Cogent right in Houston. :)


Trace to Draco, alternate IP address

2  [7922] [COMCAST-22] xe-3-1-2-sur03.east.tx.houston.comcast.net ( 7.7ms
 3  [7922] [COMCAST-22] ae-18-ar01.bearcreek.tx.houston.comcast.net ( 8.6ms
 4  [7922] [COMCAST-16] be-33662-cr02.dallas.tx.ibone.comcast.net ( 15.6ms
 5  [7922] [COMCAST-16] be-12493-pe01.houston.tx.ibone.comcast.net ( 20.4ms
 6  [7922] [CBC-COMCAST-1] 20.5ms
 7  [174] [NET-154-24-0-0] te0-0-1-0.rcr12.iah02.atlas.cogentco.com ( 21.0ms
 8  [174] [NET-154-54-0-0] be2145.ccr41.iah01.atlas.cogentco.com ( 24.1ms
 9  [174] [NET-154-54-0-0] be2441.ccr21.dfw01.atlas.cogentco.com ( 20.1ms
10  [174] [COGENT-NB-0000] te0-0-0-0.agr11.dfw01.atlas.cogentco.com ( 21.0ms
11  [174] [NET-154-24-0-0] te0-0-2-0.nr11.b000821-1.dfw01.atlas.cogentco.com ( 21.7ms
12  [174] [COGENT-A] 24.2ms
13  [15003] [NETBLK-NOBIS-TECHNOLOGY-GROUP-06] [target] 20.4ms

Amazingly, the trace gets to Dallas in the 4th hop, but then heads right back to Houston to get on Cogent's network.  It makes zero sense unless you realize that Comcast are doing this crap on purpose.  I have rarely seen a route that heads directly to the VPN server upon reaching Dallas, finding Cogent's network there instead of having to get back to Houston.


Understand that this is normal, everyday behavior.  I have another VPN provider with servers in Dallas and Atlanta.  Amazingly, all the Atlanta servers route through Dallas, and all the Dallas servers route through Atlanta.  So, the routes are available, but purposely screwed up.


Finally, check this out.


Instead of tracing the route to Draco, I instead trace the route to Cogent's router at, seen in hop 12 above.  Check out the premium routing I get now.


 2  [7922] [COMCAST-22] xe-3-1-3-sur03.east.tx.houston.comcast.net ( 10.2ms
 3  [7922] [COMCAST-22] ae-18-ar01.bearcreek.tx.houston.comcast.net ( 9.1ms
 4  [7922] [COMCAST-16] be-33662-cr02.dallas.tx.ibone.comcast.net ( 14.1ms
 5  [7922] [COMCAST-16] be-12495-pe03.1950stemmons.tx.ibone.comcast.net ( 13.7ms
 6  [7922] [IBONE-CCCS-3] 13.0ms
 7  [174] [NET-154-54-0-0] be2763.ccr21.dfw01.atlas.cogentco.com ( 14.1ms
 8  [174] [NET-154-54-0-0] te0-0-0-0.agr12.dfw01.atlas.cogentco.com ( 13.8ms
 9  [174] [NET-154-24-0-0] te0-0-2-3.nr11.b000821-1.dfw01.atlas.cogentco.com ( 15.2ms
10  [174] [COGENT-A] [target] 13.6ms



Servers online. Online Sessions: 14893 - BW: 42558 Mbit/sYour IP: Access.