我正在尝试配置新的 5505,但在打开允许外部流量进入的端口时遇到了困难。我的设置是 Comcast 商务调制解调器(带单个静态 IP)-> ASA(10.0.0.1)->(哑)交换机-> NAS(10.0.0.10)。我正尝试向 NAS 打开端口 5001。我对 IOS 还很陌生,所以我大部分时间都在 ASDM 中工作。不确定我是否让自己过于复杂,但我陷入了困境。
我的运行配置是 -
ASA Version 8.2(5)
!
hostname ciscoasa
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
names
name 10.0.0.10 MiniSrvr description MiniSrvr
!
interface Ethernet0/0
switchport access vlan 2
!
interface Ethernet0/1
!
interface Ethernet0/2
!
interface Ethernet0/3
!
interface Ethernet0/4
!
interface Ethernet0/5
!
interface Ethernet0/6
!
interface Ethernet0/7
!
interface Vlan1
nameif inside
security-level 100
ip address 10.0.0.1 255.255.255.0
!
interface Vlan2
nameif outside
security-level 0
ip address 74.x.x.249 255.255.255.252
!
ftp mode passive
object-group service Syno_HTTPS tcp
port-object eq 5001
object-group service DM_INLINE_TCP_1 tcp
group-object Syno_HTTPS
port-object eq https
access-list outside_access_in extended permit tcp any host MiniSrvr object-group DM_INLINE_TCP_1
pager lines 24
logging asdm informational
mtu outside 1500
mtu inside 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0
static (inside,outside) tcp interface 5001 MiniSrvr 5001 netmask 255.255.255.255
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 74.x.x.250 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
aaa authentication ssh console LOCAL
http server enable
http 10.0.0.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
telnet timeout 5
ssh 10.0.0.0 255.255.255.0 inside
ssh timeout 5
console timeout 0
dhcpd dns 75.75.75.75 75.75.76.76
dhcpd lease 38600
!
dhcpd address 10.0.0.100-10.0.0.199 inside
dhcpd enable inside
!
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
anyconnect-essentials
username xxx password XTTcBNvipbwHw4hk encrypted privilege 15
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum client auto
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
inspect ip-options
!
service-policy global_policy global
prompt hostname context
no call-home reporting anonymous
Cryptochecksum:33ba890463db57b8ad5a2ecbf378b412
: end
答案1
您有一个将端口 5001 映射到 NAS 的 NAT 规则。您缺少端口 5001 的防火墙规则。添加以下内容即可生效:
access-list outside_access_in extended permit tcp any host MiniSrvr object-group Syno_HTTPS
答案2
只是为了向您澄清一点,ASA 不是 IOS,所以这可能会抑制您在这方面的 googlefoo 能力。
关于您的配置,这些是配置中的重要行:
<--snip-->
object-group service Syno_HTTPS tcp
port-object eq 5001
object-group service DM_INLINE_TCP_1 tcp
group-object Syno_HTTPS
port-object eq https
access-list outside_access_in extended permit tcp any host MiniSrvr object-group DM_INLINE_TCP_1
<--snip-->
static (inside,outside) tcp interface 5001 MiniSrvr 5001 netmask 255.255.255.255
access-group outside_access_in in interface outside
<--snip-->
您有正确的 NAT 规则,但您需要将此行添加到您的访问列表中:
access-list outside_access_in extended permit tcp any host MiniSrvr object-group Syno_HTTPS
答案3
在 ASA 8.2 代码中,ACE 上的目标应该是接口地址,而不是内部网络对象(如果这是 8.3 代码,那么您就做对了)。此命令为:
access-list outside_access_in extended permit tcp any interface outside eq 5001
您的 NAT 条目看起来正确,因此这应该可以为您解决问题。