0x9h3 Posted June 2, 2018 Posted June 2, 2018 Hi everyone, I know, I know, there are about 1001 threads relating to VLANS, but I am either having a moment or I am confusing myself over this. I am trying to create a VLAN to segregate a particular device away from the school network. This device will need access to one server and the internet but I am struggling in getting this to work. I want to put this particular device on a 192.168.10.* rage with 255.255.255.0 netmask - Most of our switches are HP onsite but none of them are decent enough to manage the routing, for this I'd use smoothwall if possible. Help please! Thanks
dbu Posted June 2, 2018 Posted June 2, 2018 Hi You will need to connect the device to a port on the switch and untag that port on the VLAN you want it in (unless the device is VLAN aware then you can just tag the port) then any connections between other switches in the network will need to be tagged on that vlan. Your smoothwall will need 2 virtual interfaces, one on the old network and tagged on that network and one tagged on the new network, the switch port for the smoothwall box will need to be untagged on the old network and tagged on the new one. You will then need to sort out your routing either by adding static routes to the devices or by adding routes to both networks routers. I think that’s all.... Prob missed something vital. 1
0x9h3 Posted June 3, 2018 Author Posted June 3, 2018 Hi, Thanks for your help. It would of helped you if I commented what steps I'd attempted beforehand! So... The port that the device is connected to I have set it to untagged The uplink ports on the switch I have set to tagged with both vlans ID's But this device can not ping anything once on this VLAN. Do I need to set a interface ID with IP address on every switch if I want to tag more devices later on? I'd like smoothwall to manage the routing majority of my switches are HP 1920's and I don't think are decent enough to handle the routing. Thanks, Hi You will need to connect the device to a port on the switch and untag that port on the VLAN you want it in (unless the device is VLAN aware then you can just tag the port) then any connections between other switches in the network will need to be tagged on that vlan. Your smoothwall will need 2 virtual interfaces, one on the old network and tagged on that network and one tagged on the new network, the switch port for the smoothwall box will need to be untagged on the old network and tagged on the new one. You will then need to sort out your routing either by adding static routes to the devices or by adding routes to both networks routers. I think that’s all.... Prob missed something vital.
dbu Posted June 3, 2018 Posted June 3, 2018 Have you tagged the ports on the uplink ports of both switches? Do the VLANS exist on all switches you want to move data across? Is the smoothwall router set up and how is that configured to access the VLAN?
0x9h3 Posted June 14, 2018 Author Posted June 14, 2018 Sorry for the slow reply, it's been pretty hectic lately. Yes, I have added the VLANS on the switches and tagged the uplink ports. I am still rather confused. If the VLAN is over multiple switches around the site do I need to add an Interface IP on all the switches? I'd like smoothwall to handle the routing for this but whenever I add a device onto the VLAN they can't ping smoothwall or any other switch/device Thanks Have you tagged the ports on the uplink ports of both switches? Do the VLANS exist on all switches you want to move data across? Is the smoothwall router set up and how is that configured to access the VLAN?
ass17 Posted June 14, 2018 Posted June 14, 2018 Sorry for the slow reply, it's been pretty hectic lately. Yes, I have added the VLANS on the switches and tagged the uplink ports. I am still rather confused. If the VLAN is over multiple switches around the site do I need to add an Interface IP on all the switches? I'd like smoothwall to handle the routing for this but whenever I add a device onto the VLAN they can't ping smoothwall or any other switch/device Thanks Either your layer 3 core switch will have the IP interface or smoothwall will. Only one needed per VLAN. Maybe like us, other schools may have physical PCs running through the layer 3 switch IP interface with static routing, ACLs etc.... The WiFi network via virtual interfaces on smoothwall.
AlanD Posted June 15, 2018 Posted June 15, 2018 Are you getting smoothwall to provide dhcp and DNS on this new VLAN? Or using a static IP and gateway pointing to smoothwall?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now