請幫我把https://wiki.lineageos.org/devices/lt03lte/build/ 變成中文的指示，並用MarkDown語法包住指令

 請幫我把https://wiki.lineageos.org/devices/lt03lte/build/ 變成中文的指示，並用MarkDown語法包住指令

如果我建構我的IPSec，我應該避免那些在ISP路由中使用的嗎？

 The Answer: Yes, It's Highly Recommended to Avoid Overlapping IP Ranges

Here's why:

• Routing Conflicts:
  • If your IPsec VPN tunnel uses the same IP address range as your ISP's CGNAT, you'll create routing conflicts.
  • Your computer or network devices won't know whether to send traffic through the VPN tunnel or to the ISP's CGNAT.
  • This will result in unpredictable behavior, connectivity problems, and potential security issues.  
• Packet Confusion:
  • When packets travel through a network, routers rely on IP addresses to determine their destination.  
  • Overlapping IP ranges can lead to confusion and incorrect routing, causing packets to be lost or delivered to the wrong destination.  
• Troubleshooting Nightmares:
  • Diagnosing network problems becomes incredibly difficult when IP ranges overlap.  
  • It's hard to distinguish between issues caused by your VPN and issues caused by the ISP's CGNAT.

How to Avoid Overlapping IP Ranges:

1. Choose Private IP Ranges:
   • Stick to the standard private IP address ranges defined in RFC 1918:
     • 10.0.0.0/8  
     • 172.16.0.0/12  
     • 192.168.0.0/16  
2. Use Unique Subnets:
   • Even within the private IP ranges, use unique subnets for your VPN tunnel.
   • For example, if your home network uses 192.168.1.1/24, use 10.10.10.0/24 or 172.17.0.0/24 for your VPN tunnel.
3. Check ISP Documentation (If Possible):
   • Some ISPs might publish information about the IP address ranges they use for CGNAT.
   • If you can find this information, avoid those ranges.
4. Use less common Private Ranges:
   • If you are extra paranoid, you could use a range inside of the 172.16.0.0/12, that is not commonly used by home routers. For example 172.30.0.0/24.

In essence:

• Avoid any IP address ranges that you see in traceroute results when you're behind CGNAT.
• Using standard private IP ranges and unique subnets will help you avoid routing conflicts and ensure a stable VPN connection.

決定還是把筆撿回來

 抱歉，剛剛筆丟得太遠了。 筆咧?

被grub擺道

 新裝電腦。

從OEM Windows 7 升級到10, 用光碟安裝到BIOS/MBR, 然後裝Budgie。

接下來grub多重開機屢敗屢戰，死的不知怎麼救。

最後想起來。usb碟開機時選uefi模式安裝，所以就出現這樣神奇的問題。

砍掉uefi後,果然重裝就順利完成了。

看來uefi模式是沒法回到傳統BIOS boot。

Raid 0 LVM 創建紀錄

 手動創建LVM給Proxmox使用

fdisk -l
pvcreate /dev/sda1
pvcreate /dev/sdb1
pvscan
pvdisplay
vgscan
vgcreate -s 4M virtgr /dev/sda1 /dev/sdb1
vgscan
lvdisplay
#lvcreate -i2 -I4 -l100%FREE -n virt-p1 virtgr

最後建立部分後來刪掉，改從proxmox datacenter storage 重建

原因是這樣才抓到真實使用率(Usage)

修改ESXi 6.7安裝光碟

自從使用Evernote滿足自己的筆記需求後，就很少回頭擠blog。但是想想不行，偶爾也要寫一點筆記，不然會被當成完全棄坑。

安裝完

Add-EsxSoftwareDepot .\update-from-esxi6.7-6.7_update01.zip
Add-EsxSoftwareDepot .\net55-r8168-8.045a-napi-offline_bundle.zip
New-EsxImageProfile -CloneProfile ESXi-6.7.0-20181002001-standard -Name ESXi-20181112 -Vendor Icekimo
Set-EsxImageProfile -Name ESXi-20181112 -AcceptanceLevel CommunitySpported
Add-EsxSoftwarePackage -ImageProfile ESXi-20181112 -SoftwarePackage net55-r8168
Get-EsxSoftwarePackage
Export-EsxImageProfile -NoSignatureCheck -ImageProfile ESXi-2018111 -FilePath ESXi-6.7.0-Custom.iso –ExportToIso

OpenShot 影片編輯器安裝

支持 Ubuntu 14.04（Trusty）和更新版本的Ubuntu。

sudo add-apt-repository ppa:openshot.developers/ppa
sudo apt-get update
sudo apt-get install openshot-qt