Port Forward Bug?

I have the latest Apple Airport Extreme (AC router) and everyhting has been working flawlessly. However today, certain services that were forwarded and working, have stopped. Specifically the L2TP ports (500, 1701 and 4500) and the remote admin port (311). Others like 80 and 443 are working just fine. Using an outside service to check if the ports are open or not, it tells me the problem ports are closed, however they are configured properly in the airport extreme.
Nothing has changed. I'm completely lost.

From other reports there are indeed port forwarding bugs.. the major one is port 21 FTP which you are not using but the bug is very serious.
https://discussions.apple.com/message/22927625#22927625
The last post in this thread by.. SBeattie2
I think will condemn you to replacement of the AC by a router that actually conforms to standards.

Similar Messages

WRT160NL Port Forwarding Bug?

I have 2 NAS drives with FTP servers built in. I want to set my WRT160NL to forward single ports to these servers.
In the single port forwarding page, I set:
External port 100, Internal port 21, Both, IP: 192.168.1.10
External port 200, Internal port 21, Both, IP: 192.168.1.20
This should be fine since there are 2 devices, each with their own IP address. But, I get an error message when I try and save "The port range already exists". If i reconfigure one of the devices to use a different internal port then I can save, but I should not have to.
Is this a known bug?

Thanks, I know there are workarounds (I mentioned I could reconfigure one of the NAS servers in my post). That is not what I am after.
As it turns out, if I use the preset "FTP" then I can also use Port 21, so I can set 2 devices, but this is still not the correct solution.
After more research, this appears to be a problem with many other models, why doesn't Cisco/Linksys fix this issue. Seems easy enough to me. This could even be just an issue with the javascript and there is no technical reason why it was blocked.
Message Edited by do on 10-07-2009 01:04 PM
Message Edited by do on 10-07-2009 01:05 PM

RV320 Bug - Service Management Table (Port Forwarding)

I'm unable to add more than 16 entries for port forwarding.
It's a RV320 on v1.1.1.06 (newest to date) and it doesn't accept more than 16 entries in the "Service Management Table" required for port forwarding. As soon as I try to enter number 17 and hit save the window closes like it always does but you can see for a short time it says "Critical failure. Please contact support." Everything else works, except for the entry in the Service Management Table. I'm also unable to use it in the port forwarding section, it just doesn't save the entry. I'm unable to add any services to the list unless I delete others but it only works again until number 16.
Actually the "limit" is 37 because it comes with 21 services entered out of the box.
I couldn't find any bug reporting website that I could use without a contract. So I seek for help here.
Anybody else having this issue or is it just my device?

10 days ago a post was made in https://supportforums.cisco.com/discussion/12353771/cannot-manage-service-list-all-waited-unacceptably-long-fix indicating there is a new firmware in beta test, I've contacted support to try to get a copy.
I'm moving off Draytek, have a 2830 with latest firmware and various weird issues that they've confirmed are bugs but cannot provide a due date for fix. DHCP randomly giving out wrong DNS server addresses, tagged VLAN support flaky and giving out DHCP details from wrong VLAN (worked around using 1 cable from switch per VLAN and using port based VLAN rather than tagged), App Enforcement for IM blocking causing SMTP and Live.com login issues. And that's just what cropped up last week with the unit at work here. Still using it for our live router as we can't put the RV320 in place until we can configure all the required ACLs which needs more than 16 service entries.

Port forwarding difficult to set up, or doesn't wo...

Hello, I have a BT Home Hub 5 and needed to forward the ports for a couple of programs i use. Terefore i went on 192.168.254 to set up the forwarding of the ports.
Before that set up a static Ip in the router in the classic way (cmd - ipconfig all - copied all the addresses), then i selected in the programs list the program i needed to have (was already in the list so no need to dd a new one) but has been useless. Everything seems nice, but simply it doesn't work. It worked only once, then the day later came back as before.
Anyone can give me an hand? I read somewhere that this procedure in the router page has some bugs.
Thank you very much
Solved!
Go to Solution.

mrblue wrote:
It worked now!! I made a mistake before, i enabled the "use this ip address" but then i should have connect the new game NOT to my pc but to the user defined ip! That was the static one defined before in my pc
Thank you keith
Exactly !
Device names will normally fail, that seems to be a common "feature" of all the home hubs, and most other routers expect you to use the device IP that you have reserved in the DHCP table, or set as a static IP address, outside of the DHCP range. It could be a leftover from the "SpeedTouch" code that seems to underpins the core of all the home hubs, starting from the home hub 1, which I have.
This is where most people seem to fail, when it comes to port forwarding on the home hub.
Sometimes you can get away with it and it will appear to work for a while, but then it fails. I hear so many people complaining on this forum that it does not work, which is why I put together my guides, based on my own experience, and other forum users.
If you have set an IP address on your PC, outside of the DHCP range, then the option "always use this IP address" is not relevant, and could cause problems.
There are some useful help pages here, for BT Broadband customers only, on my personal website.
BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

Port forwarding is not working on SRP521W

Hello,
I have a problem with incoming traffic.
I opend 3 ports as followed:
I have olso anabbled de remote web menagement on port 888.
From the outside i can access the remote management. but i cannot access my webserver on prot 80 or 443. I have checked with the isp provirder en these port or not blocked.
Can anywane help,
Thanks,

Hi Danny, to my recollection there are not any bugs on the current releases for the SRP for forwarding.
To affirm, you have went to Network Setup -> NAT -> Port forwarding
Also, are you able to log in to the server locally with the LAN IP address using an internet browser for http and https?
-Tom
Please mark answered for helpful posts

Problems with Port Forwarding for RDP in WebVPN

Hi,
I'm hoping somebody can help me solve this problem that's been bugging for weeks. We recently implemented a double-layer firewall architecture. Before that, our users can access RDP via port forwarding on WebVPN or the Cisco VPN client without any problems.
After we implemented the double-layer firewall architecture, users who are going through the WebVPN and port forwarding for RDP began to experience frequent disconnections, slowness or freezing connections. The users who are using the client are fine.
I checked the logs and I'm getting repetitive TCP-O for the port forwarding connections for RDP. Additional information: the FW we installed as a 2nd layer is Netscreen. I've already set the policy on it to Any-Any for the meantime to help in troubleshooting but to no avail.
I hope somebody can help me in sorting this out as I'm kind of confused on the difference between the port-forwarding for RDP via the WebVPN and the normal RDP via the client.

Hi,
I didnt see anything marked with red in the above? (Atleast when I was reading)
I have not really had to deal with Routers at all since we all access control and NAT with firewalls.
But to me it seems you have allowed the traffic to the actual IP address of the internal server rather than the public IP NAT IP address which in this case seems to be configured to use your FastEthernet4 interfaces public IP address.
There also seems to be a Static NAT configured for the same internal host so I am wondering why the Static PAT (Port Forward) is used?
- Jouni

RV042 Port forwarding stops working when Firewall is enabled

Hey all,
I have a RV042 router on a single WAN and an internal LAN. I have configured port forwarding as follows:
HTTP[TCP/80~80]->10.0.0.6
HTTPS[TCP/443~443]->10.0.0.6
IMAP[TCP/143~143]->10.0.0.5
IMAP SSL[TCP/993~993]->10.0.0.5
SMTP SSL[TCP/587~587]->10.0.0.5
Everything works just fine when I have the firewall DISABLED. However, when I enable it the behaviour is erratic. 1 out of 10 attempts to connect to ANY port forwarded works. Almost all attempts time out.
Notice that this happens even if using only the default firewall rules (which should be bypassed by the port forwarding as I read in other posts).
My second try was to create firewall rules manually, overriding the default ones. I tried adding rules from source WAN1 (where my connection is) to ANY and to SINGLE IP's on every port. Nothing seems to work.
I don't know what I'm doing wrong, this is really bugging me. I had to turn the firewall off so we can access our servers from outside the office. This shouldn't have to be done.
Do you know anything I could try?
Best regards,
Theo
EDIT:
Just found out that my firewall is getting LOTS and LOTS of Blocked - SYN Flood entries. I think this is why we are having trouble with the firewall. Could this be the problem? I have no idea where all these SYN packets are coming from since they appear with spoofed IPs or come from different bots all over.

Hi Theo, if you want to over ride the default state table, you need to first make firewall rules to block all access then make your permission rules.
Such an example would be-
Action Deny
Service All
Source interface WAN
Source IP any
Destination IP any
Save
Action Permit
Service RDP
Source interface WAN
Source IP -xx.xx.xx.xx
Destination IP - xx.xx.xx.xx
Save
As for your concern about the syn flood, it can be a likely cause of your problems. Does the logging facility of the router give any indications?
-Tom
Please mark answered for helpful posts

Linksys WRT610N Port Forwarding

I am finding it impossible to set up port forwarding. No matter what I do I remain completely stealthed when I do a port probe via www.grc.com. The only way I seem to be able to open a port is if I enable remote management. When I do that, whatever port I specifiy as the remote management port is then fully open. Obviously, I can't leave a port exposed like this and, anyway, I need to open multiple ports for my purposes.
Is there a bug? Can technical support please help?
Some background: I'm in the UK and I connect to the internet using the Fibre-to-the-cabinet (FTTC) technology. I have a BT supplied modem (Huawei Echolife HG612) which is completely locked (it is BT property) with no ability to log in and change settings. The WRT610N is plugged into the LAN socket of the modem and connects via PPPoE. Everything else works fine.

A firewall does not open or close a port. A firewall blocks or passes transient traffic. Thus if the port is closed on the computer it doesn't matter what the firewall does. The port will never show up as open as long as the port is not in use.
ifconfig
netstat -an

HH3 Type B port forwarding not working.

Hi there.
I have searched absolutely everywhere for a solution to my problem before posting here. Basically port forwarding isn't working at all on my HH3 Type B router.
I've read all about the problems people have had with the Type A's but as far as I see nobody seems to have a problem with the Type B in regards to port forwarding or loopback.
I've set up port fowarding on many different routers with many different ISP's so I don't think it's something I'm doing, or rather, not doing but you never know.
These are the steps I take when setting up port forwarding:
Firstly setting up my static IP (obviously only needed to be done once) which I've chosen one outside of the routers DHCP range as I've always done in the past. Then I open the router screen, go to Settings / Advanced Settings / Port Forwarding / Supported Applications and click "Add new game or application".
I then enter a name, change "Copy existing game or application" to "No", and then change the "Protocol" to UDP or TCP as needed (also have tried using "Any" too with no luck). Next add a "Port Range" for example 12345 - 12345 then add "Translate To" 12345 - 12345 (port ranges obtained from portforward.com per application) then click "Add" and repeat for additional ports as needed.
Once that is all done, click "Apply" then go to Port Forwarding / Configuration or go to Home Network, select the applicable device and choose the newly added application from the "Port Forwarding" drop down list (and choose applicable device if doing it from Port Forwarding / Configuration). Click "Add" once application is selected.
Add additional applications where needed then finally click "Apply" to store the forwarded ports.
Close router page and port forwarding should be fully setup and working.
That's basically how I would do it anyway, but I also checked on portforward.com and it says pretty much the same and on these forums as well as a few other sites and I see nothing different but port forwarding still isn't working.
In my router "Event Log" it does show "The Port Forwarding entry of [xxx.xxx.x.xx] has been added or modified.".
My Firmware version is V100R001C01B036SP03_L_B. Last updated 19/05/13.
I have no firewall on my pc and the one enabled on the router is set to default but have also tried disabling it. Have tried enabling DMZ as suggested in various places with no luck and have tried changing UPnP settings again with no luck.
So if anybody has any suggestions I am all ears because this is bugging me so much as there are a few applications and games that require port forwarding and are pretty useless without it really.
Thank you.

If you follow the instructions on this page, it should work. Please see note about CG-NAT.
Port forwarding problems
There are some useful help pages here, for BT Broadband customers only, on my personal website.
BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

Router Port Forwarding not working since Mavericks

I have an iMac sat behind a BT Home Hub 3 (an ADSL router, if you're not aware), with several ports (POP3, SSH, HTTP, etc) from the outside world forwarded via the hub to my Mac. Since installing Mavericks (from Snow Leopard), NONE of these ports are now open.
They're open on the Mac, and another machine on my home network can use them locally, but from outside the network, they're hidden. Shields Up shows them as Stealth.
Things I've tried:
Rebooting everything.
Setting the Home Hub up again, forwarding all the ports again.
Turning all the sharing off in Mavericks and then back on.
Trying the same services on different ports.
Trying different services.
Turning off the Mac firewall.
Turning off the router firewall.
Trying the Mac on another IP address and reforwarding everything to the new one.
Putting the Mac in the DMZ.
I can forward ports to other devices on my network (e.g. my NAS) and they work fine, so port forwarding isn't completely broken on the router
Here's the thing though...
On a completely separate network, on a separate Mac (a 2012 MacBook Pro) that went from Mountain Lion to Mavericks, also behind a BT Home Hub 3, EXACTLY the same thing is happening. No ports can be forwarded to the MacBook Pro, but all the ports are open to the local network.
Any ideas? I'm pretty sure this must be a bug in Mavericks as I can't see anything else it can be.

It's not just single port forwarding that has bugs, the entire router has bugs and simply does not work as advertised. I have found the following bugs/aspects of this router that just does not work correctly: 1. If you have to open ports, and who doesn’t, this router will eventually stop accepting packets from WAN>LAN. You will still have Internet access but no open ports. A reboot will fix this problem. Oh, by the way, this router has no scheduled reboot option! <--That would be a workaround but a welcome one for this router. 2. Firewall Access rules do not work!! Yep, a Cisco router and basic functionality simply does not work. I called Cisco and even though the tech saw the router not working denied it was a bug! Said we have to do port mirroring, setup a workstation with WireShark and capture packets so we can debug the issues. That would take several hours. I told him I would have appreciated if Cisco would have debugged the issues with their router BEFORE they shipped the units. Stay away from Cisco Small Business Routers. I wish I had. And if there are any Cisco die-hards out there willing to prove me wrong, just reply to this and please, prove me wrong that the RV series and specifically the RV215W is not JUNK.

RV082 port forwarding limited to 30 entries ?

Hello,
we use RV082 as main gateway and need to open/forward around 50 ports to inside. But during setting of the rules I got an error message "The max of Port Range Forwarding is 30 entries. You can't add any more.".
In the online help is explicitely said "4. Click the Add to List button, and configure as many entries as you would like."
How can we setup more than 30 port forwarding rules ?
If it is this a sotfware bug, can this be corrected ?
Regards,
Petr Svoboda

Petr, I agree with tekliu. I use the UPnP rules with UPnP disabled for all of my port forwarding, unless a range is needed. They should not cause any more exposure than regular Forwarding rules, and if you use port translation they will reduce your exposure.
The only differences:
Forwarding allows port ranges
Forwarding has a "Port Triggering" section
UPnP allows port translation (because it's only single port at a time, not a range)
UPnP has unlimited entries

Does Port Forwarding Differ in AEXn from other routers?

After having many issues with using FTP in my current router, I have discovered that there is simply something wrong with the way the AEXn port forwards to my FTP server. It appears to forward such that my server cannot read the requesting host's IP number and only sees the router as the requesting host. The problem I face with this is that I have a security function on my FTP server that auto-blocks IP numbers that fail to login too many times. When this function is enabled, the FTP server ends up blocking the router's IP number when too many failed attempts occur. This causes all subsequent FTP connections to be blocked since the AEXn acts as the proxy to open all connections.
For reference, I am using the Synology DS-107e NAS for my server needs. Any tips on how to get my device to properly see the requesting host's IP number would be greatly appreciated.

Chuck H. wrote:
The issue is not getting the port forwarding working. The system works fine - it's just that there is a bug in the way port forwarding works that prevents me from using a security function to auto-block IP's that fail logins too many times in a row. When those IP's do trigger the block, my NAS blocks the IP of my router instead of the requesting host. There is some problem where the router is not properly including the requesting host IP number in the port forward to the destination host. Granted, this is not really a big deal - but for security management purposes is a necessary function for my NAS to work properly.
I would say the issue is really with your NAS or whoever is trying to connect to it. I have an Infrant (now Netgear) ReadyNAS+ 1TB connected with the AEBSn through the Gigabit connection and FTP works perfectly.
My ReadyNAS has a similar function on blocking IPs with multiple login failures. That's pretty standard on many devices that offer FTP interfaces. But I do not experience any of the failed IP logins.

Cannot get port forwarding to work on EA6500

Hi,
I have an EA6500 to replace the old WRT54G. I have an Apach server on my PC. On the WRT54G, I could easily set port forward to the server, it was working fine. But on the EA6500, I simply couldn't get it to work any more. What am I missing?
TIA

Thanks for the reply.
As it turned out for some "security" reasons, EA6500 port forwarding only allows access from outside of the network, but not from netwrok behind the router. So annoying, however I found this work around
http://community.linksys.com/t5/Wireless-Routers/EA6500-NAT-Redirection-Bug/td-p/583820/highlight/fa...
look for poster sflick1's solution, it really works.

Port forwarding Time Capsule Airport 7.6.3

Network problems. I want to run a free software called Maptool 1.3b89. I created some sweet maps in OS version 10.7.5, and assembled players, but I can't connect with other computers. I have the Time Capsule (router) with Airport version 7.6.3, updated, Cisco cable modem. I updated Java when I installed Maptool, less than a month ago.
The Maptool Networking FAQ says UPnP is by far the easiest approach, furthermore,"(An alternative is called NAT-PMP, but they are functionally the same so the second won't be mentioned again.) "This sounds as if one can plow ahead and get the same result. Believing they were functionally the same, I enabled NAT-PMP, attempted to connect with the UPnP box checked, and Maptool returned: "no internet gateway devices found UPnP port mapping will not be available."
So I asked, "If I get the server enabled, will it work for windows, or just for mac clients? Is this where it is functionally the same?"
Here is the response, though I'm not certain it addresses my concern: "The NFAQ is incorrect if it says that NAT-PMP is the same as UPNP. NAT-PMP is a new protocol from Apple that only applies to the AirPort routers, although a lot of other routers now support it as well. I'll fix the FAQ. There will be a b90 build either tonight or tomorrow that will fix the UPNP bug, but it won't help with NAT-PMP since it's a different protocol. I'll see if I can find a way to support NAT-PMP but it's not likely to be soon."
Does that translate to, give up or get a different computer, Mac user?
I searched these forums. The suggestions aren't talking about version 7.6.3 of Airport. They tell you to go to port mapping, which is not an option/selection offered. The most useful post says my version of Airport is a toy hammer with no functionality, go get old Airport, version 5.6. Did that using Unpkg. Did not run both airports at the same time. Followed another post that referenced Bit Torrent, thus, I enabled Nat-PMP, and mapped all four ports to 51234, the default port for Maptool. Airport 5.6 returned: The airport utilty was unable to find your Airport wirless device after restarting, the settings for this wirless device have successfully updated, but there was a problem rejoining the wirless network or finding the Airport wireless device. you may need to select your network from the Wi-fi menu and try again.
Lost wireless. Did a backup from Time machine and still couldn't connect wirelessly. Restarted and the wirless returned.
The NFAQ says UPnP won't work with port forwarding (at the same time) but that is what seems to need to happen on a Mac. I tried portforward.com. Does not have my router. Followed instructions for the only featured Apple/Macintosh product, Airport Extreme. Not even close.
I have clicked all the advanced buttons and menu choices through Airport and through (settings)network, and figured out you can click on the + sign. The outdated portforward.com info says, "enter both the public and private boxes with the same port number," and shows two boxes, but I have four boxes: IPV4 port mapping, public (and private) UDP ports, Public (and private) TCP ports. Should I fill all four with port 51234 and use the provided IP address?
I can't make my IP address static. I followed the portforward guide and lost my internet connection. Portforward Open Port check tool says, "this program cannot be run in dos mode," with a giant code strip following. Excuse my ignorance, but why is a dos program set up to run a test that is embedded in a Macintosh installation guide? Is that an emulator or a different dos? Shouldn't it be Unix or something? It says if I have no internet connection (which I don't at this point) to restore my original settings. Futile. The user guide offered here isn't my software version but it says to enable NAT-PNP and give the ip adress to the host, but Maptool isn't going to use this special IP because it will only see the public one, right?
I was tempted to buy one of their products like PCconfig but here is what they say, "Instead of manually configuring your network router, just pick your app from a list and update your router with a single click." but they don't bother to indicate whether it works for mac, don't feature my router, and it says you must pick an app, but Maptool is not featured in the giant list of users that, "you are forwarding ports for." I tried to download PF Setup Static IP Address but the download was a Windows app, so I couldn't run it.
I have tried just enabling Nat-PMP by itself, Canyouseeme.org returns "firewall or ISP is blocking certain parts, error, I could not see your service on (my IP address) port 51234." I have tried port mapping by itself to port 51234, which causes the time capsule to crash, requiring a backup and reboot to restore the wireless network, and both together, which is contrary to the way it is supposedly done with UPnP.
If I installed Windows that wouldn't change how it networks. What is my next step, buy another router?
Downloaded Hamachi. The tutorial no longer launches. The tech data has removed the mac screen shots and not replaced them, but I can see the headings and blank spots where they should be. I assume they aren't supporting new mac users. Logmein was just as obscure. I don't feel very confident about either product. The freeware Virtual Network Provider gets reviews like, "hard to use," and "complex interface."
Thanks in advance for your consideration.

If you want to use maptool and it is only going to work with UPNP type router. Then simply replace the TC with a standard router.. it is less than $100 for a very reasonable one like Netgear WNDR3800 which has 3rd party firmware like dd-wrt, openwrt and gargoyle as well as netgear which is pretty but lacks features.
Bridge the TC and keep it as backup target for TM which is what it does best.. and wireless AP for apple devices.

RV180W loses port forwarding rules when switching WAN connections

We have a backup WAN connection in our office, but we switch this connection manually on our RV180W when the primary goes down. Our normal connection is ADSL with PPPoE, and the backup is Cable with DHCP.
However, we also have some port forwarding rules for our VoIP PBX (UDP port 5060) as well as SSH, and these rules seem to stop working completely when we switch our WAN connection to our cable connection. We can still surf the web from our workstations, but our incoming phone calls and SSH connections all cease to work completely. The problem does not persist after we've switched back to our normal ADSL connection.
This behaviour is completely bizarre and suggests that there's some kind of bug in the Cisco RV180W.

helm,
I'm sorry, I wasn't clear which IP address renewal I am speaking about.
I believe that the problem is caused when the router renews the WHS's local IP address (192.168...). My WAN IP address remains unchanged througout the tests I performed and the problems I experienced.
The very act of changing the local clients' lease time in the router's configuration causes the forwarding to be lost immediately. (I am gusessing that when the lease time is changed, the router immediately renews the lease and begins a new countdown.)
(In fact, I might go as far as to say it is a bug in the firmware, but I haven't done enough testing to nail it down.)

Port Forward Bug?

Similar Messages

Maybe you are looking for