Extreme Networks

Jeremy_Martin · 03-25-2015

I currently have a Summit 400 48t switch that is behind a PFsense firewall. My PFsense firewall has 3 network cards in it two of which are connected to the switch. One is for the LAN (192.168.1.0) and the other is for the DMZ (192.168.2.0). I have...

Jeremy_Martin · 03-25-2015

I have no idea why though. I had Port 33 untagged originally. Probably something configured wrong on the PFsense FW when I had it untagged and through the grand scheme of trying to fix it i might have fixed that issue but screwed up something else....

Jeremy_Martin · 03-25-2015

Paul thank you for the help! What you said makes perfect sense. Port 5 though wasn't the one that needed untagged. Port 5 is an aggregate link with 6. It is the one going to my vm server that needed to be on both vlan 1 and 2. However port 33 ...

Jeremy_Martin · 03-25-2015

From the Switch: Summit400-48t:32 # ping 192.168.1.1Ping(ICMP) 192.168.1.1: 4 packets, 8 data bytes, interval= 1. 16 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=0 ms 16 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0 ms --- 192.168.1.1 ping sta...

Jeremy_Martin · 03-25-2015

Ty for the reply Paul. I think I might have confused it a bit  let me see if i can state my end goal better. Default Vlan switch IP 192.168.1.2 DMZ Vlan switch IP 192.168.2.2 PFsense IP for Default to reach 192.168.1.1 PFsense IP for DMZ to reach...

Jeremy_Martin · 03-25-2015

I just actually tagged all the DMZ ports on the switch right before i made this post in hopes it helped the issue. Prior to that all the ports in the DMZ, except for 5, were untagged. 5 has to be tagged because its in VLAN 1 and 2 and it houses my ...

Extreme Networks

User Statistics

User Activity

VLAN routing to wrong IP

RE: VLAN routing to wrong IP

RE: VLAN routing to wrong IP

RE: VLAN routing to wrong IP

RE: VLAN routing to wrong IP

RE: VLAN routing to wrong IP