wniming 最近的时间轴更新
wniming

wniming

V2EX 第 597700 号会员,加入于 2022-10-17 12:44:33 +08:00
今日活跃度排名 1285
ubuntu 24.04 怎么下载树莓派 5 的内核源码包?
程序员  •  wniming  •  3 天前  •  最后回复来自 wniming
5
payoneer 怎么注册?
问与答  •  wniming  •  12 天前  •  最后回复来自 nocover
2
wniming 最近回复了
@ranaanna 多谢提醒
@Remember 感谢回复,我是参考 ubuntu 官网的文档的下载内核的命令:

https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel

,如果官方文档不正确的话,我应该用下面的哪个包下载内核源码?

root@ubuntu:~# dpkg -l | grep 6.8.0-1010-raspi
ii linux-image-6.8.0-1010-raspi 6.8.0-1010.11 arm64 Linux kernel image for version 6.8.0 on ARMv8 SMP
ii linux-modules-6.8.0-1010-raspi 6.8.0-1010.11 arm64 Linux kernel modules for version 6.8.0 on ARMv8 SMP
root@ubuntu:~#
root@ubuntu:~#
root@ubuntu:~# apt list | grep 6.8.0-1010-raspi

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

linux-buildinfo-6.8.0-1010-raspi/noble-updates,noble-security 6.8.0-1010.11 arm64
linux-headers-6.8.0-1010-raspi/noble-updates,noble-security 6.8.0-1010.11 arm64
linux-image-6.8.0-1010-raspi/noble-updates,noble-security,now 6.8.0-1010.11 arm64 [installed,automatic]
linux-modules-6.8.0-1010-raspi/noble-updates,noble-security,now 6.8.0-1010.11 arm64 [installed,automatic]
linux-tools-6.8.0-1010-raspi/noble-updates,noble-security 6.8.0-1010.11 arm64
root@ubuntu:~#
root@ubuntu:~#
@Vtoecha 注意我说的是 “芯片组出来的那个 x16 的插槽”,这个如果不使用 acs 会和网卡那些分到同一个 iommu 组的,我把我的 iommu 分组情况给你参考一下:


d@server:~$ sudo dmidecode -t 2
# dmidecode 3.5
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: TUF GAMING B550M-PLUS (WI-FI)
Version: Rev X.0x
Serial Number: 210585824000952
Asset Tag: Default string
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Default string
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0

d@server:~$
d@server:~$ iommu
IOMMU Group 0:
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
IOMMU Group 1:
00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
IOMMU Group 2:
00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
IOMMU Group 3:
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
IOMMU Group 4:
00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
IOMMU Group 5:
00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
IOMMU Group 6:
00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
IOMMU Group 7:
00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
IOMMU Group 8:
00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
IOMMU Group 9:
00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
IOMMU Group 10:
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
IOMMU Group 11:
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
IOMMU Group 12:
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61)
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
IOMMU Group 13:
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0 [1022:1440]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1 [1022:1441]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2 [1022:1442]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3 [1022:1443]
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4 [1022:1444]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5 [1022:1445]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6 [1022:1446]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7 [1022:1447]
IOMMU Group 14:
01:00.0 Non-Volatile memory controller [0108]: Sandisk Corp WD Blue SN570 NVMe SSD 2TB [15b7:5025] (rev 01)
IOMMU Group 15:
02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset USB 3.1 XHCI Controller [1022:43ee]
IOMMU Group 16:
02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset SATA Controller [1022:43eb]
IOMMU Group 17:
02:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset Switch Upstream Port [1022:43e9]
IOMMU Group 18:
03:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea]
IOMMU Group 19:
03:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea]
IOMMU Group 20:
03:03.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea]
IOMMU Group 21:
03:08.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea]
IOMMU Group 22:
03:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea]
IOMMU Group 23:
04:00.0 PCI bridge [0604]: Intel Corporation Device [8086:4910]
IOMMU Group 24:
05:01.0 PCI bridge [0604]: Intel Corporation Device [8086:490f]
IOMMU Group 25:
05:04.0 PCI bridge [0604]: Intel Corporation Device [8086:490f]
IOMMU Group 26:
05:05.0 PCI bridge [0604]: Intel Corporation Device [8086:490f]
IOMMU Group 27:
06:00.0 VGA compatible controller [0300]: Intel Corporation DG1 [Iris Xe Graphics] [8086:4908] (rev 01)
IOMMU Group 28:
07:00.0 Audio device [0403]: Intel Corporation Device [8086:490d]
IOMMU Group 29:
08:00.0 Memory controller [0580]: Intel Corporation Device [8086:490e]
IOMMU Group 30:
09:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8161] (rev 15)
IOMMU Group 31:
0b:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
IOMMU Group 32:
0c:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 04)
IOMMU Group 33:
0d:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7)
IOMMU Group 34:
0d:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] [1002:aae0]
IOMMU Group 35:
0e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a]
IOMMU Group 36:
0f:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485]
IOMMU Group 37:
0f:00.1 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP [1022:1486]
IOMMU Group 38:
0f:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c]
IOMMU Group 39:
0f:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487]
d@server:~$
d@server:~$
肯定都是支持的,我是 5700x + b550 重炮手,芯片组出来的那个 x16 的插槽插了张 dg1 显卡,直通给虚拟转码用完全没问题
@yianing 刚才又试了一下用 http 代理,在 rule 里加的这 2 条规则是生效的,看来确实是 tun 模式不支持 SRC-IP-CIDR 这种规则了
@yianing 我试了 #7 楼给出的方法, 在 tun 模式下,在 rule 里添加了

- SRC-IP-CIDR,192.168.1.188/32,🇭l🇰 香港 15
- SRC-IP-CIDR,192.168.1.189/32,🇭 🇰 香港 16

这两条,完全不起作用
@yianing 这个在 tun 模式下也能用吗?我用 clash-verge 开启了 tun 模式后,在 connections 查看 source ip 都是 tun 设备的 ip
@WhatTheBridgeSay 批评的对,我应该多研究一下再问
@docx
@wangritian

如果设备是通过 http 代理直接连接 v2ray 或 clash 的话,这种方法应该是能用的,但我是用 tun2socks 的 wiki 里的方法做了一个旁路由,设备都是通过这台旁路由上网的,刚才用 yacd 看了一下 clash 连接的源 ip 地址发现都是我这台旁路由的 ip 地址,所以在 v2ray 或 clash 里写规则是不会起作用的,我可能得研究一下 ip rule 才能实现我的需求了
@Vintingb 意思是不依赖其他工具,仅仅 v2ray core 或 clash core 就支持是吗?

@cxtrinityy 有什么现成的工具可以比较方便的配置哪个设备的 ip 转发到哪个端口吗?如果要通过敲命令的方式手动维护 iptables 规则感觉就有点麻烦了。
关于   ·   帮助文档   ·   博客   ·   API   ·   FAQ   ·   实用小工具   ·   688 人在线   最高记录 6679   ·     Select Language
创意工作者们的社区
World is powered by solitude
VERSION: 3.9.8.5 · 20ms · UTC 21:05 · PVG 05:05 · LAX 13:05 · JFK 16:05
Developed with CodeLauncher
♥ Do have faith in what you're doing.