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

ASA 5510 Secondary Public IP Range on outside interface

· 52CE 我爱测

We are in process of upgrading from an ASA5505 to an ASA5510. I have a co-location configured for 3 ranges of public IP addresses on two different subnets. The 5505 is working as expected. Example (modified IPs): 174.136.1.1, 72.…

问题原文

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

We are in process of upgrading from an ASA5505 to an ASA5510. I have a co-location configured for 3 ranges of public IP addresses on two different subnets. The 5505 is working as expected.

Example (modified IPs): 174.136.1.1, 72.249.1.1, 72.249.2.1

The firewall is assigned to 174.136.1.2. When bringing the 5510 online, traffic does not route correctly when NAT rules are created for any IP addresses in this range: 72.249.1.1, 72.249.2.1

  • I confirmed the data packets route correctly when assigning a server to an IP that is on the same subnet as the firewall.
  • When configuring additional VLANs for IP ranges 72.249.1.1 and 72.249.2.1, all packets route correctly. I put a switch between the Firewall and Datacenter router. However we do not have enough IPs to assign to additional VLANS.
  • I tried to create a static route to 72.249.1.1, 72.249.2.1, that didn't work.
  • Packet trace results were a positive but I am not sure if I am doing it correctly.
  • I do see a Dynamic NAT rule on the 5505 vs Dynamic PAT rule on the 5510. I am unclear what the difference is. I think I have tried to toggle that on the 5510 with no luck.
  • I am researching subinterfaces on the 5510 but I'm not sure if that is the solution.

We have a small window to do the firewall upgrade and that is typically late night. I've tried multiple times with no luck. I can't create a test bed environment at the office. I may request another drop from the datacenter for testing purposes. Any help would be appreciated. I can post the full config.

已采纳解答

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

You will need arp permit-nonconnected enabled for the NAT to work properly.

arp permit-nonconnected

To enable the ARP cache to also include non-directly-connected subnets, use the arp permit-nonconnected command in global configuration mode. To disable non-connected subnets, use the no form of this command.

Usage Guidelines

The ASA ARP cache only contains entries from directly-connected subnets by default. When the no arp permit-nonconnected command is there (default behavior), the ASA rejects both incoming ARP requests and ARP responses in case the ARP packet received is in a different subnet than the connected interface.

Note that the first case (default behavior) causes a failure in case PAT is configured on the ASA and the virtual IP address (mapped) for PAT is in a different subnet than the connected interface.

Also, we do not recommend enabling this feature unless you know the security risks. This feature could facilitate denial of service (DoS) attacks against the ASA; a user on any interface could send out many ARP replies and overload the ASA ARP table with false entries.

You may want to use this feature if you use:

  • Secondary subnets.
  • Proxy ARP on adjacent routes for traffic forwarding.

Examples

The following example enables non-connected subnets:

ciscoasa(config)# arp permit non-connected

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

资料来源与适用范围

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

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

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