If memory serves me right, Dimitry Andric wrote:
> JINMEI Tatuya / 神明達哉 wrote:
>>> Confirmed. I've updated the machine on which I originally had this
>>> problem to -STABLE as of today, and the problem has disappeared.
>> I thought it was also planned to be incorporated to RELENG_6_2, right?
>
>
JINMEI Tatuya / 神明達哉 wrote:
>> Confirmed. I've updated the machine on which I originally had this
>> problem to -STABLE as of today, and the problem has disappeared.
>
> I thought it was also planned to be incorporated to RELENG_6_2, right?
I'm not sure if non-security related fixes are consider
On 1/31/07, Slawek Zak <[EMAIL PROTECTED]> wrote:
I have a question for someone familiar with this driver. I must
enforce Gb/Full-duplex before the end of boot. I have IBM BladeCenter
chassis which internally uses Nortel 2-3 switches which in turn do not
allow for autonegotiation of internal inte
> On Fri, 09 Feb 2007 23:21:33 +0100,
> Dimitry Andric <[EMAIL PROTECTED]> said:
> Bruce A. Mah wrote:
>> I've convinced myself that this problem needs to be tested in isolation
>> (i.e. you have complete control over both ends of the tunnel) because
>> incoming packets over the tunnel ca
Andrew Thompson wrote:
This is great for the bridge, it has needed to take the vlan tag into
account when deciding to forward or not. Having m_pkthdr.ether_vtag
always set makes this much easier to implement.
In the deleted code M_VLANTAG is cleared but is not done anymore, is
this right?
