OpenWRT/LEDE 分区并挂载移动硬盘

去年年初,为了体验4k的“塞尔达传说-旷野之息”,我升级了我的电脑,并在18年不断完善,目前经过optane加速的4T硬盘,速度提升非常显著,很是喜欢。但电脑里有些录音,以及家庭照片,想随时观看,而不想开电脑,另外也起到备份的作用(数据无价),所以一直在考虑采购一台NAS,但感觉现在的NAS及配件(硬盘)功能比较弱(其实就是没米。。。),所以就考虑利用现有资源,把1T的闲置移动硬盘挂载到 WRT1200路由器下,这样 Win/Mac/手机 通过sshfs/samba远程挂载目录,这样可以体验简易NAS,等时机成熟了再考虑NAS,此篇主要总结如何挂载移动硬盘,由于环境版本的不同,总结中的内容可能跟读者遇到的会有少许差异,如遇到问题,可自行google或baidu

有时候通过LEDE的luci直接挂载不起作用,也弄不明白为啥,所以还是CLI最靠谱。另外在openwrt里,移动硬盘的格式最好是ext3或ext4,这样效果高,问题少。另外就是最开始我想用sshfs,但后来发现windows访问sshfs效果非常不好,所以对于windows,就换回了samba服务器,速度不错,可以达到平均60MB/s 上下

另外Samba配置,可以参考我之前的文章 Deploy Samba on OpenWRT

1. 国内更新源,这样就可以随便更新软件了

src/gz arm_core https://mirrors.ustc.edu.cn/lede/releases/17.01.6/targets/mvebu/generic/packages
src/gz arm_base https://mirrors.ustc.edu.cn/lede/releases/17.01.6/packages/arm_cortex-a9_vfpv3/base
src/gz arm_luci https://mirrors.ustc.edu.cn/lede/releases/17.01.6/packages/arm_cortex-a9_vfpv3/luci
src/gz arm_packages https://mirrors.ustc.edu.cn/lede/releases/17.01.6/packages/arm_cortex-a9_vfpv3/packages
src/gz arm_routing https://mirrors.ustc.edu.cn/lede/releases/17.01.6/packages/arm_cortex-a9_vfpv3/routing
src/gz arm_telephony https://mirrors.ustc.edu.cn/lede/releases/17.01.6/packages/arm_cortex-a9_vfpv3/telephony

完整阅读

0

Install Yangsuite by Docker

Install

docker pull dockerhub.cisco.com/yang-tools-release-docker/yangsuite:latest
docker run -it -p 8480:8480 \
      --mount type=bind,source=/xxx/Documents/Yangsuite_data,target=/home/docker/data \
      dockerhub.cisco.com/yang-tools-release-docker/yangsuite:latest

Detail info:

xxxxx:~ xxxxx$ docker pull dockerhub.cisco.com/yang-tools-release-docker/yangsuite:latest
latest: Pulling from yang-tools-release-docker/yangsuite
4ccdce43d1e0: Already exists 
c95f13c88d92: Already exists 
82656eee95ad: Already exists 
78ff727be57a: Already exists 
448bb314afa5: Already exists 
15677038ac69: Already exists 
22da8daab8e7: Already exists 
9c3a638e7094: Already exists 
2952d6a1d978: Already exists 
bd8c0fd10ad7: Already exists 
680c72e6e1fc: Already exists 
Digest: sha256:31136ac8bca600e0a2a1696ed6798b277e6e7f05652dc1c1f2fd36415b85e930
Status: Image is up to date for dockerhub.cisco.com/yang-tools-release-docker/yangsuite:latest

xxxxx:~ xxxxx$ docker run -it -p 8480:8480 \
>       --mount type=bind,source=/Users/xxxxx/Documents/Yangsuite_data,target=/home/docker/data \
>       dockerhub.cisco.com/yang-tools-release-docker/yangsuite:latest
2018-12-17 01:26:10,395 - yangsuite.paths: INFO: Creating new 'filename' directory path /home/docker/data/logs/
Operations to perform:
  Apply all migrations: admin, auth, contenttypes, sessions
Running migrations:
  Applying contenttypes.0001_initial... OK
  Applying auth.0001_initial... OK
  Applying admin.0001_initial... OK
  Applying admin.0002_logentry_remove_auto_add... OK
  Applying contenttypes.0002_remove_content_type_name... OK
  Applying auth.0002_alter_permission_name_max_length... OK
  Applying auth.0003_alter_user_email_max_length... OK
  Applying auth.0004_alter_user_username_opts... OK
  Applying auth.0005_alter_user_last_login_null... OK
  Applying auth.0006_require_contenttypes_0002... OK
  Applying auth.0007_alter_validators_add_error_messages... OK
  Applying auth.0008_alter_user_username_max_length... OK
  Applying auth.0009_alter_user_last_name_max_length... OK
  Applying sessions.0001_initial... OK
**********************************************************************
Your input is required to define an admin user
**********************************************************************
Username (leave blank to use 'root'): 
Email address: 
Password: 
Password (again): 
The password is too similar to the email address.
This password is too short. It must contain at least 8 characters.
Password: 
Password (again): 
The password is too similar to the email address.
Password: 
Password (again): 
Superuser created successfully.
**********************************************************************
YANG Suite data is stored at /home/docker/data. Be sure to back up this directory!
**********************************************************************
Performing system checks...

System check identified no issues (0 silenced).
December 17, 2018 - 01:26:58
Django version 2.0.8, using settings 'yangsuite.settings.develop'
Starting development server at http://0.0.0.0:8480/

Check Status

xxx:~ xxx$ docker ps -a
CONTAINER ID        IMAGE                                                            COMMAND             CREATED             STATUS                     PORTS                    NAMES
xxxxxxxxxxxx        dockerhub.cisco.com/yang-tools-release-docker/yangsuite:latest   "yangsuite"         6 minutes ago       Up 3 minutes        0.0.0.0:8480->8480/tcp   frosty_wiles

Open Yangsuit

http://0.0.0.0:8480

or

http://127.0.0.1:8480
0

Enable Raid10 and Install ESXI6.7 on Cisco FlexFlash | C240 M5S

1. Config CIMC (Cisco Integrated Management Controller)

– Connect Display/Mouse to UCS, and FJ45 to CIMC Port

– Power on UCS, then press F8, config IPv4/GW, as follow

完整阅读

0

Inter-domain traffic steering solution with EPE and XTC ODN

Introduction

 

Now more customer complains their Peering network not flexible and hard to control, that will cause peering link’s utilization not balance and waste of resources. As follow the example on Router-2, customer peering device connect to multi ISP, each ISP sends full internet route, select only based on the BGP. BGP select rule only based on the route but not real traffics, that may be cause port-A’s traffics have 8G, but port-B and port-C only have 4G, if want to adjust BGP select, only change RPL that more complex, and due to route from internet and multi ISP, so route maybe change at some time, in order to balance peering link, customer must continue to adjust their RPL.

Could we have more flexible and simplest way to resolve the issue? The answer is Yes 🙂 we can achieve the task by Segment Routing – Egress Peer Engineering. Now some customer had deployed the solution, that combine NetFlow, Openbmp to check AS/traffics of prefix, then send BGP LU(EPE label) to ingress node, and easy to control traffics.

完整阅读

0

Install and deploy Cisco WAE 7.1.1

Introduction

I installed the WAE 6.4.5 at formal and summaried to Blog, e.g: INSTALL CISCO WAE 6.4.5. After 7.0, install/config have big change and similar with NSO that easy/module to deploy. For this article, only talk about how to install and enable.

Auto source profile

Similar with NSO, add “source” command to “.bash_profile” that in MacOS. That will let you direct to login to WAE but not do “source wae711/waerc”, as follow:

[root@frank ~]# echo "source /opt/wae711/waerc" >> .bash_profile
[root@frank ~]# more .bash_profile | grep wae
source /opt/wae711/waerc

完整阅读

0