Re: Trunk(4), vlan problems
Hi, I'm trying to set up an OpenBSD router against two switches (failover solution), the switches have a cable between them. em0 - connects to switch01 port 1 (switch01 addr: 10.10.1.18) em1 - connects to switch02 port 1 (switch02 addr: 10.10.1.19) switch 1 and 2 has a management vlan tagged on port 1 Now if i create vlan1 and use em0 as vlandev i can ping both switch01 and switch02, but if i create a failover trunk with em0 and em1 and use trunk0 as vlandev is don't work trunk0: flags=8802 mtu 1500 lladdr 00:0e:0c:db:3f:48 trunk: trunkproto failover trunkport em1 trunkport em0 master groups: trunk media: Ethernet autoselect status: active vlan1: flags=8843 mtu 1500 lladdr 00:0e:0c:db:3f:48 description: VLAN 1, Management vlan: 1 priority: 0 parent interface: trunk0 groups: vlan inet 10.10.1.17 netmask 0xfff0 broadcast 10.10.1.31 inet6 fe80::20e:cff:fedb:3f48%vlan1 prefixlen 64 scopeid 0xe If i ping the openbsd machine from the switch and listen on the trunk0 interface i see this: 23:21:18.907451 802.1Q vid 1 pri 0 arp who-has 10.10.1.17 tell 10.10.1.18 but if i listen to vlan1 that is connected to trunk0 i don't see any traffic. What am I doing wrong? Best regards Fredrik Carlsson I did some more testing, If i drop the tagging in the interfaces on the switch against the openbsd machine and use them as ordinary ports and assign an IP addr to trunk0 everything work fine. The switches has a vlan-trunk between them so that works as well. I unplugged the interfaces in trunk0 to test the connectivity between the switches and everything works. The problem seems to be when i attach a vlan to trunk0, the traffic don't go to trunk0. The vlan config works when I'm not using trunk(4), can this be a bug in trunk(4)? Any ideas?
Re: Trunk(4), vlan problems
On 2007/07/03 11:48, Fredrik Carlsson wrote: trunk0: flags=8802 mtu 1500 vlan1: flags=8843 mtu 1500 this is strange, where is the decode of the flags? In-Reply-To: [EMAIL PROTECTED] ahh... perhaps your mail client ate them. anyway, 8802 means your trunk0 is not ifconfig'd up.
Re: Trunk(4), vlan problems
On 2007/07/03 11:48, Fredrik Carlsson wrote: trunk0: flags=8802 mtu 1500 vlan1: flags=8843 mtu 1500 this is strange, where is the decode of the flags? In-Reply-To: [EMAIL PROTECTED] ahh... perhaps your mail client ate them. anyway, 8802 means your trunk0 is not ifconfig'd up. Thanks, up was missing, it is working now. I replied from another computer so i copied the text into a webclient. // Fredrik
Trunk(4), vlan problems
Hi, I'm trying to set up an OpenBSD router against two switches (failover solution), the switches have a cable between them. em0 - connects to switch01 port 1 (switch01 addr: 10.10.1.18) em1 - connects to switch02 port 1 (switch02 addr: 10.10.1.19) switch 1 and 2 has a management vlan tagged on port 1 Now if i create vlan1 and use em0 as vlandev i can ping both switch01 and switch02, but if i create a failover trunk with em0 and em1 and use trunk0 as vlandev is don't work trunk0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 lladdr 00:0e:0c:db:3f:48 trunk: trunkproto failover trunkport em1 trunkport em0 master groups: trunk media: Ethernet autoselect status: active vlan1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:0e:0c:db:3f:48 description: VLAN 1, Management vlan: 1 priority: 0 parent interface: trunk0 groups: vlan inet 10.10.1.17 netmask 0xfff0 broadcast 10.10.1.31 inet6 fe80::20e:cff:fedb:3f48%vlan1 prefixlen 64 scopeid 0xe If i ping the openbsd machine from the switch and listen on the trunk0 interface i see this: 23:21:18.907451 802.1Q vid 1 pri 0 arp who-has 10.10.1.17 tell 10.10.1.18 but if i listen to vlan1 that is connected to trunk0 i don't see any traffic. What am I doing wrong? Best regards Fredrik Carlsson
