How to split LAN into two? - Jikjik101's network
-
I see. The effect is now clearer on me using stephenw10's method.
Sorry for being so ignorant, but what I don't get is the how-to or the step-by-step process to make this one. ??? ???
@stephenw10:Assign a second virtual interface to the LAN interface. This interface will have different subnet.
Then you assign your 'lan B' group to use this subnet.Correct me if I am wrong (I know I'm wrong ;D), are these the steps to do stephenw10's suggestion?
1. In my pfSense box, go to Interface>(assign)>VLANs>add.
2. Create a VLAN with LAN as the parent interface.VLAN tag as 2.
3. I don't know what's the next step. -
You shouldn't be doing this! :P
I've never done it even read about doing it with VLANs. I was just speculating if it might be theoretically possible.However after you have setup the additional VLAN interface and configured it's IP address and subnet then you should go to a client computer and try to set the VLAN tagging to match. I don't know how you would do that though.
You are then in the situation where you have both tagged and untagged traffic on the same interface which can result in problems.
It's an interesting exercise but you probably won't end up with a working configuration.
Steve
-
hahaha… that is what I'm thinking. hahaha
I thought you're going to give me a HOW-TO. ::) hahaha
Anyway, I'll try to experiment with this and maybe (maybe), I can solve my problem.(cross-fingers on both hands and feet).hahaha
THANKS A LOT FOR SHARING YOUR THOUGHTS/IDEAS. I've learned a lot from this.
-
Well.. I would continue with vlan capable switch and put this to side for waiting period. What kind of client devices you're having over there?
should you need also vlan capable wireless also?!?For a good practice you could draw couple of images: "What do I have now" and "What I want to achieve with changes"
Send those drawings us to view and the we might be able to give you precise enough answers for your investments
-
In case you're crazy enough to try this! Here's some instructions for WinXP:
http://www.formortals.com/implementing-vlan-trunking/
I think you need the right network card and probably Win XP Pro. It doesn't work on my one remaining Win XP Home machine. Here's something for Ubuntu if your using that:
http://ubuntuforums.org/showthread.php?t=703387If you added a VLAN interface on your LAN and then setup all your Group A clients to use it it would be very unlikely that any machine in group B would every connect to it. There would be nothing to stop a group B user from connecting (unless you have the machines locked down) it's just not something any normal person would look for. It's such an unusual network setup. However security through obscurity is not any real sort of security! ;)
It would still require all of your group A machines to be VLAN compatible.
Steve
-
Another idea that could be done without additional hardware:
Why not connect ALL users to the guest network and install an OpenVPN or IPSec client on the production machines.
…ok, if you have infrastructure they need to access (like servers...) then it's not the best idea. That has to be connected to a physical segment. Unless you're using VMs everywhere. -
I like that idea. Why could the server not be connected to pfSense via internal VPN also?
Perhaps you could run a VPN server on your LAN server machine instead and simply restrict access to it that way. Come to think of it there must be any number of ways you could restrict access to the server via authorisation.Steve
-
Now your making my brain bleed. ???
I will post tomorrow my setup for everyone's better understanding. Sorry if my posts were a little bit ambiguous.
The only reason that I want to separate Group B from A is to restrict B in accessing the file server in A.
All devices in B are wireless while in A are both wired and wireless. -
to restrict B in accessing the file server in A.
Access policy on the server? Pretty much standard in every server software I can think of.
VPN Clients:
- Make everyone a guest.
- Allowed users/PCs tunnel into your restricted network via an IPSec or OpenVPN tunnel.
That's how road warriors typically access resources back in the company. In your case just without the road. :D
-
Okay now we're going to make different kind of decision.
Do we manage acl in- firewall/router
- switches (vlan dividing)
- servers(ntfs kind of restrictions or fileshare restrictions)
- antivirus softwares
-
Sorry for the late reply. Here's my network diagram.
I want to separate Groups E and G from the rest of the network. I thought it was a simple job. ;D
 -
I thought it was a simple job. ;D
It can be. If you have lots of time you can spend instead of cash a number of other possible solutions could be explored.
Its a nice diagram but I find the text difficult to read even when magnified.
Based on the diagram I would recommend you consider only the following two options:
-
Replace one of the existing pfSense NIC by a multiport card, connect one card port to the existing switch (this becomes the pfSense LAN port) and connect another to a suitable sized (number of ports) switch (new switch to the configuration) and move groups E and G to that new switch.
-
Purchase a suitable sized VLAN capable switch, configure two VLANs on existing pfSense LAN interface, one VLAN for your existing LAN, one for the combined group E and G. On your VLAN capable switch configure the two VLANs, configure one switch port for connection to your existing LAN interface, one port for connection to the existing switch and other ports for connection to groups E and G.
If you want future flexibility go with 2) (for example, its easy to add a another VLAN so group E could have different firewall rules from group G). You might be able to save a little bit (unlikely to be much) by going with option 1
This might be a good time to recall the proverb "the devil is in the detail". The costs will be significantly affected by the number of computers in group E. If its two then a cheap 5 port VLAN capable switch will be sufficient. If its 24 then you will need a rather more expensive VLAN capable switch. The way you have drawn the diagram suggests there might be more switches than you have shown in which case implementing either solution might require new cabling which might be a non trivial installation task.
Its simple in concept.
-
-
Sorry for the diagram. You can check it here: http://i49.photobucket.com/albums/f297/jikjik101/NewNetworkDiagram-pfsense3.jpg
I want to use this one: Intel Pro/1000 MT Quad Port Server Adapter PWLA8494MT1000 (Intel
82546EB processor) http://www.ebay.co.uk/itm/NEW-Intel-PRO-1000-Quad-Port-Server-Adp-PWLA8494MT-/170262023800 of which my pfsense box is : Dell Vostro 220 Mini Tower http://www.dell.com/us/dfb/p/vostro-220/pd#TechSpec @wallabybob:
- Replace one of the existing pfSense NIC by a multiport card, connect one card port to the existing switch (this becomes the pfSense LAN port) and connect another to a suitable sized (number of ports) switch (new switch to the configuration) and move groups E and G to that new switch.
I'm confused with Number 2. Please see attached picture if I understand correctly your suggestion sir.
.jpg)
.jpg_thumb) -
You got it right.
-
I'm confused with Number 2. Please see attached picture if I understand correctly your suggestion sir.
You understand.
You diagram suggests group G has an access restriction schedule while group E doesn't. It could be convenient to put group E and group G on separate interfaces so you can use firewall rule schedules on group G.
-
This might be a good time to recall the proverb "the devil is in the detail". The costs will be significantly affected by the number of computers in group E. If its two then a cheap 5 port VLAN capable switch will be sufficient. If its 24 then you will need a rather more expensive VLAN capable switch. The way you have drawn the diagram suggests there might be more switches than you have shown in which case implementing either solution might require new cabling which might be a non trivial installation task.
Just some clarifications sirs. If for example I have 20 computers in group E and another 20 computers in group G, does it mean I need atleast a 40-port VLAN switch? Can't I use a normal switch to connect all my clients behind Group G and E?
Thanks for all your input. Maybe I am going to change the title of this thread to jikjik101's network, because I think I need more of your expertise to help me build my network in a sound technique and more appropriate methods.
Every now and then, some problems arise in my network and I am going to post it here so that I can access it easily. I hope the moderators don't mind if I am going to "own" this thread. ;D
.jpg)
.jpg_thumb) -
This is ONE of the concerns of my network. ;D
As you can see, I have three ISPs and they are in load balance mode. But I cannot "stabilize" my ISP1 and ISP3. The connections are so erratic that it becomes so hard to connect to the internet. Unlike my ISP2, the connection is so stable and so I just use the failover mode with ISP2 in tier 1 and both ISP1 and ISP3 in tier2.
If I assign my whole network in using just one ISP, it is stable.
I already tried the following:
1. Assign an ISP as default gw
2. Not assigning a default gw
3. Check the "allow default gw switching"
4. Uncheck the "allow default gw switching"
5. Set each GW with maximum and minumum latency % base on its RRD.I have squid, squidguard, lightsquid, lusca-cache, havp, vnstat2 and bandwidthd.
I cannot fully utilize all my ISPS, it seems ISP2 is doing the hardwork. >:( and the rest are just easy-go-lucky ISPs. :-X


-
With those rules and gateways I would expect almost all traffic to using be using ISP2, and it is.
This is because most of your traffic is caught by the first rule as it's web traffic. Only non-webtraffic is reaching the second rule where it is shared between ISP1 and 3 as they are both in the same tier.
You need to change the gateway to loadbalance on the first rule if you want to see the traffic more evenly distributed.There is no need (or harm) to use tier5 in your load balancing rule. The importance of each connection is relative within the gateway and not related to the other gateways. If you had all three at tier1 it would be the same. The same applies to your failover3 gateway.
You can use a normal switch behind your VLAN switch to connect your clients.
Steve
-
Maybe I am going to change the title of this thread to jikjik101's network, because I think I need more of your expertise to help me build my network in a sound technique and more appropriate methods.
Every now and then, some problems arise in my network and I am going to post it here so that I can access it easily. I hope the moderators don't mind if I am going to "own" this thread. ;D
You might find it more workable to have as few topics as possible per thread: that is make a new thread for a new issue.
If for example I have 20 computers in group E and another 20 computers in group G, does it mean I need atleast a 40-port VLAN switch? Can't I use a normal switch to connect all my clients behind Group G and E?
Maybe I've missed something. The 40 is from 20 in group E + 20 in group G? But your diagram shows group G as WiFi clients connecting to an Access Point. The AP would use one port on a switch (VLAN or non-VLAN). The 20 computers in group E would use 20 ports in a switch (because they are shown as using wired connections) unless they are connected to another switch.
-
@stephenw10: sorry for not being clear. The fw and gw pictures that I posted are my current setup as a solution to my erratic loadbalance on ISP1 and ISP3. That is only to utilize my my ISP1 and ISP3 because they are not stable if I use the LoadBalance gw.
You are correct that my webbrowsing enters ISP2 and the rest to my Failover GWs. That is my current setup. i forgot to disable the first two rules when I took the screenshots.
But the erratic connection that I am talking about is when I use the LoadBalance gw and disabling the first two fw rules leaving this one alone active:
-
-
-
-
- LoadBalance none
-
-
-
I only use the default LAN rule with LoadBalance as gw, disable/remove other rules except the Anti-lockout but same results.
@wallybob:
The way you have drawn the diagram suggests there might be more switches than you have shown in which case implementing either solution might require new cabling which might be a non trivial installation task.
I remove some switches in the diagram because I don't find it essential for the network diagram. sorry, my bad.
The 40 is from 20 in group E + 20 in group G? But your diagram shows group G as WiFi clients connecting to an Access Point. The AP would use one port on a switch (VLAN or non-VLAN). The 20 computers in group E would use 20 ports in a switch (because they are shown as using wired connections) unless they are connected to another switch.
Actually I have more than 200 computers behind Group E and Group G. Group G atleast 100 WiFi clients and Group E another 100 both Wired And WiFi clients.
You can use a normal switch behind your VLAN switch to connect your clients.
I think stephenw10 already answered my clarification regarding a LAN switch behind a VLAN switch.
I'll go back to my concern, I use the default LAN fw rule with LoadBalance as my gw, leaving my LAN rule as follows:
* * * LAN Address 22 * * Anti-Lockout Rule
80
* * * * * LoadBalance none Default allow LAN to any ruleBut I cannot utilize my ISP1 and ISP3 because they just suddenly drop my connection, or worse they cannot get the maximum bandwidth even if I bombarded my system with lots of video streaming.
-