Hello, Look at attachment for description of the problem.
Thank you. -- Best regards, Alexander Okonnikov
Hello,
It seems that new bug has been introduced in OpenBSD 5.6.
Two hosts are connected to each other via link. Each host is configured with
VLAN 100 on this link, which is bridged with vether interface via bridge
interface, as follow:
[vether100 - bridge100 - vlan100 (em1)] ---- link ---- [vlan100 (em1) -
bridge100 - vether100].
Bug is when OpenBSD 5.6 sends packets from vether interface, they are going out
untagged from em1 interface whereas should going out tagged via vlan interface.
There is no such problem in OpenBSD 5.5
Follow are the two examples with ping from one system to another.
1) Ping from OpenBSD 5.5 to OpenBSD 5.6
# ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1): 56 data bytes
--- 192.168.100.1 ping statistics ---
56 packets transmitted, 0 packets received, 100.0% packet loss
#
OpenBSD 5.6
# tcpdump -i vlan100 -ne
tcpdump: listening on vlan800, link-type EN10MB
03:47:16.342272 02:00:13:01:01:00 ff:ff:ff:ff:ff:ff 0806 56: arp who-has
192.168.100.1 tell 192.168.100.2
03:47:16.342580 02:00:11:01:01:00 02:00:13:01:01:00 0806 56: arp reply
192.168.100.1 is-at 02:00:11:01:01:00
03:47:17.344637 02:00:13:01:01:00 ff:ff:ff:ff:ff:ff 0806 56: arp who-has
192.168.100.1 tell 192.168.100.2
03:47:17.344869 02:00:11:01:01:00 02:00:13:01:01:00 0806 56: arp reply
192.168.100.1 is-at 02:00:11:01:01:00
# tcpdump -i em1 -ne
tcpdump: listening on em1, link-type EN10MB
03:47:16.342191 02:00:13:01:01:00 ff:ff:ff:ff:ff:ff 8100 60: 802.1Q vid 100 pri
3 arp who-has 192.168.100.1 tell 192.168.100.2
03:47:16.342637 02:00:11:01:01:00 02:00:13:01:01:00 0806 56: arp reply
192.168.100.1 is-at 02:00:11:01:01:00
03:47:17.344511 02:00:13:01:01:00 ff:ff:ff:ff:ff:ff 8100 60: 802.1Q vid 100 pri
3 arp who-has 192.168.100.1 tell 192.168.100.2
03:47:17.344884 02:00:11:01:01:00 02:00:13:01:01:00 0806 56: arp reply
192.168.100.1 is-at 02:00:11:01:01:00
OpenBSD 5.5
# tcpdump -i vlan100 -ne
tcpdump: listening on vlan800, link-type EN10MB
03:47:22.627571 02:00:13:01:01:00 ff:ff:ff:ff:ff:ff 0806 42: arp who-has
192.168.100.1 tell 192.168.100.2
03:47:23.629763 02:00:13:01:01:00 ff:ff:ff:ff:ff:ff 0806 42: arp who-has
192.168.100.1 tell 192.168.100.2
# tcpdump -i em1 -ne
tcpdump: listening on em1, link-type EN10MB
03:47:22.627637 02:00:13:01:01:00 ff:ff:ff:ff:ff:ff 8100 46: 802.1Q vid 100 pri
3 arp who-has 192.168.100.1 tell 192.168.100.2
03:47:22.628418 02:00:11:01:01:00 02:00:13:01:01:00 0806 60: arp reply
192.168.100.1 is-at 02:00:11:01:01:00
03:47:23.629899 02:00:13:01:01:00 ff:ff:ff:ff:ff:ff 8100 46: 802.1Q vid 100 pri
3 arp who-has 192.168.100.1 tell 192.168.100.2
03:47:23.630672 02:00:11:01:01:00 02:00:13:01:01:00 0806 60: arp reply
192.168.100.1 is-at 02:00:11:01:01:00
2) Ping from OpenBSD 5.6 to OpenBSD 5.5
# ping 192.168.100.2
PING 192.168.100.2 (192.168.100.2): 56 data bytes
--- 192.168.100.2 ping statistics ---
7 packets transmitted, 0 packets received, 100.0% packet loss
#
OpenBSD 5.6
# tcpdump -i vlan100 -ne
tcpdump: listening on vlan800, link-type EN10MB
03:54:01.750674 02:00:11:01:01:00 ff:ff:ff:ff:ff:ff 0806 42: arp who-has
192.168.100.2 tell 192.168.100.1
03:54:02.754122 02:00:11:01:01:00 ff:ff:ff:ff:ff:ff 0806 42: arp who-has
192.168.100.2 tell 192.168.100.1
# tcpdump -i em1 -ne
tcpdump: listening on em1, link-type EN10MB
03:54:01.750693 02:00:11:01:01:00 ff:ff:ff:ff:ff:ff 0806 42: arp who-has
192.168.100.2 tell 192.168.100.1
03:54:02.754140 02:00:11:01:01:00 ff:ff:ff:ff:ff:ff 0806 42: arp who-has
192.168.100.2 tell 192.168.100.1
OpenBSD 5.5
# tcpdump -i vlan100 -ne
tcpdump: listening on vlan800, link-type EN10MB
^C
0 packets received by filter
0 packets dropped by kernel
#
# tcpdump -i em1 -ne
tcpdump: listening on em1, link-type EN10MB
03:54:08.036586 02:00:11:01:01:00 ff:ff:ff:ff:ff:ff 0806 60: arp who-has
192.168.100.2 tell 192.168.100.1
03:54:09.039991 02:00:11:01:01:00 ff:ff:ff:ff:ff:ff 0806 60: arp who-has
192.168.100.2 tell 192.168.100.1
dmesg-5.5
Description: Binary data
dmesg-5.6
Description: Binary data
