211 说说 35 标签
未分类
    Bwoywan August 6th, 2025 at 02:35 am

    Bwoywan August 6th, 2025 at 01:57 am


    应该OK了

    Bwoywan August 6th, 2025 at 01:53 am


    唉

    Bwoywan August 6th, 2025 at 01:44 am

    这个bug好像是我内存不够😭

    Bwoywan August 6th, 2025 at 12:27 am

    更新了主题，时光机的bug还是在……

    Bwoywan August 6th, 2025 at 12:13 am

    升级到typecho-v1.2了

    Bwoywan August 3rd, 2025 at 01:15 am

    呵呵

    Bwoywan August 3rd, 2025 at 12:05 am

    Bwoywan August 2nd, 2025 at 02:02 am


    今天上网站一看，字节跳动的CDN又下线了，整个页面样式全乱了，暂时切回本地源了。
    话说腾讯云轻量新加坡100M网络确实不算好，一到晚上就卡顿

    Bwoywan June 23rd, 2025 at 03:05 pm

    备案的IP不打算续了，CDN域名也关了

    Bwoywan June 4th, 2025 at 03:37 am

    换到腾讯云新加坡了，也是用上锐驰轻量云了

    Bwoywan March 12th, 2025 at 07:24 pm

    Bwoywan February 16th, 2025 at 12:56 am
    1. 登录光猫超级管理员后台：192.168.1.1/cu.html，密码默认为CUAdmin (浙江/内蒙/河北: cuadmin辽宁：lnadmin
      青海：qhuniadmin
      湖南：CUAdmin#HGU
      重庆：cqunicom
      北京：123qweasdzxc
      海南：cu@HNunicom黑龙江：8MCU@HLJ
    2. 基本配置中选择上行线路配置，第一个选项选择ipV4/V6，第三个选项连接名称中选中名为x_INTERNET_R_VID_y(Ps: x和y的值每个人可能不一样)的配置信息，尤其是 VLAN ID 值。
    3. 在ipV4/V6下添加一个新的 Bridge 模式的连接，端口绑定选择LAN1(千兆口)，其他配置与原来的PPPoE模式下相同，尤其是 VLAN ID 值。
      。 删除原来的x_INTERNET_R_VID_y连接，至于x_TR069_R_VID_y连接，据说是留给运营商进行远程控制路由器配置的，删除后超密或其他参数就不会被远程更改。理论上很长一段时间不会有问题。但是也有网友反应，删除后，联通下发了一些配置，你的猫会因为收不到这些下发的新参数，导致某些功能不能使用。不过也没关系，遇到这个情况，联系管片客服，让他们上门或者其他方式，做一下数据即可。
    4. 对 IPTV、VoIP 有需求的同学可以根据参考资料1进行相应设置。
    5. 接下来便可以使用路由器按原来的宽带账号密码拨号上网即可。

    后续

    以上密码已经失效了， [](http://192.168.1.1/backupsettings.conf) 也是404，除了[](http://192.168.1.1/hidden_version_switch.html)中切回默认版本使用默认密码登录外，最为快捷的还是去淘宝闲鱼花几块钱去买密码。应该从2023年初开始时使用随机密码，只有后台能看到，并且会定期更新。

    Bwoywan August 3rd, 2024 at 03:12 pm

    分形工艺R6

    Bwoywan July 21st, 2024 at 04:15 am


    标签机

    Bwoywan July 20th, 2024 at 07:39 pm

    REF

    Here is a link to the official Docker documentation for proxy HTTP: https://docs.docker.com/config/daemon/systemd/#httphttps-proxy

    A quick outline:

    First, create a systemd drop-in directory for the Docker service:

    mkdir /etc/systemd/system/docker.service.d

    Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY and HTTPS_PROXY environment variables:

    [Service]
Environment="HTTP_PROXY=http://proxy.example.com:80/"
Environment="HTTPS_PROXY=http://proxy.example.com:80/"

    If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable:

    Environment="HTTP_PROXY=http://proxy.example.com:80/"
Environment="HTTPS_PROXY=http://proxy.example.com:80/"
Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com"

    Flush changes:

    $ sudo systemctl daemon-reload

    Verify that the configuration has been loaded:

    $ sudo systemctl show --property Environment docker
Environment=HTTP_PROXY=http://proxy.example.com:80/
Environment=HTTPS_PROXY=http://proxy.example.com:80/

    Restart Docker:

    $ sudo systemctl restart docker

    Footnote regarding HTTP_PROXY vs. HTTPS_PROXY: for a long time, setting HTTP_PROXY alone has been good enough. But with version 20.10.8, Docker has moved on to Go 1.16, which changes the semantics of this variable: https://golang.org/doc/go1.16#net/http
    For https:// URLs, the proxy is now determined by the HTTPS_PROXY variable, with no fallback on HTTP_PROXY.

    Bwoywan June 25th, 2024 at 07:41 pm 
    rikka@aml-s812 % udevadm info  -n /dev/bus/usb/001/004                                         ~
P: /devices/platform/soc/c9040000.usb/usb1/1-1
M: 1-1
R: 1
U: usb
T: usb_device
D: c 189:3
N: bus/usb/001/004
L: 0
V: usb
E: DEVPATH=/devices/platform/soc/c9040000.usb/usb1/1-1
E: DEVNAME=/dev/bus/usb/001/004
E: DEVTYPE=usb_device
E: DRIVER=usb
E: PRODUCT=51d/2/1
E: TYPE=0/0/0
E: BUSNUM=001
E: DEVNUM=004
E: MAJOR=189
E: MINOR=3
E: SUBSYSTEM=usb
E: USEC_INITIALIZED=17111111955
E: ID_BUS=usb
E: ID_MODEL=Back-UPS_BK650M2_CH
E: ID_MODEL_ENC=Back-UPS\x20BK650M2_CH
E: ID_MODEL_ID=0002
E: ID_SERIAL=American_Power_Conversion_Back-UPS_BK650M2_CH_912101A11361
E: ID_SERIAL_SHORT=911111111111
E: ID_VENDOR=American_Power_Conversion
E: ID_VENDOR_ENC=American\x20Power\x20Conversion
E: ID_VENDOR_ID=051d
E: ID_REVISION=0001
E: ID_USB_MODEL=Back-UPS_BK650M2_CH
E: ID_USB_MODEL_ENC=Back-UPS\x20BK650M2_CH
E: ID_USB_MODEL_ID=0002
E: ID_USB_SERIAL=American_Power_Conversion_Back-UPS_BK650M2_CH_9B1111111161
E: ID_USB_SERIAL_SHORT=9B1111111161
E: ID_USB_VENDOR=American_Power_Conversion
E: ID_USB_VENDOR_ENC=American\x20Power\x20Conversion
E: ID_USB_VENDOR_ID=051d
E: ID_USB_REVISION=0001
E: ID_USB_INTERFACES=:030000:
E: ID_VENDOR_FROM_DATABASE=American Power Conversion
E: ID_MODEL_FROM_DATABASE=Uninterruptible Power Supply
E: ID_PATH=platform-c9040000.usb-usb-0:1
E: ID_PATH_TAG=platform-c9040000_usb-usb-0_1
E: ID_FOR_SEAT=usb-platform-c9040000_usb-usb-0_1
E: TAGS=:seat:
E: CURRENT_TAGS=:seat:
    Bwoywan June 24th, 2024 at 08:07 am 
    ➜  ~ cat /etc/nut/upsmon.conf 
MONITOR ups@127.0.0.1:6502 1 monuser secret master
MINSUPPLIES 1
SHUTDOWNCMD "/usr/sbin/poweroff"
NOTIFYCMD /usr/sbin/upssched
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 30
DEADTIME 15
POWERDOWNFLAG /etc/killpower
NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC
NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC
NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC
NOTIFYFLAG FSD SYSLOG+WALL+EXEC
NOTIFYFLAG COMMOK SYSLOG+WALL+EXEC
NOTIFYFLAG COMMBAD SYSLOG+WALL+EXEC
NOTIFYFLAG SHUTDOWN SYSLOG+WALL+EXEC
NOTIFYFLAG REPLBATT SYSLOG+WALL+EXEC
NOTIFYFLAG NOPARENT SYSLOG+WALL+EXEC
RBWARNTIME 43200
NOCOMMWARNTIME 300
FINALDELAY 5
    Bwoywan June 24th, 2024 at 08:04 am 
    ➜  ~ cat /etc/nut/upssched.conf
CMDSCRIPT  "/opt/scripts/upssched-cmd.sh"
PIPEFN      /var/run/nut/upssched.pipe
LOCKFN      /var/run/nut/upssched.lock

AT NOCOMM   * EXECUTE NOTIFY-NOCOMM
AT COMMBAD  * START-TIMER NOTIFY-COMMBAD 10
AT COMMOK   * CANCEL-TIMER NOTIFY-COMMBAD COMMOK
AT FSD      * EXECUTE NOTIFY-FSD
AT LOWBATT  * EXECUTE NOTIFY-LOWBATT
AT ONBATT   * EXECUTE NOTIFY-ONBATT
AT ONLINE   * EXECUTE NOTIFY-ONLINE
AT REPLBATT * EXECUTE NOTIFY-REPLBATT
AT SHUTDOWN * EXECUTE NOTIFY-SHUTDOWN
AT ONBATT   * START-TIMER SHUTDOWN 120
AT ONLINE   * CANCEL-TIMER SHUTDOWN
    Bwoywan May 23rd, 2024 at 02:02 am


    一次或多次排查，换了路由系统之后，寝室的跳板机器（挂着外面进局域网唯一的通道两个 Shadowsocks 代理）的代理突然无法访问了，将代理迁到另一台机器上正常，怀疑是跳板机的网络问题，但是上面跑的网页也十分正常，一直没找到原因就这么搁置了很久；
    今晚弄另一个代理的时候顺便排查原因，检查了 Nginx 到容器的端口问题和容器内部网络问题，在容器内部 Curl Baidu 是正常的，就让我十分费解了。
    Shadowsocks 这边能看到 Log 提示请求到了容器内部，但是客户端却响应超时，Log 内容不足，最后想着把 ss-server 的 Log Level 提升到 Debug 模式后发现有 DNS 解析相关的问题，ss-server log 显示第一次尝试解析 v4 失败，再次尝试解析 v6 失败，搜索时发现 Github Issue服务端ipv6环境使用问题 中的配置有一行

    "dns":"2001:67c:2b0::4"

    改配置指定了 SS-server 使用的 DNS，于是指定 DNS 为局域网的网关后就正常了；

    "dns":"192.168.23.1"