Choose your cart
Choose your cart
Hi, I have FIOS Internet using the ActionTec M1424-WR router. I have enabled
port forwarding successfully for UDP traffic on the ports I'm interested in.
However I am unable to do so for TCP traffic. I notice there is a fixed port
forwarding rule:
localhostlocalhost Verizon FiOS Service – TCP Any -> 4567All Broadband DevicesActive
Does that mean that incoming TCP on ANY port gets automatically forwarded
to local port 4567 -- is this the reason I can't forward specific incoming ports to
my computer using additional port forwarding rules?
If that is the case, is there any solution for using port forwarding on TCP traffic,
other than adding another (non-Verizon) router upstream? Does Verizon NEED
all these ports?
I would be grateful if someone could clarify this for me!
Thanks a lot,
Ralph
Solved! Go to Solution.
You were right, after looking at the links you provided I see it was user error on my part! 😛
In the Port Forwarding configuration I was using the same port for the "source" port as for the "destination" port. I changed the "source" port to "ANY" for my new rule and now I am receiving TCP traffic on the specified "destination" port properly. 🙂
Verizon's hardcoded rule for TCP on port 4567 is not a problem.
Thanks!
Ralph
‎10-14-2008 01:09 PM
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.
‎10-14-2008 01:20 PM
No I can't delete this rule, that is the problem.
The "Any" refers to the port range. I confirmed this by adding a new port forwarding rule.
‎10-14-2008 07:51 PM
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.
You were right, after looking at the links you provided I see it was user error on my part! 😛
In the Port Forwarding configuration I was using the same port for the "source" port as for the "destination" port. I changed the "source" port to "ANY" for my new rule and now I am receiving TCP traffic on the specified "destination" port properly. 🙂
Verizon's hardcoded rule for TCP on port 4567 is not a problem.
Thanks!
Ralph