微波炉自修，兼谈广东效率

2025-08-22 作者： Fisherworks

A boring story – my microwave oven simply broke. It took CNY ￥38 (USD $5.5) and 48 hours to get a recycled part to get this resolved.

5年出头的微波炉挂了，日常除了早餐加热牛奶，使用频次并不高。从这点看，质量只能说一般。

扫个机身码，看下收费标准，联系厂家客服，说次日上门。上门的小哥只能说人不错，至于服务么则流于形式，细节略去不表，总之结论是更换主板费用300+，几乎等于整机价格，无维修价值。

鉴于联系客服之前，我已经拆机简单测了一下保险管（fuse）和供电并未发现明显问题，结合他给的方案“换主板”，我决定去某宝找找备件。

跟着主板上不干胶标签，很顺利就找到了拆机件。下单之前还特意咨询了老板，机器供电ok但就是点不亮（上电完全无反应），老板很认真的回答，大概率主板问题，其他组件坏了至少亮屏且给个故障码之类。

夜里8点出头下单，不到20分钟就已经打包发货。我琢磨这个时间，揽件大概是第二天下午了……结果居然后半夜揽件，第二天下午到长沙，第三天上午到保定，晚上送达，等于48小时不到，东西已经能上机了！好家伙，佛山的回收件也是深圳效率，有点厉害。

完整阅读本篇»

海光KVM虚拟化兼容性实测

2025-03-31 作者： Fisherworks

两台浪潮海光，CS5260H2和CS5280H2，前者装两片海光5380，后者单片海光7390。做完KVM虚拟化后，实测vm兼容性（cpu设为host）情况如下，供参考。

CentOS 7启动完成后随机崩溃，journal说这cpu哥们没支持过。精神续作Rocky Linux 8启动过程中崩溃。Rocky 9可以正常工作，只是journal说这硬件Unmaintained，说白了就是责任自负。Rocky9 stress一直表现正常。
Debian 11和12都没啥，只是journal里说这是hygon就继续工作了，stress表现正常。11上我用incus容器带了wine，进容器后用wine运行一个win x86 cli app也正常。
Ubuntu用的不多，下载一个22.04 qcow2走cloud init启动一下，跟Debian表现基本一致，就不继续stress了。
openEuler 22.03也一切正常，stress表现正常。
Arch没有细测，手头有个2022的qcow2，cloud init起来后pacman能运行，就没有继续，毕竟能拿Arch做生产环境服务的应该不是主流…吧。
Win7启动就蓝屏（报错5D），Win10启动正常，因为日常工作完全不用win，所以没有继续测。

完整阅读本篇»

小镇做题者、disco和teen pop

2025-01-24 作者： Fisherworks

昨日午后慢跑，点开一张「猛士 Vol.01」。典型的80年代合成器音效混在一起，不可谓不嘈杂，而彼时我秒退30年的情绪，因与目之所及的巨大反差，默默调整十多秒才逐渐平静下来。

生于小镇做题者的年代，物质匮乏，照片平均每3年能拍上一张已然很知足，遑论视频。然数十年如白驹过隙，故地重游，无论所到何处，不消说，尽皆物是人非，不复当年贫苦朴实之窘态。

「猛士」、「荷东」，一声前奏想起，动次打次。那台靠小学考试成绩换得的价值不菲的国产单放，插着音质不能说全损但也有限的头戴耳机，再配上玻璃下压着课程表和一些票据的方台，台面再摆放上书籍、笔记、作业和文具…… 恰似《少林足球》里星爷闭幕仰面：“我感觉到，全部都回来了”。

家里那位问我，迪高这么吵，你确定小学生能听这个写作业？

嘿嘿。

完整阅读本篇»

PVE web portal hardening

2025-01-09 作者： Fisherworks

本文：配置fail2ban实现PVE web登录入口的暴破防护。

On a Proxmox VE host accessible to the public internet, using fail2ban to protect SSH away from malicious traffic is fairly common, but what about the web management portal?

I’ve got a blog post talking about that, which seems promising. However it’s already version 8.x, I’m learning something about journald, and so far it’s good to me – I don’t want reinstall the rsyslog just for this, then how can I get it work? Let’s find out.

WHAT HAPPENED

Daily routine, check the system journal with something like journalctl --since='yesterday' .

Jan 09 16:29:23 pve-host IPCC.xs[3863529]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx  user=root
Jan 09 16:29:26 pve-host pvedaemon[3863529]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure
Jan 09 16:31:33 pve-host IPCC.xs[3863529]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx  user=root
Jan 09 16:31:35 pve-host pvedaemon[3863529]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure
Jan 09 16:33:44 pve-host IPCC.xs[3998275]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx  user=root
Jan 09 16:33:45 pve-host pvedaemon[3998275]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure
Jan 09 16:35:54 pve-host IPCC.xs[3863529]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx  user=root
Jan 09 16:35:56 pve-host pvedaemon[3863529]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure
Jan 09 16:38:04 pve-host IPCC.xs[3998275]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx  user=root
Jan 09 16:38:05 pve-host pvedaemon[3998275]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure
Jan 09 16:40:14 pve-host IPCC.xs[3863529]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx  user=root
Jan 09 16:40:16 pve-host pvedaemon[3863529]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure
Jan 09 16:42:25 pve-host IPCC.xs[3863529]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx  user=root
Jan 09 16:42:27 pve-host pvedaemon[3863529]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure
Jan 09 16:44:35 pve-host IPCC.xs[3998275]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx  user=root
Jan 09 16:44:37 pve-host pvedaemon[3998275]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure
Jan 09 16:46:46 pve-host IPCC.xs[3863529]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx  user=root
Jan 09 16:46:48 pve-host pvedaemon[3863529]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure
Jan 09 16:48:56 pve-host IPCC.xs[3998275]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx  user=root
Jan 09 16:48:58 pve-host pvedaemon[3998275]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure

Jan 09 16:29:23 pve-host IPCC.xs[3863529]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx user=root

Jan 09 16:29:26 pve-host pvedaemon[3863529]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure

Jan 09 16:31:33 pve-host IPCC.xs[3863529]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx user=root

Jan 09 16:31:35 pve-host pvedaemon[3863529]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure

Jan 09 16:33:44 pve-host IPCC.xs[3998275]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx user=root

Jan 09 16:33:45 pve-host pvedaemon[3998275]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure

Jan 09 16:35:54 pve-host IPCC.xs[3863529]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx user=root

Jan 09 16:35:56 pve-host pvedaemon[3863529]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure

Jan 09 16:38:04 pve-host IPCC.xs[3998275]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx user=root

Jan 09 16:38:05 pve-host pvedaemon[3998275]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure

Jan 09 16:40:14 pve-host IPCC.xs[3863529]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx user=root

Jan 09 16:40:16 pve-host pvedaemon[3863529]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure

Jan 09 16:42:25 pve-host IPCC.xs[3863529]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx user=root

Jan 09 16:42:27 pve-host pvedaemon[3863529]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure

Jan 09 16:44:35 pve-host IPCC.xs[3998275]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx user=root

Jan 09 16:44:37 pve-host pvedaemon[3998275]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure

Jan 09 16:46:46 pve-host IPCC.xs[3863529]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx user=root

Jan 09 16:46:48 pve-host pvedaemon[3863529]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure

Jan 09 16:48:56 pve-host IPCC.xs[3998275]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:162.19.61.xxx user=root

Jan 09 16:48:58 pve-host pvedaemon[3998275]: authentication failure; rhost=::ffff:162.19.61.xxx user=root@pam msg=Authentication failure

CUSTOMIZED CONF FOR FAIL2BAN

The filter rule of /etc/fail2ban/filter.d/pvedaemon.conf .

[DEFAULT]
_daemon = pvedaemon

[Definition]
failregex = pvedaemon\[.*authentication failure; rhost=<HOST> user=.* msg=.*
ignoreregex =
journalmatch = _SYSTEMD_UNIT=pvedaemon.service + _COMM=pvedaemon

[DEFAULT]

_daemon = pvedaemon

[Definition]

failregex = pvedaemon\[.*authentication failure; rhost=<HOST> user=.* msg=.*

ignoreregex =

journalmatch = _SYSTEMD_UNIT=pvedaemon.service + _COMM=pvedaemon

Then enable the jail in /etc/fail2ban/jail.local .

#... below the sshd conf, add this for pve daemon
[pvedaemon]
enabled = true
port = https,http,8006
filter = pvedaemon
backend = systemd

#... others

#... below the sshd conf, add this for pve daemon

[pvedaemon]

enabled = true

port = https,http,8006

filter = pvedaemon

backend = systemd

#... others

CHECK THE RESULT

Restart the fail2ban service, here it goes.

$ fail2ban-client status pvedaemon
Status for the jail: pvedaemon
|- Filter
|  |- Currently failed:	0
|  |- Total failed:	2
|  `- Journal matches:	_SYSTEMD_UNIT=pvedaemon.service + _COMM=pvedaemon
`- Actions
   |- Currently banned:	1
   |- Total banned:	1
   `- Banned IP list:	162.19.61.xxx

$ fail2ban-client status pvedaemon

Status for the jail: pvedaemon

|- Filter

| |- Currently failed: 0

| |- Total failed: 2

| `- Journal matches: _SYSTEMD_UNIT=pvedaemon.service + _COMM=pvedaemon

`- Actions

|- Currently banned: 1

|- Total banned: 1

`- Banned IP list: 162.19.61.xxx

Then we can also check the iptables -nvL and fail2ban.log for some more detail – try it by yourself, could be interesting.

References: 1 2

完整阅读本篇»

Pi 5b运行Proxmox VE

2024-12-09 作者： Fisherworks

使用Proxmox-Port，成功在Pi 5b上搞起PVE。

其上又装了个Arch、Rocky9和WoA（Windows on Arm），把host和三个vm都塞进一张32G tf卡，加之WoA的一些特定配置，过程是崎岖了一点，但结果还是显而易见的 —— 这一天还是来了，PVE on aarch64。

Arm Linux KVM再带Linux vm是蛮有实际意义的，家里已经用了两年多了（外加incus容器），只不过那块RK3399没搞pve，用的是更传统的libvirt。

pi 5b走kvm虚拟化运行arch和win两台vm

得益于树莓派5b不错的性能，简单操作一下WoA，体验上也不再是行为艺术。至于WoA本身是不是行为艺术，只能说高通的X Elite明显还是拖不动微软的意兴阑珊，不由得让人想起当年Nokia、木马哥和Win Phone的那场爱恨情仇。

完整阅读本篇»

微波炉自修，兼谈广东效率

海光KVM虚拟化兼容性实测

小镇做题者、disco和teen pop

PVE web portal hardening

WHAT HAPPENED

CUSTOMIZED CONF FOR FAIL2BAN

CHECK THE RESULT

Pi 5b运行Proxmox VE

关于Fisherworks

最近文章

功能

本站友链

实时天气

2025年九月
一	二	三	四	五	六	日
« 8月
1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30