Hallo!
I am trying out trunk interface with em and fxp adapters and though
trunk seems to work all right i cant figure out how it takes itself mac
address. It does switch between the two physical interfaces' addresses,
but if someone expresses the alogithm on higher abstraction level than
looking up from the source i would be very thankful!
Imre
I believe it is my erranous hardware but i fiddled with trunk and
shuffled under it physical adapters with a sequence like (and switching
also between failover and roundrobin trunkprotos)
# ifconfig trunk0 -trunkport em0
# ifconfig em0 up
# ifconfig trunk0 trunkport em0
# ifconfig trunk0 -trunkport fxp3
# ifconfig fxp3 up
and there i came to the ddb> prompt, like this
ddb> show panic
the kernel did not panic
ddb> trace
_bus_dmamap_load(d07985e0,41,d65d6000,800,0) at _bus_dmamap_load+0xe
fxp_add_rfabuf(d0fd2000,0,d0fd2dfc,0) at fxp_add_rfabuf+0x1b9
fxp_init(d0fd2000,80206910,d95acd60,d04584e6,d0fd2040) at fxp_init+0x5ee
fxp_ioctl(d0fd2040,80206910,d95ace78,8943) at fxp_ioctl+0xab
ifioctl(d660aee8,80206910,d95ace78,d62ee41c,0) at ifioctl+0x3ae
sys_ioctl(d62ee41c,d95acf68,d95acf58,ffff8943,38) at sys_ioctl+0x125
syscall() at syscall+0x24e
--- syscall (number 54) ---
0x1c007ced:
ddb> continue
uvm_fault(0xd62ed180, 0x0, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at _bus_dmamap_load+0xe: cmpl 0(%ebx),%esi
ddb> boot sync
Ja tried the same kind on sequence with fxp2 and couldnt get to the
ddb>. Is it under the circumstances quite probable that it is the
hardware? Although under netstrain fxp3 with leads to the ddb> works
good and netstat -I fxp3 -w 1 shows no errors.
