How I can assign same vlan to multiple interfaces
-
@KpuCko said in How I can assign same vlan to multiple interfaces:
@NogBadTheBad said in How I can assign same vlan to multiple interfaces:
vlan X on your LACP trunk wouldn't be the same vlan X on another router port.
Hm why not? The vlan tag is what all are interested in, so using same vlan tag, will carry same data. Or I have misunderstanding.
pfSense is a router not a switch that's why, same with a Cisco router if you created a subinterface on g0/0.101 and g0/1.101 it would tag the packets as vlan 101 but they are two independent interfaces.
The packets may contain the same vlan tag but they are on a different broadcast domain.
-
@NogBadTheBad said in How I can assign same vlan to multiple interfaces:
@KpuCko said in How I can assign same vlan to multiple interfaces:
@NogBadTheBad said in How I can assign same vlan to multiple interfaces:
vlan X on your LACP trunk wouldn't be the same vlan X on another router port.
Hm why not? The vlan tag is what all are interested in, so using same vlan tag, will carry same data. Or I have misunderstanding.
pfSense is a router not a switch that's why, same with a Cisco router if you created a subinterface on g0/0.101 and g0/1.101 it would tag the packets as vlan 101 but they are two independent interfaces.
The packets may contain the same vlan tag but they are on a different broadcast domain.
Good. Many thanks for the clarification.
I really needed to understand how this works. -
@KpuCko said in How I can assign same vlan to multiple interfaces:
In the Cisco world is much easier,
Yup, that's only true in the world of Cisco switches.
Steve
-
I'm looking for basically the same thing.
Best I found was simple bridge vs assigned bridge
https://www.netgate.com/resources/videos/wireless-access-points-with-pfsense.html
around 38min markbut I'm not having much luck with it
-
Yeah, as discussed, you need to bridge them but don't if you have any other option!
-
@stephenw10 from what I'm getting here, it's worse than not being ideal... Bridging is broken/not even an option
-
Between VLANs it may be. I don't ever seen one in reality.
-
Just shooting in the dark, but I'm wondering how hard can be to implement Open vSwitch in pfSense?
-
This post is deleted! -
@mackjone said in How I can assign same vlan to multiple interfaces:
You can't traverse the equivalent vlan over different switch ports, vlan X on your LACP trunk wouldn't be the equivalent vlan X on another switch port.
Sure I've got it, so how they do it?
For example:In Mikrotik you can create a bridge, then create all the vlans you need to work with, and set it as follow:
vlans: 1,2,3 should be tagged on port 2,4,5
vlan: 4, should be untagged on port 1,3,5We already discussed Cisco, and how they do it.
The question is what they use under the hood? -
You can bridge in pfSense, I’d advise against it.
FYI Open vSwitch isn’t a pfSense thing.
https://docs.netgate.com/pfsense/en/latest/bridges/index.html
-
johnpoz LAYER 8 Global Moderatorlast edited by johnpoz Oct 21, 2020, 12:26 PM Oct 21, 2020, 12:20 PM
@KpuCko said in How I can assign same vlan to multiple interfaces:
afterwords vlan support for bridge was invented and Mikrotik implemented
What specific mikrotik are you talking about? For example many of their devices have built in switch. Not discrete interfaces.
I fail to understand why users continue to insist on forcing the square block into the round hole.. If you want a switch in your router, then get hardware that does that. There are few models of netgate boxes that have switches built in.
While bridging has its uses sure.. But your desire to use a interface port as a switch port via bridging is not one of them..
If you want a switch, use a switch.. If unused ports on your router are driving your OCD into overdrive. Use them in a lagg, or use them as intended, and actual interface for network(s) you want to route.
If you want all your ports to be used for all your vlans to quiet your OCD of seeing a port with nothing in it.. Then put them all in a lagg, and throw your vlans on the lagg..
-
again total n00b here but I thought the whole point of these intel dual/quad port NICs was that they ARE switches... Are they not?
(check out schematic layout):
options list according to ifconfig:
RXCSUM, TXCSUM, VLAN_MTU, VLAN_HWTAGGING, JUMBO_MTU, VLAN_HWCSUM, TSO4, TSO6, LRO, VLAN_HWFILTER, VLAN_HWTSO, RXSUM_IPV6, TXSUM_IPV6I'm not trying to be difficult... Just trying to learn.
-
@OGsadpanda said in How I can assign same vlan to multiple interfaces:
ntel dual/quad port NICs was that they ARE switches... Are they not?
No they are not switches... They are 2 or 4 discrete interfaces on the same card.. Not switches..
-
I know some of the models has a switch built in, but not all of them.
So some of the processing power is handled by the main processor, but the other one by the switch processor and so on. But nevermind.
My thoughts are I expect to be able to do switching and routing with one device, but it seems this doesn't apply here.
-
@KpuCko said in How I can assign same vlan to multiple interfaces:
My thoughts are I expect to be able to do switching and routing with one device
You can - just get a box that has switch ports in it, that does routing.. SG3100 has switch ports, the new sg2100 has switch ports. The 5100 for example does not..
My sg4860 does not.. I didn't want switch ports on it, because switching should be done on your "switch" ;) Not your router..
Keep in mind that with routers with switches, the uplink into the routing is going to be limited.. Look at the above block diagrams for example.. Notice the 1gbps and 2.5gbps uplinks from the switches..
The proper tool for the job.. Do you go buy the hammer at the store, when you need to hammer in a nail? Or do you pound on nails with your screwdriver?
Switches are not expensive these days... You could pick up a 8 port gig smart switch for like $40.. Or get a 16.. Or 24 if what you are after are switch ports. I would always suggest if you think you need a 5 port switch, get an 8 or 16.. That way when your needing another port - you don't start eyeing your router interfaces thinking you can use them as switch port ;)