XG-7100: multiple VLAN interfaces on single physical port
-
I don't see a pfSense interface for WAN2 (4092).
It is normal to see checksum errors when checksum offloading is enabled because at the point of the pcap the checksum has not been calculated yet since it's done by the ethernet hardware.
You might have to explain what exactly isn't working at this point if you want more directed feedback.
-
Yes, WAN2 is not being used yet.
What exactly isn't working? None of the VLAN (11-14) interfaces can reach the net, in any direction. On those interfaces, any traffic originated on the host or directed to it seems to die on the physical port. Looks like a disconnected port.
On SG-8860, with the same setup (4 VLANS on a physical port), with the same rules and same configuration on the switch port it's connected to (tried 2 different switchs so far), it works as expected.
I never had this problem before. Just setting up XG-7100 to be a CARP backup node, the other interfaces work just fine, but can't get VLAN interfaces to work. I don't know if I'm missing something about how the new "switch interfaces" work, just not sure what else to try.
Thanks
-
Can you ping the closest interface address?
Did you add firewall rules? Did you check outbound NAT?
-
What is the configuration of the switch connected to port 4?
-
Yes, all that. I also captured traffic but nothing shows on those interfaces. Examples:
Host A (8860) 192.168.14.10 (VLAN14)
Host B (7100) 192.168.14.11 (VLAN14)- If I ping from host A to B, I can see icmp traffic coming out from A, and nothing getting to B (it works OK with any other host on the net)
- If I ping from host B to A, I can only see ARP traffic coming out from B, asking for B's MAC (it doesn't work pinging any other host on the net)
- If I capture packets on VLAN interface 14 on B, I don't get any broadcast from the network either. I see VRRP coming out, but not getting to B or the net
Config on the switch: it's a trunk port, PVID 1, tagging all VLAN's. I use the same switch port configuration with the physical port I use for VLAN's on 8860, and it works!
Also tried setting port ETH5 as untagged VLAN 14, on an untagged switch's port, and works OK. So it's not a switch trunking or firewall rules issue
-
Just for the record. I finally found the cause of this: the interface was connected to the wrong switch port. It's hard to spot things like this when working remotely, but that was the problem.
Thanks anyway for your help
-
Thanks for letting us know.
-
@maliaga Hi, how can you have vlan 4091 AND vlan 11 on the same ETH2 port?
-
@nick-loenders said in XG-7100: multiple VLAN interfaces on single physical port:
@maliaga Hi, how can you have vlan 4091 AND vlan 11 on the same ETH2 port?
Tagged or untagged?
-
@derelict I don't fully understand the difference.
Basically I want one network cable connected on one port , eg ETH2 and pass two vlans on it, the 4091 (LAN) with DHCP 10.0.0.0/24 and the vlan 70 (VLAN) with DHCP 192.168.70.0/24
Problem is, I could connect the LAN on ETH2 and the VLAN 70 on ETH8 so with two cables to the first switch, but there is only 1 cable going from the first switch to the second at this time :(
-
@nick-loenders But you need to say whether you want one VLAN untagged and one tagged or both tagged (both cannot be untagged on the same port so that is not an option). It depends on how the device you are connecting to that port is configured.
-
-
@nick-loenders And then it went quiet :)
-
@nick-loenders Considering this is in Off-Topic and Non-Support Discussion I would expect it to get lost.
You still didn't specify what you wanted tagged and untagged and where.
How is the switch port connected configured?
-
@derelict Well as far as I understand tagged and untagged I would say the vlan 4090 (which is the normal LAN) is untagged and vlan70 is tagged??
-
@nick-loenders VLAN 70 is untagged on port 8. The switch port on the 7100 needs to match the switch port it is patched to. It's just like any other external switch with a pfSense lagg connected to it as a "trunk" link.
