Port Forwarding a Range in UC540 NAT

Hi all,
I am trying to forward a range of ports (55736-55863 for Synology Surveillance Station) from the WAN interface to an internal IP on a Cisco UC540. I'm not great with the CLI so I generally stick to CCA but right now I'm not even sure it's possible with the CLI.
I've found this tutorial online: http://evilrouters.net/2010/05/25/port-forwarding-a-range-of-ports-on-cisco-ios/
The first step in the tutorial is to setup a NAT IP Pool (which I *can* do in CCA) but unfortunately, the tutorial tells me to use the IP address of the internal device I want to foward the range of ports to but CCA (and its documentation) tells that the IP address must be on the same subnet as the WAN IP address?
I tried following the tutorial anyway by telnetting in to the UC540 and entering the following via the CLI:
UC540 config t
UC540 ip nat pool PORTFWD 192.168.12.121 192.168.12.121 netmask 255.255.255.0 type rotary
UC540 access-list 121 permit udp any any range 55736 55863
UC540 ip nat inside destination list 121 pool PORTFWD
I can now see the 121 access list in CCA, although it has no Interface or Direction assigned to it?
Does anyone know if this is possible? I really don't fancy setting up 127 entries in the NAT table!
Thanks in advance everyone!

The range isn't going to work in CCA. As you are probably aware, CCA has limits to what it can do, even if something can be done in the CLI.
That being said, I think this is a better write up on how to do this:
http://ping8888.com/2014/01/21/cisco-ios-port-forwarding-pat/

Similar Messages

Port forwarding, NAT, QoS..

I have a LinkSys E3000, but I'm having mad problems with QoS & port forwarding. I've tried the following:
Port range forwarding, from port 53 to 3074, to the IP of my xbox. My understanding is that it opens all ports in that range. Moderate NAT.
Single port forwarding, 53, 80, 88, 3074 (all both UPD & TCP - and the ports it says to open on portfoward.com), to the IP of my xbox. Moderate NAT.
DMZ, putting the IP of my Xbox in the DMZ. Moderate NAT.
DMZ, putting the MAC address of my Xbox in the DMZ. Moderate NAT.
I've no idea why none of the above work? I've also set the QoS to give my Xbox high priority (it is another option under Gaming & Applications alongside Port range forwarding, port forwarding, DMZ), so I doubt that is working either.
The only thing that gives me open NAT is if i have uPnP enabled (none of the above have any effect at all), but the connection is very dodgy. Voice chat is choppy, bit of lag in game, even when I'm the only one using an 8Mb connection (it was fine on a basic netgear router before, when no one else was on, but now I can't even get that far). I believe it should work without uPnP and with the above options I've set.
Even if the lag is sorted, it doesn't even begin to solve the QoS problem that I bought the router to fix.

Who is your internet service provider is that cable or DSL connection
Please let me know so that Acoordingly we can decide whether we should go for port range triggering or port range forwarding

Port forwarded - but 'Transmission' shows it's still closed!

I'm having real issues with this one, so I thought it was time to turn to those who usually know. I have a Linksys Router connected to a Safecom Modem. I have chosen a range of ports in the router and enabled them to be forwarded. I've also made sure UPnP is enabled too. As far as the modem is concerned, all I seem to be able to do is to ensure NAT is enabled with the mode Dynamic NAPT selected also. I've gone into System Preferences/Sharing/Firewall created a new port name and opened the same range of port numbers thus letting through all TCP and UDP traffic on my chosen ports (also tried it with the Firewall off). Yet still the port remains closed and Transmission remains unable to automatically map. Any guidence would be really appreciated.
This is what it shows in Transmission's message log (if anyone can decipher it):
4/20 09:02:56 INF stopping nat-pmp
4/20 09:02:56 INF stopping upnp
4/20 09:02:58 INF starting nat-pmp
4/20 09:02:58 DBG nat-pmp create multicast socket 10
4/20 09:02:58 INF starting upnp
4/20 09:02:58 DBG sending upnp ssdp discover message
4/20 09:03:01 DBG sending upnp ssdp discover message
4/20 09:03:09 DBG sending upnp ssdp discover message
4/20 09:03:24 DBG sending upnp ssdp discover message

Hi Simon,
It could be under LAN configuration or maybe NAT. But the one that looks really interesting is Virtual Server. That sounds like something which might be port forwarding.
You see, a NAT routing device has two interfaces, one for the WAN and one for the LAN. The WAN interface might have an IP address like 71.146.152.150 and the LAN interface might have an address of 192.168.1.1. When packets come to the LAN interface from an address like 192.168.1.2, the NAT subsitutes 71.146.152.150 for the return address and sends them out the WAN interface. When replies come, the NAT puts the original address back in the source address and sends it out the LAN interface.
But let's say you want to ftp to 192.168.1.2 from the outside world. All you can connect to is 71.146.152.150. Not very likely that your modem has an ftp server, or that you would want it. The only possibility is to forward packets with port 21 to 192.168.1.2. So this process could possibly be called "virtual serving". So I think you should check out Virtual Server and see if it isn't really port forwarding with a fancy name.
-Phil

Port Forwarding with Port Translation RV042, RV016, RV082

This is a feature request for the Linksys RV series Routers. Currently, it appears that the Cisco/Linksys RV042, RV082, and RV016 only support port forwarding and 1-to-1 Nat. One item that I find very helpful with customers is port forwarding with port translation. I am requesting that this feature be included with a future firmware relase for these RV series routers.
Here is an example of the request.
Take an incoming service request on a TCP or UDP destination port and forward it to an internal IP on a different TCP or UDP port. For example, customer A wants to allow different machines on the internal network to receive Windows RDP connections inbound. To make PC maintenance identical between the internal machines, the customer does not want to change the listening port for RDP on the individual PC workstations through the Windows Registry. The customer also does not want to dedicate separate IP's to each machine in a 1-to-1 NAT setup. The only option is to have remote connections to each of these PC's to use a different destination port. So, for example, PC one could be reached on TCP port 5151, PC two on TCP port 5152, and PC three on port 5153. This requres a firewall that is able to translate each of these connection requests to a different internal IP on the default RDP port (TCP 3389). So, the following setup is required:
Port Forwarding with Port Translation:
Router External IP on TCP port 5151 ---> forwarded to PC One's internal IP on TCP 3389
Router External IP on TCP port 5152 ---> forwarded to PC Two's internal IP on TCP 3389
Router External IP on TCP port 5153 ---> forwarded to PC Three's internal IP on TCP 3389
There are several comparable "small business" class router competitors to the RV042, RV082, and RV016 that will perform this port forwarding with port translation process without incident. Unfortunately, these Cisco/Linksys small business routers will not accomplish this task currently.
Please implement this feature in a future firmware release.
Thanks!

Excellent. I see this now. None of our customers actually use the UPNP feature, so we never realized that Port Forwarding with Port Translation features existed on this page along with the ability to enable or disable UPNP.
Perhaps, in the future, this functionality could be moved to and incorporated into the port forwarding page which seems to be a more logical location.
In either case I'm very happy to know that this feature is available on the RV's.
Thanks for your assistance.

Port Forwarding & Access List Problems

Good morning all,
I am trying to set up port forwarding for a Webserver we have hosted here on ip: 192.168.0.250 - I have set up access lists, and port forwarding configurations and I can not seem to access the server from outside the network. . I've included my config file below, any help would be greatly appreciated! I've researched a lot lately but I'm still learning. Side note: I've replaced the external ip address with 1.1.1.1.
I've added the bold lines in the config file below in hopes to forward port 80 to 192.168.0.250 to no avail. You may notice I dont have access-list 102 that i created on any interfaces. This is because whenever I add it to FastEthernet0/0, our internal network loses connection to the internet.
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname pantera-office
boot-start-marker
boot-end-marker
no logging buffered
enable secret 5 $1$JP.D$6Oky5ZhtpOAbNT7fLyosy/
aaa new-model
aaa authentication login default local
aaa session-id common
dot11 syslog
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.0.1 192.168.0.150
ip dhcp excluded-address 192.168.0.251 192.168.0.254
ip dhcp pool private
import all
network 192.168.0.0 255.255.255.0
dns-server 8.8.8.8 8.8.4.4
default-router 192.168.0.1
ip auth-proxy max-nodata-conns 3
ip admission max-nodata-conns 3
ip domain name network.local
multilink bundle-name authenticated
crypto pki trustpoint TP-self-signed-4211276024
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-4211276024
revocation-check none
rsakeypair TP-self-signed-4211276024
crypto pki certificate chain TP-self-signed-4211276024
certificate self-signed 01
3082025A 308201C3 A0030201 02020101 300D0609 2A864886 F70D0101 04050030
31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 34323131 32373630 3234301E 170D3132 30383232 32303535
31385A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649
4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D34 32313132
37363032 3430819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281
8100B381 8073BAC2 C322B5F5 F9595F43 E0BE1A27 FED75A75 68DFC6DD 4C062626
31BFC71F 2C2EF48C BEC8991F 2FEEA980 EA5BC766 FEBEA679 58F15020 C5D04881
1D6DFA74 B49E233A 8D702553 1F748DB5 38FDA3E6 2A5DDB36 0D069EF7 528FEAA4
93C5FA11 FBBF9EA8 485DBF88 0E49DF51 F5F9ED11 9CF90FD4 4A4E572C D6BE8A96
D61B0203 010001A3 8181307F 300F0603 551D1301 01FF0405 30030101 FF302C06
03551D11 04253023 82217061 6E746572 612D6F66 66696365 2E70616E 74657261
746F6F6C 732E6C6F 63616C30 1F060355 1D230418 30168014 31F245F1 7E3CECEF
41FC9A27 62BD24CE F01819CD 301D0603 551D0E04 16041431 F245F17E 3CECEF41
FC9A2762 BD24CEF0 1819CD30 0D06092A 864886F7 0D010104 05000381 8100604D
14B9B30B D2CE4AC1 4E09C4B5 E58C9751 11119867 C30C7FDF 7A02BDE0 79EB7944
82D93E04 3D674AF7 E27D3B24 D081E689 87AD255F B6431F94 36B0D61D C6F37703
E2D0BE60 3117C0EC 71BB919A 2CF77604 F7DCD499 EA3D6DD5 AB3019CA C1521F79
D77A2692 DCD84674 202DFC97 D765ECC4 4D0FA1B7 0A00475B FD1B7288 12E8
quit
username pantera privilege 15 password 0 XXXX
username aneuron privilege 15 password 0 XXXX
archive
log config
hidekeys
crypto isakmp policy 1
encr 3des
authentication pre-share
group 2
crypto isakmp key xxxx address 2.2.2.2
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto map SDM_CMAP_1 1 ipsec-isakmp
description Tunnel to 2.2.2.2
set peer 2.2.2.2
set transform-set ESP-3DES-SHA
match address 100
interface FastEthernet0/0
description $ETH-WAN$
ip address 2.2.2.2 255.255.255.0
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
crypto map SDM_CMAP_1
interface FastEthernet0/1
description $ETH-LAN$
ip address 192.168.0.1 255.255.255.0
ip nat inside
ip virtual-reassembly
duplex auto
speed auto
interface Serial0/0/0
no ip address
shutdown
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 1.1.1.1
no ip http server
ip http authentication local
no ip http secure-server
ip nat inside source route-map SDM_RMAP_1 interface FastEthernet0/0 overload
ip nat inside source static tcp 192.168.0.254 20 1.1.1.1 20 extendable
ip nat inside source static tcp 192.168.0.254 21 1.1.1.1 21 extendable
ip nat inside source static tcp 192.168.0.252 22 1.1.1.1 22 extendable
ip nat inside source static tcp 192.168.0.252 25 1.1.1.1 25 extendable
ip nat inside source static tcp 192.168.0.250 80 1.1.1.1 80 extendable
ip nat inside source static tcp 192.168.0.252 110 1.1.1.1 110 extendable
ip nat inside source static tcp 192.168.0.250 443 1.1.1.1 443 extendable
ip nat inside source static tcp 192.168.0.252 587 1.1.1.1 587 extendable
ip nat inside source static tcp 192.168.0.252 995 1.1.1.1 995 extendable
ip nat inside source static tcp 192.168.0.252 8080 1.1.1.1 8080 extendable
ip nat inside source static tcp 192.168.0.249 8096 1.1.1.1 8096 extendable
access-list 1 remark CCP_ACL Category=2
access-list 1 permit 192.168.0.0 0.0.0.255
access-list 100 remark CCP_ACL Category=4
access-list 100 remark IPSec Rule
access-list 100 permit ip 192.168.0.0 0.0.0.255 10.0.100.0 0.0.0.255
access-list 101 remark CCP_ACL Category=2
access-list 101 remark IPSec Rule
access-list 101 deny ip 192.168.0.0 0.0.0.255 10.0.100.0 0.0.0.255
access-list 101 permit ip 192.168.0.0 0.0.0.255 any
access-list 102 remark Web Server ACL
access-list 102 permit tcp any any
snmp-server community public RO
snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
snmp-server enable traps vrrp
snmp-server enable traps ds1
snmp-server enable traps tty
snmp-server enable traps eigrp
snmp-server enable traps envmon
snmp-server enable traps flash insertion removal
snmp-server enable traps icsudsu
snmp-server enable traps isdn call-information
snmp-server enable traps isdn layer2
snmp-server enable traps isdn chan-not-avail
snmp-server enable traps isdn ietf
snmp-server enable traps ds0-busyout
snmp-server enable traps ds1-loopback
snmp-server enable traps ethernet cfm cc mep-up mep-down cross-connect loop config
snmp-server enable traps ethernet cfm crosscheck mep-missing mep-unknown service-up
snmp-server enable traps disassociate
snmp-server enable traps deauthenticate
snmp-server enable traps authenticate-fail
snmp-server enable traps dot11-qos
snmp-server enable traps switch-over
snmp-server enable traps rogue-ap
snmp-server enable traps wlan-wep
snmp-server enable traps bgp
snmp-server enable traps cnpd
snmp-server enable traps config-copy
snmp-server enable traps config
snmp-server enable traps entity
snmp-server enable traps resource-policy
snmp-server enable traps event-manager
snmp-server enable traps frame-relay multilink bundle-mismatch
snmp-server enable traps frame-relay
snmp-server enable traps frame-relay subif
snmp-server enable traps hsrp
snmp-server enable traps ipmulticast
snmp-server enable traps msdp
snmp-server enable traps mvpn
snmp-server enable traps ospf state-change
snmp-server enable traps ospf errors
snmp-server enable traps ospf retransmit
snmp-server enable traps ospf lsa
snmp-server enable traps ospf cisco-specific state-change nssa-trans-change
snmp-server enable traps ospf cisco-specific state-change shamlink interface-old
snmp-server enable traps ospf cisco-specific state-change shamlink neighbor
snmp-server enable traps ospf cisco-specific errors
snmp-server enable traps ospf cisco-specific retransmit
snmp-server enable traps ospf cisco-specific lsa
snmp-server enable traps pim neighbor-change rp-mapping-change invalid-pim-message
snmp-server enable traps pppoe
snmp-server enable traps cpu threshold
snmp-server enable traps rsvp
snmp-server enable traps syslog
snmp-server enable traps l2tun session
snmp-server enable traps l2tun pseudowire status
snmp-server enable traps vtp
snmp-server enable traps aaa_server
snmp-server enable traps atm subif
snmp-server enable traps firewall serverstatus
snmp-server enable traps isakmp policy add
snmp-server enable traps isakmp policy delete
snmp-server enable traps isakmp tunnel start
snmp-server enable traps isakmp tunnel stop
snmp-server enable traps ipsec cryptomap add
snmp-server enable traps ipsec cryptomap delete
snmp-server enable traps ipsec cryptomap attach
snmp-server enable traps ipsec cryptomap detach
snmp-server enable traps ipsec tunnel start
snmp-server enable traps ipsec tunnel stop
snmp-server enable traps ipsec too-many-sas
snmp-server enable traps ipsla
snmp-server enable traps rf
route-map SDM_RMAP_1 permit 1
match ip address 101
control-plane
line con 0
logging synchronous
line aux 0
line vty 0 4
scheduler allocate 20000 1000
end
Any/All help is greatly appreciated! I'm sorry if I sound like a newby!
-Evan

Hello,
According to the config you posted 2.2.2.2 is your wan ip address and 1.1.1.1 is the next hop address for your wan connection. The ip nat configuration for port forwarding should look like
Ip nat inside source static tcp 192.168.0.250 80 2.2.2.2 80
If your provider assigns you a dynamic ipv4 address to the wan interface you can use
Ip nat inside source static tcp 192.168.0.250 80 interface fastethernet0/0 80
Verify the settings with show ip nat translation.
Your access list 102 permits only tcp traffic. If you apply the acl to an interface dns won't work anymore (and all other udp traffic). You might want to use a statefull firewall solution like cbac or zbf combined with an inbound acl on the wan interface.
Best Regards
Lukasz

Is WRT54G v5 'Port Range Forward' mean the same as NAT ?

Dear all:
As title said.
Do I missunderstand anything?
I would like to sent magic packet pass through WRt54G, thus I would like to set port forward.
Could anyone help ?
I thank you in advance.
Best Regards
chen min

NAT represent network address translation as well.
I think WRT54G supports WOL except WOW directly.
I try to sent magic packet pass through WRT54G. And according of log information, It did passed through WRT54 on the port which I assigned.
I think it would be possible if boardcasting IP was allowed in Port Range Forward.
I kept looking for more information from forum.
Best Regards
chen min

Forwarding a range of ports in 8.4

I have an ASA 5505 running 8.4(1), and I'm configuring it with ASDM 6.4(1). The outside interface is configured with a single static address. I have a few services port forwarded sucessfully to three different servers on the inside network.
I need to make a media proxy on a SIP server available to the outside. It requires a large range of forwarded UDP ports for the media channels.
I tried adding a network object NAT rule like the others I'm already using to forward HTTP and RDP. I entered a range of ports for the real port and the mapped port using the syntax 60000-60999. ASDM accepted it, but the NAT rule list displays "Any" in the service column. When I apply the change, I get the following error:
nat (inside,outside) static interface service tcp 60000-60999 60000-60999
^
ERROR: % Invalid input detected at '^' marker.
How do I forward a large range of UDP ports from the outside interface to a single server on my inside network? I'd like to use ASDM, but I can switch to the CLI if that works better.
Thanks,
Alan

Hi Alan,
After version 8.3 the Nat is more flexible.
You can configure an object service and apply this to the Nat.
On this way you configure just one line for the Nat.
Also remember to open the ports on the ACL that you have applied to the outside interface.
For example:
You have an internal server"10.10.10.10"
object service UDP-PORTS
service udp source range 60000 60999
exit
object network obj-10.10.10.10
host 10.10.10.10
exit
nat (inside,outside) source static obj-10.10.10.10 interface service UDP-PORTS UDP-PORTS
Please rate helpful posts.
Regards,
Harvey

How to setup a UDP port forward range

Hi,
We are trying to figure out how to setup UDP port forward range. This is the configuration that we are using.
ip nat pool voip-rtp 10.10.10.3 10.10.10.3 netmask 255.255.255.0 type rotary
ip nat inside destination list 114 pool voip-rtp
access-list 114 permit udp any any range 16384 32767
Where 10.10.10.3 is the host I want to forward the ports 16384 to 32767 to.
This is not working. We use a similar set of commands for TCP range forwarding which work perfecting. Can anyone advise of the correct way to port forward a UDP range.
Damien

thanks for the suggestion.
I tried the same , but still the udp port 514 is not available. when i run nmap tool to scan the ports, the udp port 514 is not available to the external world and hence the syslog msgs i send to tat port is not being received. kindly help me out.
thanks again!!

NAT port forwarding

I have recently purchased a Cisco 871 router. In the GUI from the installed software, I have been able to configure which ports are forwarded to a specified IP address within my local area network.
This seems to output a configuration line like this:
ip nat inside source static tcp 192.168.1.123 1000 interface Dialer0 1000
However, I can only do this one port at a time. Is there a function or command that I can use to specify a range of ports? For example, I would like to forward tcp ports 1000-2300 to the IP address 192.168.1.123.
Any help would be appreciated.
(p.s: I think I posted in the wrong Topic previously)

Hi
I own a 2621xm which I have used for port forwarding with NAT overload. from what I can see your options are to forward a port onto the address of your NATed interface with the command:
ip nat inside source static (tcp/udp) your.inside.ip.address portnumber your.interface.ip.address externalportnumber
eg
ip nat inside source static tcp 192.168.1.43 22 194.41.66.2 8022
would allow me to reach 192.168.1.43 port 22 from outside using 8022 or whatever port you specify in the command.
alternatively you could change the interface address to one in the same network so that it is seen as a different devicewith a different ip that only has the forwarded port open.
the final way would be to forward the entire inside address to a new external ip address for example if you have a 192.168.0.0 /24 NATed to 194.41.66.0 /24 through an interface with an ip of 194.41.66.2 you could run the folowing command:
ip nat inside source static 192.168.1.43 194.41.66.43
allowing you to communicate with that host as if there was no NAT. from here you can use the access-list feature to close ports that you don't need.
Hope this helps!
Barry

WRT320N. Port forwarding help. Xbox and ps3 playing at same time. NAT issues

Hi
I'm trying to have both my xbox and ps3 play with open NAT's for online gaming. I have had success utilizing info from 'portforward.com'. But the solutions will unlock OPEN NAT for either the ps3 or the xbox .. one at a time. Is there a way to get both to be open?
It seems like one main conflict is the success depends on both utilizing port 3074. But I can't have both use it? ( obviously).
I tried port forwarding the xbox per specs off of this forum and that works great.. And DMZ ing the PS3. But like i said before. Most solutions
leave one console with OPEN and one with Moderate.
Is there a solution that allows both NAT OPEN's on both consoles?

First of all XBOX works on a different port number and PS3 works on a different port numbers. Follow the steps below to open the ports on your router for XBOX and PS3.
Open an Internet Explorer browser page on your wired computer(desktop).In the address bar type - 192.168.1.1 and press Enter...Leave Username blank & in Password use admin in lower case...
This settings are for your XBOX.
On the set-up tab change the MTU Size to 1365 and click Save Settings...
Click on "Administration" tab and disable the option UPnP and click Save Settings...
Click on "Applications and Gaming" tab and then click on "Port Range Forwarding" subtab...
1) On the first line in Application box type in ABC, in the start box type in 53 and End box type in 3074, leave the protocol as both and under ip address type in 192.168.1.20 and check the enable box, click Save Settings once done...
2) Once you return to the set up page click on the Security tab and uncheck Block Anonymous Internet Requests and click on Save Settings...
3)Click on the Status tab and take note of DNS1 and DNS2 Addresses...
4) Goto the XBox Network Settings and IP Address Settings and select manual IP Settings and assign the following on your Xbox IP Address :- 192.168.1.20, Subnet Mask :- 255.255.255.0, Default Gateway :- 192.168.1.1...
5) Also assign the DNS Addresses on the Xbox Use DNS1 and DNS2 Addresses you took note off of the router status tab as Primary DNS & Secondary DNS for the xbox...
6) Turn off your modem, router, and Xbox...Wait for a minute...
7) Plug the modem power first, wait for another minute and plug the router power cable, wait another minute and turn on the Xbox and test it...it will connect...
For PS3 Follow the steps below
Click on "Administration" tab and disable the option UPnP and click Save Settings...
Once you return to the set up page click on the Security tab and uncheck Block Anonymous Internet Requests and click on Save Settings...
Click on "Applications and Gaming" tab and then click on "Port Range Forwarding" subtab...
1) On the first line in Application box type in ABC, in the start box type in 80 and End box type in 80, leave the protocol as both and under ip address type in 192.168.1.20 and check the enable box...
2) On the second line in Application box type in DEF, in the start box type in 443 and End box type in 443, leave the protocol as both and under ip address type in 192.168.1.20 and check the enable box...
3) On the third line in Application box type in GHI, in the start box type in 5223 and End box type in 5223, leave the protocol as both and under ip address type in 192.168.1.20 and check the enable box...
4) On the fourth line in Application box type in JKL, in the start box type in 3478 and End box type in 3479, leave the protocol as both and under ip address type in 192.168.1.20 and check the enable box...
5) On the fifth line in Application box type in MNO, in the start box type in 3658 and End box type in 3658, leave the protocol as both and under ip address type in 192.168.1.20 and check the enable box...
6) On the sixth line in Application box type in PQR, in the start box type in 10070 and End box type in 10080, leave the protocol as both and under ip address type in 192.168.1.20 and check the enable box and click on Save Settings
7) Now assign the given ip address on your PlayStation ip address :- 192.168.1.20, subnet mask :- 255.255.255.0, default gateway :- 192.168.1.1...
8) Also assign the dns addresses on the PlayStation Primary dns :- 4.2.2.2...Secondary dns :- 192.168.1.1
9) Turn off your modem, router, and PlayStation...Wait for a minute...
10) Plug the modem power first, wait for another minute and plug the router power cable, wait another minute and turn on the PlayStation and test it...

Wrt160nv2 xbox strict NAT port forwarding/port triggering

I am having trouble stabalizing my NAT on 2 Xboxes. They are both connected to the wrt160nv2 with ethernet cables and I don't know whether I need to do port forwarding or port triggering. Right now, I am using port range triggering, triggered range 53 to 3074 and forwarded range 53 to 3074, and under Setup, MTU size is 1452. I got that off of another post on here but I think they were trying to set it up for an ethernet cable and wireless. I just need to know what to do since both Xboxes are using ethernet cables so both Xboxes can have open NATs.

No need to forward/trigger any ports on the router . Sometimes 2 gaming consoles do not work on a router.
You can try to upgrade the firmware on the router , reset it and reconfigure .

Router won't save settings of Single Port Forward or Port Range Forwarding

Hi everyone, I'm having a bit of trouble tonight trying to get my Playstation 3 to play games online and in doing so I'm attempting to enable Single Port Forwarding and or Port Range Forwarding.
To start, I am using this link below this paragraph as a guide.
http://portforward.com/english/routers/port_forwarding/Cisco/Linksys-E1000/PS3_Endless_Saga.htm
Each time I go and set the settings and click save, it tells me the settings have been saved successfully then when I click continue onto the next page it shows they actually haven't saved at all. My router is out of it's 90 day phone support with Linksys and I refuse to pay anything extra for support so I'm hoping someone else will be able to help me with my issue since they refuse to unless I pay them.

Hello. Sucks you ran into trouble just after PSN got back online
Try clearing your cache / cookies then re-do the settings. Also, try using a different Internet browser.

Question about port forwarding 2 xbox 360s to get rid of NAT on one of them

I have a xbox 360 with the official xbox 360 wireless antenna that is already set up for port forwarding and my NAT is fine. My brother has a xbox 360 and he has a NAT problem but he doesn't have a official xbox 360 wireless antenna, he hooked up his laptop to his xbox 360 via ethernet cable and is using his laptops wireless card for the connection and he gets a NAT error when he tests his connection to xbox live. Is it possible to port forward 2 xbox's? I'm sure I have to set up some type of static IP for him but the thing is that I'm not sure what IP address to assign to him. If it is possible, would he have to use a static IP address on his laptop since he's using that for a wireless connection? If this is at all possible could someone post some step-by-step instructions on how I should set this up? Below I will give you what I have set up for my xbox 360 to open up my NAT I just want to know what static IP I can use for him. Can I use just any numbers?
In my port forwarding tab in my wireless modem I have the following:
and in my xbox i have the following settings:
IP address: 192.168.1.20
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
Primary DNS: 4.2.2.2
Secondary DNS: 192.168.1.1
I have all that entered for myself and my xbox NAT is open. I just need to set up his xbox if it is at all possible. Please help!!!
P.S. My router is a WRT54GS v2.0 with updated firmware, just incase you need that info.
Message Edited by nourotherleft on 01-08-2009 03:20 PM

ok that still didn't help me.... he still has a NAT problem.... I don't....I went to port triggering and added the ports that you described but it didn't open his NAT... If the connection is going through his laptop(acting like the xbox 360's wireless antenna) wouldn't either his laptop or his xbox need a static ip? because I had to set up my xbox manually with the following addresses:
ip: 192.168.1.20
subnet mask: 255.255.255.0
default gateway: 192.168.1.1
primary dns: 4.2.2.2
secondary dns: 192.168.1.1
so in essence wouldn't his laptop need to be configured with some kind of static ip or something? because if he puts in what I just stated into his xbox it wont connect at all because I guess the ip's are conflicting....so what do I do now?

NAT Port Forwarding Issues

I am running a Mac Mini Server with 10.6.4 and have just the Firewall and NAT services running on this computer at this time.
I have two ethernet connections on this computer. One is the built in adapter (en0) and the other is the Apple USB 100mbit adapter (en2). The en2 adapter is plugged into the internet gateway from my ISP with a static addresss (something like 333.333.333.1) and the en0 adapter is connected to my switch with an internal address (something like 10.0.0.1). I can go out to the internet from the computer and also see it from my internal network, which means that from a network prospective, it is properly configured.
I enabled the NAT service with the Server Admin tool by clicking the "IP Forwarding and Network Address Translation (NAT)" radio button. I selected the USB Ethernet from the "External network interface" and checked the "Enable NAT Port Mapping Protocol" from the options.
After that I followed the directions of adding the following lines to my natd.plist from the /etc/nat/ directory:
<array>
<dict>
<key>proto</key>
<string>tcp</string>
<key>targetIP</key>
<string>10.0.0.123</string>
<key>targetPortRange</key>
<string>80</string>
<key>aliasIP</key>
<string>333.33.333.1</string>
<key>aliasPortRange</key>
<string>80</string>
</dict>
</array>
I also left the top part of the plist file as such:
<key>clamp_mss</key>
<true/>
<key>deny_incoming</key>
<false/>
<key>dynamic</key>
<true/>
<key>enable_natportmap</key>
<true/>
<key>interface</key>
<string>en2</string>
<key>log</key>
<true/>
<key>log_denied</key>
<false/>
<key>natportmap_interface</key>
<string>en2</string>
<key>proxy_only</key>
<false/>
<key>reverse</key>
<false/>
<key>same_ports</key>
<true/>
<key>unregistered_only</key>
<true/>
<key>use_sockets</key>
<true/>
The section I added is correctly located directly above the final </dict></plist>.
Unfortunately, this does not work and according to the directions from Apple this is exactly how you are supposed to be able to enable port forwarding. I have also opened up the port 80 on my firewall to allow incoming requests. When I go to the external IP address for that server it just sits and waits forever and nothing is resolved.
If someone has experience with this issue please advise.

Gateway configurations are problematic with Mac OS X Server.
(There are many previous discussions around the forums.)
Getting this to work is fussy, at best.
You can also end up with ports unexpectedly open.
An external firewall is usually the easiest choice.

NAT port-forwarding and WAN side IP addresses

I have my Airport Extreme setup to forward port 21 to an FTP server on the LAN side of my network. The AE is connected via DSL to my ISP.
When a client from the WAN side connects to my server, the server's LOGS don't list the IP of the client, rather it says the client connected from my assigned WAN IP. For example (fake ip's):
Client ----> AE ----> FTP-SERVER
130.129.12.3 76.99.89.3 10.0.1.2
Log states client connected
from IP: 76.99.89.3
My previous Linksys router, with the same DSL modem and ISP, would report the client as connecting from 130.129.12.3.
Am I missing something in how I am configureing my AE? Or, is this how the AE manages port-forwarding and there's nothing I can do about it?
I used to use firewall rules to control access to the FTP server, i.e. rules set on the server. This can't be done anymore with the AE operating as it does.

Seems to me that the NAT translation in the Airport 802.11n is such that it does not use the incoming IP of clients connecting from the WAN side to a computer on the LAN side. The ingoing and outgoing packets reach their respective destinations, it is just that the AE uses some kind of non-standard routing (at least not that I am used to working with).
This is bad because it prevents the use of some forms of access controls on BSD and Linux servers on the LAN side, TCP Wrappers and iptables for example. This can create obvious security problems when WAN ports are set to forward to such a LAN client. We are already getting hit with robot-like script attacks on our server, this was a problem with our Linksys router, but with the above mentioned tools and scripts we were able to block abusive clients.
Perhaps an Apple can work on resolving this issue in a future firmware release, at least make it an option... Anyone from Apple out there?
jmj

Port Forwarding a Range in UC540 NAT

Similar Messages

Maybe you are looking for