Comments on: Verizon FIOS Actiontec MI424WR and multiple subnets

By: tmclaugh

tmclaugh — Sat, 13 Mar 2010 20:38:06 +0000

The images look to have been lost unfortunately. They’re listed in wordpress but the files are missing. Sorry about that.

By: Ken

Ken — Sat, 13 Mar 2010 15:06:23 +0000

Do you have the images relating to the blog. I would like to subnet my actiontec.

By: Ben

Ben — Mon, 03 Aug 2009 16:49:01 +0000

I’m having the same problem as Frank and Ike. Anyone make any progress with this? I’d rather not go ahead and put the router into bridge mode.

By: Jigar soni

Jigar soni — Sun, 14 Jun 2009 01:18:44 +0000

can now go back to a routed vpn rather than bridged. Thanl you

By: Ike

Ike — Sat, 04 Apr 2009 06:00:06 +0000

I have the exact same problem as Frank describes.

I can get between subnets internally, but the inside subnet (behind the the wireless client) on 192.268.2.0/24 won’t make it to the Internet.

I’m not seeing the blocked NAT out failed message in the security logs, but it sure seems like a NAt issue.

By: Frank

Frank — Sat, 07 Mar 2009 21:21:21 +0000

Hey I saw this and had a question:

Were you able to get out to the internet from your remote subnet? The problem I am having right now is that the Actiontec router will not NAT my traffic from the inside network.

In your example the inside network would be 192.168.2.0/24. The Actiontec network to the Router is 192.168.1.0/24.

I can log into the Actiontec and reach things on the inside and I can even put my PC on the 192.168.1.0/24 network and print to my HP Network printer on the 192.168.2.0/24 network.

The problem I am having is the outbound NAT is being blocked. I get the:

Blocked – NAT out failed

Message. I don’t see anywhere in the Actiontech where I can verify that my 192.168.2.0/24 network is permitted to be NAT’d out to the internet.

(Yes this is 100% a problem with traffic going through the Actiontec- yes routing from the Actiontec to the inside subnet works fine it appears to be a NAT issue)

By: Simon

Simon — Thu, 05 Feb 2009 23:27:57 +0000

Thanks! I can now go back to a routed vpn rather than bridged. I thought for a while that the actiontec was incapble of rerouting packets back out through the same interface similar to cisco pix but this works great.

By: Matthew

Matthew — Fri, 23 Jan 2009 00:20:32 +0000

Awesome, this is exactly the answer I needed to solve my VPN routing issues.

By: Art

Art — Mon, 12 Jan 2009 04:30:45 +0000

wonderful guide. thanks! Couldn’t get it to work though. In my situation I have the physical network on 192.168.2.1 and I have a d-link WAP which has a static IP out of the box set to 192.168.0.50. The install guide wants me to change the setup PC to the same subnet and physically connect the two things to each other and then change the IP of the WAP to whatever I want. I was hoping that twiddling with the ActionTec settings would let me avoid that. You guide seems like it should work but, alas…

By: scott

scott — Tue, 23 Dec 2008 15:33:16 +0000

Follow your conversation. Why is the gateway address 192.168.1.253 ?
Have you fixed the gateway address to 253.