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

Allow pfSense to route from WAN to LAN

· 52CE 我爱测

I have a pfSense instance with two network interfaces set up between a LAN and WAN: 192.168.1.0/24 (WAN) <-> (192.168.1.100) pfSense (10.0.1.100) <-> 10.0.1.1/24(LAN) For simplicity, I have allowed all traffic in the filtering ru…

问题原文

原帖链接 · 0x90 · CC BY-SA 3.0

I have a pfSense instance with two network interfaces set up between a LAN and WAN:

192.168.1.0/24 (WAN) <-> (192.168.1.100) pfSense (10.0.1.100) <-> 10.0.1.1/24(LAN)

For simplicity, I have allowed all traffic in the filtering rules.

This works fine and a machine on the LAN with pfSense (10.0.1.100) as the gateway can connect to hosts on the WAN:

<10.0.1.5> $ ping 192.168.1.10
64 bytes from 192.168.1.10: icmp_seq=0 ttl=51 time=11.753 ms

However, a machine on the WAN with pfSense (now 192.168.1.100) as the gateway can not connect to hosts on the LAN:

<192.168.1.10> $ ping 10.0.1.5
*timeout*

The firewall rules allow all traffic in both directions.

tcpdump shows that the packets arrive on the WAN interface correctly but are never sent on the LAN interface.

Is there a function of pfSense that prohibits routing from WAN to LAN? What must be done to allow machines in WAN to route to LAN.

I am aware of the security implications. This is a simplified example.

已采纳解答

原帖链接 · Ron Maupin · CC BY-SA 3.0

NAT is your problem. Unless you are using one-to-one NAT, you are going to need to originate traffic from one side only. Even with one-to-one NAT, you will need to ping from the outside using the translated address.

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

资料来源与适用范围

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

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

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