I successfully have two vlans running over one physical interface
connected to my managed switch (a PowerConnect 5224), but I can't get
the same two vlans to work when running over a trunk interface spanning
four physical interfaces.
Before: (this works, but only uses one physical interface)
---------
# cat hostname.gem0
inet xx.xxx.xxx.x 255.255.255.0 NONE [public ip masked]
# cat hostname.hme0
up
# cat hostname.vlan2
inet 10.0.2.1 255.255.255.0 NONE vlan 2 vlandev hme0
# cat hostname.vlan3
inet 10.0.3.1 255.255.255.0 NONE vlan 3 vlandev hme0
After: (this doesn't work)
--------
# cat hostname.gem0
inet xx.xxx.xxx.x 255.255.255.0 NONE [public ip masked]
# cat hostname.hme0
up
# cat hostname.hme1
up
# cat hostname.hme2
up
# cat hostname.hme3
up
# cat hostname.trunk0
trunkproto roundrobin trunkport hme0 trunkport hme1 trunkport hme2
trunkport hme3
# cat hostname.vlan2
inet 10.0.2.1 255.255.255.0 NONE vlan 2 vlandev trunk0
# cat hostname.vlan3
inet 10.0.3.1 255.255.255.0 NONE vlan 3 vlandev trunk0
Assuming all looks good above, the changes I made on the switch were:
- create a bogus vlan (id 1111)
- make the four ports untagged members of vlan id 1111
- remove the four ports as members of vlan id 1
- make the four ports be members of trunk 1
- make trunk 1 tagged member of vlans 2 and vlan 3
But no traffic gets through. For instance, ssh-ing through the firewall
and switch to target results in "Network is unreachable" during which
pflog shows a match for "pass out on vlan2"; `tcpdump -n -i trunk0`
shows nothing; `tcpdump -n -i vlan2` shows nothing; heck, even `tcpdump
-n -i hme0` shows nothing. Likewise, `tcpdump` on the target shows no
traffic.
Any ideas?
Thanks,
Kent
