Free republic blocked

Self

[MomwithHope]

I won’t say anything considering your tagline. Thanks for your service, brother.

[Doogle]

My honor....

[Albion Wilde]

LOL!

[Albion Wilde]

Oh, sorry I missed that! What a fun thread!

[Vermont Lt]

I love those. Thanks.

[timestax]

[Sidebar Moderator]

LMAO

[George from New England]

Problem original reported Sat nite is now 100% working.

Is it permanent, who can tell, can they do it again, sure. ? is was it intentionally a block on a conservative site?

I have logged in from my desktop and dsl provider and have my HAPPY KB in hand !!

I did find during my blockage that the secure free site at port 443 was accessible. But noone can login with just port 443. Jim has it setup that port 80 is needed for a login to submit and work.

fyi

p.s. I have not heard back from any of my contacts admitting who or what was the problem. I will post again in this thread should maybe 5% of freepers care.

[George from New England]

This is the current trace ..

george@linux-3:/var/log/apache2$ tcptraceroute freerepublic.com 80
Selected device br0, address 192.168.1.73, port 48395 for outgoing packets
Tracing the path to freerepublic.com (209.157.64.200) on TCP port 80 (http), 30 hops max
1 192.168.1.1 0.537 ms 0.390 ms 0.330 ms
2 fl-71-48-224-1.dhcp.embarqhsd.net (71.48.224.1) 17.972 ms 17.836 ms 26.680 ms
3 orlf-agw1.inet.qwest.net (75.160.222.145) 18.380 ms 19.269 ms 18.144 ms
4 nap-brdr-01.inet.qwest.net (67.14.29.102) 24.912 ms 24.617 ms 24.828 ms
5 63.146.27.154 32.495 ms 25.579 ms 24.423 ms
6 ae-5.r05.miamfl02.us.bb.gin.ntt.net (129.250.3.166) 125.950 ms 104.191 ms 171.308 ms
7 ae-4.r20.miamfl02.us.bb.gin.ntt.net (129.250.2.184) 195.206 ms 93.418 ms 34.710 ms
8 ae-4.r23.asbnva02.us.bb.gin.ntt.net (129.250.2.86) 44.380 ms 51.939 ms 49.642 ms
9 ae-10.r22.snjsca04.us.bb.gin.ntt.net (129.250.6.237) 178.905 ms 102.748 ms 102.631 ms
10 ae-40.r02.snjsca04.us.bb.gin.ntt.net (129.250.3.121) 121.935 ms 103.992 ms 103.283 ms
11 ae-2.r00.mlpsca01.us.bb.gin.ntt.net (129.250.4.101) 235.666 ms 103.088 ms 145.067 ms
12 129.250.24.196 103.403 ms 103.245 ms 181.633 ms
13 129.250.130.254 182.470 ms 112.138 ms 103.396 ms
14 128.242.105.82 130.469 ms * 109.967 ms
15 209.157.64.200 [open] 103.631 ms 121.996 ms 104.695 ms

compared to the bad trace from Sat nite ...

TCP route trace to freerepublic.com on port 80 (HTTP):
Tracing the path to freerepublic.com (209.157.64.200) on TCP port 80
(http), 30 hops max
1 192.168.1.1 0.496 ms 0.326 ms 0.320 ms
2 fl-71-48-224-1.dhcp.embarqhsd.net (71.48.224.1) 18.501 ms 18.108 ms
18.155 ms
3 orlf-agw1.inet.qwest.net (75.160.222.145) 20.859 ms 18.134 ms 18.362 ms
4 * * *
5 * * * etc

[samtheman]

I stuck on small KB sorry Qwest is blocking Mr Any ody else

I must say that I have no idea of meaning of that sentence, if that’s what you can call it.

---

My guess at translation:

I am stuck on low bandwidth (just a few kb per second). Sorry, Quest is blocking my access. Is this happening to anybody else?

[samtheman]

All Creepers Locked And Guilted As Ordered, SIR !

---

LOL!