On 2016/11/28 17:16, Masanobu SAITOH wrote:
Hello, Jarle.
On 2016/11/27 0:45, Jarle Greipsland wrote:
Masanobu SAITOH <[email protected]> writes:
Hi.
On 2016/03/07 21:12, Tobias Nygren wrote:
On Mon, 7 Mar 2016 20:57:02 +0900
Masanobu SAITOH <[email protected]> wrote:
One of the possibility is that the multicast filter table and broadcast
bit in a register aren't set correctly on ICH9.
I'm not sure if this is relevant to the discussion, but I have a wm(4)
device (8086:1502) on -current that does not work after boot. It comes
to life only after running "tcpdump -n -i wm0" once. I am using vlan(4),
but haven't checked if that makes any difference. I usually run the
tcpdump command then forget about it until the next reboot.
It must be a bug! Could you tell me how you set up network interface include
vlan? (e.g. part of /etc/rc.conf, /etc/ifconfig.xxx, and the output of
"ifconfig -a)
Was this problem ever fixed?
Perhaps no. I've added a lot of changes into if_wm.c, but I've not
touched vlan related stuff.
Please test the latest -current. knakahara found a problem:
Module Name: src
Committed By: msaitoh
Date: Fri Jan 13 06:11:56 UTC 2017
Modified Files:
src/sys/net: if_ethersubr.c if_vlan.c
Log Message:
Fix a bug that the parent interface's callback wasn't called when the vlan
interface is configured. A callback function uses VLAN_ATTACHED() function
which check ec->ec_nvlans, the value should be incremented before calling the
callback. This bug was added in if_vlan.c rev. 1.83 (2015/11/19).
To generate a diff of this commit:
cvs rdiff -u -r1.234 -r1.235 src/sys/net/if_ethersubr.c
cvs rdiff -u -r1.93 -r1.94 src/sys/net/if_vlan.c
--
-----------------------------------------------
SAITOH Masanobu ([email protected]
[email protected])
