pfSense English Support > General Questions

Proper setup of switches

(1/3) > >>

kcallis:
I am using a Netgate APU with three interfaces:

WAN (re1) -- DHCP
LAN (re2) --  192.168.4.1/24
OPT (re0) --  VLAN05 (re0.5)    --> 192.168.5.1/24
                    VLAN10 (re0.10)  --> 192.168.10.1/24
                    VLAN15  (re0.15) --> 192.168.15.1/24
                    VLAN20  (re0.20) --> 192.168.20.1/24

I have used the baseline guide along with nguvu's guide to making use of the Netgear GS108E switch (although, I am actually using a Tl-Link SG108E), but somewhere I am blowing it, since after I reboot, I am not able to access any of the interfaces and I have to do a factory reset.

I have connected my LAN interface as well as my OPT interface on the switch and have set the address to 192.168.5.2 (which is my MGMT VLAN05). I also have my Ubiquiti NanoStation connected to the switch (192.168.5.5). I have tagged port 2 on the switch with my VLANS 5-20 as well as port 3 as well (which is connected to the Ubiquiti NanoStation with the VLANs configured on the NS). If I am clear then the remaining ports should be untagged. But once I reboot the APU, I am not able to connect to any port.

I have a second switch, the Netgear GS108E. I am wondering if since I have the first switch set to the 192.168.5.0/24 but I have the LAN interface, plugged into the same switch, is that what might me causing the fact that my LAN interface is conflicting with the OPT interface on the same switch? Maybe I need to plug the LAN interface into the second switch?

Any pointers would be appreciated!





Derelict:
Well you would really have something like this:


WAN (re1) -- DHCP
LAN (re2) --  192.168.4.1/24
OPT1 (re0.5)   VLAN05 --> 192.168.5.1/24
OPT2 (re0.10)  VLAN10 --> 192.168.10.1/24
OPT3 (re0.15)  VLAN15 --> 192.168.15.1/24
OPT4 (re0.20)  VLAN20 --> 192.168.20.1/24


The switch port connected to re0 would have to have VLANs 5, 10, 15, and 20 TAGGED on that switch port.

kcallis:

--- Quote from: Derelict on January 01, 2018, 07:52:52 pm ---Well you would really have something like this:


WAN (re1) -- DHCP
LAN (re2) --  192.168.4.1/24
OPT1 (re0.5)   VLAN05 --> 192.168.5.1/24
OPT2 (re0.10)  VLAN10 --> 192.168.10.1/24
OPT3 (re0.15)  VLAN15 --> 192.168.15.1/24
OPT4 (re0.20)  VLAN20 --> 192.168.20.1/24


The switch port connected to re0 would have to have VLANs 5, 10, 15, and 20 TAGGED on that switch port.

--- End quote ---

I cleaned up my original posting. I have the trunk on port 2 with all of the VLANS as well as with port 3.

JKnott:

--- Quote ---(although, I am actually using a Tl-Link SG108E)
--- End quote ---

Bad choice.  TP-Link switches don't handle VLANs properly.  There's another thread about problems with the similar SG105E.

kcallis:

--- Quote from: JKnott on January 01, 2018, 09:48:40 pm ---
--- Quote ---(although, I am actually using a Tl-Link SG108E)
--- End quote ---

Bad choice.  TP-Link switches don't handle VLANs properly.  There's another thread about problems with the similar SG105E.

--- End quote ---

Well, I have Netgear GS108E v2 (which is why I was using the TL-Link because of being able to access via the web interface as opposed to the configuration program for the v2) or a Mikrotik Routerboard RB951Ui (which I really didn't want to mess with because of the learning curve). Would any of these work better?

Navigation

[0] Message Index

[#] Next page

Go to full version