大网数据广告活动
服务器运维问答

Is it reasonable to use IPv6 Link-local address for local storage network?

· 52CE 我爱测

I am bringing up an NFS server (actually a ZFS pool with any number of data sets exported with NFS) in a co-location rack. I don't need or want any outside systems to have NFS access. Is there any reason not to simply use the IPv…

问题原文

原帖链接 · AlanObject · CC BY-SA 3.0

I am bringing up an NFS server (actually a ZFS pool with any number of data sets exported with NFS) in a co-location rack. I don't need or want any outside systems to have NFS access.

Is there any reason not to simply use the IPv6 link-local address for the server and restrict the NFS server to using only that? It seems that this would help secure the SAN.

已采纳解答

原帖链接 · Sander Steffann · CC BY-SA 3.0

Technically it should be possible. Configuration might be a bit more difficult because on every device you'll need to configure not only the IPv6 address of the server but also which network interface to use for reaching it. Some client software might not provide an option for that. It might also create problems later when you want multiple networks to reach your storage, because link-local addresses are not routable.

I would personally just use global addresses to keep things easy, and use simple firewall rules to block access to the storage network. If you really want private address I would recommend using ULA addresses over link-local for this purpose. Use one of the online ULA generators to get an almost certainly unique block, and use that. That way you can expand the number of networks, build a VPN for management etc if/when you need them.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2017-10-15)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。