Initial Configuration

Coop59

@stephenw10

Each host is configured like this (above)

The Main Switch:

VLan 1

Vlan2

Vlan3

I think that should be enough to give you an idea. Thank you in advance for your time.
Michael

stephenw10

OK, so which switch ports are the NIXs in Proxmox from each bridge connected to?

Where are the hosts connected that cannot communicate?

Coop59

@stephenw10
Hey Stephen,

Thank you for responding sorry I was busy at work all week. Just now seeing this.
Port 12 is the trunk port to the unmanaged switch and the PVID is 3, and the Promox hosts are connected to 11,12,13,15 and the PVIDs are 2.

Now with that said the 3rd Nic in the Proxmox hosts are physically plugged in to ports 1,2,3,4 of the unmanaged 2.5 gb switch. They talk to each other fine I can ping host1 from host2, host3 amd so on and vice-versa. However I get a failed response when I ping pfsense at .3.0/24 network (Vlan3). Just an fyi it does ping itself successfully (pfSense I mean). Oh, and I can ping .3.1 (pfSense) from my workstation which is on .2.0/24 network. So I am trying to figure out where the disconnect is. I create a rule in the firewall from the lan to the wan and I also created a rule from the lan to the lan as well and it still is not working.

I hope that explains it better.

Thank you again,
Michael

P.S. @johnpoz @stephenw10 Thank you sincerely for helping I appreciate you guys. Since my last post I have bought a Managed Multi GB router that has 8 access ports and one uplink port. A Cheap one but I am learning when I get good at this I will buy a nice one.

stephenw10

@Coop59 said in Initial Configuration:

Port 12 is the trunk port to the unmanaged switch

You mean port 19? That's the only trunk port shown in the screenshots.

All 3 VLANs are untagged on port 12 which is odd. You would normally only ever have one VLAN untagged on a port and that should match the PVID in order to pass traffic both ways.

You have 4 Proxmox hosts? With VMs on each?

I think a diagram may help here.

johnpoz

@stephenw10 said in Initial Configuration:

All 3 VLANs are untagged on port 12 which is odd.

Odd is the wrong word, borked is the word your looking for ;)

You can't run multiple untagged vlans on same port and expect something to figure out what traffic is what..

stephenw10

I mean... there are some scenarios where that's legitimate but.... probably not this one!

Coop59

Hello Guys,

I will try and make a map of the way I have it now. So I may have misunderstood what a trunk was I thought a Trunk could be tagged or untagged and an untagged trunk goes to an unmanaged switch. Tagged is suppose to be an uplink and a port for all tagged traffic to communicate with the switch upstream from it.

Is this understanding incorrect?

Thank you,
Michael

Coop59

@stephenw10
I believe you are correct in your response. Unfortunately I suck at networking. I have a friend who is a network guru but I can't pin him down because facebook is running him ragged right now.

Thanks again sir,
Michael

johnpoz

@stephenw10 said in Initial Configuration:

. there are some scenarios where that's legitimate but.

Yeah I have seen them setup, many an ISP run multiple layer 3 on the same layer 2... If your in the process of transition from one ip range to another IP range, etc..

But if your goal is to create 3 different vlans, just running multiple layer 3 on the same layer 2 is borked way to go about it.

stephenw10

Trunk is actually a Cisco term but is commonly used to refer to a link that carries more than one VLAN. A trunk can carry tagged and untagged traffic but in order to keep them separated only one VLAN can be untagged.