topic Re: FWSM nat problem in Network Security https://community.cisco.com/t5/network-security/fwsm-nat-problem/m-p/1124882#M893904 <HTML><HEAD></HEAD><BODY><P>global (outside) 1 X.Y.177.50-X.Y.177.253 netmask 255.255.255.0</P><P>global (outside) 1 X.Y.177.254 </P><P></P><P>It seems ok, because the first global statement has a public IP range, so till the range is exhasted it will do on-to-one nat and after that the 2nd global statemnt comes into action doing PAT.</P></BODY></HTML> Fri, 07 Nov 2008 10:13:16 GMT dhananjoy chowdhury 2008-11-07T10:13:16Z FWSM nat problem https://community.cisco.com/t5/network-security/fwsm-nat-problem/m-p/1124881#M893903 <P>Hi,</P><P></P><P>I've got problem with user behind a multi-context/transparent FWSM. The FW is doing PAT in the NAT pool. Did anyone ever experience this issue.</P><P></P><P></P><P>firewall transparent</P><P></P><P></P><P>global (outside) 1 X.Y.177.50-X.Y.177.253 netmask 255.255.255.0</P><P></P><P>global (outside) 1 X.Y.177.254</P><P>nat (inside) 1 10.10.240.0 255.255.252.0 dns norandomseq</P><P></P><P>sh xlate</P><P>17 in use, 37 most used</P><P>Global X.Y.177.51 Local 10.10.240.36</P><P>Global X.Y.177.54 Local 10.10.240.59</P><P>Global X.Y.177.58 Local 10.10.240.5</P><P>Global X.Y.177.60 Local 10.10.240.200</P><P>Global X.Y.177.61 Local 10.10.240.32</P><P>Global X.Y.177.63 Local 10.10.240.31</P><P>Global X.Y.177.65 Local 10.10.240.104</P><P>Global X.Y.177.52 Local 10.10.240.37</P><P>Global X.Y.177.86 Local 10.10.241.135</P><P>Global X.Y.177.51 Local 10.10.243.10</P><P>Global X.Y.177.51 Local 10.10.240.49</P><P>Global X.Y.177.52 Local 10.10.241.103</P><P>Global X.Y.177.50 Local 10.10.241.249</P><P>Global X.Y.177.52 Local 10.10.240.33</P><P>Global X.Y.177.52 Local 10.10.241.246</P><P>Global X.Y.177.52 Local 10.10.241.252</P><P>Global X.Y.177.52 Local 10.10.241.245</P><P>Global X.Y.177.52 Local 10.10.241.251</P><P>Global X.Y.177.52 Local 10.10.241.102</P><P>Global X.Y.177.52 Local 10.10.243.12</P><P>Global X.Y.177.52 Local 10.10.241.250</P><P>Global X.Y.177.52 Local 10.10.241.254</P><P>Global X.Y.177.52 Local 10.10.240.70</P><P>Global X.Y.177.53 Local 10.10.243.252</P><P>Global X.Y.177.54 Local 10.10.241.42</P><P>Global X.Y.177.50 Local 10.10.240.10</P><P>Global X.Y.177.56 Local 10.10.240.11</P><P>Global X.Y.177.57 Local 10.10.240.7</P><P>Global X.Y.177.68 Local 10.10.240.2</P><P>Global X.Y.177.70 Local 10.10.240.6</P><P>Global X.Y.177.71 Local 10.10.240.18</P><P>Global X.Y.177.74 Local 10.10.240.102</P><P>Global X.Y.177.59 Local 10.10.240.103</P><P>Global X.Y.177.69 Local 10.10.241.107</P><P></P><P></P><P></P> Mon, 11 Mar 2019 14:09:19 GMT https://community.cisco.com/t5/network-security/fwsm-nat-problem/m-p/1124881#M893903 dominic.caron 2019-03-11T14:09:19Z Re: FWSM nat problem https://community.cisco.com/t5/network-security/fwsm-nat-problem/m-p/1124882#M893904 <HTML><HEAD></HEAD><BODY><P>global (outside) 1 X.Y.177.50-X.Y.177.253 netmask 255.255.255.0</P><P>global (outside) 1 X.Y.177.254 </P><P></P><P>It seems ok, because the first global statement has a public IP range, so till the range is exhasted it will do on-to-one nat and after that the 2nd global statemnt comes into action doing PAT.</P></BODY></HTML> Fri, 07 Nov 2008 10:13:16 GMT https://community.cisco.com/t5/network-security/fwsm-nat-problem/m-p/1124882#M893904 dhananjoy chowdhury 2008-11-07T10:13:16Z