- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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 Correct Answer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you delete that rule of..
localhostlocalhost Verizon FiOS Service – TCP Any -> 4567All Broadband DevicesActive
?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
http://www.portforward.com/english/routers/port_forwarding/Actiontec/MI-424-WR/MI-424-WRindex.htm
http://www.portforward.com/english/routers/port_forwarding/Actiontec/MI-424-WRv2/MI-424-WRv2index.htm
Very strange that UPD works but not TCP. Because you forward almost the same way other than TCP / UPD and the port number(s).
Check what the security level is set to.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
