Link to home
Create AccountLog in
Avatar of Randy Pitts
Randy PittsFlag for United States of America

asked on

NETWORKING WITH VLANS

Setting up a Netgear M4250 for the first time in a bench environment.  I've setup four VLANS (10,20,30, and 40) and made each of them do DHCP.  DHCP for the native VLAN is handled by the router. 


When connecting through the native vlan, client devices get an IP (directly from the router) and can access the internet.


However, when connecting through any of the VLANs I created (DHCP from the M4250), the devices cannot access the internet.


Other info:

   - When connecting thru VLANS 10, 20, 30 or 40, devices receive the appropriate IP from their respective VLAN (i.e., VLAN 10 is on 192.168.80, VLAN 20 is on 192.168.90, etc...)

    - From client devices, I can ping router, but not beyond.

 

I've tried different routers and setups to work with the M4250 and get the same result.  I'm currently back to using a LinkSys LRT214.


   - Tried both with and without custom VLAN info replicated on the router. Current setup is without custom info.


Seems like a no-brainer problem, but I simply cannot get this up and running.  Would appreciate some advice if you have any.


 

Avatar of Christopher Hippensteel
Christopher Hippensteel

I think the issue lies in the routing configuration for the VLANs


  1. Verify VLAN configuration: Make sure that the VLAN interfaces are created and associated with the correct VLAN IDs (10, 20, 30, and 40). Verify that the switch ports are correctly assigned to their respective VLANs.

  2. Check DHCP settings: Confirm that DHCP is enabled for each VLAN

  3. Verify default gateway settings

  4. Verify inter-VLAN routing: Confirm that inter-VLAN routing is enabled

  5. Capture network traffic: If the above steps don't resolve the issue, consider capturing network traffic using tools like Wireshark. Analyze the captured packets to identify any anomalies or errors that might help pinpoint the problem.

Avatar of Randy Pitts

ASKER


Verify VLAN configuration: Make sure that the VLAN interfaces are created and associated with the correct VLAN IDs (10, 20, 30, and 40). Verify that the switch ports are correctly assigned to their respective VLANs.


User generated image


I'm focusing on just getting VLAN 10 working at this point.


User generated image

Port 5 is connected to computer, port 40 is  connected to the gateway.


Port PVID configuration:


User generated image

  • Check DHCP settings: Confirm that DHCP is enabled for each VLAN

            

            DHCP is enabled for each VLAN, except 999,which has been assigned a static IP of 192.168.2.2


  • Verify default gateway settings


           Default gateways each VLAN is set to 192.168.x.1.


  • Verify inter-VLAN routing: Confirm that inter-VLAN routing is enabled


           I don't have any ACL's preventing inter-VLAN routing.  This model doesn't have a simple checkbox to enable/disable inter-vlan routing (that I can find).


  • Capture network traffic: If the above steps don't resolve the issue, consider capturing network traffic using tools like Wireshark. Analyze the captured packets to identify any anomalies or errors that might help pinpoint the problem.


           Working with a NETGEAR rep, I did use Wireshark to capture traffic and it looks like requests are getting out to the internet and back again at the switch port level, but not to the computer.  I've wondered if the VLAN tagging is dropping from return traffic.



Here's some routing info:

User generated image

I've also setup static routing in the router:


User generated image


Avatar of Craig Beck

You should only have one untagged VLAN per port. The port that connects the router to the switch should just be on VLAN 999. All VLANs will route via the switch.

ASKER CERTIFIED SOLUTION
Avatar of Randy Pitts
Randy Pitts
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account