On May 19, 2011, at 7:49 AM, Frank Razenberg wrote:
> > What happens if you'd directly bridge it to an em(4) without the lagg etc.
> > in between
> Thanks, you're right, taking the lagg0 out and adding em0 to the bridge
> instead works indeed. Can I assume that's a bug in if_lagg then? If so, w
> What happens if you'd directly bridge it to an em(4) without the lagg
etc. in between
Thanks, you're right, taking the lagg0 out and adding em0 to the bridge
instead works indeed. Can I assume that's a bug in if_lagg then? If so,
where should I report it, the freebsd-bugs list?
Frank
On 5/1
On May 18, 2011, at 6:07 PM, Frank Razenberg wrote:
> As requested
>
> [root@ /root]# ifconfig -a
...
> epair0a: flags=8943 metric 0
> mtu 1500
>ether 02:a6:7d:00:0e:0a
>
>
> [root@ /root]# arp -an
Do you have the ifconfig epair0b, netstat -rn and arp -an from inside the
VIMAGE as well?
As requested
[root@ /root]# ifconfig -a
em0: flags=8943 metric 0
mtu 1500
options=219b
ether bc:ae:c5:27:ae:57
media: Ethernet autoselect (1000baseT )
status: active
em1: flags=8943 metric 0
mtu 1500
options=219b
ether bc:ae:c5:27:ae:57
media: Ethernet autoselect
On May 18, 2011, at 4:41 PM, Frank Razenberg wrote:
> The combination of VirtualBox 4.0.6 + VIMAGE gave me a lot of kernel panics
> so yesterday I checked out 8.2-STABLE and VirtualBox 4.0.8. The kernel panics
> are mostly gone. My problem now is that the epair interface is not reachable
> fro
