NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
VLAN Configuration
[This is a generic query on the function VLANs on Netgear switches, no specific switch model as I have to work with nearly all variations. Firmware can be updated I have no problem doin that, in the ...
I just want to follow-up on this. Let us know if you have further questions.
Otherwise, if ever your concern has been addressed / resolved, I encourage you to mark the appropriate reply as the “Accepted Solution” so others can be confident in benefiting from the solution. The NETGEAR Community looks forward to hearing from you and being a helpful resource in the future!
Regards,
DaneA
NETGEAR Community Team
I understand that you are trying to avoid as much configuration as possible such as setting up ACLs. With regard to this, you might want to consider setting up Asymmetric VLAN.
Regards,
DaneA
NETGEAR Community Team
DaneA,
I had never heard of this variant of VLANs and that was a usefull excercise to read through. This may be possible but it means changing the default VLAN or at least removing the default VLAN from most of the switch ports to avoid cross communication on all the VLANs... obviously this leads to management issues when you need to remote in to the switch unless there is a dedicated management access port, I also think it will not be possible due to the nature of the WiFi access points as they require trunked VLAN ports.
I think the solution is going to have to include at least VLAN Routing and maybe the ACLs too. I have found that I should be able to configure both on the M4100-D12G switch according to the manual (I'm a bit sketchy when it comes to what is possible on certain Netgear Switches).
I did have trouble with the VLAN routing setup before when I last attempted it, but I am thinking that was caused by trying to setup VLAN interfaces subnetted within the range that was already set as the default VLAN interface (i.e. I didn't realise that the switch IP and subnet was not only the management interface but also the default VLAN interface) so I guess I was trying to subnet a subnet(!) and the switch didn't like that so gave me configuration errors.
Regardless of the issues, all the reading and advice has got me to the point were I am happy to purchase some APs and an M4100 switch and try to simulate what I have been discussing. I will Likely come back and mark one of your posts as an answered. I will however no doubt be posting a specific configuration issue cback here once I actually get down to configuration.
Regards
SchoolsTST
Thanks for the feedback. About VLAN Routing, kindly access and read the article below because this would help:
VLAN Routing on NETGEAR Smart Switches
Regards,
DaneA
NETGEAR Community Team
I just want to follow-up on this. Let us know if you have further questions.
Otherwise, if ever your concern has been addressed / resolved, I encourage you to mark the appropriate reply as the “Accepted Solution” so others can be confident in benefiting from the solution. The NETGEAR Community looks forward to hearing from you and being a helpful resource in the future!
Regards,
DaneA
NETGEAR Community Team
Hi All,
The wireless configuration is all but completed at least to the point of testing, implementation is delayed due to a 3rd party not being available - usual mutil-provider bureacracy that affects all organisations small or large! Below I will state what has been done and the final question for the thread is just a nice to have.
We have configured two VLANs (1 and 500) on the M4100 switch.
Interface for VLAN1 is 10.122.x.11/22 and the gateway for this network is 10.122.x.11/22
Interface for VLAN500 is 10.87.x.2/24 and the gateway for this network is 10.87.x.2/24
DHCP has been configured for these ranges on the Windows Server on VLAN1
Static IP addresses for both networks have been assigned to the NIC on the Windows Server
A Global IP Helper has been configured with the destination set as the Window Server enabling UDP DHCP requests from VLAN500
Once the Windows Server has assigned a DHCP address to a device on VLAN500 in the 10.87 range there seems to be no communication between the networks and this is presumably because the IP Helper is only UDP. I'm not entirely happy with this but setting up IP Helpers on specific DHCP port numbers did not enable the assignment of address.
So we are using the VLAN routing as only a method of network assignment via DHCP. As far as I understand it, more routing configuration would only be required only if the number of VLANs and segregated networks was greater than the number of physical interfaces I am trying to bridge to the WAPs. Currently we do not have to create more than two SSIDs but that will change in the furture, I am unsure if there is more to configure on the M4100 in this scenario apart from additional VLANs, it appears that the additional routing information would have to be configured on the router.
If anyone wants to work on this problem with me them feel free to write a private message, but I think I have gone far enough in this thread.
Anyway, answered or not this question remains but I have a working solution.
Thank you for your help.
Kindly answer the questions below:
a. What if you will try to set a static IP address on the device on VLAN 500, does same problem occur?
b. How is everything connected? Is the M4100 switch connected to another switch or to a router? You may post a diagram of your existing network setup.
Regards,
DaneA
NETGEAR Community Team
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
