Ispánovits Imre wrote:
This switch is a 24 ports one, which can be configured to 6x4 trunks. So I
guess I have to set max. 3 vlans on a NIC in pfSense and connect it to a
trunk on the switch, 3 free ports in the trunk can then be used to connect to
the different nteworks. Or am I wrong?
Wrong :-)
You are victim of the original interpretation of the same terms that
it's done by the switch manufacturers.
In Cisco-world, a trunk port is one where packets belonging to multiple
VLANs are flowing, each one tagged with the related VLAN id (in simple
words, an additional 16 (??) bit integer is added to the ethernet
header: the VLAN TAG, tying each packet to its VLAN)
Other vendors (I know Allied Telesyn for first hand experience, from
your words DLink must be usin the same glossary) define trunk an
aggregation of more than one physical port, used to increase the
bandwidth of a single link. In these switches the Cisco's 'trunk' ports
are instead defined (I think more correctly) 'tagged' ports.
The NIC (or NICs) where you define VLANs on in pfSense, must be
connected to a port on your switch which is a 'tagged' member of those
same VLANs. I mean: if you define three VLANs with tags 3,4,5 on your
xl0 interface, you must define VLANs with the same tags on the switch,
and define at least one port belonging to the three as a tagged port, to
which you will connect the cable from your xl0 interface.
Keep also in mind that it's better not to use a NIC where you define
VLANs also as an untagged port (in my previous example, never use the
xl0 interface directly, but only the vlanX that you will get).
Hope this helps
Angelo.
Modena - Italy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
