Getting the Verizon FIOS Actiontec MI424-WR Router to work with multiple VLAN

Getting the Verizon FIOS Actiontec MI424-WR Router to work with multiple VLAN’s

While working on my VMWare vSphere Home Lab I was running into many issues with not being able to route my internal network traffic which exist on multiple VLAN‘s to the outside world. Anything that was on the same network of my Verizon FIOS Actiontec MI424-WR router worked fine but as soon as I went to a different VLAN traffic would stop working.

The issue is centered around the Verizon FIOS Actiontec MI424-WR router not being able to initially NAT other internal networks besides the one it is on. In order to fix this issue there are a few things that need to be done to get your VLAN traffic to the outside world.

My current multiple VLAN setup is as follows:

  • VLAN 1
    • Network where my Verizon FIOS Actiontec MI424-WR router is installed.
    • Network: 192.168.1.X/24
    • Needs Internet: Yes
  • VLAN 2
    • All workstations, printers, iPAD’s, Andriod and just about any other device exists.
    • Network: 10.0.2.X/24
    • Needs Internet: Yes
  • VLAN 12
    • VMWare Storage Network
    • Network: 10.0.12.X/24
    • Needs Internet: No
  • VLAN 13
    • Server Network
    • Network: 10.0.13.X/24
    • Needs Internet: Yes
  • VLAN 14
    • Server Network
    • Network: 10.0.14.X/24
    • Needs Internet: Yes
  • VLAN 15
    • Server DMZ Network
    • Network: 10.0.15.X/24
    • Needs Internet: Yes

The Steps to allowing VLAN traffic through on the Verizon FIOS Actiontec MI424-WR router

  • Log into the Verizon FIOS Actiontec MI424-WR router.
  • Click “My Network.”
  • On the left, click “Network Connections.”
  • Click the edit button for the “Ethernet” connection under “Network (Home/Office).”
multiple VLAN
  • Once in the Ethernet Properties, click the “Settings” button.
  • You will now be in the Configure Ethernet page. From here you will see an area stating “Additional IP Addresses.”
  • Click “New IP Address.”
multiple VLAN
  • This step is up to you but be sure to document this IP address, you’ll not to accidentally have it reused. For each of my networks I need additional NATT’ing I am using a .254 address. For example VLAN 2 will use 10.0.2.254. Enter in the correct subnet mask, most people will use 255.255.255.0
    • The IP’s you assign here will never be used but you will want to make sure to reserve them so they are not reused and cause you issues.
multiple VLAN
  • Click Apply
  • You will see in the “Configure Ethernet page a drop down box labeled “4 Ports Ethernet Switch” with the option set to “Hide.” Change this to “Show.”
multiple VLAN
  • Click the “Edit” action for the Port you are using to to connect to your main switch.
  • Use the following settings for the Ports VLANs page.
    • Ingress Policy: Untagged
    • Egress Policy: Untagged
    • Click “Add” for Port VLANs IDs. Enter in the VLAN you need to NAT
    • Click Apply and confirm you want to make the change.
multiple VLAN
multiple VLAN
  • Click on “Advanced” located at the top of the Verizon FIOS Actiontec MI424-WR router page.
  • Select “Yes.”
  • Find and select “Routing”
multiple VLAN
  • Click on “New Route.”
multiple VLAN
  • Enter in the correct Destination / Gateway / Netmask Information.
    • Rule Name = Leave default “Network (Home/Office).”
    • Destination = Network such as 10.0.2.0
    • Gateway = IP Address of the switch VLAN interface for me it is 192.168.1.24
    • Netmask = Match the subnet mask of your Destination network, for me it was 255.255.255.0
    • When finished click “Apply.”
multiple VLAN
  • On my Cisco SG300-20 I did not assign any VLANs to the port in which my Verizon FIOS Actiontec MI424-WR is plugged into. It is set as a Trunk port with the Admin/Operating VLAN of 1.

Setting up multiple VLAN‘s and then having them rout to the outside world may be easier in some cases but when doing this in conjunction with Verizon FIOS Actiontec MI424-WR multiple VLAN routing can be a real big pain. Hopefully this post helps you solve some of your multiple VLAN routing issues on your network or VMWare vSphere Home Lab.

Advertisement

About Craig Irvin

In the IT industry since 1993. My passion is systems automation, solving things that people say can't be solved. I love to get my hands on just about anything to learn. I currently work for a non-profit IT company that hosts well over 2,400 Microsoft Exchange 2010 and Terminal Server connections.

Comments

  1. Hi Craig,

    Thanks for posting this tutorial. I was wondering if you knew how to configure trunking on an Actiontec that receives its data from Coax? It appears you have ethernet connected to the WAN port of your actiontec, not coax? My status for Ethernet is “Disconnected”. What do you suggest?

    • Craig Irvin says:

      Will,

      I am actually using the Coax portion for the web connection. My understanding is if you use Ethernet you lose a few things on your Verizon STB’s. However in order to get the Ethernet to work you’ll need to contact Verizon FIOS support to have them enable the port on the ONT. From there I’m not sure what else would need to be done.

  2. Hi Craig,

    Was slightly confused why my Network (Home / Office) => Ethernet showed a status of Disconnected, it still does. I went ahead and followed your tutorial and it worked perfectly! Have internet access to my other VLANS! Thanks again, great blog!

  3. Hi Craig,
    I looked at your writeup on the ActionTec with great interest. I’m sure that my lack of success is based on soemthin in the process of steps to make mine work properly. I started your steps and then arrived on VLANs 1 and 2 already established. I also saw a routing table implemented by your example but not sure how it connects to the VLAN you established.

    What might I be missing?

    Thanks as I have put hours into this and suspect I am missing something pretty basic.

    Jay

Speak Your Mind

*