On Sat, Sep 05, 2015 at 01:31:38PM +0100, Stuart Henderson wrote: > On 2015/09/05 13:18, Dimitris Papastamos wrote: > > On Sat, Sep 05, 2015 at 12:39:21PM +0100, Stuart Henderson wrote: > > > On 2015/09/05 12:13, Dimitris Papastamos wrote: > > > > On Sat, Sep 05, 2015 at 12:04:20PM +0100, Dimitris Papastamos wrote: > > > > > Scenario 1 - boot with em0 active > > > > > 1) pinging via em0 works > > > > > 2) switch to iwn0, ping doesn't work <-- problem > > > > > 3) switch to em0, ping works > > > > > 4) sh /etc/netstart > > > > > 5) pinging via em0 works > > > > > 6) switch to iwn0, ping works > > > > > > > > Note that if I tcpdump on trunk0, I do not even see the echo > > > > request in step 2. > > > > > > > > > > Showing output of "ifconfig -A" at various stages might give some clue. > > > > Sorry yes I forgot to mention this. As you can see in the output below > > there is no difference between ifconfig -A in the problematic and working > > case except the signal strength. > > > > I also just realized that I made a mistake in Scenario 1. To get > > iwn0 to work in this trunk setup, I need to unplug the cable and _then_ > > run sh /etc/netstart. > > > > 1) pinging via em0 works > > 2) switch to iwn0, ping doesn't work <-- problem > > 3) sh /etc/netstart > > 4) pinging via iwn0 works > > > > From this point on all further transitions work. > > > > The ifconfig -A output for step 1: > > > > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 32768 > > priority: 0 > > groups: lo > > inet6 ::1 prefixlen 128 > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > > inet 127.0.0.1 netmask 0xff000000 > > em0: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST> > > mtu 1500 > > lladdr aa:bb:cc:dd:ee:ff > ^^^^^^^^^^^^^^^^^ > > This obfuscation destroys exactly one of the things I was looking out for.
The original lladdr was 00:21:cc:5d:e1:40 and was the same across em0, iwn0 and trunk0.
