Need help Port forwarding on PIX 501

Hey guys,

I just got my pix 501 working, Im no near a PIX guru here, Im just a noobie. We used have a Netgear FS318, btw can I bridge them together?? Now, I want to opens up few port 3389, smtp, www,ftp and pop. I have an MS Exchange 2003 running and one ftp server fyi.

Here's how my network was setup and I included sh config. Can some verify if this line config it correct?

[LAN]------>inside192.168.1.1{pix}outside PPPoE----------->( cloud )

PIX Version 6.3(1) interface ethernet0 auto interface ethernet1 100full nameif ethernet0 outside security0 nameif ethernet1 inside security100 enable password ******************* encrypted passwd **********************encrypted hostname 199pix domain-name katapole fixup protocol ftp 21 fixup protocol h323 h225 1720 fixup protocol h323 ras 1718-1719 fixup protocol http 80 fixup protocol ils 389 fixup protocol rsh 514 fixup protocol rtsp 554 fixup protocol sip 5060 fixup protocol sip udp 5060 fixup protocol skinny 2000 fixup protocol smtp 25 fixup protocol sqlnet 1521 names access-list 100 permit icmp any any echo-reply access-list 100 permit icmp any any time-exceeded access-list 100 permit icmp any any unreachable access-list outbound permit tcp any any eq 3389 access-list outbound permit tcp any any eq smtp pager lines 24 mtu outside 1500 mtu inside 1500 ip address outside pppoe setroute ip address inside 192.168.1.1 255.255.255.0 ip audit info action alarm ip audit attack action alarm pdm location 192.168.1.2 255.255.255.255 inside pdm logging informational 100 pdm history enable arp timeout 14400 global (outside) 1 interface nat (inside) 1 0.0.0.0 0.0.0.0 0 0 static (inside,outside) tcp interface 3389 192.168.1.2 3389 netmask

255.255.255.255 0 0 static (inside,outside) tcp interface smtp 192.168.1.2 smtp netmask 255.255.255.255 0 0 timeout xlate 0:05:00 timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00 timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00 timeout uauth 0:05:00 absolute aaa-server TACACS+ protocol tacacs+ aaa-server RADIUS protocol radius aaa-server LOCAL protocol local aaa authentication telnet console LOCAL http server enable http 192.168.1.0 255.255.255.0 inside no snmp-server location no snmp-server contact snmp-server community public no snmp-server enable traps floodguard enable telnet 192.168.1.0 255.255.255.0 inside telnet timeout 5 ssh timeout 5 console timeout 0 vpdn group pppoe_group request dialout pppoe vpdn group pppoe_group localname USRNAME vpdn group pppoe_group ppp authentication pap vpdn username USRNAME password ********* dhcpd lease 3600 dhcpd ping_timeout 750 dhcpd auto_config outside username admin password 1ZXpWLcm3C.25OQ/ encrypted privilege 15 terminal width 80 Cryptochecksum:93b3f2cf0e1fcf9a5c357d2b3d6404a9
Reply to
kennylee88
Loading thread data ...

access-list outbound permit tcp any host 192.168.1.2 eq smtp is sufficient, also: you have to define an access-group that the access-list applies to:

access-group outbound in interface outside (even though the name is confusing, you shoul call it "inbound" "outside_in" or something

looks good,

M
Reply to
mak

Mak,

What about the port 3389, does that look right to you?

I should change to this: access-list outbound permit tcp any host 192.168.1.2 eq smtp

thanks ken

mak wrote:

or something

Reply to
kennylee88

No, that's wrong.

access-list outbound permit tcp any interface outside eq smtp access-list outbound permit tcp any interface outside eq 3389

In the case of the original poster who only has a single outside IP (the one assigned to the PIX), there is only very marginal extra security in specifying 'interface outside' instead of 'any' (i.e., better security in the theoretical chance that the PPPoE connection would eventually be converted to a non-PPPoE connection and multiple public IPs assigned.)

Yes, the access-group is a necessity.

Reply to
Walter Roberson

Queue my usual advice to upgrade to 6.3(5)112 as soon as practical. The upgrade is free and available to any original owner of a PIX running 6.3 . [If you got the device used and did not pay the 'relicensing' fee, then you could try asking the person you got it from for the update; if you aren't the registered owner then Cisco probably won't release the software to you.]

Reply to
Walter Roberson

Thanks for the rpely guys. Anyone have PPPoE setup here? I know the static IP is tabid easier to config than the dymanic IP.

Walter Robers> >

Reply to
kennylee88

I've done it. The examples in the configuration guide should work for you.

Reply to
Walter Roberson

Yeah that example you see here that came out from my pix 501. I got everything to work(surfing the internet part anyway).

Now I need to do some port forwarding. How do you config FTP port 21? Same way like I entered for port 3389?

thanks all.

Walter Robers> > >Thanks for the rpely guys.

Reply to
kennylee88

Yes. In particular, do NOT configure for port 20 (FTP's control port), only permit port 21 and only static port 21; but DO configure fixup ftp 21 (which is on by default) and the PIX will take care of all the other details of port 20 and negotiated PORT commands

Reply to
Walter Roberson

without protocol FIXUP ftp always create issues

Walter Robers> >

Reply to
ahmad.lists

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.