首页 注册 登录
V2EX = way to explore
V2EX 是一个关于分享和探索的地方
现在注册
已注册用户请  登录
V2EX 提问指南
广告
Biwood
V2EX  ›  问与答

下载链接经常被指定到 124.202.164.* 这个 IP 段，是运营商劫持还是 CDN 部署？

  •   
  •   Biwood · 2015-12-05 14:21:09 +08:00 · 4848 次点击
    这是一个创建于 3281 天前的主题，其中的信息可能已经有所发展或是发生改变。

    我在使用 Linode 的 SpeedTest 页面的下载链接进行测速时，下载地址发生了变化，但是仍然能够正常下载。

    原地址是：http://speedtest.tokyo.linode.com/100MB-tokyo.bin
    Chrome 的下载页面显示的地址却是：http://124.202.164.4/files/118400000600AA94/speedtest.tokyo.linode.com/100MB-tokyo.bin
    下载速度有 1M/s 。

    今天下载最新版 VirtualBox 的安装文件时也遇到了这种情况。
    原地址是：http://download.virtualbox.org/virtualbox/5.0.10/VirtualBox-5.0.10-104061-Win.exe
    Chrome 下载页显示的地址却是：http://124.202.164.16/files/117900000722B058/119.147.135.245/tech.down.sina.com.cn/20151111/c50dbed4/VirtualBox-5.0.10-104061-Win.exe
    下载速度有 6M/s ，基本满速。

    如图：
    截图

    变化之后的链接地址都是 http://124.202.164.4/files/xxx 这种形式，这是什么意思？关键是下载速度都还比较快，到底是 CDN 还是什么。

  • 下载
  • 地址
  • Chrome
  • CDN
    19 条回复  •  2015-12-06 02:59:10 +08:00
    imgalaxy
        1
    imgalaxy  
       2015-12-05 14:33:05 +08:00 via Android
    这是一种叫缓存服务器的东西 一般三方运营商和校园网布置较多
    热门文件会进服务器 进行网内传输 达到节省运营商外网流量的目的
    大概就是这样 以上都是我瞎说的
    datocp
        2
    datocp  
       2015-12-05 15:07:34 +08:00
    用 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.
    datocp
        3
    datocp  
       2015-12-05 15:11:02 +08:00
    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
    Andy1999
        4
    Andy1999  
       2015-12-05 15:11:59 +08:00 via iPhone
    ISP 劫持无误
    bazingaterry
        5
    bazingaterry  
       2015-12-05 15:30:47 +08:00
    IP ： 124.202.164.4 来自：北京市 鹏博士
    Biwood
        6
    Biwood  
    OP
       2015-12-05 15:32:02 +08:00 via Android
    @bazingaterry 我用的就是鹏博士
    Biwood
        7
    Biwood  
    OP
       2015-12-05 15:32:59 +08:00 via Android
    @Andy1999 关键是下载速度还挺快，要是劫持了怎么还能下载到源文件呢
    wsy2220
        8
    wsy2220  
       2015-12-05 15:34:43 +08:00
    运营商缓存
    just1
        9
    just1  
       2015-12-05 15:34:46 +08:00 via Android
    @Biwood 局域网内的缓存啊，兄弟
    Andy1999
        10
    Andy1999  
       2015-12-05 15:37:35 +08:00 via iPhone
    @Biwood 缓存到内网 目测是彭博士的代理服务器 前几天刚被日过一次
    yexm0
        11
    yexm0  
       2015-12-05 16:01:58 +08:00
    有谁懂 openwrt 路由怎么设置才能绕开这种内网缓存不?
    luckykong
        12
    luckykong  
       2015-12-05 16:31:46 +08:00
    @Biwood 为什么劫持了就不能下载到文件？
    这个不就相当于迅雷的离线下载么，服务商替你下载好，你直接从内网的服务器瞎子啊
    luckykong
        13
    luckykong  
       2015-12-05 16:32:31 +08:00
    @Biwood 抱歉 按键太快了
    最后三个字“瞎子啊”，应该是“下载”。。打错了
    yexm0
        14
    yexm0  
       2015-12-05 16:41:58 +08:00
    @luckykong 楼主下载测速文件是想测试它家电脑到 vps 之间的线路速度,现在被运营商截掉了那还怎么测试呢?
    Biwood
        15
    Biwood  
    OP
       2015-12-05 16:43:34 +08:00
    @luckykong 这也太不安全了，万一他们把下载文件替换了我都不知道，谁特么要运营商替我缓存文件的，真是自作多情
    baijd
        16
    baijd  
       2015-12-05 17:06:22 +08:00
    移动 ftth ，也碰到>_<

    有时候下下来文件被修改了
    fengxing
        17
    fengxing  
       2015-12-05 17:13:25 +08:00
    @yexm0 openwrt 设置 ss 透明代理吧，国外地址全部走代理
    Cu635
        18
    Cu635  
       2015-12-05 17:21:41 +08:00
    运营商缓存。

    不过 lz 你算是幸运的，运营商的缓存还没问题，要是赶上运营商跳转到自己的缓存、这缓存还三天两头损坏你就会想烧了运营商机房的。

    不知道你这运营商缓存会不会出现上游文件同名更新，缓存文件却不更新的情况。
    mengskysama
        19
    mengskysama  
       2015-12-06 02:59:10 +08:00
    之前游戏公司遇到过大量玩家投诉无法按照，最后查出来是缓存错了 1 个字节
    关于   ·   帮助文档   ·   博客   ·   API   ·   FAQ   ·   实用小工具   ·   5806 人在线   最高记录 6679   ·     Select Language
    创意工作者们的社区
    World is powered by solitude
    VERSION: 3.9.8.5 · 26ms · UTC 02:54 · PVG 10:54 · LAX 18:54 · JFK 21:54
    Developed with CodeLauncher
    ♥ Do have faith in what you're doing.