> Currently, I am using a bridge. From what I understand from the patch > and the cvsweb history, that patch is waiting for ok and commit.
I've actually held back on that diff since it's a bit insufficient by itself. > This time, the switch does not close. However, I am still unable to > ping 8.8.8.8 with the switch. As usual, I am able to ping 8.8.8.8 > using a bridge. Actually, you said that you had just em0 on that switch. Can you try adding a local port (addlocal instead of add) alongside em0? It will be a vether(4) interface that needs to be given em0's current address, in its place. > There is a continuous stream of messages when running "switchd -dvv": > ... I can't say what they are without the full output, but you will tend to see broadcasts (periodic or otherwise) like your second example even on your bridge. From a second look at your earlier logs, it seems the 1->1 'loops' are generated by the switch seeing VLAN traffic in other parts of the network. > Finally, I have a query - What does the tap0 interface do? I ask this > because currently I do not pass in/out tap0 traffic in pf. This is > because I do not know what tap0 is and what it does. tap0 is a control interface created by switchd to communicate with switches. It won't carry normal network traffic.
