Search results for query: *

I hate to admit this, but the root of all my issues ended up being an unmanaged PoE switch I had been using being connected to my Nortel. Two ports actually. I basically started from scratch, port by port until I saw what connection brought the whole thing down. Sheesh. Time for a beer.

Yep. I think there's something with VLAN1 that I'm just going to have to face the music and build out a specific VLAN. I'm trying to figure out a way to get rid of VLAN1 on the switch, and just move it's management IP over to another VLAN, like VLAN101. But then, all traffic that all the...

Using the settings I outlined above, I just migrated 17 of my 25 devices, and something still isn't right with VLAN1. If I remove port 1 from VLAN1, change the default to VLAN20, then VLAN20 works (gets DHCP from VLAN20 DHCP Server, can browse web, etc..). The minute I associate VLAN1 with the...

I really must have goofed up on describing the LAN interface's functionality :( sorry about that. I don't know why I would do that since I don't think I can setup the LAN physical interface as a VLAN in pfSense. Setting the VLAN assignments how you have it listed replicates exactly how I want...

Hmm...that was the only thing I could think of for the reason as to why setting port 1 as tagAll(trunk) would kill everything but VLAN10/20. For clarity, can you relist how you would setup my port tag assignments with the pfSense interfaces of WAN/LAN (all normal traffic)/VLAN10 (segmented from...

Eeek...sorry for the confusion. This is how I have had pfSense setup for a long time and would like to keep it that way. WAN (obvious) LAN (everything not in VLAN10 or VLAN20) VLAN10 - segmented traffic from LAN VLAN20 - segmented traffic segmented traffic from LAN

I didn't mention it, but I really removed VLAN1 off of all ports. No worries, I just readded it via the console menu. I've got a little bit of work to do here in the next couple hours, but will reconnect pfSense back to this and will remove VLAN1 off on every port but port 1 and see if that...

Basically I accidentally took VLAN1 off port 1, so I lost communication with it's management web interface. I was trying to eliminate VLAN1 from all other ports it had been applied to so I could see if those ports' functionality returned.

Bit myself in my own rear end while waiting to hear back from you. About to head down and get into the switch's console and resetup it's management IP. At any rate, yes I use the LAN interface a lot. That is the majority of my home network. I don't think I have any use for an explicit VLAN1...

No I only have a WAN & LAN interface outside of my two other interfaces. It almost sounds like the Nortel is explicitly using VLAN1 and needing it configured in the router in order to handle that traffic. Which, if true, is something I would have never thought coming from my Netgear. Can I...

You bet. VLAN in pfSense configuration: How the Netgear Smartswitch is setup (and working): VLAN1 VLAN20 (disregard VLAN10 in the pic, it's been changed to 20 long ago)

So the question is, if I set up port 1 as tagAll, all network connectivity dies. Only the untagPvidOnly or untagAll options on port 1 let network communication work. If untag options on Port 1 are set, port 25/VLAN20 as tagPvidOnly won't work still, but VLAN1 (my normal prod vlan) works.

Hopefully someone can chime in, as it's one of the last pieces of the puzzle before I do the flip to to the Nortel. I currently have 2 VLANs setup in pfSense & a Netgear GS724v3 switch. So, in the Netgear web interface, I have the uplink port of my pfSense router as a tagged port on each of...