R:\>wget http://download.microsoft.com/download/b/a/4/ba4a7e71-2906-4b2d-a0e1-80
cf16844f5f/dotnetfx45_full_x86_x64.exe
--15:11:13-- http://download.microsoft.com/download/b/a/4/ba4a7e71-2906-4b2d-a0
e1-80cf16844f5f/dotnetfx45_full_x86_x64.exe
=> `dotnetfx45_full_x86_x64.exe'
Resolving download.microsoft.com... 183.134.43.146
Connecting to download.microsoft.com|183.134.43.146|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 50,352,408 (48M) [application/octet-stream]

9% [==> ] 4,618,710 488.58K/s ETA 01:32^
C
R:\>wget http://dl.softmgr.qq.com/original/Drivers/dotnetfx45_full_x86_x64.exe
--15:11:49-- http://dl.softmgr.qq.com/original/Drivers/dotnetfx45_full_x86_x64.
exe
=> `dotnetfx45_full_x86_x64.exe.1'
Resolving dl.softmgr.qq.com... 183.61.224.110, 123.151.152.123, 101.226.129.171
Connecting to dl.softmgr.qq.com|183.61.224.110|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://221.228.67.148/dl.softmgr.qq.com/original/Drivers/dotnetfx45_fu
ll_x86_x64.exe?mkey=5662a8c772bcfd86&f=1324&p=.exe [following]
--15:11:49-- http://221.228.67.148/dl.softmgr.qq.com/original/Drivers/dotnetfx4
5_full_x86_x64.exe?mkey=5662a8c772bcfd86&f=1324&p=.exe
=> `dotnetfx45_full_x86_x64.exe@mkey=5662a8c772bcfd86&f=1324&p=.exe'
Connecting to 221.228.67.148:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 50,352,408 (48M) [application/octet-stream]

3% [> ] 1,572,864 442.26K/s ETA 01:47^
C

用 wget 下载吧，有 302 重定向提示，不过电信线路应该是不会显示转向这个 url 链接的。刚想演示一下结果。。。可怜的 linode


R:\>wget http://speedtest.tokyo.linode.com/100MB-tokyo.bin
--15:06:37-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
=> `100MB-tokyo.bin'
Resolving speedtest.tokyo.linode.com... 106.187.96.148
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:37-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try: 2) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:37-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try: 3) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:37-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try: 4) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:37-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try: 5) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:37-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try: 6) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:37-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try: 7) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:37-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try: 8) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:37-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try: 9) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:37-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try:10) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:37-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try:11) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:37-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try:12) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:37-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try:13) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:37-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try:14) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:37-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try:15) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:38-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try:16) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:38-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try:17) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:38-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try:18) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:38-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try:19) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Retrying.

--15:06:38-- http://speedtest.tokyo.linode.com/100MB-tokyo.bin
(try:20) => `100MB-tokyo.bin'
Connecting to speedtest.tokyo.linode.com|106.187.96.148|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in
headers.
Giving up.

GMO 的东西比较变态的，传闻虽然说是不限流量，但是大流量就挂起。重启 DHCP 半天没分配到 ip 看起来像是故意的，这种问题对方技术人员都没注意到吗。而且一旦违反 tos 规定，主机直接删除，里面的余额就直接吃定，哈哈，太 NB 了。这个不限流量比较坑，如果不自己给自己限制，一旦把服务器分享出去，分分钟钟超流量，时时刻刻被挂起。这家也只能挂挂代理了，而按目前的情况来看超售应该也蛮厉害的，白天的流量还不如搬瓦工稳定，不知道为什么我这里的线路动不动就掉到 1000kbps ，感觉流量非常得不足，白天看个 720p 都叫苦连天啊。

http://tieba.baidu.com/p/4051372707
conoha 不允许上传任何 windows 系统镜像，包括正版，只允许使用他们自己的授权（旧版）。不允许 linux 机型上传 win 镜像，月流量限制 5TB ，日平均带宽不可超过 25mbps ，违规基本下场就是 ban

时代在变化，以前用书签多简单， ie 弹出单 html 页面，然后保存到网站。还有什么难度，收藏这个页面什么书签都有了。

用搬瓦工的代理看起来没问题，可是去哪验证美国的号码，

使用入门 请注意， Google 语音仅在美国可用。 您将需要验证一个现有的美国电话号码以获取 Google 语音号码。我接受 Google 语音的条款和隐私权政策。

ping 一定程序反映了网络饱合情况，可能本地网络繁忙，也可能远程网络繁忙，一个拥塞的网络通常都可以高达 600ms ， 600ms 算什么，在无线网络 10000ms 以上都遇到过了。

这里有客户端下载

https://www.ipip.net/

string 没希望的，现在到处都是 302 重定向，服务器一个个添加手都疼了，关键最后会造成像 wget 这样单线程软件没有任何反应。电信还好，虽然前几天遇到下酷市场变成应用宝，不知道什么原因导致的，甚至有一些特别的链接会导致本地 qos 策略失效，这个是最 NB 的至今找不出原因。
小软件就挂代理吧，老这样的话换 isp 。

回程就成这样了。

http://ww1.sinaimg.cn/large/0060lm7Tgw1eyhs52o1k9j30qo0mxtgz.jpg

昨天晚上还有点速度，以前没测过回程。现在回程经过 202 这个延迟制造区，所以到底是 z.com 还是电信的错呢， 99%是电信的问题。这个东西要持续没速度，这个价位完全可以无视了。以前还指望它可以多人共享，自己给自己限速了，现在倒好电信帮我限速了。。。

熟能生巧

输入法的选择也是个学问，电脑用久了提笔不知道字怎么写，拼音就是这个原因排斥的，当然跟自己方言分不清灰 飞有关系，虽然以前在用 linux scim 模糊音时输入也蛮快的。

正是因为不想让自己忘了中文是如何书写的所以选择了形码。花了二个星期学了那王旁青头兼五一，哈哈什么玩意，人家对五笔的评价是，不按中文笔划顺序拆分的，学得很废劲，忘得也很快。当我看到一个老人对表形码是在他 60 多岁学成时，我就去学表形码了，学了它就忘了五笔了，可惜这个在 win98 se 出现的输入法，再也没有出现过。后续的 win7 开始就要用 多多输入法平台 转换 win98 的码表才可以在新平台继续使用。

手机用的笔画码，这个输入法其实也非常不错就是相对四码上屏输入笔画多了点。

是 12306 官方提供的手机客户端，提前打开看是否有更新，不是浏览器。只要有准确的延时基本是一按就有。

。。。按 2014 年的时候是晚二分钟二十秒以上。最好用手机浏览器。自己找别的线路再验证一下吧。

现在上网环境很不安全，没听过墙有返回探测功能吗，据说这就是当年打败 t 开头的法宝，现在 stunnel 都用 tls 1.2 了，终端上还有各种 ssl 错误，结合服务器日志，各种突然断开， tcp reset 的提示，幸好 stunnel 具备 pki 认证，还是能很有效的防止中间人问题。

话说昨天下了 android maxthon ，这东西就是老出现 https 证书问题才不用的，然后直接提示有在线书签是否同步，好狠连帐号都没申请过，它就同步了书签，当然设置部分有各种同步选项，当然是默认开启的，有得上传没得删除。隐私这种问题，大量的数据就能拼凑出一个人的日常行为，哎，远离国产 app 简直是把木马装在手机上。

什么叫家用的小网站。。。

阿里的东西还是觉得贵，用惯了国外的不限流的，再用 100kb 的线路好慢。偶那小网站就架在路由器上，还不错有 140kb/s 上行。