That may not be a concern in your setup, but it gives unintended consequences regardless. If your switch loses its config or is reset to defaults all of the ports will gain membership in VLAN 1 and inadvertently put any clients that attach to the switch on your 10.0.1.0/24 network. In fact it looks like you are pretty close to creating a loop since you have VLAN 1 assigned to both ports 51 and 52.īest practices say don't use VLAN 1 specifically because it is the default VLAN. A loop will cause a broadcast storm and bring your network down.
Spanning Tree Protocol should guard against this if enabled and configured properly but the chance exists.
This is because of what frennzy said about potentially creating a bridging loop if misconfigured. I would use a single connection and trunk all of your Vlans on it, unless you want to use a LAG. Of course if I did that, I could probably just use the single LAN port on my router since I seem to be able to trunk all the other vlan traffic over port #52 without difficulty.Īgain, thanks for all the help and I do appreciate everyones patience, especially Frennzy, who I know is very active in helping out on this forum. Jelloman's reply above mentions that I shouldn't use the default vlan 01, which I can certainly try, but I don't understand the reason why I shouldn't. I've tried tagging port 51 for the default vlan 01, but then none of the machines on vlan 01 have connectivity. On my switch, ports 51 goes to the LAN port (the default vlan 01) and port 52 goes to the OPT port and carries all the VLAN's, which from the sounds of it, it the so-called trunk. Here's what I ended up with and it works and sort of makes sense to me:
WINDOWS ETHERNET TESTING TOOLS 802.1Q PRO
I'm not a network guy, I'm a physician, and as any IT pro can tell you, doctors are largely computer idiots. But I would highly recommend you pursue the first thing and don't bother with the second thing unless you want dual links to a server or something.įirst off, I'd like to really thank all of you for helping me figure this out.
WINDOWS ETHERNET TESTING TOOLS 802.1Q MANUAL
You'll have to consult your manual on what your switch interface means. This pretty much always requires special config and protocol support on both ends (the switch and whatever it connects to, another switch, a server, etc.) to be worth the effort. On many other brand switches, 'trunking' is the name for 'bonding' 2 or more physical links into one logical link and doing some kind of load sharing or at least failover between the associated physical links. In most implementations, this is normally VLAN 1 out of the box but it is almost always a good idea to change that setting. Both devices can also have a default/native/private VLAN assigned that is the VLAN used for untagged frames that arrive. When they arrive at the other end, the device on that end also needs to read those tags and filter the frames into their corresponding VLANs (if they exist on the other end). In the Cisco world and some others, 'trunking' is passing multiple VLANs on one physical/logical link by tagging frames as they are sent out of the port so that the Ethernet frames are identified as being part of a specific 802.1q VLAN. This is the nasty part when dealing with varying switch vendors. Keep in mind that I'm not an IT professional, so any explanations will have to be in laymans terms. I power cycle them etc and they don't get an IP address from the VLAN (10.0.2.0/24).Īt this point, I've watched several youtube video's of people setting up VLAN's on Pfsense as well as searched the pfsense forums, but I'm beginning to wonder if my cheap-ass switch simply doesn't work correctly. What is happening is that the devices on the VLAN tagged ports keep pulling IP addresses from the 10.0.1.0/24 address range.
Tagged them as 10, and then in pfsense, created the VLAN also with #10 and tried using both my LAN port as a parent, and when that didn't work, the unused OPT port.īoth times, I set the IP address of the VLAN to 10.0.2.0/24 and enabled the DHCP server. I made a new VLAN on the switch with a few of the ports. All the ports in the house work just fine on the 10.0.1.0/24 network. The whole network works fine if I use it as a dumb switch. Here's my network in all glory that Sharpie can offer: